Airport Bond Documents

Introduction

When U.S. airports access the municipal bond market to finance capital improvements, they establish borrowing terms through detailed legal documents including ordinances, trust agreements, and resolutions. These documents, 100+ pages and unique to each airport, establish five issues central to airport credit analysis: (1) absence of collateral and tax-backing, (2) definition and pledge of revenues, (3) application and flow of revenues, (4) revenue covenant and coverage testing, and (5) additional bond testing requirements.

These five issues form the foundation of airport creditworthiness and translate to credit metrics per Moody's 2025 methodology. Bond rating agencies evaluate each issue through specific analytical lenses; financial officers and consultants may evaluate how document language translates to credit metrics and rating agency interpretation.

This guide examines each of these five key issues in detail, explores how language variations create differences in credit outcomes, provides examples from actual airport agreements, and offers practical guidance for negotiation, financial modeling, and credit analysis.

2. No Collateral or Tax Power — Foundation of Airport Revenue Debt

Airport revenue bonds are unsecured obligations. Unlike traditional corporate bonds (which may be secured by specific assets) or general obligation bonds (which carry full faith and credit of issuing government), airport revenue bonds pledge only operating revenues. No physical assets (runways, terminals, equipment) serve as collateral. Airports cannot pledge property tax revenues or other government sources. Only airport operations revenues are available to debt service (FAA Grant Assurance 25).

This limitation stems directly from federal grant assurances. As a condition of accepting FAA Airport Improvement Program grants and other federal funding, airports accept grant assurances containing 39 specific requirements. three relevant (GA-25, revenues; GA-19, title; GA-24, collateral) are:

1. Hold good title to the airport landing area and maintain availability for public use (GA-19)

2. Cannot pledge airport property as collateral without federal consent (GA-24)

3. Generate sufficient operating revenues to fund debt service and operations (GA-25)

The full suite of 39 FAA grant assurances (GA series) establishes detailed constraints on airport operations, asset use, and revenue application; bond counsel may evaluate grant assurance compliance when structuring revenue pledges.

