Which drones are exempt from Remote ID?

Very few aircraft are exempt from Remote ID once they are in the air, and the list is shorter than most operators expect. An aircraft escapes the broadcast requirement only if it is not registered and not required to be registered, if it stays inside an FAA-Recognized Identification Area, if the FAA has authorized the flight for aeronautical research or to show compliance with regulations, or if it is a Part 91 operation transmitting ADS-B Out. Everything else broadcasts, either from the aircraft itself or from a module.

That short list surprises people because the exemptions quoted most often in forums and product pages come from a different part of the rule entirely. This article separates the operating requirement, which decides what you may fly today, from the design and production requirements, which decide what a manufacturer may build and sell. It then walks the real exemptions one at a time, explains what each one costs you operationally, and closes with the record a commercial program needs to prove which basis it was flying under.

Where the requirement starts and who it reaches

The broadcast requirement attaches to registration, not to weight, price, or use. Part 89 reaches anyone operating an unmanned aircraft registered or required to be registered under Part 47 or Part 48, plus foreign civil unmanned aircraft flown in the United States. That single sentence does most of the work. Commercial operations register every aircraft regardless of weight, so a two hundred gram drone flown for hire is registered, and a registered aircraft broadcasts. The same airframe flown purely for recreation at under half a pound needs no registration and therefore falls outside the rule.

This is why the popular shorthand about a weight cutoff misleads commercial teams. The half pound threshold is real, but it decides registration for recreational flyers, and it decides what manufacturers must build into aircraft. It does not create a class of professional aircraft that may fly silently. A drone program buying small airframes for confined interior work or for training should assume broadcast obligations apply the moment those aircraft are used for the business, because that use is what forces the registration that pulls Part 89 in behind it.

The three ways to fly without broadcasting

Once an aircraft is inside the rule, 14 CFR 89.101 and the operating sections that follow leave three narrow doors. The first is the FAA-Recognized Identification Area. Inside an approved FRIA, an aircraft with no Remote ID equipment may fly, provided both the aircraft and the person at the controls stay within the boundaries for the whole flight and the pilot can see the aircraft at all times. The second is an FAA authorization for flights conducted solely for aeronautical research or to show compliance with regulations, which is granted case by case rather than claimed.

The third door is not really an exemption at all. A Part 91 operation transmitting ADS-B Out sits outside the subpart, which matters for larger unmanned aircraft operating under a certificate rather than under Part 107. Note the trap buried alongside it: ADS-B Out may not be used to satisfy Remote ID for aircraft that are inside the rule. Programs sometimes read the two provisions together and conclude that fitting ADS-B solves the problem. It does the opposite for a typical Part 107 fleet, adding equipment without removing the broadcast duty.

The production exclusions people mistake for exemptions

The exemptions quoted most often are home built aircraft, aircraft owned by the United States Government, aircraft weighing half a pound or less at takeoff, and aircraft produced only for research or to show compliance. Those four are real, they are written into the rule, and they exempt nobody from flying with Remote ID. They sit in the design and production subpart, and they tell a manufacturer or builder which aircraft need not be produced to the standard Remote ID specification. A home built aircraft may lawfully leave the workshop with no broadcast capability at all.

Flying it is a separate question with a separate answer. If that aircraft is registered or required to be registered, its operator still has to meet the broadcast requirement, which in practice means fitting a broadcast module and listing the module serial on the registration. The gap between what may be built and what may be flown is where operators get caught, usually after buying or building something on the strength of an exemption that governs the factory rather than the flight. Read the subpart heading before relying on any exemption you find quoted.

Proving which basis you were flying under

An exemption is a claim about a specific flight, and a claim is only as good as what the operation can show afterward. A FRIA flight is lawful because the aircraft and the pilot stayed inside a boundary on a particular afternoon. A research authorization covers named work under stated conditions. A sub registration aircraft is outside the rule only for as long as nobody uses it commercially. Each of those facts lives in the operation, not in the airframe, and none of them is visible to an inspector three months later unless somebody wrote it down at the time.

Programs that run mixed fleets feel this hardest. Some aircraft broadcast natively, some carry modules, one or two may sit in a training role that nobody has quite decided about, and the registration entries drift out of step with what the aircraft are doing. The fix is unglamorous. Record the compliance basis against each airframe alongside its registration and serial, attach it to the jobs that aircraft flies, and update it when the aircraft changes role. Then the answer to a Remote ID question is a lookup rather than a reconstruction.

Common mistakes in Remote ID exemptions

Reading a weight cutoff as a commercial exemption. The half pound line governs recreational registration and production requirements. A commercial aircraft is registered whatever it weighs, and a registered aircraft is inside the broadcast rule.

Treating a home built or government exclusion as permission to fly quietly. Those exclusions sit in the design and production subpart. They release the builder from a production standard, and they leave the operating requirement untouched.

Assuming ADS-B Out satisfies Remote ID. The rule states plainly that ADS-B Out equipment cannot be used to comply with Remote ID. Fitting it to a Part 107 aircraft adds cost and changes nothing about the obligation.

Believing a FRIA travels with the aircraft. A FRIA is a place, not a status. Cross the boundary, or lose sight of the aircraft, and the exemption ends mid flight while the aircraft is still in the air.

Leaving the compliance basis undocumented. Knowing that an aircraft is exempt is not the same as being able to demonstrate why on a date somebody names. File the basis with the airframe record before anyone asks.

FAQ

Are drones under 250 grams exempt from Remote ID?

Only when they are not registered and not required to be registered, which in practice means recreational use. The same aircraft flown commercially must be registered under Part 107, and registration brings the broadcast requirement with it.

Can I fly without Remote ID if my drone has no internet connection?

Yes, because Remote ID is a local radio broadcast rather than an internet upload. The aircraft or module transmits directly, so connectivity has nothing to do with compliance, and no data is sent to the FAA in flight.

Does a FRIA let my company fly without Remote ID equipment?

Only inside the boundaries, and only if the pilot keeps the aircraft in sight throughout. FRIAs are also established for community based organizations and educational institutions, so most commercial operators have no route to one.

What happens if my Remote ID equipment fails in flight?

The rule requires the pilot to land as soon as practicable once the aircraft stops broadcasting the required message elements. A standard aircraft should also refuse to take off if its Remote ID self test fails beforehand.

Closing thought

The exemptions are narrow by design, and the ones circulating most widely are answers to a question about manufacturing rather than flying. For a commercial program the working assumption should be that every aircraft in the fleet broadcasts, that the few genuine exceptions are tied to a place or a written authorization, and that both need evidence attached to the flight rather than a recollection attached to the pilot.

If you are auditing which aircraft in a fleet have to broadcast, FlybyOps was built for the operational record problem at the center of regulated drone work. An equipment registry carrying per airframe history, a document vault with expiration tracking, role based access for the people who maintain those records, and an append-only audit log are all part of how the platform keeps the reason each aircraft is allowed to fly the way it does written down before anyone asks.