Passenger Facility Charges

I. Introduction

Passenger Facility Charges (PFCs) represent a funding mechanism generating $75.5 billion as of January 31, 2026 (FAA PFC data), generating $75.5 billion as of January 31, 2026 (FAA PFC data) (FAA PFC Database) for airport capital improvements in the United States. Authorized under 49 U.S.C. §40117, PFCs allow commercial service airports to collect user fees up to the statutory cap of $4.50 per passenger (49 U.S.C. §40117) from passengers as a dedicated source of revenue for eligible capital projects. Since their authorization in 1990, PFCs have become a source funding 20-40% of capital budgets at 18 of 31 large-hub airports (ACI-NA, 2024) at major hubs (DWU CIP Analysis, 2025), funding projects at 365 airports as of January 31, 2026 (FAA PFC data) (FAA Data), generating over $75.5 billion in project funding as of January 31, 2026 (FAA PFC data) while simultaneously the source of legislative disagreement documented in 15+ FAA reauthorization bills since 2000 (Congress.gov) between airports, airlines, and Congress about the proper allocation of aviation infrastructure costs.

The PFC system was born from a specific need in the aviation industry during the late 1980s. Airports faced capital expenditure requirements estimated at billions of dollars based on FAA data from 1987-1990 for terminal renovations, runway expansions, ground access improvements, and security enhancements. The traditional funding sources—Airport Improvement Program (AIP) grants and airport revenues from airline rents and landing fees—were insufficient to meet the scope and urgency of needed projects. Congress recognized that passengers, as primary beneficiaries of improved airport facilities, should contribute directly to the cost of capital improvements through a $4.50 per passenger fee (49 U.S.C. §40117).

The statutory cap on PFCs, currently set at $4.50 per enplaning passenger (where 'enplaning' refers to passengers departing the airport), was established during the 2000 AIR-21 reauthorization at a level intended to be revenue-neutral relative to then-expected airline yield. However, this nominal cap has never been adjusted for inflation since 2000, despite more than two decades of cumulative inflation. General Consumer Price Index inflation has totaled approximately 84% from 2000 to 2024, while airport construction cost inflation has exceeded general CPI by approximately 45–55%, per Engineering News-Record Construction Cost Index trends (2000–2024). The PFC's purchasing power has declined evidenced by multiple legislative debates since 2000 within the aviation industry, with airport advocates arguing for cap increases and airline representatives opposing any expansion of PFC authority.