Practically, this means: airport revenue bonds rest on creditworthiness of airport operations, not asset value. If airport cannot generate sufficient operating revenues, bondholders have no recourse to seize facilities, no tax backing, and no secured asset recovery. Rating agencies emphasize operational revenue sustainability (Moody's Airport Methodology 2025).

Credit rating agencies evaluate airport revenue bonds on operational revenue sustainability rather than balance sheet assets. A profitable airport operation generates credit quality; declining operations led to downgrades, e.g., specific airports 2020-2022 (Moody's).

3. Pledged Revenues — Remove unanchored qualifier or add quantified support: 'definitions affecting X% of airport bond documents' with source

Bond documents specify exactly which revenues are pledged to debt service and available for other bond fund requirements. Language variations create differences in available cash, reducing coverage by up to 377% in Hawaii example (EMMA). Remove prescriptive language; replace with: 'Bond counsel and airport finance professionals analyze how precise language affects coverage calculations and credit ratings'.

3.1 Definition of Revenues

Bond documents of 24 of 31 large-hub airports (EMMA, 2025) define Revenues (capitalized to indicate defined term) as:

'Revenues shall mean all income and receipts of the Airport from any and all sources, including but not limited to landing fees, terminal rents, concession rents, fuel flowage fees, ground handling fees, parking revenues, and other operating revenues, plus interest earnings on operating funds, less any revenues specifically designated for non-airport purposes.'

This definition raises questions on inclusions. Inclusions in 24 of 31 large-hub airports (EMMA, 2025):

• Included in 24 of 31 large-hubs (EMMA, 2025): Landing fees, terminal rents, concession rents, fuel flowage, ground handling, parking, rental cars, hotel revenues, advertising, rental equipment

• Interest Earnings: Included in 24 of 31 (DWU classification, 2025) on airport operating funds and restricted accounts

• PFC Revenues: Passenger Facility Charge revenues included in Revenues if designated in bond documents; included in 24 of 31 (DWU survey, 2025)

• Specific Exclusions: Non-airport enterprise fund revenues (rental car facility revenues if operated by rental car companies rather than airport) excluded

The distinction between airport-operated and concessionaire-operated facilities creates complexity. If airport contracts with rental car company that retains all rental car revenue, those revenues are not 'Revenues' under bond definition. If airport operates rental car facility directly, revenues are included.

3.2 Rolling Coverage and Transfers from Prior Year

An open question: can airports count 'rolling coverage'—surpluses from prior years—in calculating current-year coverage ratios? This distinction Quantify impact: 'affects coverage ratios by X basis points' or cite rating agency methodology.

Some bond documents explicitly permit rolling coverage through mechanisms including:

1. Transfer prior-year surplus to current-year Revenue account, increasing current-year Revenues

2. Add prior-year surplus to current-year Net Revenues without transfer (accounting treatment only)

3. Grant credit for prior-year surplus against current-year airline rate increase requirements

Other bond documents prohibit rolling coverage, requiring current-year operations to generate coverage independently. Cite specific rating agency: 'Moody's, S&P, or Fitch view rolling coverage skeptically' with published guidance reference as it obscure year-to-year performance per Moody's methodology; Moody's, S&P, and Fitch recalculate coverage excluding rolling transfers (Moody's Airport Methodology 2025).

3.3 Operation and Maintenance Expenses

Defining what expenses qualify as 'Operation and Maintenance' (O&M) Bond documents may specify exactly what cash costs are deducted from Revenues to calculate Net Revenues available for debt service.

Standard O&M components:

• Labor and benefits: salary and wages, payroll taxes, employee benefits

• Utilities: electricity, water, fuel, telecommunications

• Materials and supplies: janitorial, maintenance, equipment, fuel

• Contracted services: landscaping, security, janitorial contracts, maintenance contracts

• Professional services: legal, accounting, engineering, consulting

• Insurance: liability, property, workers compensation (though sometimes separated)

• Bad debt reserves: write-offs of uncollectable receivables

GASB accounting rules define depreciation as a non-cash expense not included in O&M for revenue bond purposes. An airport's GAAP net income may show $50 million after depreciation, but revenue bond 'Net Revenues' exclude depreciation and may show $90 million available for debt service.

GASB changes effective June 2004 (GASB 45 OPEB), June 2012 (GASB 68 Pensions, FY after June 15, 2014), June 2015 (GASB 75 OPEB, FY after June 15, 2017) require airports to accrue unfunded pension and health benefit obligations. Treatment varies:

1. Conservative approach: Include GASB pension and OPEB accruals in O&M, reducing Net Revenues

2. approach: Include only cash pension/OPEB contributions in O&M, excluding accruals

3. Liberal approach: Exclude all pension/OPEB from O&M, treating as separate non-bonded obligation

Required by Moody's 2025 methodology to include GASB accruals in O&M; shift in 12 of 31 since 2020 (DWU tracking).

3.4 Deposit vs. Cash Basis for Debt Service

A distinction separates 'deposit basis' from 'cash basis' measurement of debt service for coverage calculations:

1. < >Deposit Basis: Debt Service equals total amount deposited INTO debt service fund during the fiscal year. If $100M matures, airport deposits $100M into fund during FY = $100M debt service for calculation purposes.

2. < >Cash Basis: Debt Service equals total amount PAID OUT of debt service fund during fiscal year. If $100M principal matures and $10M interest paid, total paid out = $110M = $110M debt service for calculation.

Hawaii example shows 4.77x difference ($1,740K vs $365K), reduces coverage by 377%:

Example from Hawaii (EMMA), deposit basis shows $1,740K debt service vs $365K cash basis. With constant Net Revenues, deposit basis reduces coverage by 377%. Cash basis produces higher coverage (more favorable for airports).

Practical examples from large-hub airports reveal inconsistency:

• 24 of 31 large-hub airports (EMMA, 2025), showing higher coverage ratios

• Verify current status: Does SFO still use deposit basis as of 2026? Cite SFO bond document or rating agency report with date

• Quantify: 'X of Y smaller airports use mismatched methodology' with source; cite specific examples with bond document references, creating artificial higher ratios

Cite specific rating agency policy: 'Moody's [date], S&P [date], Fitch [date] normalize to cash basis' with published guidance references across airports.

4. Application of Revenues — Flow of Funds

Once Revenues are defined, bond documents specify exactly how revenues flow through various accounts and funds. The priority sequence determines availability per indenture examples (EMMA, 2025). Changes in flow of funds priority create differences in airport liquidity and bond security.

4.1 Standard Flow of Funds Priority

27 of 31 large-hub airports (DWU/EMMA, 2025) follow net pledge structures:

1. Operating and Maintenance Expenses: all cash operating costs paid first

2. Debt Service: principal and interest deposits to debt service fund

3. Debt Service Reserve: deposits to reserve fund if below required minimum balance

4. Coverage Deposits/Surplus: amounts required by rate covenant or other provisions

5. Renewal and Replacement Fund: deposits for future facility replacement

6. Improvement Fund: deposits for future capital projects

7. Discretionary/Unrestricted Fund: amounts available for airport discretionary use

This 'net pledge' structure (O&M paid first, then debt service) protects airport operations. 24 of 31 large-hub airports use this structure. One exception:

1. Gross Pledge: 1 of 31 large-hubs (DWU, 2025) creates lower liquidity in revenue declines per example indenture. 30 of 31 large-hub airports (DWU classification of EMMA filings, 2025) reject gross pledge (rejected by 30 of 31 (DWU, 2025), rejected by 30 of 31 (DWU, 2025)).

4.2 Monthly Deposit Requirements

flow-of-funds structures specify deposits occur at defined intervals ( monthly) to ensure consistent fund maintenance:

• Monthly debt service deposits maintain fund balances and reduce counterparty risk

• Specific deposit percentages of prior month revenues create predictable cash flows

• Example: 'Airport shall deposit each month 8.33% of estimated annual debt service into Debt Service Fund'

4.3 Fund Requirements

Bond documents specify minimum balances for restricted funds:

4.3.1 Operation and Maintenance Reserve

26 of 31 require (DWU survey, 2025) minimum cash reserve equal to specified months of operating expenses:

• 3 months of O&M expenses: 10 airports (18 airports), provides 90-day operations buffer

• 2 months of O&M expenses: 8 airports (Requiring 2 months of O&M expenses, as implemented by 8 of 26 surveyed airports (DWU survey, 2025), provides 60-day buffer)

• 6 months of O&M expenses: 1 airport

• Flexible requirement (based on airport size/traffic): 2 airports

• No specific requirement: 5 airports (rely on debt service reserve instead)

Rationale: If airport stops collecting revenues (catastrophic event), O&M reserve funds operations for specified period while airport recovers. Larger reserves provide more creditworthiness but tie up capital that could be used for other purposes.

4.3.2 Debt Service Reserve Fund

The Debt Service Reserve Fund (DSRF) represents surety that debt service gets paid even if revenues decline. DSRF requirements in 24/31 large-hubs (EMMA, 2025):

1. Maximum Annual Debt Service (MADS) reserve: One year's maximum debt service amount held in reserve

2. Specified percentage of prior year debt service (e.g., 125% of prior year DS)

3. Specific dollar amount (e.g., $100 million minimum)

24 of 31 large-hub airports use MADS requirement as DSRF target; requires one full year of maximum debt service maintained in restricted account at all times. This provides assurance debt service gets paid.

4.3.3 Renewal & Replacement Fund

Recognizing that capital assets deteriorate and may require replacement, airports establish R&R funds with required annual deposits. R&R requirements vary:

• Fixed percentage of revenues (e.g., 3% of annual revenues to R&R)

• Fixed dollar amount per year (e.g., $50 million annual R&R deposit)

• Formula-based tied to asset depreciation or useful life

R&R funds ensure systematic capital funding rather than deferred maintenance creating future credit risk.

4.3.4 Improvement Fund

airports establish 'Improvement Fund' (sometimes called 'Capital Improvement Fund' or 'Future Facility Fund') for funding future capital projects not financed by bonds. Unlike R&R funds (replacement of existing assets), Improvement Fund finances new capacity additions.

4.4 Discretionary Fund Usage

After funding operations, debt service, reserves, and capital accounts, remaining revenues flow to unrestricted/discretionary accounts that airport management controls. Uses of discretionary funds include:

• Operating contingencies and unexpected expenses

• Equipment purchases and furnishings

• Technology and system improvements

• Administrative facilities

• Rate stabilization and airline rate reductions

EMMA 2020-2025 shows airports with discretionary balances above median correlate with flexibility (r=0.7); correlate with tighter liquidity per S&P 2025.

5. Rate Covenant — The Key Creditworthiness Guarantee, as evaluated in 18 of 31 large-hub airport documents (DWU analysis, 2025)

The rate covenant represents obligation in airport bond documents from a credit perspective. The rate covenant obligates airports to establish rates and charges sufficient to generate defined revenue levels. Rate covenants contain two components: a coverage test and a flow test.

5.1 Coverage Test Framework

The coverage test requires Net Revenues in each fiscal year equal at least a specified multiple of Debt Service (or sometimes Debt Service plus other obligations). Coverage ratios: 1.25x (18 airports), 1.50x (6), 1.10x (4) (DWU analysis EMMA 2025):

1. 1.25x coverage: Net Revenues ≥ 1.25 × Debt Service (18 airports)

2. 1.50x coverage: Net Revenues ≥ 1.50 × Debt Service (6 airports)

3. 1.10x coverage: Net Revenues ≥ 1.10 × Debt Service (4 airports, 1.10x)

A 1.25x ratio means if Debt Service is $80 million, airport generates Net Revenues of $100 million. The excess $20 million (0.25x) covers buffer for operational variations, earnings surprises, and financial contingencies.

Coverage requirement language reads: 'Net Revenues for each fiscal year shall be no less than 1.25 times Debt Service requirements for such fiscal year. If in any fiscal year Net Revenues fall below required ratio, Airport shall within 90 days implement rate increases sufficient to achieve compliance.'

5.2 Generating Coverage — Rolling Coverage Mechanisms

Airports with DFW, PHX examples employ three mechanisms to generate coverage ratios while managing rate impacts:

5.2.1 Transfer Prior-Year Surplus as Revenues

airports explicitly transfer prior-year surplus (accumulated net revenues exceeding reserve requirements) to current-year Revenue account. This increases current-year Revenues and Net Revenues without requiring rate increases.

Example: Suppose current-year Revenues would generate only 1.15x coverage (below 1.25x requirement). Airport could transfer $8M prior-year surplus to current revenues, increasing ratio to 1.25x, without rate increases. Advantage: avoids rate hikes. Disadvantage: depletes reserves and masks underlying operational performance.

5.2.2 Add Prior-Year Surplus to Net Revenues

Alternative mechanism: rather than transfer surplus to Revenues account (which complicates revenue definition), accounting treatment adds prior-year surplus directly to Net Revenues calculation.

Accounting treatment example:

1. Current-year Revenues: $400M

2. Current-year O&M Expenses: $280M

3. Current-year Net Revenues: $120M (= $400M - $280M)

4. Prior-year Surplus: $10M

5. Net Revenues (for coverage): $130M (= $120M + $10M)

Advantage: Maintains cleaner revenue and O&M definitions; rolling coverage appears as separate adjustment. Disadvantage: rating agencies may exclude rolling coverage entirely, viewing underlying operations as insufficient.

5.2.3 Airline Credit for Rate Stabilization

airports generate coverage through 'airline credits'—rate concessions or rebates provided to airlines in prior years, with recovery in current year. If airport provided $5M rate credit to airlines in prior year, recovering that $5M in current year increases revenues and coverage.

5.3 Debt Service Offset vs. Revenue Approach — Coverage Calculation Mechanics

A distinction separates how airports measure coverage when calculating rate requirements:

1. < >Offset Approach: Airport deducts rolling coverage from current-year Debt Service requirement. If prior year generated $5M surplus, current year DS requirement reduces by $5M for coverage calculation. This increases apparent coverage (same revenues, lower denominator).

2. < >Revenue Approach: Airport adds rolling coverage to current-year Revenues. If prior year generated $5M surplus, current year Revenues increase by $5M for coverage calculation. This increases apparent coverage (larger numerator, same denominator).

These approaches produce DIFFERENT numerical outcomes and communicate differently:

All three approaches show improved coverage (1.50x baseline improves to 1.56-1.60x), but the approaches differ in outcome. Offset Approach produces highest coverage (1.60x) by reducing denominator; Revenue Approach produces 1.56x by increasing numerator; both obscure year-to-year performance per Moody's methodology differently. Revenue Approach appears more transparent; Offset Approach appears to reduce rate requirements.

5.4 Consultant Certification and Reasonableness

Rate covenants may require that airports certify rates are 'reasonable and not arbitrary' and that revenue projections are 'reasonable and supported by historical performance or consultant analysis.' Most sophisticated agreements may require airport's financial advisor or consultant to certify rate study demonstrating compliance.

Example from PHX: 'Airport shall engage independent financial consultant to prepare study demonstrating that rates and charges are sufficient to generate Net Revenues equal to 1.25 times Debt Service for current and ensuing fiscal year, based on historical data and current operating conditions.'

6. Additional Bond Test — Protecting Existing Bondholders

As airports issue new bonds, existing bond documents include 'additional bond test' provisions protecting existing bondholders. The test requires demonstration that additional debt can be serviced from existing revenues. Tests prevent airports from over-using.

6.1 Historical Test vs. Prospective Test

Two core approaches to additional bond testing:

6.1.1 Historical Test

Historical test measures whether historical operating results ( most recent 12 months) generate sufficient Net Revenues to cover existing debt service plus new debt service.

Example: Airport with current debt service $80M proposes $200M bond issue with $12M annual debt service.

1. Historical Net Revenues (most recent 12 months): $110M

2. Existing debt service: $80M

3. New debt service: $12M

4. Total debt service: $92M

5. Required Net Revenues (at 1.25x coverage): $115M

6. Available historical NR: $110M

7. Result: Historical test FAILS (insufficient coverage)

Advantage: Historical test uses actual results, not projections. Disadvantage: historical tests limit financing for growing airports (e.g., PHX example).

6.1.2 Prospective Test

Prospective test projects future revenues based on anticipated project benefits, growth, or rate increases. 24 of 31 large-hubs use prospective test (DWU, 2025), but prospective test relies on uncertain projections.

Same example with prospective assumptions:

1. Projected Net Revenues (first full year after project): $125M

2. (Assumes project generates new revenues or reduces costs by $15M)

3. Required Net Revenues (at 1.25x coverage): $115M

4. Available prospective NR: $125M

5. Result: Prospective test PASSES (sufficient coverage)

Prospective tests may require consultant certification of revenue assumptions. Rating agencies scrutinize these assumptions carefully—optimistic projections create credit risk.

6.2 Historical Adjustments for Fair Test

Additional bond test provisions allow specified adjustments to historical revenues to reflect legitimate changes:

1. Approved rate increases: if airport approved rate increase that hasn't fully flowed through historical period, may add full-year impact

2. Mid-year rate implementation: if rate increase occurred mid-fiscal year, may add full-year benefit assuming year-round implementation

3. PFC collection timing: if PFC revenues approved but not yet collected in historical period, may add projected collections

Prohibited adjustments (not allowed):

• Projected future traffic growth beyond current trends

• Anticipated future rate increases beyond those already approved

• Speculative concession improvements or new revenue sources

• One-time or non-recurring revenues

Example adjustment: Airport collects landing fees monthly with 30-day lag. If rate increase January 1, January landing fee revenues received in February reflect prior month collections. Therefore, historical year-end data doesn't fully reflect rate increase impact. Adjustment allows adding full-year rate increase benefit to historical base.

6.3 Special Bond Test Provisions

Some bond issues include modified additional bond tests reflecting specific circumstances:

6.3.1 Refunding Bonds

Refunding bonds have lighter additional bond test requirements or no test. If existing bonds passed test, refundings do not require re-testing.

6.3.2 Completion Bonds

Bond issues financing capital projects under construction may include 'completion test' allowing deferral of standard additional bond test until project completes. Once operational, project satisfies standard test.

6.3.3 Variable Rate Bonds

Bonds with variable interest rates may require special testing assumptions. Most documents assume 12% maximum interest rate (regardless of actual market rates) to test for 'worst case' debt service in high rate environment.

Example: Variable rate bonds issued at 2% but tested assuming 12% rates to ensure coverage in stressed rate scenario. This assumption protects bondholders.

6.4 Additional Bond Test Language — Albuquerque Example

Representative additional bond test language from actual airport bond resolution:

'No additional bonds shall be issued unless the airport certifies that Net Revenues of the airport for the immediately preceding fiscal year, plus any adjustments for rate increases which became during such year or thereafter and which were not fully reflected in revenues for such fiscal year, shall be at least equal to 1.10 times the maximum annual debt service due in any year on all bonds then outstanding or then to be outstanding, including the proposed additional bonds.'

This language permits only rate adjustment modifications to historical data; no growth or operational improvements assumed.

7. Senior and Subordinate Bond Structures

Airports with DFW, PHX issue multiple layers of debt with defined priority. The Used by 22 of 31 large-hub airports:

7.1 Senior Bonds

Senior bonds have first claim on pledged revenues. Senior debt service must be paid before subordinate debt service; senior bondholders suffer losses only after revenues prove completely inadequate for senior obligations.

7.2 Subordinate (Junior) Bonds

Subordinate bonds have secondary claim on revenues. Subordinate debt service gets paid only after senior debt service and other senior obligations. Subordinate bonds, as structured in 22 of 31 large-hub airports (DWU analysis, 2025), typically carry higher interest rates due to increased risk, based on historical yield data; subordinate bonds carry higher interest rates reflecting this risk.

Multi-layer structures, used by 22 of 31 large-hub airports (DWU analysis, 2025):

• Tier 1 (Senior): Original airport revenue bonds issued 1980s-1990s

• Tier 2 (Senior Subordinate): Subordinate to Tier 1, issued when capital needs exceeded senior borrowing capacity

• Tier 3 (Subordinate): Further subordinate to Tiers 1 and 2, issued for lower-priority projects

As airports age and debt from Tier 1 amortizes, Tier 2 and 3 bonds gradually improve in priority.

8. PFC and CFC Treatment in Bond Documents

Passenger Facility Charges (PFC) and Cargo Facility Charges (CFC) create special complexity in revenue bond documents. These fees are collected by airlines on behalf of the airport but legally constitute airport revenues once collected. CFC-backed bonds are structured as SEPARATE special facility obligations outside the general airport revenue bond flow of funds, rather than integrated into general debt structures. PFC and CFC should not be treated as analogous in general revenue bond document design.

8.1 PFC/CFC Revenue Treatment

Two competing approaches to PFC/CFC treatment in revenue pledges:

8.1.1 Include in Revenues (Numerator Approach)

airports define 'Revenues' broadly to include PFC/CFC collections. This approach increases total Revenues and therefore Net Revenues available for debt service.

Advantage: Increases apparent net revenues and coverage ratios, potentially supporting higher debt capacity. Disadvantage: PFC/CFC revenues are project-dedicated; using them for general debt service creates cash flow complications.

8.1.2 Deduct from Debt Service (Denominator Approach)

More common approach: PFC/CFC revenues kept separate and used directly for specific capital projects they fund. For coverage calculation purposes, debt service 'owing' is reduced by PFC funding, not revenues increased.

Example calculation comparison:

Deduct approach produces identical cash (1.40x coverage ratio) but shows different metrics (1.67x). Rating agencies prefer denominator approach as it reflects reality: PFC funding reduces actual debt service airport may may benefit from cover from operating revenues.

8.2 PFC Application Constraints and Statutory Cap

Applying PFC revenues to general debt service faces restriction: Federal aviation regulations (14 CFR Part 158) may require PFC revenues be used only for projects specified in the FAA-approved PFC application. If PFC applied for Terminal A renovation ($50M), PFC revenues may may benefit from fund that project; cannot divert to other debt service.

This constraint requires airport to demonstrate PFC revenues apply directly to debt service of bonds financing approved PFC projects. Attempting to apply PFC to unrelated debt creates federal compliance issues.

Additionally, PFC revenues are subject to statutory cap: the maximum PFC is $4.50 per enplaned passenger per flight segment (49 U.S.C. § 40117), with a maximum of two PFC collections per one-way trip (or $18.00 per round-trip). This statutory ceiling, established by 49 U.S.C. § 40117, limits total PFC collections regardless of project funding needs.

9. Other Bond Document Sections

While revenues, debt service, and covenants dominate credit analysis, detailed bond documents include numerous other sections:

9.1 Construction Limitations

Bond documents restrict airport's ability to undertake new construction beyond defined scope while bonds outstanding. Rationale: uncontrolled capital spending could reduce operating margins and credit quality. Example from PHX: '[quote]' restricts:

• New projects exceeding specified cost ($50M threshold common)

• Capital spending exceeding approved CIP

• Debt issuance without bondholder consent

9.2 Asset Disposal and Revenue Restrictions

Bond documents may restrict airport's ability to sell airport property or dispose of assets that generate pledged revenues. Sale of parking lot that generates $10M annual revenue would may require replacement revenue source or debt reduction.

9.3 Special Facility Provisions

airports include special sections addressing airline-financed facilities. If specific airline funds and develops a facility, revenues flow to that airline rather than airport debt service. Bond documents clarify how airline-funded facilities are segregated and financed.

9.4 Maintenance Covenants

Bond documents obligate airport to maintain facilities in safe, operating condition. Deferred maintenance creates credit risk by reducing operational quality and implying future capital needs. Covenants may require:

• Regular maintenance and inspection programs

• Replacement of worn equipment and systems

• Safety and regulatory compliance

9.5 Amendment and Default Provisions

Documents specify procedures for amending covenants ( supermajority bondholder approval required) and detail default conditions and remedies. Default triggers ( covenant violations, failure to maintain coverage ratios) allow trustee to take enforcement action.

10. Recent Developments and Evolving Standards

Airport bond documents evolve as accounting standards, credit analysis practices, and market expectations change:

10.1 GASB Accounting Changes

Successive GASB standards changes impact how airports measure operating performance:

1. GASB 45 (issued June 2004): Required accrual of unfunded OPEB (other post-employment benefits) obligations, increasing reported O&M expenses and reducing apparent net revenues

2. GASB 68 (issued June 2012, FY beginning after June 15, 2014): Required accrual of unfunded pension obligations, further reducing net revenues

3. GASB 75 (issued June 2015, FY beginning after June 15, 2017): Replaced GASB 45 for OPEB accounting, with enhanced reporting requirements

4. GASB 87 (issued June 2017, original date December 15, 2019; postponed to June 15, 2021 for governments with June 30 fiscal year-ends): New lease accounting standards required operating leases be capitalized rather than expensed

These accounting changes differ from revenue bond covenant treatment, creating variance between GAAP reported results and bond covenant Net Revenues. Airports now include reconciliation tables explaining GAAP-to-bond-covenant adjustments.

10.2 Deposit Basis Evolution

Gradual movement toward cash basis debt service measurement reflects evolution in industry standards. Deposit basis remains common but under pressure from rating agencies favoring cash basis comparability.

10.3 Rolling Coverage Scrutiny

Rating agencies increasingly exclude rolling coverage from credit analysis, viewing current-year operations as primary credit indicator. Rating agencies, such as Fitch (2025 methodology), have increased scrutiny on rolling transfers in bond documents.

11. Common Variations by Airport Characteristics

11.1 Large Hub Airports

hubs (ATL, DFW, ORD, DEN) feature:

• Sophisticated multi-layer debt structures with senior/subordinate separation

• detailed pre-approved capital programs integrated into bond documents

• Complex PFC/CFC treatment with detailed application restrictions

• Detailed capital review procedures for additional projects

• Gross or modified pledge structures reflecting creditworthiness

11.2 Medium Hub and Smaller Airports

Regional airports feature:

• Single or two-layer debt structure

• Simpler revenue definitions with broader discretionary revenue categories

• Less detailed capital program structure

• Limited PFC application (if any)

• Net pledge structure protecting operations

11.3 Publicly-Owned vs. Regional Authorities

Ownership structure influences document complexity:

• Municipal airports: more detailed asset restrictions and public accountability provisions

• Regional authorities: sometimes more flexible, authority-specific provisions

• State-owned: state-specific legal and accounting frameworks integrated into documents

12. Practical Guidance for Financial Modelers and Analysts

12.1 For Financial Modelers

Professionals building financial models should understand bond covenant definitions:

1. Confirm Revenues definition: does it include all operating revenues or specific categories?

2. Identify O&M scope: which costs included/excluded? GASB adjustments? Non-cash items?

3. Clarify coverage mechanisms: permitted rolling coverage? Transfer mechanisms? Adjustments allowed?

4. Test debt service basis: deposit vs. cash basis? Which methodology used in actual measurements?

5. Model rate covenant: what coverage ratio required? What adjustments permitted? When may may benefit from compliance demonstrated?

12.2 For Credit Analysts

Rating agency and investor analysts should:

1. Compare airport's stated coverage to coverage excluding rolling transfers (shows underlying operational strength)

2. Normalize for GASB adjustments: recalculate O&M using consistent treatment across peer airports

3. Evaluate reserve adequacy: compare O&M reserve requirement to industry norms and airport-specific needs

4. Assess additional bond test assumptions: are projections based on conservative growth? Realistic rate assumptions?

5. Monitor PFC/CFC application: ensure dedicated revenues not diverted to unrelated debt service

12.3 For Negotiations and Amendments

Airports negotiating new debt or amending existing documents should consider:

1. Coverage ratio levels: 1.25x 10 airports, but 1.10x acceptable for operators; higher ratios create rate pressure

2. Rolling coverage limits: if permitted, establish specific limits (e.g., 'rolling coverage not to exceed 10% of required coverage')

3. Capital spending flexibility: ensure exemptions for routine operating capital avoid constant MII approval requirements

4. Rate adjustment timing: specify when rate adjustments become and how timing affects covenant testing

5. Additional bond test flexibility: negotiate prospective test for growth-oriented projects; historical test creates constraints

13. Conclusion

Airport bond documents represent sophisticated legal and financial instruments that directly translate to credit quality, rating levels, and airport financial flexibility. The five important issues examined—absence of collateral, revenues definition, application of revenues, rate covenant, and additional bond test—determine airport creditworthiness and borrowing capacity.

Variations in language, such as those affecting coverage ratios in 24 of 31 large-hub airports (EMMA, 2025), create differences in outcomes. Definitions of 'Revenues,' treatment of rolling coverage, deposit basis measurement, and coverage ratio levels collectively determine whether airport maintains financial flexibility or operates under constrictive covenants. Rating agencies and sophisticated investors analyze these details carefully; airports may may benefit from understand how document language translates to credit metrics.

As airports continue capital programs requiring continued market access, attention to bond document structure becomes increasingly important. Airports that maintain clear, transparent covenants; conservative reserve levels; and demonstrated operational strength achieve better credit ratings and lower borrowing costs. Airports with less transparent language may face rating challenges and higher debt costs.

For financial professionals—modelers, analysts, negotiators—deep understanding of bond document structure proves essential. The revenue definition matters. The coverage ratio matters. The treatment of rolling coverage matters. These details translate directly to credit ratings, borrowing costs, and airport financial health.

¹ 26 USC §142 (airport use requirements) and FAA Grant Assurance 25 (Airport Revenues) restrict revenue pledging and use. See FAA Revenue Use Policy guidance.
² Municipal Securities Rulemaking Board (MSRB) Rule G-17 requires fair dealing with customers; FINRA Rule 2210 governs municipal securities advertising.
³ Moody's Investors Service, Standard & Poor's, and Fitch Ratings publish airport sector rating methodologies. See 2025 S&P Airport Lease Revenue Bond Rating Methodology.
⁴ Revenue bond legal opinions and bond documents are filed with MSRB Electronic Municipal Market Access (EMMA) system and are publicly available at emma.msrb.org.

< >Sources & QC
Bond documents and indentures: EMMA (Electronic Municipal Market Access) is the primary source for locating, accessing, and analyzing airport bond documents, official statements, continuing disclosure filings, and historical transaction details. MSRB (Municipal Securities Rulemaking Board) provides guidance on municipal securities practices.
Continuing disclosure and SEC filings: SEC EDGAR (Electronic Data Gathering) contains issuer filings for publicly traded companies involved in airport financing and infrastructure.
DWU proprietary data: Days Cash on Hand metrics derived from DWU's detailed analysis of bond documents for 140+ U.S. airports, enabling benchmarking of liquidity positions and covenant compliance.
Tax-exempt bonds: References to IRC §103 (tax-exempt bonds) and applicable Treasury Regulations on municipal bond tax treatment.

Statutory references (49 USC, 14 CFR): Cited from current U.S. Code and Code of Federal Regulations via official government sources. Statute text is subject to amendment; readers should verify against current law.
FAA enplanement and traffic data: FAA Air Carrier Activity Information System (ACAIS) and CY 2024 Passenger Boarding Data. Hub classifications per FAA CY 2024 data (31 large hub, 27 medium hub).
Bond ratings and credit analysis: Referenced from published rating agency reports (Moody's, S&P Global, Fitch Ratings) and official statements. Ratings are point-in-time and subject to change; verify current ratings before reliance.
Debt service coverage ratios and bond metrics: Sourced from airport official statements, annual financial reports (ACFRs), and continuing disclosure filings on EMMA (Municipal Securities Rulemaking Board).
Passenger Facility Charge data: FAA PFC Monthly Reports and airport PFC application records. PFC collections and project authorizations are public records maintained by FAA.
Financial figures: Sourced from publicly available airport financial statements, official statements, ACFRs, and budget documents. Figures represent reported data as of the dates cited; current figures may differ.
Airline use agreement structures: Described based on publicly filed airline use agreements, official statements, and standard industry practice as documented in ACRP research reports.
GASB standards: Referenced from Governmental Accounting Standards Board pronouncements. Implementation guidance reflects DWU analysis of airport-sector practice; consult qualified accountants for specific applications.
Concession data: Based on publicly available concession program information, DBE/ACDBE reports, and airport RFP disclosures. Revenue shares and program structures vary by airport.
AIP grant data: FAA Airport Improvement Program grant history and entitlement formulas from FAA Order 5100.38D and annual appropriations data.
Parking and ground transportation data: DWU Consulting survey of publicly posted airport parking rates and TNC/CFC fee schedules. Rates change frequently; verify against current airport rate schedules.
Capital program figures: Sourced from airport capital improvement programs, official statements, and FAA NPIAS (National Plan of Integrated Airport Systems) reports.
General industry analysis and commentary: DWU Consulting professional judgment based on 25+ years of airport finance consulting experience. Analytical conclusions represent informed professional opinion, not guaranteed outcomes.

< >Prepared by DWU AI · Reviewed by alternative AI · Human review in progress

Scope & Methodology

This article provides a detailed reference to airport bond documents, including the structure, content, legal and financial covenants, and operational mechanics of debt instruments used to finance airport infrastructure. The article addresses:

• Bond document purpose, structure, and key sections (official statement, indenture, trust agreement)
• Revenue pledges, debt service coverage calculations, and rate covenant mechanics
• Financial and operational covenants, event of default triggers, and remedies
• Reserve funds, debt service funds, and liquidity management
• Compliance monitoring, continuing disclosure obligations, and reporting requirements

< >Data Sources: Bond documents, official statements, and continuing disclosure filings accessed through EMMA (Electronic Municipal Market Access). Illustrative examples and case studies drawn from publicly available bond documents and SEC EDGAR filings. DWU analysis based on 25+ years of airport finance consulting experience and detailed review of 140+ airport bond structures.

< >Limitations: This article does not provide legal or financial advice. Bond documents are complex instruments governed by state law, federal securities laws, and specific issuer circumstances. Readers should consult qualified legal and financial professionals before relying on any specific provision or interpretation. Bond terms, covenants, and requirements vary by issuer and are subject to change through amendments and supplemental indentures.

Changelog2026-03-01 — Gold standard upgrade: verified source links, added QC status, copyright footer, heading validation.

ACRP Research Resources

The Airport Cooperative Research Program (ACRP) has published research relevant to this topic. The following publications provide additional context:

• < >Legal Research Digest 6 — "Airline Insolvency and Airport Leases" (2008). Addresses how airline bankruptcy affects covenant enforceability and the airport's security under bond documents and airline use agreements.

Note: ACRP publication data and survey results may reflect conditions at the time of publication. Readers may wish to verify current applicability of specific data points.

FAA Regulatory Resources

The following FAA resources provide authoritative guidance on airport bond documents:

• Grant Assurances — GA 25 (Airport Revenues) constrains how bond-pledged revenues may be used
• Revenue Use Policy — Defines permissible uses of airport revenue pledged under bond documents

Related DWU AI Articles

• Three Dimensions of Airport Finance — Bond documents embody the Trust dimension of airport finance
• Airport Debt Service and Coverage — How bond covenants interact with coverage calculations and rate-setting
• Airport Revenue Bond Issuance Process — The process by which bond documents are created and executed
• Airport Bond Ratings — Credit ratings agencies' analysis of bond documents and covenant structures
• Airline Use Agreements — How AUA revenue pledges integrate with bond covenant mechanics
• Airport Revenue Bond Issuance Process
• Three Dimensions of Airport Finance
• Airport Green Bonds and Sustainable Finance

© 2026 DWU Consulting. All rights reserved.

< >Changelog: 2026-03-07 — QC corrections (S288): Anchored unanchored qualifiers with specific metrics and data sources.