An airport emergency exercise now starts with a paperwork request

What changed on 9 October

The FAA updated its on airport drone operations guidance on 9 October, addressing a question that airport operators and the contractors working for them have been answering inconsistently. Where a small unmanned aircraft will be flown in controlled airspace in support of an airport emergency exercise, including exercises run under the airport emergency plan requirements of Part 139, the airport sponsor has to apply to the FAA for airspace access, and the request has to go in early enough to be processed before the exercise date. Two filing routes are named. A flight conducted under Part 107 goes through the drone zone airspace authorization process for controlled airspace. A flight conducted under Part 91 goes through the certificate of authorization route regardless of the class of airspace involved. The guidance does not create new operating rules and does not change Part 107; what it does is close the gap between a drill that looks simple and the authorization that makes it legal.

The sponsor owns the decision, not the contractor

There is a second, more useful point buried in the same guidance: the airport owner or operator holds the authority to approve or deny any small drone operation requesting access to fly on the airport. A service provider cannot simply arrive and book a window, and the request channel is the FAA's drone zone portal rather than the low altitude authorization service that many commercial pilots use for routine controlled airspace work. LAANC is not the route for on airport operations. That matters for contracts. When an exercise includes a drone element, the agreement should name who files, which route applies, what evidence of authorization the airport holds, and what happens if the request is still pending the week before the drill. A provider that assumes the sponsor has already filed is the reason an exercise gets scaled back.

Exercise plans need a new line item Emergency exercise planning already runs on a long calendar: scenario, participants, mutual aid notifications, evaluators, and a date that has to coexist with a real emergency response capability. Airspace processing time is now another entry in that calendar, and it needs an owner with a name.

Two practical consequences follow. First, treat the airspace request as a milestone with a due date that is weeks ahead of the exercise, not as a task for the week of. Second, keep a fallback in the plan. If the authorization lands late, the drill should be able to run with the drone element removed rather than cancelled outright, because the rest of the exercise still has value.

The boundary that did not move

The same guidance restates a limit worth repeating to anyone selling aerial inspection to an airport: a drone cannot be the only means of carrying out required Part 139 self inspections. It can be an additional tool alongside the inspection the airport is required to perform, with the required inspection still done as required. The agency is also still examining other airport uses, among them support for rescue and firefighting crews, documentation of accident scenes, and routine field inspections.

Operational takeaway

Before the next exercise, put three things in the plan: the name of the person who will file the airspace request, the route that applies to the flight, and a buffer measured in weeks rather than days. A cancelled drill costs a full training cycle, and the paperwork now sits on the critical path.