FAA Urges Halt To Falcon Field Landing Fees

Why It Matters

If enforced, the fees could limit flight‑training and general‑aviation traffic, affecting regional airport revenue and airspace efficiency.

Key Takeaways

• FAA cites possible conflict with grant assurances and Surplus Property Act
• Landing fees could restrict legitimate aeronautical activities, violating FAA policy
• AOPA demands stay until economic impact analysis is released
• Fees set at $20.35 for based, $24.35 for itinerant aircraft
• Implementation delayed; collection to start July 30, billing Aug. 1

Pulse Analysis

The Federal Aviation Administration routinely monitors municipal airport fee structures to ensure they align with federal grant assurances and the Surplus Property Act, which transferred many airports to local control under strict non‑discriminatory use clauses. In its April 13 letter, the FAA’s Office of Airport Compliance flagged Falcon Field’s proposed landing fees as potentially inconsistent with these obligations, as well as with the agency’s Rates and Charges Policy. By questioning whether the fees could unreasonably limit aeronautical activities, the FAA is exercising its oversight role to protect the national airspace system from localized pricing barriers.

For Falcon Field, a hub for flight‑training schools and general‑aviation traffic in the Phoenix metro area, the dispute carries operational weight. The $20.35 fee for based aircraft and $24.35 for itinerant planes, collected via ADS‑B data, could raise costs for student pilots and charter operators, prompting diversions or go‑arounds that strain nearby airports. The Aircraft Owners and Pilots Association has already petitioned for an immediate stay, arguing that without a transparent economic impact study the fees may depress airport usage and exacerbate pattern saturation during peak training hours.

The outcome will reverberate beyond Mesa. Municipalities nationwide rely on modest landing fees to fund infrastructure while remaining compliant with federal mandates. A precedent that upholds the FAA’s objections could force cities to redesign revenue models, emphasizing cost‑recovery mechanisms that do not impede aeronautical freedom. Conversely, a ruling that validates Falcon Field’s schedule may encourage other airports to adopt data‑driven fee collection, provided they conduct rigorous impact analyses. Stakeholders now await the FAA’s final determination, which will shape the balance between local fiscal needs and the broader goal of an open, efficient airspace.