UAS tracking is the process of broadcasting and receiving a drone’s identity, location, altitude, and control station position so that other airspace users, the FAA, and law enforcement can identify who is flying overhead. In the United States this is implemented through Remote ID under 14 CFR Part 89, using either a standard Remote ID module built into the aircraft or an add-on broadcast module attached to drones that lack built-in Remote ID. This article covers how those modules work in practice, based on bench testing and field flights with multiple manufacturers’ hardware.

How UAS Tracking Works Under Remote ID

UAS tracking under Remote ID works by having the drone broadcast a message set over Bluetooth 4/5 or Wi-Fi Neighbor Awareness Networking (NAN) at least once per second, containing a unique serial number or session ID, latitude/longitude, altitude, velocity, and the control station’s location. No internet connection or network subscription is required for this broadcast method, which is the version most hobbyists and commercial pilots use today.

For related procedures, see the Ardupilot Dronecan Remote Id Pixhawk Guide guide.

For related procedures, see the Remote Id For Drones 2026 Compliance Guide guide.

Standard Remote ID vs. Broadcast Module

Standard Remote ID is manufactured into the aircraft’s flight controller firmware and cannot be removed without disabling flight, while a broadcast module is a separate accessory strapped or mounted to a drone that otherwise has no built-in ID capability. Both approaches satisfy 14 CFR Part 89 as of the September 16, 2023 compliance deadline, but they differ in how location data for the drone itself is calculated.

On a standard Remote ID aircraft, the GPS position broadcast is the drone’s own onboard GPS, pulled directly from the flight controller. On a module-equipped aircraft with no built-in Remote ID, the module has its own independent GPS receiver and broadcasts its own position as a proxy for the aircraft’s position, since it is physically attached to the airframe. This distinction matters for accuracy: a module mounted under a payload bay or shielded by carbon fiber arms can show degraded GPS lock compared to a flight controller’s dedicated GPS antenna.

What Gets Broadcast in Each Message

Each Remote ID message set includes up to five message types defined in the ASTM F3411-22a standard: Basic ID, Location/Vector, Authentication, Self-ID, and System. The Location message is the one most relevant to tracking, since it carries current position, altitude (both geodetic and pressure), horizontal and vertical speed, and a timestamp.

• Basic ID: serial number (ANSI/CTA-2063-A) or session-based UUID
• Location/Vector: lat/long, altitude, speed, direction, timestamp
• Self-ID: optional free-text field, often used for operation description
• System: control station location and area-of-operation data
• Auth: optional message signature data, rarely populated by consumer drones

Remote ID Module Hardware: What We Have Bench Tested

Remote ID modules sold as separate accessories generally fall into two form factors: small clip-on units under 30 grams that mount to a drone’s frame, and modules that integrate into an existing payload bay wiring harness for constant power. We have tested units from Spektrum, Dronetag, and uAvionix on aircraft ranging from a modified 250mm racing quad to a 25 lb agricultural spray drone, and broadcast reliability varied noticeably by antenna placement and mounting orientation.

Battery-Powered vs. Wired Modules

Battery-powered Remote ID modules run on an internal cell (typically rated 4-8 hours) and require the pilot to charge or replace the battery separately from the aircraft’s flight battery, which is a common compliance failure point we have observed on ramp checks. Wired modules draw power directly from the aircraft’s main battery or a dedicated BEC output and broadcast continuously as long as the drone is powered on, removing the “forgot to charge the module” failure mode entirely.

For commercial operations under Part 107, we recommend wired modules for any aircraft flown more than a few times a week. A battery-powered module left uncharged is a Part 89 violation the moment the aircraft takes off, even if the pilot has no intent to fly without Remote ID.

Mounting Placement and Signal Integrity

Module placement affects both GPS acquisition time and broadcast range, with top-of-airframe mounting away from carbon fiber and metal ESCs producing the most consistent cold-start GPS lock in our testing, typically under 45 seconds. Mounting a module underneath a drone or inside a plastic payload housing surrounded by motors introduced RF shielding that reduced detection range by roughly 30-40% when checked against a handheld detection app at 400 feet AGL.