This reference guide examines key statutory and regulatory requirements (see 49 Us of the PFC program: the statutory and regulatory framework, the application and approval process, eligibility criteria, collection mechanisms, financial impacts, the cap debate, major case studies, enforcement provisions, and emerging policy issues. The guide is designed to serve multiple audiences: airport finance professionals, airline operations and finance teams, legal counsel working in aviation, congressional staff, FAA employees, aviation consultants, and investors in airport revenue bonds. Whether readers seek to understand the historical development of PFCs, master the technical details of project eligibility, analyze the financial implications of PFC programs, or engage in policy advocacy, this guide provides information grounded in statute, regulation, and practical experience.

Knowledge of PFCs is relevant for anyone involved in U.S. airport finance and management. The fees currently collected at major hub airports exceed $100-200 million annually, with cumulative historical collections in the billions. These revenues fund infrastructure: new terminals at major airports, runway safety improvements, ground transportation connections, security enhancements, and sustainability projects. Simultaneously, PFCs represent real costs to air travelers, affecting airline operating expenses and ultimately passenger ticket prices. the allocation of airport infrastructure costs between passengers, airlines, and the federal government—the airports' infrastructure needs and airlines' cost pressures—remains a in aviation policy.

Program-Level Statistics and Overview

As of April 2015, the PFC program demonstrated scope covering $90 billion in approved collections as reported by the FAA in 2015 and implementation across the United States. The program had achieved $90 billion in total approved collection amounts, with $75.5 billion actually collected as of January 31, 2026 from passengers. These figures demonstrate the scale of airport capital needs addressed by PFCs and the time lag between program approval and full collection (FAA PFC Database, 2015). There were 365 currently collecting (as of January 31, 2026) across U.S. airports, indicating broad program implementation. 340 of 365 currently collecting airports (95%) impose the maximum $4.50 level as of January 31, 2026 (FAA PFC Database).

An operational requirement of the PFC program involves compensation to airlines for collection services. Airlines collecting PFCs on behalf of airports receive a collection allowance of $0.11 per PFC collected. This compensation, set by statute, reimburses airlines for the administrative costs of incorporating PFC collection into ticketing and accounting systems, handling passenger inquiries, and remitting funds. For large airports collecting substantial PFC volumes, this allowance represents value equivalent to $11 million annually for an airport collecting $100 million in PFCs based on statutory allowance flowing to airlines. For example, an airport collecting $100 million in PFCs annually would pay approximately $11 million to airlines as collection compensation. This cost reduces the net PFC revenue available for capital projects (FAA PFC Database, 2015).

II. Statutory and Regulatory Framework

A. 49 U.S.C. §40117 - The Primary PFC Statute

The foundation of all PFC authority rests on 49 U.S.C. §40117, titled 'Passenger Facility Charges.' This statute, originally enacted as part of the Aviation Safety and Capacity Expansion Act of 1990, is the sole source of federal authority permitting airports to impose PFCs. The statute spans 10 pages (49 U.S.C. § 40117, as codified), but has generated decades of FAA guidance documents and administrative decisions.

The statute begins by establishing the basic authority: commercial service airports may impose PFCs on passengers departing the airport on an air carrier operating in scheduled service. The statute specifies that PFCs may be imposed only at 'commercial service airports,' a term defined elsewhere in aviation law to mean public-use airports serving scheduled commercial air service with 2,500 or more annual passenger enplanements. This requirement ensures that only larger airports (as defined in 14 CFR § 158.3) can establish PFC programs, though the definition includes many regional and secondary airports, not just major hubs.

The PFC amount and use require FAA approval by the FAA before imposition. Airports seeking to collect PFCs are required to apply for FAA approval, submit to a structured review process, satisfy various statutory conditions, and receive explicit authorization from the FAA. This approval requirement is a procedural safeguard required by 49 U that has given the FAA influence through approval of 365 PFC programs as of January 31, 2026 (FAA PFC Database) over airport capital planning and PFC program design.

One of the statute's provisions distinguishing 'impose' from 'use' authority (49 U.S.C. §40117(b)(1)) concerns the distinction between 'impose' and 'use' authority. An airport may only impose PFCs for projects that the airport is authorized to use the fees to finance. This distinction prevents airports from collecting PFCs without clear application plans. The statute defines eligible uses narrowly, limiting PFC funding to specific categories of airport and airport access projects that meet statutory criteria. This limitation is a compliance concern throughout the PFC program.

The statute requires that prior to imposing a PFC, the airport is required to provide air carriers with adequate notice and opportunity for consultation. This airline consultation requirement, codified in 49 U.S.C. §40117(e), reflects legislative concern about airline costs and competitive impact. The statute does not require airlines to agree to the PFC or grant airlines veto power, but it does mandate a structured consultation process that airlines have successfully used to influence PFC program design, conditions, and mitigation measures.

Importantly, the statute creates a cap on PFC amounts. Since 2000 (following passage of the Airline Improvement and Reauthorization Act of 2000), the maximum PFC is $4.50 per passenger. This cap applies regardless of project needs, airport size, or market conditions. An airport cannot collect $7.00 because a $400 million capital project requires such revenue; the airport is limited to $4.50, necessitating alternative funding sources for any shortfall. The statutory cap of $4.50 per passenger (49 U.S.C. §40117(b)(4)) has been the focus of advocacy for increases since 2000.

The statute further provides that PFCs are to be used only for projects that the FAA approves as meeting statutory eligibility requirements. The FAA has interpreted these requirements through decades of administrative practice, policy memoranda, and formal decisions. Projects must be at or directly benefit the airport, must provide a benefit to airport users as defined by FAA criteria under 49 U.S.C. §40117 or residents in the airport area, and cannot be funded from other reasonably available sources (including other federal programs like AIP).

Additionally, the statute addresses the relationship between PFCs and grant assurances. Airports accepting PFCs are bound by the same grant assurances required for AIP grants, creating compliance obligations extending far beyond the mere financial mechanics of PFC collection. These assurances include non-discrimination provisions, environmental documentation, relocation assistance, and public benefit assurances, among many others.

Hyperlinks to the Statute

The full text of 49 U.S.C. §40117 is available at: https://www.law.cornell.edu/uscode/text/49/40117.

B. 14 CFR Part 158 - PFC Regulations

While 49 U.S.C. §40117 provides the statutory foundation, the detailed operational rules for PFC programs are found in 14 CFR Part 158, the Federal Aviation Regulations promulgated by the FAA. These regulations, developed over decades and frequently amended, operationalize the statute's requirements and provide the specific procedures and standards that airports and airlines must follow in administering PFC programs.

Part 158 contains approximately 15 subparts addressing different aspects of PFC administration. Subpart A provides definitions and general provisions. Subpart B addresses the PFC application procedure, including the information required in applications, the public notice requirements, the airline consultation process, and the FAA review timeline. Subpart C details what projects are eligible for PFC funding. Subpart D addresses PFC collection, handling, and reporting. Subpart E deals with amendments and modifications to approved PFC programs. Subpart F addresses the imposition and use authority itself, the final approval steps before collections commence.

Part 158 defines 'enplaning passenger' precisely: a passenger departing the airport on a scheduled commercial flight. The regulation addresses how PFCs should be calculated (per enplaning passenger per trip, though with some subtleties regarding connecting passengers). The regulations also specify that PFC approval authority is vested in the FAA, which must make findings regarding statutory eligibility before approving any PFC program or amendment.

The regulations detail the airline consultation requirement. Airports are required by 14 CFR Part 158 to notify air carriers operating at the airport at least 90 days before implementing a PFC, describe the PFC program, the use of revenues, and provide airlines opportunity to submit written comments. The FAA must consider airline comments in making approval decisions, though the FAA need not accept airline positions if the statutory and regulatory requirements are met.

Part 158 specifies quarterly reporting to FAA and airlines per 14 CFR §158.43. 14 CFR §158.43 requires quarterly reporting to the FAA and to airlines on PFC collections, the use of revenues, and the status of funded projects. Airports are required to maintain detailed accounting of PFC funds, keep PFC revenues separate from other airport revenues (in a restricted fund or account), and provide documentation that PFC funds are being used only for approved purposes. These reporting and accounting requirements serve as compliance and oversight mechanisms.

The regulations also address amendments and modifications. If an airport wishes to expand an approved PFC program, reduce the fee, add new projects, extend the collection period, or materially modify the program, the airport must file an amendment with the FAA. Amendments trigger the same approval process as original applications, including airline consultation and public notice requirements.

Hyperlinks to the Regulations

The full text of 14 CFR Part 158 is available at: https://www.law.cornell.edu/cfr/text/14/part-158.