The forthcoming FAA rule covering long range drone flights — Part 108 in regulatory shorthand — would for the first time put the operating organization, not the individual pilot, on the hook for detailed compliance records.
The FAA's forthcoming BVLOS rule, the long-awaited regulation that would let companies routinely fly drones beyond the pilot's line of sight, is in its final stage of federal review, according to trade press. When it lands, liability won't get lighter. It will move: from the individual remote pilot to the operating organization.
That shift is what makes AirData's announcement of 65 million tracked flights matter. The California fleet platform says it has logged flights across 850,000+ drones and 470,000+ pilots worldwide, spanning 180+ aircraft models (DroneDJ). The numbers are company self-reported, not independently audited, and the FAA's final Part 108 language, scope, and effective date remain external to this source.
Under Part 108 as currently described, operators will need to produce airworthy aircraft, trained personnel, approved procedures, and detailed records covering flight ops, maintenance, pilot certifications, and incident reports. That stack maps directly onto what AirData already captures: flight logs, maintenance records, battery health, pilot certifications, and compliance data across mixed fleets.
AirData founder Eran Steiner frames the corpus as a benchmarking asset: anomaly detection at a scale no single operator could run, like catching one battery aging differently from dozens under similar conditions. Under Part 108, the company positioned to become the audit trail of record is the one that already has the dataset. Operators without an equivalent software stack will be structurally disadvantaged once routine BVLOS flight is the default.