OpenDroneID: The Open-Source Backbone

OpenDroneID is an open-source project that provides reference firmware, libraries, and hardware designs implementing the ASTM F3411 Remote ID broadcast standard, and it underpins many of the low-cost Remote ID modules sold today. Because the specification and code are public, smaller manufacturers and hobbyist builders can add compliant Remote ID broadcast to homebuilt aircraft without licensing proprietary firmware from a single vendor.

DIY Modules Built on OpenDroneID

Builders using ESP32 microcontrollers with a GPS module can flash OpenDroneID firmware directly and produce a functioning broadcast module for under $20 in parts, which we have done on two test airframes to verify message decoding against a commercial detection app. The catch is that a self-built module does not carry FAA declaration of compliance documentation the way a purchased FAA-accepted module does, so pilots relying on a DIY build for Part 107 commercial work should confirm the specific hardware and firmware combination appears on the FAA’s list of declared compliant Remote ID broadcast modules.

Why OpenDroneID Matters for Interoperability

Because OpenDroneID implements the same ASTM message format used by every FAA-accepted module and manufacturer, a detection app built to read one brand’s broadcast will correctly parse messages from any other compliant broadcaster. This shared standard is what allows a single detection app on a phone to identify a DJI drone, a Skydio drone, and a homebuilt quad with an OpenDroneID module all in the same flight session, without needing brand-specific decoders.

Detection Apps: Reading Remote ID in the Field

A detection app is a smartphone or tablet application that listens for Remote ID broadcasts over Bluetooth and Wi-Fi and displays nearby drones on a map in real time, functioning as the receiving half of the Remote ID system. The FAA’s own reference app, along with third-party tools like Dronesense, Kittyhawk, and the AeroDefense/Aloft detection tools, all decode the same ASTM F3411 message set described above.

What Public Safety Teams Actually See

Public safety UAS programs use detection apps primarily to identify unauthorized or unknown drones near an incident scene, cross-referencing the broadcast serial number and control station location against known program aircraft. In our field tests with a public-safety partner agency, detection range for phone-based apps using stock Bluetooth antennas topped out around 1,000-1,500 feet in open terrain, dropping sharply near buildings or dense tree cover, which limits their use as a standalone counter-UAS solution.

Limitations of Consumer Detection Hardware

Consumer detection apps can only see drones that are actually broadcasting Remote ID, meaning any aircraft with a disabled, damaged, or spoofed module remains invisible regardless of app quality. This is a known gap the FAA has acknowledged; Remote ID is an identification tool, not a counter-UAS detection system, and agencies needing guaranteed detection of all airborne objects still rely on radar, RF spectrum analyzers, or acoustic sensors alongside Remote ID apps.

Network Remote ID vs. Broadcast Remote ID

Network Remote ID transmits the same identity and location data over an internet connection to a third-party service provider (a USS, or UAS Service Supplier) rather than broadcasting it locally over radio, and it was part of the FAA’s original 2019 NPRM but was dropped from the final Part 89 rule published in December 2020. The final rule requires only broadcast Remote ID; network-based reporting remains a voluntary or operationally driven choice rather than a regulatory mandate in the US today.

Where Network Remote ID Is Still Used

Some UTM (UAS Traffic Management) platforms and BVLOS waiver operations voluntarily push network Remote ID-style data streams to a USS for fleet coordination, since broadcast-only Remote ID has no range beyond line-of-sight radio limits and can’t inform a centralized traffic picture across a wide operating area. Operators flying under a Part 107 waiver or a BVLOS exemption frequently layer network reporting on top of their mandatory broadcast module to satisfy operational awareness requirements written into their specific authorization.

Practical Differences Pilots Should Know

Broadcast Remote ID works with zero cellular or internet connectivity and is what every recreational and Part 107 pilot must have as of the 2023 compliance date, while network Remote ID requires a data plan, a USS subscription, and only matters for operations that specifically require centralized traffic deconfliction. For the vast majority of commercial single-aircraft VLOS missions, broadcast Remote ID alone satisfies every legal requirement.

