Remote ID and Flight Authorization

Remote ID: The License Plate for Drones

Just as automobiles require license plates for identification and accountability, drones operating in UTM-managed airspace must broadcast Remote ID information. The FAA's Remote ID rule (implemented 2021, enforced 2023) and equivalent international regulations establish this fundamental requirement enabling safe airspace integration.

Remote ID serves multiple critical functions beyond simple identification:

• Accountability: Links drones to registered operators, enabling enforcement of violations
• Security: Allows law enforcement to identify unauthorized operations near sensitive sites
• Safety: Provides situational awareness for other airspace users, both manned and unmanned
• UTM Integration: Enables USS to track conformance with approved flight plans
• Public Acceptance: Addresses privacy and security concerns by making operations transparent

ASTM F3411 - Remote ID Standard

The ASTM F3411 standard defines technical specifications for Remote ID implementation, ensuring interoperability across manufacturers and receivers. The standard specifies two primary methods:

1. Broadcast Remote ID

Drones directly transmit identification and telemetry data using radio frequencies (typically WiFi or Bluetooth in 2.4 GHz or 5.8 GHz bands). Anyone with an appropriate receiver (smartphone app, dedicated device) can receive these broadcasts within range (typically 400-1000 meters depending on conditions).

Broadcast Message Types:

2. Network Remote ID

Instead of local broadcast, drones transmit Remote ID data to internet-based services via cellular or satellite links. These services make the data available to authorized parties (law enforcement, UTM systems) through APIs. Network Remote ID is useful for operations beyond radio range of populated areas or where broadcast signals might be unreliable.

Standard Remote ID vs. Remote ID Broadcast Module

Drones can comply with Remote ID requirements in two ways:

• Standard Remote ID: Remote ID capability built into the drone at manufacture. Provides both broadcast and (if capable) network Remote ID. Must broadcast from takeoff through landing.
• Broadcast Module: External device attached to drones manufactured before Remote ID requirements. Provides broadcast Remote ID only. Used for retrofitting existing fleets.

Both approaches must meet the same technical requirements: message formats per ASTM F3411, broadcast frequency requirements, and accuracy specifications.

Remote ID Message Format and Data Elements

Location/Vector Message (Most Critical)

The Location/Vector message provides real-time position and motion data:

{
  "timestamp": "2025-01-15T14:23:45.123Z",
  "latitude": 37.7749,
  "longitude": -122.4194,
  "geodetic_altitude": 125.5,  // meters MSL
  "height_agl": 75.2,           // meters above takeoff
  "horizontal_accuracy": 3,      // EPH category
  "vertical_accuracy": 5,        // EPV category
  "speed_horizontal": 12.5,      // m/s
  "speed_vertical": 0.2,         // m/s
  "track_direction": 135,        // degrees true
  "operational_status": "Airborne"
}

Accuracy Categories

Remote ID specifies accuracy in categories rather than exact values, simplifying implementation while providing useful precision information:

Most commercial GPS-equipped drones achieve Category 9 or 10 accuracy (under 3 meters horizontal, under 1 meter vertical) under good conditions.

System Message - Operator Location

The System message includes operator/control station location, enabling authorities to locate the person controlling a drone:

• Operator Latitude/Longitude: Ground control station position
• Area Count: Number of aircraft under operator's control (swarm operations)
• Classification: EU classification type (if applicable)
• Timestamp: When operator position was determined

This data is particularly valuable for enforcement—locating the operator of a drone violating restricted airspace.

LAANC: Low Altitude Authorization and Notification Capability

Before UTM, obtaining authorization to fly near airports could take weeks of manual FAA review. LAANC revolutionized this process, providing near-instant automated approvals for eligible operations. LAANC is perhaps the most successful early implementation of UTM concepts.

LAANC Architecture and Workflow

Step 1: Operator Requests Authorization

An operator planning to fly within controlled airspace uses a LAANC-approved USS application to submit an authorization request including:

• Geographic coordinates defining the operation area
• Maximum altitude (AGL) the drone will reach
• Start time and duration of operation
• Drone and operator registration information

Step 2: USS Validates and Submits to LAANC

The USS performs initial validation:

• Checks operator has valid Part 107 certification or recreational exemption
• Verifies drone is properly registered
• Confirms request is within USFM altitude limits for the grid cell
• Ensures no TFRs or special restrictions affect the area

If validation passes, USS submits the request to the FAA's LAANC system via secure API.

Step 3: LAANC Automated Processing

LAANC performs automated checks:

• Compares requested altitude against USFM ceiling for the location
• Checks for conflicts with active Notices to Airmen (NOTAMs)
• Verifies no special airspace restrictions apply
• Confirms the airport's ATC facility is not objecting (if required)

For operations within USFM limits and absent conflicts, approval is instant—literally seconds. Operations exceeding USFM ceilings are flagged for manual review by ATC personnel.

Step 4: Authorization Delivery

LAANC returns the authorization decision to the USS, which notifies the operator. Approvals include:

• Authorization number for record-keeping
• Exact approved volume (3D + time)
• Any special conditions or limitations
• Duration of authorization

Operators must carry proof of authorization while flying, typically on their mobile device.

LAANC Success Metrics

LAANC's impact has been transformative:

• Speed: Median approval time reduced from 2-4 weeks to under 5 seconds
• Volume: Processing over 1 million authorizations annually (as of 2024)
• Availability: 99.9%+ system uptime; operates 24/7 including holidays
• Coverage: Expanded to over 750 airports across the United States
• Safety Record: Zero reported incidents of LAANC-authorized operations conflicting with manned traffic

Beyond LAANC: Advanced Authorization Systems

Part 107 Waivers and Authorizations

Some operations require waivers from standard Part 107 rules:

• Operations over people or moving vehicles
• Night operations without anti-collision lighting
• Operations from moving vehicles or aircraft
• Multiple drone operations by a single pilot

While LAANC handles airspace authorizations, waivers still require manual FAA review—though increasingly, USS can bundle airspace authorization with waiver applications for streamlined processing.

Beyond Visual Line of Sight (BVLOS) Authorizations

BVLOS operations—flying beyond where the pilot can see the drone—require Part 107 waivers and often additional risk mitigations:

• Detect and avoid systems (radar, ADS-B, visual observers)
• Enhanced operational procedures and pilot training
• Contingency planning for lost link or equipment failures
• Additional insurance coverage

UTM plays a critical role in enabling BVLOS by providing awareness of other traffic and coordinated airspace access. As DAA systems mature and UTM capabilities expand, BVLOS operations will transition from exceptional to routine.

International Authorization Approaches

While LAANC is U.S.-specific, other regions have developed similar systems:

• Europe (U-Space): Geo-awareness services and dynamic airspace information integrated with flight authorization
• Japan: DIPS (Drone Information Platform System) for flight notifications and approvals
• Singapore: OneMap portal integrated with automated authorization checking
• Australia: CASA's digital services for drone approvals and registration

International harmonization efforts aim to enable cross-border operations with mutually recognized authorizations.