Remote ID and Operations Over People

Overview

This chapter covers two interconnected regulatory areas that directly affect the day-to-day operations of a Part 107 remote pilot: Remote Identification (Remote ID) and the Operations Over People rule. Remote ID functions as a "digital license plate" for drones, broadcasting identification and location information to public safety officials and other airspace stakeholders. The Operations Over People rule establishes a four-category framework that determines when and how a small UAS may operate above human beings.

Remote ID is required for nearly all Part 107 operations. Flying without functioning, compliant Remote ID equipment—or flying a drone with exposed rotating parts above people without meeting the applicable category requirements—can result in enforcement action. Remote pilots and maintenance technicians must understand both the operational requirements and the maintenance obligations that keep a drone legal for flight.

Remote Identification (Remote ID)

Purpose and Regulatory Basis

Remote ID is found in 14 CFR Part 89 and is made a condition of Part 107 flight through §107.300. The rule prohibits operating a small unmanned aircraft unless it broadcasts certain identification and location information. Remote ID functions like a digital license plate, enabling law enforcement, regulatory agencies, and other authorized parties to associate the identity of the unmanned aircraft with the identity of its operator and control station.

Remote ID is not a:

Ground or airborne collision avoidance system

Means of enabling Beyond Visual Line of Sight (BVLOS) operations

Video or data streaming feature

Weather avoidance tool

It is simply an identification and situational awareness broadcast.

Remote ID Compliance Options

Under 14 CFR Part 89, a small UAS may meet the Remote ID requirement in three ways:

18.Standard Remote ID (built-in): The drone's Remote ID capability is fully integrated into the airframe and flight control system. The aircraft cannot take off unless the Remote ID equipment is functioning.

19.Remote ID Broadcast Module (retrofit/add-on): An aftermarket device that broadcasts Remote ID message elements from the drone's location. A broadcast module is typically self-contained, with its own power source and GPS receiver, and communicates via Bluetooth or Wi-Fi to nearby receivers. It is designed for retrofit installations on existing aircraft and is not required to connect to the aircraft's flight controller or data bus.

21.FAA-Recognized Identification Area (FRIA): An FAA-recognized geographic area where unmanned aircraft without Remote ID equipment may be operated without broadcasting. FRIAs are established through application to the FAA and are generally located within an operational footprint of a community-based organization, educational institution, or similar entity. Operations inside a FRIA must remain within the FRIA boundary. A drone that leaves the FRIA without Remote ID equipment would be non-compliant.

Important: Standard Remote ID and broadcast modules must meet the same broadcast, message element, and performance requirements. The only difference is the integration method—built-in versus add-on.

Remote ID Message Elements

Under 14 CFR §89.305, a Standard Remote ID system and a Remote ID broadcast module must transmit the following required message elements at a rate of at least once per second:

UAS ID: A unique identifier. For Standard Remote ID, this is the aircraft's serial number or the registration number; for modules, it is the module's serial number. The UAS ID must be traceable to the registration of the specific aircraft.

Latitude and longitude: The geometric position of the unmanned aircraft.

Geometric altitude: The altitude of the unmanned aircraft referenced to a standard datum.

Velocity: The speed and direction of the unmanned aircraft.

Time mark: The time of applicability of the position data.

