The new integration streams flight data from AirData's drone platform into LeoSight's public safety command software, but no agency has reported field results yet.
When a drone reaches a scene, dispatchers and field commanders will now see its flight path, telemetry, and operational status in the same console as 911 call data and map overlays, without switching platforms or waiting for a radio relay. The change comes from a new technical link between AirData UAV, a commercial flight-data platform with 62 million logged flights, and LeoSight, a Dallas-area seller of unified command software for public safety. The question for DFR buyers is not whether the data feed exists. It is what, exactly, that feed changes during a real call, and what it leaves on the floor.
The integration wires AirData's flight and telemetry stream into LeoSight's LeoCommand console, the same pane that public-safety agencies already use to consolidate computer-aided dispatch, mapping, and other live inputs. AirData, used by hundreds of thousands of pilots and fleet operators in more than 200 countries, brings a long flight log and a sizable installed base. LeoSight brings the dispatch-side aggregation layer aimed at DFR (Drone First Responder) programs. Mutual customers can now see aerial telemetry in the same view as other response data, per a DRONELIFE report on the partnership.
Before any agency treats the announcement as a workflow upgrade, three concrete questions follow.
First, the data shape. AirData's contribution is flight data, telemetry, and operational insights, in the partnership's own language. That is the kind of state a dispatcher wants for situational awareness: where the aircraft is, where it has been, battery and link status, mission telemetry. It is not the same thing as a live video feed from the aircraft's camera, which is what a 911 call taker usually associates with "drone footage." The press material does not commit LeoCommand to hosting the airframe's video stream, and the distinction matters when a commander is deciding whether the new pane replaces an existing viewer or just augments it.
Second, the workflow. The integration is meant to let dispatchers, command staff, and field personnel coordinate aerial operations alongside other live response inputs, including during daily calls, large incidents, and multi-agency events. The operational claim is reasonable, and the DFR market treats telemetry consolidation as a recurring buyer ask. But neither company has named an agency that has run both products in production under the new link, and the announcement carries no measured effect on response times, dispatcher workload, or handoff latency. "Shared visibility" is a vendor claim, not an outcome.
Third, the policy backdrop. AirData joined the Commercial Drone Alliance in May 2026, a trade group that has positioned itself around the FAA's anticipated Part 108 rule for routine beyond-visual-line-of-sight operations. AirData's CDA membership is a compliance and lobbying posture, not a deployment, but it is the regulatory frame in which DFR buyers will evaluate the integration. Part 108 timing remains uncertain. DRONELIFE describes the rule as anticipated, not finalized, and the DFR market is still waiting on the FAA's text.
The open questions are concrete. Which agencies are running both AirData and LeoSight today, and what changes in their dispatcher workflow once telemetry lands in the same pane as 911 data? What is the latency between the aircraft and LeoCommand, and what happens to the feed when the link drops or the drone returns to base? Is the airframe's video stream coming next, or is this strictly a flight-data and telemetry integration? Until at least one agency answers those on the record, the AirData-LeoSight link is a credible workflow hypothesis awaiting a field result.