AirData Joins the Commercial Drone Alliance: What It Signals About Part 108 Compliance

By Wesley Alexander • May 11, 2026 • 7 min read

This week AirData UAV, a fleet management and analytics platform widely used by Part 107 and Part 135 operators, announced it has joined the Commercial Drone Alliance (CDA). On the surface it is a membership press release. Read carefully, and it is a tell about where the FAA's anticipated Part 108 rule is going to land for the rest of us.

Part 108 is widely expected to expand routine Beyond Visual Line of Sight (BVLOS) operations in the United States. The interesting question for operators is not whether the rule will pass. It is what the rule will require you to keep, prove, and report once it does. AirData's positioning, and CDA's framing of the announcement, suggest the compliance burden under Part 108 will live as much in data systems as in aircraft.

What Was Actually Announced

AirData UAV has joined the Commercial Drone Alliance, the industry's most active policy coalition in Washington. Per the company, the platform currently supports more than 61 million flights logged across roughly 450,000 pilots and 850,000 aircraft. Those numbers come from AirData and have not been independently audited, but they are consistent with what you see in the field: AirData logs and reports are now a default artifact at many enterprise and public safety programs.

Lisa Ellman, CEO of the CDA, framed the move around scaled BVLOS:

"As the industry moves toward broader BVLOS operations and frameworks like Part 108, access to scalable, reliable operational data such as that which AirData provides will help to safely unlock the full potential of the drone economy."

That quote is the lead, and it is doing work. The CDA is not selling aircraft, detect-and-avoid systems, or a particular C2 link architecture this week. It is selling the idea that operational data and continuous reporting are now first-class regulatory infrastructure.

Why Part 108 Is a Data Rule, Not Just an Aircraft Rule

Most operator conversation about Part 108 still defaults to airframes, detect-and-avoid, and risk-categorized operational areas. Those matter. But the reporting tail of Part 108 is what most small operators are underestimating.

Based on the published Notice of Proposed Rulemaking and the CDA and industry summaries circulating ahead of finalization, the operational requirements Part 108 is expected to introduce go well beyond what a typical Part 107 program tracks today:

Pre-flight, in-flight, and post-flight documentation for every operation in scope.
Defined personnel roles, including operational oversight functions that look more like Part 135 than Part 107.
Risk-categorized operational areas, with documentation that ties each flight to the risk model that authorized it.
Mandatory continuous data reporting to the FAA covering aspects of operational performance and safety.
Maintenance documentation, pilot currency tracking, and asset-level history that can be audited on demand.

A spreadsheet and a folder of PDF logs will not meet that bar at any kind of scale. Neither will a flight-app screenshot. The practical answer for most operators is going to be a fleet management platform with automated capture from the aircraft, structured exports the FAA can ingest, and an audit trail that is harder to backfill than a clipboard.

That is the gap AirData is positioning into. The same gap is also being chased by Aloft (now inside Versaterm), DroneDeploy, DroneLogbook, Skyward, and a handful of OEM-native platforms. Joining the CDA is partly a competitive marker, but the broader signal stands: the FAA's expected ask under Part 108 is data-shaped.

The Operator-Side Reading

For a working commercial program, here is what this week's news actually changes.

First, your software vendor selection is now a regulatory decision. If you fly under Part 107 today and a vendor change is cosmetic, that becomes harder to say once Part 108 takes effect. Whatever platform owns your flight logs, maintenance logs, pilot currency, route history, and incident reporting will own your audit posture. That is no longer a back-office choice.

Second, your data capture has to move upstream. Manual flight logs entered after the fact will not survive a Part 108 audit cleanly. The cleanest pattern is automated ingest directly from the flight controller or ground station, with the platform reconstructing the operational record from telemetry. AirData's model does that today. So do several competitors. If your program is still on hand-entered logs, that is the gap to close before the rule lands, not after.

Third, route planning and Remote ID become part of the same artifact stack. Under Part 108's expected structure, your authorization for a given flight is going to be tied to where you flew, the risk class of that volume, and what you reported back. That ties together what used to be three separate workflows: route planning and NOTAM and TFR review, Remote ID broadcast, and post-flight reporting. If those still live in three different tools that do not share state, you have a stitching problem to solve.

Fourth, contingency and failure-state evidence will matter. The most useful thing a fleet platform can give you under Part 108 is not the green-line log of a normal flight. It is the captured state when something went sideways: a C2 link dropout, a lost-link RTH event, a battery anomaly, a deviation from the planned corridor. Those are the events the FAA will care most about, and they are the events most likely to be lost if your reporting depends on a pilot remembering to write a paragraph at the end of a long day. Pick a platform that captures them automatically.

Where the CDA Move Fits in the Broader Picture

The CDA has been the loudest voice arguing for a workable BVLOS rule for years. Its current member roster reflects that focus: it leans heavily toward operators, integrators, and infrastructure providers, with some interesting absences. Amazon's recent split from the CDA over electronic conspicuity (see our coverage of the FAA Part 108 industry response and Amazon's exit) is the obvious example. That split was about what aircraft need to broadcast and detect. AirData joining now is, in a sense, the other half of that debate: not what the aircraft sees, but what the operator records.

Both ends matter. Detect-and-avoid is what keeps the airspace safe in the moment. Operational data is what makes that safety legible to the regulator after the fact. Part 108 has to do both, and the industry conversation is now visibly broken into those two work streams.

For smaller operators watching the CDA from the outside, the practical implication is straightforward. Membership in a coalition is not required to comply with Part 108. But the requirements the coalition is helping shape are going to apply whether you joined or not. The cheaper move is to assume your tooling will need to look more like an enterprise data platform than a flight app, and to budget accordingly.

What To Do This Quarter

A short, opinionated checklist for operators who do not want to be caught flat-footed when Part 108 finalizes:

Audit how your flight data is captured today. If a human types it, that is risk.
Confirm your fleet platform exports structured records, not just PDFs.
Tie pilot currency and maintenance records into the same system as flight logs.
Stand up a written process for capturing C2 link events, lost-link RTH activations, and route deviations as discrete records.
If you run Part 135 or are planning to step up to BVLOS at scale, treat your software stack as part of your safety case, not as overhead.

None of this requires waiting for the final rule. All of it gets easier the earlier you start.

The Operator Bottom Line

The AirData and CDA announcement is one of those stories where the headline understates the signal. The interesting thing is not which company joined which alliance. The interesting thing is that a data and analytics vendor was the natural next addition to the industry's leading BVLOS policy coalition. That is a quiet confirmation that Part 108 is going to be enforced through the operational record as much as through the airframe.

If you are running a commercial drone program and you do not yet know exactly where every flight in the last 90 days went, when it launched, who was in the seat, what the aircraft state looked like at landing, and which authorization covered it, this is the news cycle to fix that.