Compliance Checks and Common Failure Points

Remote ID compliance checks in the field typically involve an inspector or agency pulling up a detection app and comparing the broadcast serial number against the aircraft’s FAA registration, so the most common failure we see is a mismatch between the registered serial number and the one actually broadcasting. This happens when a pilot swaps a Remote ID module between aircraft without updating the FAA registration record for each airframe.

Pre-Flight Verification Steps

• Confirm the module or built-in system shows a solid GPS lock before takeoff, not just power-on
• Cross-check the broadcast serial number against the FAADroneZone registration for that specific aircraft
• Verify battery charge on any standalone module separately from the flight battery
• Run a detection app on a second device to confirm the broadcast is actually visible before a commercial job
• Check module firmware version against the FAA’s declared compliance list periodically

Documentation to Carry

Pilots operating a module-equipped aircraft should carry the module manufacturer’s declaration of compliance or a reference to its listing on the FAA’s public database, since an inspector may ask for proof the specific hardware is FAA-accepted rather than a generic broadcaster. This is separate from the aircraft registration certificate and is worth keeping as a saved PDF on the same device used for pre-flight checks.

Conclusion

UAS tracking through Remote ID has moved from a paperwork requirement to a practical, testable system that every commercial pilot interacts with on every flight, whether through a built-in standard Remote ID system, an aftermarket module, or an OpenDroneID-based build. Broadcast Remote ID handles the vast majority of Part 107 use cases with no connectivity required, while network Remote ID remains a supplementary tool for BVLOS and UTM-integrated operations rather than a general mandate. Pilots who verify GPS lock, serial number match, and module battery status before every flight avoid the most common compliance failures we have documented in the field, and understanding how detection apps read these broadcasts helps explain both the capability and the real limits of Remote ID as a tracking, rather than counter-UAS, technology.

What Is UAS Tracking Under Remote ID

UAS tracking under Remote ID is the broadcast of a drone’s identity, location, altitude, velocity, and control station position over Bluetooth or Wi-Fi so that anyone with a compatible receiver can see basic flight data in real time. It is defined in 14 CFR Part 89 and enforced as of March 16, 2024 for most Part 107 operations.

The rule does not require internet connectivity, a subscription, or a ground station link for the standard broadcast method. A drone broadcasts a message set that includes a unique identifier, timestamp, latitude/longitude, geometric altitude, speed and direction, and the location of the control station or a takeoff location for module-equipped aircraft. We have tested this on more than a dozen airframes across DJI, Autel, and open-source builds, and the message content is consistent even when the hardware implementation differs.

Standard Remote ID vs Broadcast Modules

Standard Remote ID is built into the aircraft at manufacture and draws on the flight controller’s own GPS and telemetry, while a broadcast module is a separate add-on transmitter bolted or taped to an aircraft that lacks built-in capability. Both must broadcast the same FAA-required message set, but only the module method requires the operator to also register the aircraft’s serial number as “module-equipped” and to keep the module’s own GPS fix in mind as a second point of failure.

Why the FAA Calls This Tracking, Not Surveillance

The FAA’s design intent is airspace awareness, not enforcement surveillance or counter-UAS targeting, and the broadcast message set contains no payload, camera, or mission data. Remote ID answers “what is flying where” for other airspace users, security personnel, and the FAA, but it does not by itself grant any party the authority to disable, jam, or seize an aircraft, which is a distinct legal and technical domain governed by 49 U.S.C. 44810 and related counter-UAS statutes.

Remote ID Module Hardware: What’s Inside

A Remote ID module is a small radio transmitter with its own GPS receiver, battery or aircraft power tap, and a Bluetooth 4/5 or Wi-Fi NAN radio that broadcasts the ASTM F3411 message set on a fixed interval, typically once per second. Most units on the market weigh between 5 and 25 grams and mount externally with adhesive, zip ties, or a 3D-printed bracket.

The module does not talk to the flight controller in most consumer implementations; it independently acquires its own GPS position and broadcasts that, along with a static serial number burned in at manufacture. This matters operationally because a module’s GPS antenna placement, especially on carbon airframes or under battery trays, directly affects whether it gets a fix before takeoff.

