Understanding FAA Grant Assurance Obligations for Airport Sponsors
Federal airport grants are not free money — they come with strings, and those strings are the grant assurances. When a sponsor accepts Airport Improvement Program (AIP) funds, it contractually agrees to a long list of continuing obligations about how the airport is operated, maintained, funded, and developed. For planners and consultants, the assurances quietly shape what a project can and cannot do, so it pays to know the ones that bite.
What the grant assurances are
The grant assurances are the conditions a sponsor accepts in exchange for federal airport development funding. They flow from federal statute and are incorporated into every AIP grant agreement; by signing, the sponsor commits to comply for the duration of the obligation. The FAA enforces them through its airport compliance program. There are roughly three dozen assurances for airport sponsors, covering everything from how the airport is managed to who may use it and what happens to the revenue it generates.
The obligations that matter most to a planner
You do not need all of them memorized, but a handful come up constantly in planning and design work:
- Airport Layout Plan (Assurance 29). The sponsor must keep an up-to-date Airport Layout Plan on file with the FAA and must not make or permit changes to the airport that are inconsistent with it without FAA approval. This is why an ALP update — and FAA review of it — is the gate for almost any physical change.
- Operation and Maintenance (Assurance 19). The airport and its facilities must be operated and kept in a safe and serviceable condition; the sponsor cannot let federally funded facilities decay.
- Economic Nondiscrimination (Assurance 22). The airport must be available for public use on reasonable terms and without unjust discrimination to all types, kinds, and classes of aeronautical activity.
- Fee and Rental Structure / Self-Sustainability (Assurances 24 & 25 area). The sponsor must maintain a fee and rental structure that makes the airport as self-sustaining as possible, and airport revenue must be used for the airport — revenue diversion is prohibited.
- Compatible Land Use & Hazard Removal (Assurances 20 & 21). The sponsor must take appropriate action to restrict incompatible land uses around the airport and to protect approaches by removing, lowering, lighting, or marking hazards. These tie directly into airspace and RPZ land-use work.
- Preserving Rights and Powers / Good Title (Assurances 5 & 4). The sponsor must hold good title to the airport land and not take actions that would deprive it of the rights and powers needed to comply with the assurances.
How long the obligations last
The assurances do not last forever in the same way for everything — the duration depends on what the grant funded:
| What was funded | How long the obligation runs |
|---|---|
| Most development / equipment grants | Generally 20 years from grant acceptance |
| Land acquired with federal funds | For as long as the property is used as an airport (no 20-year cutoff) |
| Surplus property / certain conveyances | Can be perpetual, per the conveyance instrument |
The practical consequence: a sponsor that accepted a grant years ago may still be fully bound today, and land obligations can outlive every other commitment. Before assuming an obligation has expired, check the grant history and the terms that attach to the land itself.
Why this shapes planning work
Grant assurances are the legal backdrop to the documents planners produce:
- The ALP is an obligation, not a formality. Because Assurance 29 binds the sponsor to a current, FAA-approved ALP, a master plan or ALP update is the mechanism that keeps the airport in compliance while it changes — and FAA approval is what unlocks federally consistent development.
- Land and property interests are tracked for a reason. Title, avigation easements, and federally obligated parcels feed the Exhibit A property map — which is itself how a sponsor demonstrates it holds the interests the assurances require.
- Revenue and access constraints frame the alternatives. A plan that proposes diverting airport revenue, closing the field to a class of users, or building something inconsistent with the ALP runs straight into an assurance — better to catch that in planning than in a Part 16 complaint.
Two AvPlot tools sit directly on this terrain. The ALP Data Tables generator produces the standardized data-table set behind an ALP, and the Exhibit A tool supports the property-interest inventory and completeness checklist that documents the land obligations the assurances depend on.
This article is a reference summary for planning use, not legal advice or a substitute for the governing text. Citations refer to 49 U.S.C. §47107 (sponsor assurances), the FAA Airport Sponsor Assurances document, and FAA Order 5190.6B (FAA Airport Compliance Manual). Assurance numbers and durations are summarized as commonly applied — always confirm the current assurances document and consult your FAA Airports District Office and legal counsel on any compliance question. See the full airport planning glossary or the AvPlot toolkit.