Drone registration and Remote ID

A small unmanned aircraft operated under Part 107 generally must be registered with the FAA regardless of weight. Recreational registration rules are different, so do not use the recreational weight threshold to decide a commercial Part 107 mission. Registration is associated with the responsible registrant and aircraft details; mark the aircraft as required and carry or make available the registration information under the applicable rule. Registration does not establish airworthiness, grant airspace access, or make an otherwise unsafe flight acceptable.

Check the registration status and aircraft identity before accepting a job, especially when a fleet changes hands or a client supplies an aircraft. Keep records current when ownership or registration information changes. If an aircraft is used in different operating categories, confirm which rules apply to the specific flight. A registration number, Remote ID serial number, and aircraft serial number may be different data fields; record the correct identifier in the correct FAA system.

Under Part 89, a drone that is required to be registered, or is registered, generally must comply with Remote ID unless an exception applies. A Standard Remote ID aircraft broadcasts identification and location information directly from the aircraft using built-in capability. A nonstandard aircraft may use an FAA-accepted broadcast module, which has its own installation, broadcasting, and operating conditions. Operators should verify that the exact make/model or module is accepted and functioning rather than relying on a retailer's vague 'Remote ID ready' description.

A drone without compliant Remote ID may be operated in an FAA-Recognized Identification Area (FRIA) only under the rule's conditions, including remaining within visual line of sight of the person manipulating the controls. A FRIA is a defined site, not a general exemption for nearby parks or an entire municipality. Remote ID is also distinct from registration and airspace authorization: satisfying one does not satisfy the others. If broadcast capability fails before takeoff, do not launch unless a lawful exception and compliant operating arrangement actually apply.

Build Remote ID into aircraft acceptance and preflight: verify registration, determine the applicable compliance method, check firmware and module installation, confirm required broadcast elements are available, and observe the status indication or manufacturer's procedure. A pilot should know what the system reports if GNSS input or the broadcast signal fails, and should avoid improvising a workaround in the field. Document maintenance or configuration changes that may affect the system.

For a module-based aircraft, verify the required broadcast of aircraft identity and location plus the takeoff location. A Standard Remote ID aircraft broadcasts aircraft identity and location plus the control-station location. Confirm the built-in broadcast status and aircraft association for the exact system in use. A flight in a FRIA is a separate location-specific path with boundaries and conditions to verify. If any critical assumption cannot be confirmed, delay launch and consult current FAA information rather than treating the app's map or a buyer's guide as the legal source.