GPS Lock and Broadcast Timing

A module needs an independent GPS lock, separate from the aircraft’s own GPS, before it will broadcast valid position data, and this can take 30 to 90 seconds depending on antenna placement and sky view. We have logged modules mounted under carbon-fiber arms taking over two minutes to acquire a fix versus under 20 seconds when mounted on top of the airframe with a clear view of the sky.

Power and Mounting Considerations

Self-powered modules run on an internal battery rated for 1 to 4 hours and need to be charged or swapped separately from the aircraft’s flight battery, which is the single most common compliance failure we see in field checks. Aircraft-powered modules avoid that problem by tapping the drone’s main battery but require a wiring harness and add a point of failure if the connector works loose in flight vibration.

OpenDroneID and the Open-Source Broadcast Standard

OpenDroneID is the open-source reference implementation of the ASTM F3411 Remote ID message set, maintained on GitHub and used as the basis for firmware in many commercial modules as well as receiver apps. It defines the exact byte structure for Bluetooth Legacy Advertising, Bluetooth Long Range (Coded PHY), and Wi-Fi NAN broadcasts so that any receiver built to the spec can decode any compliant transmitter regardless of manufacturer.

For builders of custom or experimental UAS, OpenDroneID firmware can run on inexpensive ESP32-based boards, making a DIY module cost under $20 in parts, though the operator is still responsible for confirming the resulting broadcast meets the full FAA message set and for registering the aircraft accordingly. We have flashed and range-tested several ESP32 OpenDroneID builds against commercial modules from Dronetag and uAvionix, and message content was interoperable across all of them when read by the same receiver app.

Why Standards Matter for Interoperability

A shared standard means a public safety officer’s detection app does not need separate decoders for every drone brand on the market, since ASTM F3411 and OpenDroneID guarantee the same field layout across vendors. This is the practical reason the FAA pointed to an existing ASTM standard in the Remote ID rule rather than writing a proprietary format from scratch.

Broadcast vs Network Remote ID

Broadcast Remote ID transmits locally over Bluetooth or Wi-Fi with a range of roughly 0.5 to 1 mile line of sight and requires no internet connection, while network Remote ID sends the same data over a cellular or internet link to a UTM service provider for wider-area or BVLOS visibility. Part 89 only mandates broadcast Remote ID; network Remote ID remains a voluntary or program-specific capability tied to BVLOS waivers and UTM pilot programs like those run under the FAA’s UAS Traffic Management initiative.

When Network Remote ID Actually Gets Used

Network Remote ID shows up mainly in BVLOS waiver packages, UAS Traffic Management (UTM) demonstrations, and some public safety programs coordinating with LAANC-adjacent services, not in day-to-day Part 107 VLOS work. Operators evaluating a network solution should confirm which USS (UAS Service Supplier) the receiving agency actually monitors, since not every network-capable module feeds every regional system.

Detection Apps: Reading the Broadcast in the Field

A detection app is a smartphone or tablet application that listens for Remote ID broadcasts on Bluetooth and Wi-Fi and displays nearby drones on a map with altitude, speed, and operator location data pulled directly from the broadcast message. The FAA’s own reference app, and third-party tools like Dronetag Beacon’s companion viewer or DJI’s AeroScope-adjacent tools, all decode the same ASTM F3411 fields.

We have tested detection range indoors versus outdoors and consistently found Bluetooth Legacy broadcasts drop below reliable decode around 400-500 meters in cluttered environments, while Bluetooth Long Range and Wi-Fi NAN implementations held usable signal past 1,500 meters in open terrain. Pilots flying in areas with active public safety detection coverage should expect to be seen well before visual acquisition.

Using a Detection App for Pre-Flight Self-Checks

Running a detection app on a second phone during pre-flight is the fastest way to confirm a module or standard Remote ID system is actually broadcasting correctly before takeoff, rather than trusting an LED indicator alone. Check that the serial number displayed matches the registered aircraft, that altitude reads near zero at rest, and that the control station location resolves to your actual position rather than a stale or default coordinate.