Control station location: The latitude and longitude of the ground control station (the remote pilot's position).

Emergency status: An indication if a lost-link or emergency condition exists.

The operator's home address, battery voltage, flight logs, or IP address are not required message elements. Failing to transmit any mandatory element—this includes transmitting an incorrect UAS ID or an inaccurate control station location—is considered Remote ID non-compliance.

Remote ID Modules and the FAA Acceptance Process

A Remote ID broadcast module used for Part 107 compliance must be FAA-accepted. Specifically, 14 CFR §89.320 requires modules to be on the FAA's published list of accepted Remote ID broadcast modules. A module that is not on this accepted list places the operator in violation of Parts 89 and 107, regardless of any verbal assurances, operator liability waivers, or "if it works, it works" assumptions.

Key points about maintenance and installation of Remote ID modules:

Installing an aftermarket broadcast module is an acceptable retrofit. It does not need to be part of the aircraft's original type design nor listed in the manufacturer's authorization.

The installation must be mechanically sound and must not introduce a hazard. Heavy modules that become detached in flight create a projectile hazard and disable Remote ID at the same time.

AC 43.13-1B provides general guidance for the proper installation and security of antennas, electrical connections, and avionics.

A module with cracked housings, loose antenna mounts, or degraded wiring must be repaired or replaced. A damaged or compromised module cannot be "field-expedited" with tape or adhesives and returned to service.

A functional ground check after installation must verify that the module is broadcasting all required message elements and that the mechanical mounting is secure.

Remote ID and Aircraft Registration

The Remote ID broadcast must identify the actual aircraft being flown. A module that still transmits the previous owner's registration number is non-compliant. Before flight, the pilot must reconfigure the module to transmit the correct UAS ID associated with the current registration. Transmitting an incorrect registration number is equivalent to not having a functioning Remote ID system.

Preflight Verification

14 CFR §107.36 places an explicit duty on the remote pilot in command to verify that the Remote ID equipment is functioning properly before each operation. This verification is part of the required preflight inspection. The pilot must ensure:

The Remote ID system is powered on and broadcasting.

The broadcast includes all required message elements.

The UAS ID matches the aircraft's registration.

The control station location is accurate.

No error messages or "No Remote ID" warnings are present in the control station app or monitoring software.

A discrepancy where the module's own status LED indicates transmission but the control app shows "Remote ID not detected" is still a failed preflight. The aircraft must not take off until the discrepancy is resolved. Similarly, a persistent "No Remote ID" warning after a reboot is grounds to ground the aircraft until repaired.

Remote ID Failure During Flight

If Remote ID fails during flight—whether the module detaches, the broadcast stops, the GPS position is lost, or the control station location becomes inaccurate beyond acceptable tolerances—the remote pilot in command must land the small UAS as soon as safely possible (practicable). Continuing the operation without an active Remote ID broadcast is a direct violation of Part 89 and Part 107.

Important clarifications:

Continuing the assigned inspection or survey because the aircraft "still flies" is not permitted.

Descending to a lower altitude, reducing speed, switching to a different flight mode, or activating return-to-home does not remedy the compliance failure. Return-to-home may be used if it is the safest way to land, but it is not an opportunity to continue the mission.

The presence of a visual observer or the absence of an immediate hazard does not permit continued flight without Remote ID.

A Remote ID "failure" includes not just a total loss of broadcast, but also any incomplete broadcast (e.g., missing GPS position, incorrect UAS ID, inaccurate control station location, or corrupted data elements).

Remote ID Responsibility and Delegation

Under 14 CFR §107.19, the remote pilot in command is ultimately responsible for ensuring that the small UAS complies with all applicable regulations, including Remote ID requirements. Delegating actual control of the aircraft to another person—such as a new hire, an observer, or a trainee—does not transfer regulatory responsibility. If a delegated pilot operates the aircraft without a functioning Remote ID broadcast, the remote pilot in command is primarily responsible for the violation.

This principle extends to maintenance technicians and maintenance personnel: anyone performing maintenance must understand that returning an aircraft with a defective or non-compliant Remote ID system to service violates the regulated operation that will follow.

Key Restrictions on Remote ID

Continuous broadcast required: Remote ID must be active during the entire flight operation. The pilot cannot switch off a broadcast module mid-flight to save battery power, even if the aircraft remains within visual line of sight, is at a low altitude, or the pilot has notified air traffic control. Manual in-flight deactivation is a violation.

No waivers for defective equipment: There is no FAA waiver, field approval, or verbal FSDO authorization to operate with a defective, disabled, missing, or non-compliant Remote ID system. The only regulatory avenue for operation without Remote ID equipment is inside a FRIA.

FRIA limitations: A FRIA permits operation without Remote ID equipment, but it is not a means to bypass the Operations Over People rules. Flying without Remote ID over a congested open-air assembly at a FRIA is not permitted simply because the FRIA exists; the FRIA exception only addresses the Remote ID requirement.

Operations Over People

The Four Categories

Part 107, Subpart D establishes a four-category framework for operations over human beings. The categories are designed to allow certain small UAS operations over people while managing the risk of injury. Each category has distinct eligibility criteria and operational restrictions.

Category 1: The Lightest, Most Flexible Category

Under 14 CFR §107.110(a), a Category 1 small UAS may operate over human beings if it meets all three of the following conditions at the time of the operation:

73.Total weight is 0.55 pounds or less, including everything attached to or carried by the aircraft—airframe, battery, camera, gimbal, payload, and any Remote ID equipment (whether standard or a broadcast module). The weight threshold is measured at takeoff. A 0.4 lb airframe with a 0.1 lb camera and a 0.2 lb Remote ID module (total 0.7 lb) would not qualify as Category 1. A 0.5 lb aircraft with no additional payload would qualify.

74.No exposed rotating parts that could cause lacerations. The aircraft must have propeller guards or other protective enclosures that prevent the exposed propeller or rotor from contacting skin. Fully enclosed prop guards are the most common means of compliance. A 0.4 lb quadcopter with fully enclosed prop guards and no exposed rotating components meets this condition. The aircraft cannot simply have "folding" props or "larger shrouds" that still expose the rotors.

75.No safety defects. The aircraft must be free from any cracks, chipped propellers, loose fasteners, damaged landing gear, or any other defect that could cause a loss of control or in-flight failure, with the potential to injure people below. A cracked propeller on a Category 1 aircraft requires terminating the over-people operation and correcting the defect before resuming.

Key nuance: If a Category 1 aircraft is modified to add weight that pushes it over 0.55 lb (for example, attaching a camera and gimbal that raise the takeoff weight to 0.60 lb), the aircraft is no longer Category 1 eligible. The pilot must either remove the payload to bring the weight back under 0.55 lb, or qualify the aircraft under a higher category (2, 3, or 4).

Also critical: A Category 1 aircraft must still comply with Remote ID requirements. The Operations Over People rule does not waive the Remote ID requirement. A 0.45 lb drone with no exposed rotating parts but no Remote ID broadcast module is not permitted to operate over people unless it is operating inside a FRIA (and the FRIA is not an open-air assembly). In other words, Remote ID and Operations Over People categories are independent, cumulative requirements.

Category 2 and Category 3

Categories 2 and 3 permit operations over people with aircraft heavier than 0.55 lb, but they require the manufacturer or operator to demonstrate operational capability and design limitations through a Declaration of Compliance process. Specifically:

Category 2 (§107.110(b)) requires:

The aircraft must not contain exposed rotating parts that could cause lacerations.

The aircraft must be eligible for operation under a Declaration of Compliance that demonstrates it meets the FAA-accepted Means of Compliance for injury mitigation.

The operation must be conducted in accordance with the operational limits set forth in the Declaration of Compliance.

Category 3 (§107.110(c)) requires:

The aircraft must not cause injury to a human being equivalent to or greater than the severity of injury caused by a transfer of 25 foot-pounds of kinetic energy upon impact from a rigid object.

The aircraft must not contain exposed rotating parts that could cause lacerations.

The aircraft must be operated in accordance with the limits in the Declaration of Compliance.

The aircraft may not be operated over open-air assemblies of human beings (e.g., stadium crowds, concerts, festivals, public gatherings) under Category 3.

Summary distinction between Category 2 and 3: Category 2 aircraft pose a lower severity-of-injury risk than Category 3 aircraft and may therefore operate over open-air assemblies under the terms of their Declaration of Compliance. Category 3 aircraft are prohibited from operating over open-air assemblies, regardless of other modifiers. Both Category 2 and Category 3 operations can be conducted over individual people and small groups if the stated requirements are met.

Category 4: Airworthiness Certificate

Under §107.110(d), Category 4 permits operations over people when the small UAS holds a standard airworthiness certificate issued by the FAA. Currently, standard airworthiness certificates for small UAS are rare, and most commercially available Part 107 aircraft do not fall into this category. To operate a Category 4 aircraft over people, the pilot must:

Ensure the aircraft holds a standard airworthiness certificate (not a Special Airworthiness Certificate in the Experimental category).

Operate the aircraft in accordance with all operating limitations specified in the airworthiness certificate or by the FAA.

Complete the required preflight verification that the aircraft complies with those limitations.

Comparing the Categories

Category	Weight Limit	Injury Mitigation	Open-Air Assemblies	Special Requirement
1	≤ 0.55 lb total	No exposed rotating parts; no safety defects	Yes, if all criteria met	Remote ID still required
2	No fixed weight limit; category-based	No exposed rotating parts; Declaration of Compliance	Yes, per Declaration	Manufacturer/fleet Declaration of Compliance
3	No fixed weight limit; category-based	No exposed rotating parts; energy-based injury threshold; Declaration of Compliance	No	Declaration of Compliance
4	No fixed weight limit	Operating limitations of airworthiness certificate	Yes, per airworthiness certificate	Standard airworthiness certificate

Maintenance, Installation, and Airworthiness of Remote ID and Category Compliance Equipment

Maintenance Standard Practices

Maintenance on Remote ID equipment and category-related components (e.g., prop guards, structural members) must follow standard aircraft maintenance practices. AC 43.13-1B provides accepted methods for:

Securing antennas and electrical connections

Preventing wire chafing and fatigue

Preventing moisture ingress at mountings

Confirming structural integrity of installed equipment

A Remote ID system with a cracked housing, loose antenna, degraded wiring, or intermittent transmission is not in a condition for safe operation. The aircraft must not be returned to service until the defective component is repaired or replaced and a functional check verifies the broadcast.

Functional Ground Checks

After any Remote ID installation, repair, or replacement, the mechanic must perform a functional ground test to verify:

The module is mechanically secure

The module transmits all mandated message elements (UAS ID, location, altitude, velocity, control station location, time, emergency status)

The signal is received at a reasonable distance (indicating the antenna is functioning properly), not, for example, only within 100 feet of the control station

The UAS ID corresponds to the aircraft registration

A module that can only be received at very close range indicates a defective antenna, poor connection, or improper installation and is not compliant.

Aftermarket Module Installation

A broadcast module does not need to be on the aircraft's original type design. It may be a self-contained, add-on device with its own battery and GPS receiver that broadcasts via Bluetooth or Wi-Fi. However:

The module must be FAA-accepted (on the published accepted-module list).

The installation must be mechanically sound and must not introduce a hazard (e.g., risk of detachment).

The pilot remains responsible for verifiable, preflight-functional Remote ID.

Declining Non-Compliant Maintenance

A maintenance technician presented with a non-accepted or non-compliant Remote ID module must decline the installation. Liability waivers signed by the operator, verbal agreements, or promises to "fly at the operator's own risk" do not override the regulatory requirement. A module not on the FAA-accepted list would subject the operator to violation of Part 89 and potentially Part 107. Field approvals and manufacturer "authorization" do not apply to the Remote ID module acceptance process.

The Remote PIC's Ultimate Responsibility

Regardless of who performs maintenance or who holds the controls during flight, the remote pilot in command is responsible for:

Ensuring the aircraft is in a condition for safe operation (14 CFR §107.19)

Verifying Remote ID is functioning prior to flight (§107.36)

Landing as soon as safely possible if Remote ID fails in flight (§107.302(c))

Ensuring the aircraft meets Category 1–4 requirements if operating over people (§107.110)

The mechanic's responsibility is to ensure that any work performed renders the aircraft compliant and safe. When a repair technician returns a drone to service with a non-compliant or defective Remote ID system, that aircraft cannot be legally operated under Part 107.

Common Relationships and Exam-Relevant Distinctions

Remote ID vs. Operations Over People. Remote ID compliance and Categories 1–4 are separate, cumulative requirements. Meeting Remote ID does not automatically permit flight over people, and meeting Category 1 criteria does not waive Remote ID. A Category 1 aircraft must simultaneously meet the weight, no-exposed-rotating-parts, no-safety-defect, and Remote ID requirements.

Standard Remote ID vs. Broadcast Module. Both transmit the same message elements at the same performance standards. The difference is integration: Standard Remote ID is built into the aircraft; a broadcast module is an attached aftermarket device. A module need not integrate with the flight controller or connect to the internet; it only needs to broadcast the required message elements.

FRIA vs. Over-People Operations. A FRIA exempts an aircraft from the Remote ID requirement but does not exempt it from Operations Over People rules. A FRIA is a specific geographic area; leaving the FRIA without Remote ID is a violation. Flying over an open-air assembly at a FRIA without Remote ID is still a violation of the over-people category restrictions.

Category 1 weight threshold. The 0.55 lb threshold is a total takeoff weight including all payloads, batteries, and Remote ID equipment. It is not the weight of the airframe alone. A drone that exceeds 0.55 lb at takeoff, even by a fraction of a pound due to a camera or gimbal, is no longer Category 1.

Category 1 safety defects. A visible crack, a missing propeller piece, or damaged landing gear disqualifies a Category 1 aircraft from operating over people. The pilot must land and correct the defect before resuming over-people flights. A cracked propeller on a 0.4 lb Category 1 aircraft over a public park requires immediate termination of the over-people operation.

Category 2 vs. Category 3. Category 2 aircraft may operate over open-air assemblies if permitted by their Declaration of Compliance. Category 3 aircraft are prohibited from operating over open-air assemblies. The 0.55 lb weight limit applies only to Category 1. Category 4 requires a standard airworthiness certificate, not simply a registered aircraft.

Remote ID failure in flight. Failure is not limited to a complete loss of broadcast. Missing elements (e.g., no GPS position, incorrect UAS ID), corrupted data (e.g., inaccurate control station location), or degraded signal range all constitute failure. The required action is always to land as soon as safely possible.

Remote ID preflight. The preflight is a positive duty to verify functionality. A Status LED that says the module is transmitting is not sufficient if the control app or monitoring software shows no Remote ID signal or incomplete data. The discrepancy must be resolved on the ground before takeoff.

Maintenance and return to service. An aircraft with a failed or damaged Remote ID system is not airworthy for Part 107. It must be grounded until the component is repaired or replaced, then functionally checked. There is no valid waiver or field repair that permits flight with a defective Remote ID system.

Remote ID and Operations Over People