Click to enlarge

The FAA just updated its information page on UAS Remote Identification.

UAS Remote Identification

Drones or unmanned aircraft systems (UAS) are fundamentally changing aviation, and the FAA is committed to working to fully integrate drones into the National Airspace System (NAS). Safety and security are top priorities for the FAA and remote identification (remote ID) of drones is crucial to our integration efforts.

What is Remote ID?

Remote ID is the ability of a drone in flight to provide identification and location information that can be received by other parties.

Why Do We Need Remote ID?

Remote ID helps the FAA, law enforcement, and other federal agencies find the control station when a drone appears to be flying in an unsafe manner or where it is not allowed to fly. Remote ID also lays the foundation of the safety and security groundwork needed for more complex drone operations.

Final Rule on Remote ID

The final rule on remote ID will require most drones operating in US airspace to have remote ID capability. Remote ID will provide information about drones in flight, such as the identity, location, and altitude of the drone and its control station or take-off location. Authorized individuals from public safety organizations may request identity of the drone’s owner from the FAA.

The FAA’s Notice of Proposed Rulemaking (NPRM) on Remote Identification of Unmanned Aircraft Systems was published on December 31, 2019. The FAA received over 53,000 comments on the NPRM during the 60-day comment period following publication. The FAA reviewed all of the comments and considered them when writing the final rule. The final rule (PDF) has been submitted to the Federal Register for publication.

There are three ways drone pilots will be able to meet the identification requirements of the remote ID rule:

  • Operate a Standard Remote ID Drone (PDF) that broadcasts identification and location information about the drone and its control station. A Standard Remote ID Drone is one that is produced with built-in remote ID broadcast capability in accordance with the remote ID rule’s requirements.
  • Operate a drone with a remote ID broadcast module (PDF). A broadcast module is a device that broadcasts identification and location information about the drone and its take-off location in accordance with the remote ID rule’s requirements. The broadcast module can be added to a drone to retrofit it with remote ID capability. Persons operating a drone with a remote ID broadcast module must be able to see their drone at all times during flight.
  • Operate (without remote ID equipment) (PDF) at FAA-recognized identification areas (FRIAs) sponsored by community-based organizations or educational institutions. FRIAs are the only locations unmanned aircraft (drones and radio-controlled airplanes) may operate without broadcasting remote ID message elements.

Changes From the NPRM

Following public comments and technical challenges, the FAA decided to eliminate the NPRM “Limited Remote Identification UAS” category to transmit remote ID messages through an internet connection to a Remote ID UAS Service Supplier. This option has been replaced by the remote ID broadcast module option that allows for retrofit of existing drones.

The FAA made several other changes to the proposed rule for the final rule on remote ID after evaluating commenters’ feedback. Changes from the NPRM to the final rule include:

  • Compliance dates –
    • The compliance date for manufacturers was reduced from 24 months to 18 months after the rule’s effective date. See below for details.
    • The compliance date for operators was shortened from 36 months to 30 months after the rule’s effective date. See below for details.
  • Registration – Under the NPRM, recreational drone pilots had to have a unique registration number for each of their aircraft. Under the final rule, recreational drone pilots may continue to register once and apply that unique registration number to multiple aircraft. During registration, they have to list the serial number of any Standard Remote ID unmanned aircraft (including drones and model aircraft) they register. If they use a remote ID broadcast module, the module’s serial number must be listed on their registration, which will permit them to move the module from unmanned aircraft to unmanned aircraft so long as the unmanned aircraft are on the same registration number.

Changes From the NPRM for Manufacturers

In addition to changes affecting drone pilots, the final rule also provides for changes in requirements for manufacturers. The chart below provides some examples of changes from the NPRM. For more information, visit the Remote ID for Industry page.

Manufacturing Requirement NPRM Final Rule
Remote ID Broadcast Module N/A Performance requirements added for the retrofit module
Process for certificated aircraft Every drone went through Declaration of Compliance (DOC) process Part 21 certificated aircraft must be standard remote ID drone and/or ADS-B Out equipped, compliance with Means of Compliance (MOC)/Performance requirements determined during certification process
Manufacturing compliance date 24 months after the rule’s effective date 18 months after the rule’s effective date

Changes From the NPRM for Requesting a FRIA

Another set of changes from the NPRM applies to FRIAs. After the operational compliance date (MO/DAY/YR), FRIAs are the only locations where someone may fly an unmanned aircraft (drone or model airplane) without remote ID capability without FAA authorization. The chart below provides some examples of changes from the NPRM to the final rule.

FRIAs NPRM Final Rule
Who can request to establish a FRIA? Only FAA-recognized Community-Based Organizations (CBOs) CBOs and educational institutions
When can someone apply for a FRIA? 12-month period beginning on rule effective date No deadline to apply; applications can be sent to the FAA starting 20 months after rule publication date
Where can a FRIA be established? Locations based on four criteria in NPRM 89.215 Updated criteria (similar to proposed criteria) in 89.215

Which Drone Pilots Must Comply With the Rule?

All drone pilots required to register their UAS must operate their aircraft in accordance with the final rule on remote ID beginning 30 months after the rule’s effective date, which gives drone owners sufficient time to upgrade their aircraft.

What Information Will be Broadcast?

Whether using a Standard Remote ID Drone or a remote ID broadcast module, the message elements must be broadcast from take-off to shutdown. A Standard Remote ID Drone or a drone with a remote ID broadcast module must transmit the following message elements:

  • A unique identifier for the drone;
  • The drone’s latitude, longitude, geometric altitude, and velocity;
  • An indication of the latitude, longitude, and geometric altitude of control station (standard) or take-off location (broadcast module);
  • A time mark; and
  • Emergency status (Standard Remote ID Drone only)

See the Remote ID for Drone Pilots page for more details.

Effective Dates

Almost all of the final rule on remote ID becomes effective 60 days after publication of the rule in the Federal Register. The subpart covering the process for FRIA applications from community-based organizations and educational institutions becomes effective 60 days and 18 months after publication of the rule in the Federal Register.

Here are other dates of note:

  • 18 months after the rule’s effective date:
    • Drone manufacturers must comply with the final rule’s requirements for them.
  • 30 months after the rule’s effective date:
    • All drone pilots must meet the operating requirements of part 89. For most operators this will mean flying a Standard Remote ID Drone, equipping with a broadcast module, or flying at a FRIA.

Source: FAA

UAV DACH: Beitrag im Original auf https://www.uasvision.com/2021/01/05/faa-updates-uas-remote-identification-overview/, mit freundlicher Genehmigung von UAS Vision automatisch importiert. Der Beitrag gibt nicht unbedingt die Meinung oder Position des UAV DACH e.V. wieder. Das Original ist in englischer Sprache. Für die Inhalte ist der UAV DACH e.V. nicht verantwortlich.