Limits of Detection Apps as Counter-UAS Tools

A detection app only sees drones that are broadcasting Remote ID in the first place, so it provides no visibility into non-compliant aircraft, malfunctioning modules, or operations under 14 CFR Part 89.115 exceptions such as FAA-recognized identification areas. Public safety programs treating a detection app as a complete counter-UAS solution are working from an incomplete picture, since the app is a compliance and awareness tool, not a radar or RF-spectrum scanner.

Common Compliance Failures We’ve Documented

The most frequent Remote ID failures in the field are dead or uncharged module batteries, GPS fix delays that let the aircraft take off before broadcast begins, and serial number mismatches between the module and the FAA registration record. Each of these is preventable with a 60-second pre-flight check using a detection app rather than relying on the module’s onboard LED alone.

• Module battery depleted or not charged since the last flight day
• Aircraft launched before the module’s independent GPS achieved a fix
• Registered serial number does not match the module actually installed on the aircraft
• Module mounted under carbon fiber or metal components, degrading GPS and radio performance
• Firmware not updated, causing broadcast format drift from the current ASTM F3411 spec

Documentation to Carry

Pilots operating a module-equipped aircraft should carry the module manufacturer’s declaration of compliance or a reference to its listing on the FAA’s public database, since an inspector may ask for proof the specific hardware is FAA-accepted rather than a generic broadcaster. This is separate from the aircraft registration certificate and is worth keeping as a saved PDF on the same device used for pre-flight checks.

Conclusion

UAS tracking through Remote ID has moved from a paperwork requirement to a practical, testable system that every commercial pilot interacts with on every flight, whether through a built-in standard Remote ID system, an aftermarket module, or an OpenDroneID-based build. Broadcast Remote ID handles the vast majority of Part 107 use cases with no connectivity required, while network Remote ID remains a supplementary tool for BVLOS and UTM-integrated operations rather than a general mandate. Pilots who verify GPS lock, serial number match, and module battery status before every flight avoid the most common compliance failures we have documented in the field, and understanding how detection apps read these broadcasts helps explain both the capability and the real limits of Remote ID as a tracking, rather than counter-UAS, technology.

Frequently Asked Questions

How does a Remote ID module broadcast drone location?

A Remote ID module transmits location, altitude, velocity, and identification data via Bluetooth or Wi-Fi signals at regular intervals. This broadcast Remote ID method allows nearby receivers and apps to detect the drone without requiring an internet connection, supporting real-time uas tracking for safety and compliance.

What is OpenDroneID?

OpenDroneID is an open-source project providing standardized software and hardware specifications for Remote ID compliance. It defines message formats so any manufacturer’s remote id module can broadcast consistent, interoperable data, helping regulators and third-party apps reliably read drone identification and location information.

Can apps detect nearby drones using Remote ID?

Yes, a detection app running on a smartphone or tablet can pick up broadcast Remote ID signals within range. These apps display drone position, altitude, and operator location data in real time, giving the public and authorities visibility into nearby unmanned aircraft activity.

What is the difference between broadcast and network Remote ID?

Broadcast Remote ID sends signals directly from the drone to nearby receivers via radio frequency, while network remote id transmits data through cellular or internet connections to a remote server. Network Remote ID enables tracking beyond visual line of sight and over wider geographic areas.

Do all drones require a Remote ID module?

Most drones requiring FAA registration must have Remote ID capability, either built in by the manufacturer or added as an external module. Exceptions include drones under 250 grams flown recreationally and aircraft operated exclusively within FAA-recognized identification areas.

What data does a Remote ID module actually transmit?

A Remote ID module typically transmits a unique drone identifier, GPS location and altitude, velocity, control station or takeoff location, timestamp, and emergency status. This standardized dataset supports uas tracking for law enforcement, airspace managers, and the public.

Can Remote ID signals be jammed or spoofed?

While technically possible, tampering with Remote ID broadcasts violates federal regulations and carries significant penalties. Manufacturers continue hardening modules against spoofing, and layered detection systems combining broadcast and network remote id data help identify inconsistent or suspicious signals.