FAA Urges Halt to Falcon Field Landing Fees
The FAA has sent a formal letter urging Mesa, Arizona to pause Falcon Field Airport's landing fee program pending federal review, citing potential violations of grant assurances, the Surplus Property Act, and FAA Rates and Charges Policy. AOPA has also intervened, flagging safety concerns over using ADS-B data for billing. The outcome could set precedent for publicly funded airports nationwide.
The FAA's Office of Airport Compliance and Management Analysis sent an April 13 letter to Mesa, Arizona officials urging them to pause Falcon Field Airport's (KFFZ) landing fee schedule pending federal review — a rare direct intervention that signals the agency considers the program legally problematic before it collects a single dollar. The fees, structured at $20.35 per landing for based aircraft and $24.35 for itinerant aircraft under 6,000 lbs, were originally set to begin data collection May 1; Mesa has since pushed that date to August 1. The delay hasn't closed the legal questions.
What the FAA Is Objecting To
Falcon Field received federal grant money, which means it operates under federal grant assurances — a set of binding public-use commitments attached to that funding. The FAA's letter identifies three potential violations:
| Legal Framework | Allegation |
|---|---|
| Federal Grant Assurances | Fees may conflict with the airport's obligation to make the facility available on reasonable, non-discriminatory terms |
| Surplus Property Act | Falcon Field occupies land transferred from federal surplus — that conveyance carries use restrictions |
| FAA Rates and Charges Policy | GA landing fees at this airport type may not meet the policy's cost-justification standard |
At least two informal complaints have been filed under 14 CFR Part 13.2, the provision that allows individuals to flag potential regulatory violations to the FAA. The agency's April letter follows those complaints and constitutes a formal notice to Mesa that review is underway — not a final order, but a clear signal that the fee program is on thin legal ice.
AOPA's Intervention and the ADS-B Safety Flag
AOPA sent its own letter on May 28, requesting an immediate stay of the program. Beyond the grant assurance arguments, AOPA raised a concern that goes beyond legal compliance: using ADS-B transponder data as the billing mechanism creates a safety incentive problem.
The logic is straightforward. If pilots know that squawking their transponder triggers a landing fee, some will turn it off — or avoid equipping in the first place. ADS-B was mandated as a safety and traffic separation tool. Routing billing through it inverts that purpose: the safety system becomes a cost generator, and the rational pilot response is to defeat it. AOPA's letter frames this not as speculation but as a foreseeable behavioral outcome that the FAA should weigh alongside the legal questions.
Mesa's Two-Airport Fee Strategy
Falcon Field is not Mesa's only fee experiment. Mesa Gateway Airport (KIWA), also operated by the city, already has an active ADS-B billing program running. Mesa is simultaneously pursuing landing fees at two federally obligated airports using the same underlying mechanism — ADS-B data collection — while federal regulators are actively questioning whether either program is lawful.
| Airport | ICAO | Fee Status | Data Collection Start |
|---|---|---|---|
| Falcon Field | KFFZ | Pending — FAA review underway | August 1, 2026 (delayed) |
| Mesa Gateway | KIWA | Active | Already running |
The two-airport posture matters for understanding Mesa's intent. This isn't a local budget patch; it's a systematic program to monetize GA traffic at publicly funded facilities using surveillance infrastructure the FAA mandated for safety purposes.
Legislative Battleground
The ALERT Act, which has passed the House, includes Section 105 — a provision that would explicitly ban ADS-B-based billing at federally funded airports. The critical question is what happens when the ALERT Act goes to the Senate for reconciliation with the ROTOR Act, the Senate's competing aviation reauthorization bill.
The Senate version does not currently contain an equivalent ADS-B billing prohibition. Whether Section 105 survives conference is the single most important near-term variable for this issue. If it does, Mesa's program at both KFFZ and KIWA would face a direct federal statutory bar. If it's stripped, the only remaining check is FAA enforcement — which, as the Falcon Field situation illustrates, operates slowly and through informal pressure rather than immediate prohibition.
What this means for GA pilots: If you fly into KFFZ or KIWA, landing fees are either imminent or already active. More broadly, the legal outcome here will determine whether any publicly funded airport in the country can build a fee program on top of ADS-B data — a question that affects every GA pilot who operates under the 2020 ADS-B mandate at any federally obligated field.
The Broader Principle
What Mesa is testing is whether federal grant assurances have teeth when an airport decides to monetize the traffic those grants were meant to encourage. The FAA's April letter suggests the agency believes they do — but a letter urging a pause is not the same as an enforcement action, and Mesa has not stopped its program, only delayed it. If the city proceeds in August and the FAA does not escalate, the de facto precedent will be that federally obligated airports can implement GA landing fees and wait for litigation. That outcome would reshape the economics of publicly funded general aviation infrastructure in ways that go well beyond Falcon Field's $20 landing charge.