Summary

  • A September 11 FCC order permits limited airborne mobile-network testing for MNAAP, with authorisation expiring at the start of October 1, 2029, Eastern Time.
  • The test module still requires both FCC equipment authorisation and approval through nationwide mobile providers' certification programmes; permission to test is not a service guarantee.

For a device supplier, the important word in an airborne connectivity trial may be “approved”, rather than “connected”. A signal can be observed before a device is accepted by a network, and both can happen before an aviation customer has a service worth buying. The FCC's new MNAAP order makes those distinctions commercially relevant without resolving them.

The September 11 order supports the DOT programme's assessment of existing commercial mobile networks in the contiguous United States. Its simultaneous participation ceilings are 2,000 authorised general-aviation pilots using the app and 200 authorised non-federal module participants. These are limits on testing, not a customer forecast. Information goes to a DOT-managed database.

Two routes into the experiment

The app uses ordinary consumer devices and information normally available to them. Its reporting cannot exceed once every two seconds, and DOT must be able to disable a participant remotely. The module follows a different route: FCC equipment authorisation plus approval under nationwide mobile providers' equipment certification programmes. Modules are restricted to authorised participants, cannot be transferred and must be decommissioned when the waiver ends.

For suppliers, that second route makes network acceptance part of the integration task. The order provides no approval prices, processing times or carrier-specific results. It would therefore be premature to call certification either an inexpensive formality or a deliberate barrier. What is clear is that regulatory equipment authorisation does not replace it.

The two-second rule also needs careful handling. A maximum reporting frequency says nothing by itself about network latency or whether a connection can support a safety-critical command. Treating it as a performance specification would confuse how evidence is collected with what an eventual service must deliver.

A reason to measure, not an answer in advance

DOT's electronic-conspicuity explanation describes research into making aircraft detectable to one another as manned and unmanned traffic share airspace. Crucially, its depiction of mobile signals at different altitudes is labelled illustrative: testing is needed to establish capabilities and limits. It is a research rationale, not an aerial coverage certificate.

A useful commercial result would consequently do more than show that some flights received a signal. Buyers would need to understand which locations, heights and operating conditions were represented, what failures occurred and whether another device or network could reproduce the result. A large sample with poorly described conditions could be less informative than a smaller, well-characterised one. That is a question for the test method, not a criticism of results that have yet to be supplied here.

The immediate opportunity is to reduce uncertainty around the use of an existing network asset in a different environment. The order does not announce tariffs, revenue, a network-performance guarantee or general permission for commercial drone flights. Existing technical constraints and interference protections remain relevant. For operators and equipment makers, a bounded route to evidence is progress; its value will depend on what can be demonstrated and integrated before anybody promises an aviation service.