Order 5500.1 Passenger Facility Charge
ORDER 5500.1
PASSENGER FACILITY CHARGE
August 9, 2001
DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
Note: Portions of this Order are under review for update, particularly with respect to nonhub primary airports. Please contact the appropriate Regional Office or Airports District Office for assistance.
Distribution: ZRP-510; A-FAS-1 (Ltd) Initiated By: APP-530
Record of Changes
RECORD OF CHANGES 5500.1
CHANGE SUPPLEMENTS OPTIONAL CHANGE SUPPLEMENTS OPTIONAL TO BASIC
TO BASIC
FOREWORD
This order provides guidance and procedures to be used by FAA personnel in the administration of the Passenger Facility Charge (PFC) Program. The guidance and procedures reflect established FAA practices that have successfully met the statutory and regulatory requirements of the PFC Program. The guidance and procedures are current as of the date of issuance of this order, and incorporate all changes to the PFC Program introduced by the "Wendell H. Ford Aviation Investment and Reform Act for the 21st Century’’ (AIR 21), as well as prior legislation.
Foreword
This order references several other FAA orders and advisory circulars. The references are made using the latest publication numbers for such documents as of the date of issuance of this order. However, in cases where a referenced document is updated following the issuance of this order, the latest official release of the document should be used as the reference.
Original signed by
Catherine M. Lang Director of Airport
Planning and Programming
i (and ii)
Table of Contents
TABLE OF CONTENTS
CHAPTER 1. INTRODUCTION … 1
SECTION 1. GENERAL … 1
1-1. Overview … 1 1-2. Distribution … 1 1-3. Authorizing Legislation … 1 1-4. Policy and Guidance Principles … 1 1-5. Order Format … 1 1-6. Definitions … 3 1-7 to 1-10. Reserved … 8 SECTION 2. TITLE 49, UNITED STATES CODE … 8
1-11. PFC Authority-Section 40117 … 8 1-12. Reduction in AIP Apportionments-Section 47114(f) … 10 1-13. Use of Funds Recovered Under Section 47114(f) … 11 1-14 to 1-15. Reserved … 11 SECTION 3. DELEGATION OF AUTHORITY … 11
1-16. Overview … 11 1-17. Delegation of Limited Authority to FAA Airports Offices … 11 1-18 to 1-20. Reserved … 12 SECTION 4. OVERVIEW OF THE PFC PROCESS … 12
1-21. The PFC Process … 12 1-22. PFC Program and Its Relationship to AIP … 12 1-23 to 1-25. Reserved … 13 SECTION 5. REDUCTION IN AIP APPORTIONMENTS … 13
1-26. Apportionment Reduction for Collection Levels of $3 or Below … 13 1-27. Apportionment Reduction for Collection Levels Above $3 … 13 1-28. Implementation of Apportionment Reduction … 14 1-29. Adjustments to Apportionment Reduction … 14 1-30 to 1-35. Reserved … 14
CHAPTER 2. ADVANCE COORDINATION … 21
SECTION 1. BACKGROUND … 21
2-1. Overview … 21 2-2 to 2-5. Reserved … 21 SECTION 2. OPTIONAL APPLICATION FORMULATION MEETING … 21
2-6. Overview … 21 2-7. Project Description, Eligibility, Objectives, and Justification … 22 2-8. Project Cost and Funding Strategies … 22 2-9. Project Schedules and Environmental, Airspace, and ALP Requirements … 23 2-10. Alternative Projects (for impose-only projects) … 23 2-11. Preparation for and Timing of Carrier Consultation … 23 2-12. Application Forms … 24 2-13. Public Agency PFC Assurances … 24
iii
2-14. Exemption of a Class or Classes of Carriers … 25 2-15. Additional Requirements for Imposing a PFC Level Above $3 … 25 2-16. Identification of Additional Information … 25 2-17 to 2-20. Reserved … 26 SECTION 3. CONSULTATION MEETING … 26
2-21. Requirement to Consult … 26 2-22. Content of Notice to Carriers … 26 2-23. Carrier Written Acknowledgment … 27 2-24. Consultation Meeting … 27 2-25. Carrier Written Certification of Agreement or Disagreement … 28 2-26. Carrier Failure to Provide Written Acknowledgment or Certification … 28 of Agreement/Disagreement 2-27. Summary of Meeting … 28 2-28. Changes by Public Agency after the Consultation … 29 2-29 to 2-35. Reserved … 29 SECTION 4. DRAFT PFC APPLICATION REVIEW … 29
2-36. Overview … 29 2-37 to 2-40. Reserved … 30
CHAPTER 3. APPLICATION SUBMITTAL … 35
SECTION 1. GENERAL … 35
3-1. Overview … 35 3-2. Flow Chart of Approval/Disapproval Process … 35 3-3 to 3-5. Reserved … 35 SECTION 2. PROCEDURES FOR SUBMITTAL … 35
3-6. Form … 35 3-7. Timing of Submission … 35 3-8. Application File … 37 3-9 to 3-15. Reserved … 38 SECTION 3. APPLICATION COMPLETENESS REVIEW … 38
3-16. Overview … 38 3-17. Receipt of Application … 39 3-18. Determination of Completeness … 39 3-19. Processing of Application Supplement … 42 3-20. Public Agency Coordination … 42 3-21 to 3-25. Reserved … 42
CHAPTER 4. PROJECT AND APPLICATION REVIEW … 49
SECTION 1. GENERAL … 49
4-1. Overview … 49 4-2. Application Evaluation … 49 4-3 to 4-5. Reserved … 50 SECTION 2. EVALUATION CRITERIA … 50
4-6. Project Eligibility … 50 4-7. Project Objective … 55 4-8. Project Justification … 56 4-9. Amount and Duration of PFC … 61 4-10. Collection Process … 62 4-11. Exclusion of Class or Classes of Carriers … 63 4-12. Compliance with the ANCA … 65 4-13. Compliance with Airport Revenue Use Requirements … 66 4-14. Alternative Uses … 66 4-15. Consultation Procedures … 67
iv
4-16. Air Carrier Consultation Comments … 68 4-17. ALP/Airspace/NEPA Requirements … 69 4-18. Schedule for Project Implementation … 69 4-19. Financial Viability … 70 4-20 to 4-25. Reserved … 71
CHAPTER 5. APPROVAL/DISAPPROVAL OF APPLICATIONS … 75
SECTION 1. GENERAL … 75
5-1. Overview … 75 5-2 to 5-5. Reserved … 75 SECTION 2. DECISIONMAKING AUTHORITY … 75
5-6. Determining Delegation of Record of Decision … 75 5-7 to 5-10. Reserved … 77 SECTION 3. ROD PREPARATION PROCESS … 77
5-11. Application Approval/Disapproval Documentation … 77 5-12. ROD Language to Address Exceptional Circumstances … 77 5-13. Treatment of Federal Register Comments in ROD’s … 80 5-14. Notification of Approval/Disapproval … 82 5-15 to 5-20. Reserved … 82
CHAPTER 6. COLLECTION, HANDLING, AND REMITTANCE OF PFC'S … 87
SECTION 1. GENERAL … 87
6-1. Overview … 87 SECTION 2. PUBLIC AGENCY COLLECTION ISSUES … 87
6-2. Public Agency Notification to Carriers … 87 6-3. Public Agency Notification to Excluded Carriers … 88 6-4. Beginning Collection … 88 6-5. Adjustments to the Duration of Collection … 88 6-6. Expiration of Collection … 89 6-7 to 6-10. Reserved … 89 SECTION 3. COLLECTION ON TICKETS ISSUED IN THE UNITED STATES … 90
6-11. Collection of PFC’s … 90 6-12. Information Required on Tickets … 90 6-13. Adjustments … 90 6-14. Essential Air Service (EAS) … 91 6-15. Frequent Flyer Awards … 91 6-16. Exemptions for Certain Flights in Hawaii and Alaska … 92 6-17 to 6-20. Reserved … 92 SECTION 4. COLLECTION OF PFC’S ON TICKETS ISSUED OUTSIDE THE UNITED STATES … 92
6-21. Regulatory Options for Collecting PFC’s … 92 6-22. No Air Service to United States … 92 6-23. Collection for the Gateway Airport … 92 6-24. Collection at Ticket Issuance … 93 6-25. Collection at Time of Enplanement … 93 6-26. Handling of PFC … 93 6-27 to 6-30. Reserved … 93 SECTION 5. AIR CARRIER ACCOUNTING AND HANDLING OF PFC REVENUE COLLECTED … 94
6-31. Overview … 94 6-32. Air Carrier Remittance of PFC Revenue Collected … 94 6-33. Property Interests … 94 6-34. Collection Compensation … 95 6-35 to 6-40. Reserved … 95
v
CHAPTER 7. REPORTING, RECORDKEEPING, AND AUDITS … 99
SECTION 1. BACKGROUND … 99
7-1. Overview … 99 7-2 to 7-5. Reserved … 99 SECTION 2. PUBLIC AGENCY REPORTING REQUIREMENTS … 99
7-6. Quarterly Report … 99 7-7. Large/Medium Hub Airport Yearly Report … 100 7-8. Annual Collections Report … 100 7-9 to 7-10. Reserved … 100 SECTION 3. AIR CARRIER REPORTING REQUIREMENTS … 101
7-11. Quarterly Report … 101 7-12 to 7-15. Reserved … 101 SECTION 4. RECORDKEEPING AND AUDITING—PUBLIC AGENCY … 101
7-16. Account … 101 7-17. Accounting Record … 101 7-18. Audit … 102 7-19. Acceptable Level of Assurance … 102 7-20. FAA Review of Public Agency Audits … 103 7-21 to 7-25. Reserved … 103 SECTION 5. RECORDKEEPING AND AUDIT—AIR CARRIERS … 103
7-26. Account … 103 7-27. Audit … 103 7-28. Acceptable Level of Assurance … 104 7-29. Review of Air Carrier Audits … 104 7-30 to 7-35. Reserved … 104 SECTION 6. FEDERAL OVERSIGHT … 104
7-36. Public Agency … 104 7-37. Carriers … 105 7-38. Access to Documentation … 105 7-39 to 7-45. Reserved … 105
CHAPTER 8. APPLICATION OVERSIGHT … 109
SECTION 1. GENERAL … 109
8-1. Overview … 109 8-2 to 8-5. Reserved … 109 SECTION 2. DURATION OF AUTHORITY TO IMPOSE PFC’S BEFORE PROJECT IMPLEMENTATION … 109
8-6. Timing … 109 8-7. Reserved … 111 8-8. Notification of Carriers … 111 8-9. Restriction on Authorization to Re-Impose a PFC … 111 8-10 to 8-20. Reserved … 111 SECTION 3. DURATION OF AUTHORITY TO IMPOSE A PFC AFTER PROJECT IMPLEMENTATION … 111
8-21. Overview … 111 8-22 to 8-30. Reserved … 112 SECTION 4. EXCESS PFC REVENUE … 112
8-31. Overview … 112 8-32. FAA Monitoring of Project Costs … 112 8-33 to 8-34. Reserved … 113 8-35. Excess PFC Revenue Plan … 113 8-36 to 8-40. Reserved … 114
vi
CHAPTER 9. EXTENSIONS … 119
SECTION 1. GENERAL … 119
9-1. Overview … 119 9-2 to 9-5. Reserved … 119 SECTION 2. NOTICE … 119
9-6. Public Notice … 119 9-7 to 9-10. Reserved … 119 SECTION 3. REQUEST FOR EXTENSION … 119
9-11. Request … 119 9-12. Description of Progress … 119 9-13. Schedule … 120 9-14. Explanation for Delay … 120 9-15. Summary Financial Report … 120 9-16. Carrier Consultation … 120 9-17. Local Notice Comments … 120 9-18. Confirmation/Validation of Alternative Projects … 120 9-19 to 9-20. Reserved … 120 SECTION 4. REVIEW AND APPROVAL/DISAPPROVAL … 120
9-21. Review … 120 9-22. Approval/Disapproval … 121 9-23 to 9-30. Reserved … 122
CHAPTER 10. PFC LEVELS ABOVE $3 … 127
SECTION 1. GENERAL … 127
10-1. Overview … 127 10-2 to 10-5. Reserved … 127 SECTION 2. PFC LEVELS ABOVE $3 AT SMALL AIRPORTS … 128
10-6. Method to Evaluate PFC Level Above $3 at Small Airports … 128 10-7. Finding That Projects Cannot Be AIP Funded … 128 10-8. Finding That Airside Needs Are Met … 130 10-9. Treatment of a Project Qualifying for PFC Approval … 131 at $1, $2, or $3 Level But Not at Levels Above $3 10-10. Reserved … 131 SECTION 3. PFC LEVELS ABOVE $3 AT MEDIUM AND LARGE HUB AIRPORTS … 131
10-11. Method to Raise PFC Level Above $3 at Large and Medium Hub Airports … 131 10-12. Determination of Significant Contribution Procedures … 131 10-13. Procedures … 132 10-14 to 10-15. Reserved … 133 SECTION 4. ESTABLISHMENT OF APPLICATION PFC LEVEL … 133
10-16. Overview … 133 10-17. Setting the PFC Level for a Single Project Application … 133 10-18. Policy on Setting the PFC Level for Multiple Projects with Mixed PFC Levels … 133 10-19. Procedure to Set the PFC Level for a Single Application with Multiple Projects … 135 10-20. Examples of PFC Level Calculations for Single Applications … 137 10-21. Procedure for Multiple RODs … 138 10-22. Examples of PFC Level Calculations for Multiple RODs … 142 10-23 to 10-25. Reserved … 144 SECTION 5. OTHER MODIFICATIONS TO THE PFC PROGRAM … 144
10-26. Additional Reduction in AIP Apportionments … 144 10-27. Other Effects of AIR-21 on the PFC Program … 145 10-28 to 10-30. Reserved … 148
vii
CHAPTER 11. AMENDMENTS NOT REQUIRING CONSULTATION … 153
SECTION 1. GENERAL … 153
11-1. Overview … 153 11-2 to 11-5. Reserved … 153 SECTION 2. AMENDMENTS W HICH CAN BE INSTITUTED BY PUBLIC AGENCY NOTICE … 153
11-6. Type and Timing of Amendments … 153 11-7. Notice—Content and Distribution … 155 11-8. FAA Review … 155 11-9 to 11-15. Reserved … 156
CHAPTER 12. AMENDMENTS REQUIRING CONSULTATION … 161
SECTION 1. GENERAL … 161
12-1. Overview … 161 12-2 to 12-5. Reserved … 161 SECTION 2. AMENDMENTS W HICH REQUIRE CONSULTATION WITH … 161
AIR CARRIERS AND FORMAL SUBMISSION TO FAA 12-6. Type and Timing of Amendment … 161 12-7. Notice—Content and Distribution … 162 12-8 to 12-10. Reserved … 164 SECTION 3. NO CARRIER DISAGREEMENT … 164
12-11. FAA Review of Proposal and Approval/Disapproval … 164 12-12. Public Agency Notice to Carriers … 165 12-13 to 12-15. Reserved … 165 SECTION 4. CARRIER DISAGREEMENT … 165
12-16. FAA Review and Approval/Disapproval … 165 12-17. Public Agency Notice to Carriers … 166 12-18 to 12-20. Reserved … 166 SECTION 5. ADMINISTRATIVE AMENDMENTS … 166
12-21. Overview … 166 12-22. Administrative Amendment Due to Use Application … 166 12-23. Administrative Amendment Due to Automatic Expiration … 167 12-24 to 12-25. Reserved … 167
CHAPTER 13. TERMINATION PROCEDURES … 171
SECTION 1. GENERAL … 171
13-1. Overview … 171 13-2. Identification of Potential Violation … 171 13-3. Investigation of Complaints … 172 13-4 to 13-5. Reserved … 172 SECTION 2. INFORMAL RESOLUTION … 172
13-6. Letter to Public Agency … 172 13-7. Meeting Between FAA and Public Agency … 173 13-8. Informal Resolution of the Violation … 173 13-9 to 13-15. Reserved … 173 SECTION 3. FORMAL TERMINATION PROCEEDINGS … 173
13-16. FAA Determination That Informal Resolution was Not Successful … 173 13-17. Federal Register Notice of Proposed Termination … 174 13-18. Public Hearing … 174 13-19. Final Decision … 174 13-20 to 13-25. Reserved … 176 SECTION 4. IMPACT ON AIP … 176
13-26. Loss of Federal Grant Funds … 176 13-27. Amount of Reduction … 176
viii
13-28. Impact on Existing Grants … 176 13-29 to 13-30. Reserved … 176 SECTION 5. SPECIAL INFORMAL RESOLUTION AND TERMINATION … 176
PROTECTION TO FACILITATE PFC STAND-ALONE FINANCING 13-31. Overview … 176 13-32. Protracted Informal Resolution … 176 13-33. Termination Protection … 177 13-34 to 13-35. Reserved … 177
CHAPTER 14. PROJECT COMPLETION AND PFC CLOSEOUT … 181
SECTION 1. GENERAL … 181
14-1. Overview … 181 14-2. Recordkeeping and Audit … 181 14-3 to 14-5. Reserved … 181 SECTION 2. PFC PROJECT COMPLETION … 181
14-6. Physical Completion Requirements, No AIP Funds … 181 14-7. Joint PFC/AIP Funded Projects … 182 14-8. Financial Completion Requirements … 182 14-9. FAA Actions Associated with Project Physical Completion … 182 14-10. FAA Actions Associated with Project Financial Completion … 183 14-11. Project Completion Notification and Record Requirements … 183 14-12 to 14-15. Reserved … 184 SECTION 3. PFC DECISION CLOSEOUT … 184
14-16. Overview … 184 14-17. Quarterly Reports … 184 14-18. PFC Decision Closeout Report … 184 14-19. Decision Closeout Notification and Record Requirements … 185 14-20. Use of Excess PFC Revenue … 185 14-21. Loss of Federal Airport Grant Funds … 186 14-22 to 14-25. Reserved … 186
CHAPTER 15. ASSURANCES … 191
SECTION 1. GENERAL … 191
15-1. Overview … 191 15-2 to 15-5. Reserved … 191 SECTION 2. DISCUSSION OF ASSURANCES … 191
15-6. Responsibility and Authority of the Public Agency … 191 15-7. Compliance with Regulation … 192 15-8. Compliance with State and Local Laws and Regulations … 192 15-9. Environmental, Airspace, and ALP Requirements … 193 15-10. Nonexclusivity of Contractual Agreements … 193 15-11. Carryover Provisions … 195 15-12. Competitive Access … 196 15-13. Rates, Fees, and Charges … 197 15-14. Standards and Specifications … 199 15-15. Recordkeeping and Audit … 200 15-16. Reports … 200 15-17. ANCA … 200 15-18 to 15-25. Reserved … 201
ix
APPENDIX 1. PFC PROCESS FLOWCHARTS … 1
1-1. Application for Authority to Impose a PFC … 3 1-2. Application for Authority to Impose and Use a PFC … 5 1-3. Application for Authority to Use a PFC … 7
APPENDIX 2. ASSURANCES … 1
APPENDIX 3. PROJECT CONSTRUCTION OVERSIGHT … 1
SECTION 1. GENERAL … 1
3-1. Overview … 1 3-2. Coordination of Projects … 1 SECTION 2. PFC/AIP FUNDED PROJECTS … 1
3-3. Oversight of PFC/AIP Funded Projects … 1 3-4 to 3-6. Reserved … 1 SECTION 3. PFC FUNDED PROJECTS—NO AIP FUNDS … 1
3-7. Preconstruction Conference … 1 3-8. Labor/Disadvantaged Business Enterprise (DBE) … 2 3-9. Design, Construction, and Equipment Standards … 2 3-10. Notice to Proceed … 2 3-11. Construction Records … 2 3-12. Safety … 2 3-13. Parts 107 and 139 Requirements … 2 3-14. Environmental Compliance … 3 3-15 to 3-20. Reserved … 3
APPENDIX 4. AIRPORT DEBT FINANCING … 1
4-1. Overview … 1 4-2. Debt Financing Associated with PFC Applications … 1 4-3. Definitions of Financing Terms … 1 4-4. Types of Financing Scenarios … 2 4-5. The FAA’s Role in PFC-Backed Financing … 3 4-6. Protracted Informal Resolution … 3 4-7. Termination Protection … 4
x
Chapter 1. Introduction
CHAPTER 1. INTRODUCTION
SECTION 1. GENERAL
1-1. OVERVIEW. This order provides guidance and procedures for Federal Aviation Administration (FAA) Airports offices' use in administering the Passenger Facility Charge (PFC) program.
1-2. DISTRIBUTION. This order is distributed to all addressees of the PFC Branch (APP-530) special mailing list and all Airports District and Field Offices.
1-3. AUTHORIZING LEGISLATION. The PFC is authorized by 49 United States Code (U.S.C.) §40117, which is referred to as the “Statute.” The PFC statute’s broad objective is to provide funds through the local imposition of a $1, $2, $3, $4, or $4.50 charge per enplaned passenger.
1-4. GUIDANCE PRINCIPLES.
a. The PFC program must be administered uniformly nationwide with regard to the procedures and requirements dictated by legislation, regulation, and this order. However, the diversity among the FAA Regions in program and public agency needs, available resources, and Airports Division organizational structures dictates that some flexibility be given Airports Division Managers for administration of program elements not specifically required by the regulation. The administration of these elements are left to the discretion of the regional Airports Division Manager.
b. The statute is implemented by the PFC regulation (14 Code of Federal Regulations (CFR) Part 158, "Passenger Facility Charges"). The PFC regulation was adopted on May 22, 1991, and was substantially amended on May 30, 2000. The regulation is intended to provide public agencies with the flexibility to tailor their PFC programs to their own needs while meeting the requirements of the statute. In addition, it is intended to reduce the administrative burden as much as possible for public agencies and air carriers.
c. This order reflects the interpretation and refinement of statutory and regulatory provisions, based on the experience of administering the PFC program.
1-5. ORDER FORMAT.
a. This order is arranged beginning with definitions, legislative history, and overall requirements, followed by the step-by-step procedures to be used by FAA personnel to administer the PFC program from the public agency's first indication of interest through PFC closeout or termination proceedings.
b. This order summarizes appropriate information from other guidance material when possible, so direct reference to the original material is seldom needed. When needed, the current version of the following guidance materials should be used in conjunction with this order:
(1) 14 CFR Part 158, Passenger Facility Charges (referred to as "the regulation" or "Part 158");
(2) 49 U.S.C. Compilation of Selected Aviation Laws;
(3) FAA Order 1050.1D, Policies and Procedures for Considering Environmental Impacts;
(4) FAA Order 5050.4A, Airport Environmental Handbook;
(5) FAA Order 5100.38A, Airport Improvement Program (AIP) Handbook, regarding project eligibility;
(6) Program Guidance Letters (PGL's) issued under FAA Order 5100.38A regarding project eligibility;
(7) FAA Order 7400.2, Procedures for Handling Airspace Matters;
(8) Advisory Circular (AC) 150/5300-13, Airport Design;
(9) AC 150/5370-2C, Operational Safety on Airports During Construction;
(10) Those AC's contained on the list entitled, Current FAA Advisory Circulars for PFC Projects, which is included with each PFC Record of Decision; and
(11) Agency directives, regulations, future AC's which may pertain, and additional information, which should be considered companion documents to this order and should be utilized in conjunction with the PFC program.
c. The following is a list of appendices to this order:
(1) Appendix 1, PFC Project Approval Process. Appendix 1 provides flowcharts for the review and approval/disapproval of:
(i) an application for authority to impose a PFC;
(ii) a concurrent application for authority to impose and use PFC revenue; and,
(iii) an application for authority to use PFC revenue.
(2) Appendix 2, Assurances. Appendix 2 contains the assurances required of a public agency in the submittal of its request to impose and use PFC revenues.
(3) Appendix 3, Project Construction Oversight. Appendix 3 contains the information for construction oversight and responsibilities to insure public agency compliance with the PFC standards and specifications under PFC Assurance 9.
(4) Appendix 4, Airport Debt Financing. Appendix 4 contains information for the analysis of airport bond and other similar types of debt financing associated with PFC applications.
d. All guidance issued in future "PFC Update" letters will be included in subsequent order changes.
1-6. DEFINITIONS. The following definitions apply. Terms in bold lettering are also found in the PFC regulation, but, in many cases, the definitions have been expanded for clarity in this order. All these expanded definitions are based on decisions on individual PFC applications.
a. Administrator means the Federal Aviation Administrator or other person designated by the Administrator to act on his/her behalf.
b. Airport means any area of land or water, including any heliport, that is used or intended to be used for the landing and takeoff of aircraft, and any appurtenant areas that are used or intended to be used for airport buildings or other airport facilities or rights-of-way, together with all airport buildings and facilities located thereon.
c. Airport capital plan means a capital improvement program that lists all airport-related planning, capital development, or noise compatibility projects expected to be accomplished with anticipated available funds (PFC, AIP, local funds, bonds, revenue from other Federal and state agencies, etc.) within a specified timeframe (normally 3 to 5 years).
d. Air carrier means any person providing passenger air transportation for hire that is incorporated under the laws of the United States.
e. Airport layout plan (ALP) means a plan showing the existing and proposed airport facilities and boundaries in a form prescribed by the Administrator.
f. Airport revenue means revenue generated by a public airport
(1) Through any lease, rent, fee, or other charge collected, directly or indirectly, in connection with any aeronautical activity conducted on an airport that it controls; or
(2) In connection with any activity conducted on airport land acquired with Federal financial assistance, or acquired with PFC revenue under this part, or conveyed to such public agency under the provisions of any Federal surplus property program or any provision enacted to authorize the conveyance of Federal property to a public agency for airport purposes.
g. Air transportation means the transportation of passengers by aircraft in common carriage for which the air carrier receives remuneration between a point in the United States and a point outside the United States, between a point in a State and another State, and between points entirely within the same State.
h. Air travel ticket means all documents pertaining to a passenger's complete itinerary necessary to transport a passenger by air, including passenger manifests.
i. Allowable cost means the reasonable and necessary costs of carrying out an approved project including costs incurred prior to and subsequent to the approval to impose a PFC, and making payments for debt service on bonds and other indebtedness [financing costs] incurred to carry out such projects. A public agency's costs of administering its PFC program are also included in allowable costs. Allowable costs include only those costs incurred on projects implemented on or after November 5, 1990 (the date the statute was enacted). In addition, under the terms of the “Wendell H. Ford Aviation Investment and Reform Act for the 21st Century” (AIR-21) (P.L. 106-181) allowable costs include terminal development incurred after August 1, 1986, at an airport that did not have more than .25 percent of the total annual passenger boardings in the United States in the most recent calendar year for which data are available and at which total passenger boardings declined by at least 16 percent between calendar year 1989 and calendar year 1997.
j. Approved project means a project for which use of PFC revenue has been approved. Specific projects contained in a larger single or multi-phased project or development described in an airport capital plan may also be approved separately. (Note: To facilitate financing arrangements and program accountability, it is strongly recommended that each project be discrete and readily identifiable and approved separately.)
k. Charge effective date means the first date on which carriers are obliged to collect a PFC.
l. Charge expiration date means the date on which carriers are to cease to collect a PFC.
m. Class of carrier means a category(s) of air carriers based on common carrier classifications found in FAA operational regulations, DOT economic regulations, or on any other basis that is reasonable, not arbitrary, nondiscriminatory and otherwise in compliance with the law. A class of carriers may be employed by a public agency to exempt those carriers from PFC collection requirements.
n. Collecting carrier means an issuing carrier or other carrier collecting a PFC, whether or not such carrier issues the air travel ticket.
o. Collection means the acceptance of payment of a PFC from a passenger.
p. Commercial service airport means a public airport that annually enplanes 2,500 or more passengers and receives scheduled passenger service by aircraft.
q. Covered airport means a medium or large hub airport at which one or two air carriers control more than 50 percent of passenger boardings.
r. Debt service means payments for such items as principal and interest, sinking funds, call premiums, periodic credit enhancement fees, trustee and paying agent fees, coverage, and remarketing fees.
s. Eligible point means a point receiving air transportation under the Essential Air Service program (see paragraph 6-14).
t. Excess revenue means PFC revenue collected, plus interest, exceeding the allowable costs of a project(s). Excess revenue may also include revenue generated from the sale of property purchased with PFC funds.
u. Excluded class of carriers means those air carriers or foreign air carriers not required to collect PFC's from passengers enplaning at a specific airport. A class approved by the FAA may be excluded if the number of passengers enplaned by the carriers in the class constitutes no more than 1 percent of the total number of passengers enplaned annually at the airport at which the PFC is imposed (see paragraph 4-11).
v. Exclusive long term lease or use agreement means an exclusive lease or use agreement between a public agency and an air carrier or foreign air carrier with a term of 5 years or more. This term also applies to exclusive leases of less than 5 years that have automatic renewal or carryover options, and to leases that have the effect of granting exclusive use rights.
w. FAA Airports office means a regional, district, or field office of the FAA that administers Federal airport-related matters.
x. Financial plan is the public agency's depiction of the means of and timeframe for paying for proposed PFC projects in the application. The plan should include information on the financing of all projects in the airport capital plan, clearly identifying projects to be funded with PFC revenue. (Note: This information is usually provided in the Attachment B for each individual project in the PFC application.)
y. Financing costs means the costs of financing a bond [or other debt instrument (other than debt service)] and includes such costs as those associated with issuance, underwriting discount, original issue discount, capitalized interest, debt service reserve funds, initial credit enhancement costs, and initial trustee and paying agency fees. (Note: The financial community suggests that these costs do not ordinarily exceed two percent of the debt package, but the FAA has not imposed a regulatory limit. If such costs prove to be excessive, the FAA may find that the costs are not reasonable and therefore not allowable.)
z. Foreign air carrier means any provider of passenger air transportation for hire that is incorporated under the laws of a country other than the United States.
aa. Frequent flyer award certificate means a zero-fare award of air transportation that an air carrier or foreign air carrier provides to a passenger in exchange for accumulated travel mileage credits in a customer loyalty program, whether or not the term “frequent flier” is used in the definition of that program. The definition of “frequent flier award coupon” does not extend to redemption of accumulated credits for awards of additional or upgraded service on trips for which the passenger has paid a published fare, “two-for-the-price-of-one" and similar marketing programs, or to air transportation purchased for a passenger by other parties.
bb. Gateway means the last enplaning airport prior to departure from the United States.
cc. Implementation of an approved project means: 1) with respect to construction, issuance to a contractor of notice to proceed or the start of physical construction; 2) with respect to non-construction projects other than property acquisition, commencement of work by a contractor or public agency to carry out the statement of work; or 3) with respect to property acquisition projects, commencement of title search or execution of a contract or agreement for a parcel.
dd. Issuing carrier means any air carrier or foreign air carrier that issues an air travel ticket or whose imprinted ticket stock is used in issuing such ticket by an agent.
ee. Medium or large hub airport means a commercial service airport that has more than 0.25 percent of the total number of passenger boardings at all such airports in the United States for the prior calendar year, as determined by the Administrator.
ff. Nonrevenue passenger means a passenger receiving air transportation from an air carrier or foreign air carrier for which remuneration is not received by the air carrier or foreign air carrier and as defined under Department of Transportation (DOT) Regulations or as otherwise determined by the Administrator. Air carrier employees or others receiving air transportation against whom token service charges are levied are considered nonrevenue passengers. Infants for whom a token fare is charged are also considered nonrevenue passengers.
gg. One-way trip means any trip that is not a round trip (also see definition of trip).
hh. Passenger enplaned means a domestic, territorial, or international revenue passenger enplaned at a point in the United States in scheduled or nonscheduled service on aircraft in intrastate, interstate, or foreign commerce. (Note: Passengers are not considered enplaned at technical stops, such as for refueling or customs inspection, which are not shown on the passenger's ticket.)
ii. PFC means a passenger facility charge imposed by a public agency on passengers enplaned at a commercial service airport it controls. It is referred to in the Statute as the passenger facility fee.
jj. Point means the airport at which travel begins or ends. In the case where a locality is serviced by more than one airport (coterminal airports), the "point" is determined by referencing the current version of the Official Airline Guide. For defining a round-trip as it pertains to calculating applicable PFC's, a trip can begin and end at any of these coterminal airports. (Note: This definition is used to determine whether a given itinerary constitutes a round-trip or a one-way trip.)
kk. Project means airport planning, airport land acquisition, or development of a single component, a multi-phased development program (including but not limited to development described in an airport capital plan), or a new airport for which PFC financing is sought or approved (see also definition of approved project).
ll. Public agency means a State or any agency of one or more States; a municipality or other political subdivision of a State; an authority created by Federal, State, or local law; a tax-supported organization; an Indian tribe or pueblo that controls a commercial service airport; or for the purposes of [the PFC regulation], a private sponsor of an airport approved to participate in the Pilot Program on Private Ownership of Airports.
mm. Remittance means the transmittal of PFC revenue by the collecting air carrier to the public agency.
nn. Revenue passenger means a person receiving air transportation from the air carrier for which remuneration is received by the air carrier as defined under existing DOT Regulations, except passengers using frequent flyer award certificates, as defined in this order (see definition of nonrevenue passenger).
oo. Round trip means a trip on a complete air travel itinerary [to at least one destination point and back] which terminates at the origin point (also see definitions of point and trip).
pp. Secretary means the Secretary of Transportation or other person designated by the Secretary to act on his/her behalf.
qq. Stand-Alone Financing means a financing instrument backed solely by a PFC revenue stream without any other commitment of airport or general revenue (see appendix 4).
rr. State means a State of the United States, the District of Columbia, the Commonwealth of Puerto Rico, the Virgin Islands, American Samoa, the Commonwealth of the Northern Mariana Islands, the Trust Territory of the Pacific Islands, and Guam.
ss. Trip means air travel from one point to another point. In the case of a trip with only one enplanement and one deplanement, the deplanement must occur at a separate point from the enplanement. Consequently, air tours that begin and end at one point without stopping at intermediate points (other than technical stops such as for refueling) are not trips for PFC purposes. In addition, travel between a point and a nonairport location, e.g. a logging camp, is not considered a trip for PFC purposes.
tt. Unliquidated PFC revenue means revenue received by a public agency from collecting carriers and interest earned thereon but not yet used on approved projects.
1-7 to 1-10. RESERVED.
SECTION 2. TITLE 49, UNITED STATES CODE
1-11. PFC AUTHORITY - SECTION 40117. The PFC program is authorized by 49 U.S.C. Subtitle VII, Part A - Air Commerce and Safety, §40117. This statute was implemented by the Aviation Safety and Capacity Expansion Act of 1990 which amended the Federal Aviation Act of 1958, as amended, to remove the restriction against a PFC. The statute authorizes the Secretary of Transportation to allow a public agency that controls at least one commercial service airport to impose a fee for each paying passenger of an air carrier enplaned at the airport. This revenue finances eligible airport projects to be carried out at the commercial service airport or any other airport which the public agency controls.
The Federal Aviation Act of 1994, the Federal Aviation Reauthorization Act of 1996, and most significantly, the Wendell H. Ford Aviation Investment and Reform Act for the 21st
Century (signed into law on April 5, 2000), made significant modifications to §40117. The Codification of Certain United States Transportation Laws (July 5, 1994) changed the U.S.C. references in 14 CFR Part 158.
The following summarizes the major provisions of the statute, as amended. These provisions are described in much more detail in appropriate sections of this order.
a. PFC level. A public agency that controls a commercial service airport may request the authority to impose a PFC of $1, $2, $3, $4, or $4.50 on revenue passengers enplaned at such an airport.
b. Requirements. A public agency which controls a commercial service airport may be granted authority by the FAA to impose a PFC only if the FAA finds, on the basis of an application submitted by the public agency, that the amount and duration of the PFC will not result in excess revenues and the proposed project(s) is: eligible; preserves or enhances capacity, safety, or security, reduces noise, or furnishes opportunities for enhanced competition; and is adequately justified. Additional findings are required for approval of a PFC level above $3 (see chapter 10).
c. Limitation. A public agency may not impose a PFC on a passenger enplaning on a subsidized flight to an eligible point for which Essential Air Service compensation is paid. (Note: This does not prohibit the imposition of a PFC from an eligible point unless that flight is also to an eligible point.) A public agency may not impose a PFC on a passenger who obtains a ticket for air transportation with a frequent flyer award coupon without monetary payment. A PFC may not be imposed on a passenger on flights, including flight segments, between 2 or more points in Hawaii; and in Alaska aboard an aircraft having a seating capacity of less than 60 passengers.
d. Two enplanements per trip limitation. A PFC may not be collected from a passenger in excess of two charges per one-way trip or four charges per round trip (see paragraph 6-11).
e. Air carrier rates, fees, and charges. A public agency may not include in its price base the portion of the capital costs of a project paid for by using PFC revenue to establish a price (i.e., a rate, fee, or charge) under a contract between the public agency and an air carrier or foreign air carrier. However, the Statute requires that, for PFCfunded projects for terminal development, gates and related areas, or a facility occupied or used by one or more air carriers or foreign air carriers on an exclusive or preferential basis, the rates fees, and charges payable by such carriers that use such facilities will be no less than the rates, fees, and charges paid by such carriers using similar facilities at the airport that were not funded by PFC revenue.
f. Exclusivity of authority.
(1) A State, political subdivision of a State, or authority of a State or political subdivision that is not the eligible agency may not tax, regulate, or prohibit or otherwise attempt to control in any manner, the imposition or collection of a PFC or the use of the revenue from the PFC.
(2) No contract or agreement between an air carrier or foreign air carrier and a public agency may impair the authority of the public agency to impose a PFC or impair use of the PFC revenue.
g. Nonexclusivity of contractual agreements. No project funded with PFC revenue may be subject to an exclusive long-term lease or use agreement with an air carrier or foreign air carrier. No lease or use agreement of an air carrier with respect to a project constructed or expanded with PFC revenue may restrict the public agency which controls the airport from funding or developing new capacity at that airport with PFC revenue or assigning that capacity as it sees fit.
h. Collection and handling by air carriers. Air carriers and their agents are required to collect PFC's imposed by public agencies and must remit those charges, less an FAA-specified handling fee, in a timely manner. In addition, the charges collected by the carrier must be noted on the passenger's ticket.
i. Application process.
(1) A public agency interested in imposing a PFC must submit to the FAA an application for authority to impose such fee.
(2) The application must contain the information and be in the form required by regulation as further developed by the FAA (see Preamble to the Regulation).
(3) Before submission of the application, the public agency must provide reasonable notice to, and an opportunity for consultation with, air carriers and foreign air carriers operating at the airport.
(4) After receiving the application, the FAA must provide notice and an opportunity for comment on the application by carriers and interested persons.
(5) A PFC may only be imposed if the FAA approves an application for authority to impose the PFC. The FAA has 120 days from receipt of an application to render a final decision.
j. Recordkeeping and audits. The public agency and the air carriers are required to abide by any regulations which the FAA may issue with regard to recordkeeping and audits of collection of the PFC and use of PFC revenue. If the FAA determines that collection is excessive or that revenue is not being used on approved projects or otherwise not properly used, the FAA may terminate PFC authority and/or offset such amounts otherwise payable to the public agency from AIP under the terms of 49 U.S.C. 47114(c).
k. Terms and conditions. Authority granted to a public agency to impose a PFC is subject to terms and conditions established by the FAA.
1-12. REDUCTION IN AIP APPORTIONMENTS - SECTION 47114(f). The AIP entitlement funds apportioned to a public agency that controls a large or medium hub airport will be reduced if the public agency imposes a PFC at such airport. For further discussion see section 5 of this chapter.
1-13. USE OF FUNDS RECOVERED UNDER SECTION 47114(f). Twenty-five percent of the funds not apportioned under 49 U.S.C. 47114(f) will be added to the AIP discretionary funds with half of this additional amount being designated for use at small hub airports. The remaining 75 percent of these recovered funds will constitute the "Small Airport Fund." One-third of the funds in the Small Airport Fund will be distributed to general aviation (including reliever) airports with the remainder of the funds being distributed to nonhub commercial service airports.
1-14 to 1-15. RESERVED.
SECTION 3. DELEGATION OF AUTHORITY
1-16. OVERVIEW. The Associate Administrator for Airports is delegated limited authority to sign, in coordination with the Chief Counsel, approvals and disapprovals of PFC applications submitted under Part 158. This delegation does not apply to applications involving:
(a) Significant policy precedent;
(b) Significant legal issues, as determined by the FAA's Chief Counsel;
(c) Significant controversy, as evidenced by significant opposition to the FAA's proposed action by the applicant or other airport authorities, airport users, Federal, State or local agencies, elected officials, or communities;
(d) Multimodal projects; or
(e) Significant airport noise, access, or revenue diversion issues, including compliance with 49 U.S.C. 47521 et seq. (the Airport Noise and Capacity Act of 1990 (ANCA) and 49 U.S.C. 47111(e) (Action on Grant Assurances Concerning Airport Revenues)).
The Administrator may delegate decisional authority on an individual application involving any of these exceptions on a case-by-case basis.
1-17. DELEGATION OF LIMITED AUTHORITY TO FAA AIRPORT OFFICES. On October 28, 1996, the Associate Administrator for Airports delegated to FAA Regional Airports Division Managers on a limited basis the authority to sign approvals and disapprovals of certain PFC applications submitted under Part 158. This delegation does not apply to applications involving:
(a) Applications not delegated to the Associate Administrator for Airports (see paragraph 1-16);
(b) Applications that receive negative comments in response to FAA's notice published in the Federal Register;
(c) Any application involving eligibility determinations for which Order 5100.38 and subsequent Program Guidance Letters refer field staff to Headquarters offices, or which require a case-by-case eligibility determination; and
(d) Applications requesting the inclusion of PFC termination protection language.
Specific instructions on the management and procedures for decisions delegated to FAA Regional Airports Division Managers are provided in chapter 5 of this order.
1-18 to 1-20. RESERVED.
SECTION 4. OVERVIEW OF THE PFC PROCESS
1-21. THE PFC PROCESS. Appendix 1 illustrates the steps to be taken by the FAA, air carriers, and the public agency for approvals to impose a PFC and approvals to expend PFC funds on eligible projects. Details on requirements and procedures for each of the steps are found in chapters 3, 4, and 5 of this order.
1-22. PFC PROGRAM AND ITS RELATIONSHIP TO AIP. PFC's are related to funds available under AIP in the following areas:
a. Public agencies are authorized under Part 158 to use the PFC revenue as the matching local share of an AIP project;
b. PFC revenue can be used by a public agency to supplement an AIP project;
c. PFC revenue can be used to pay debt service and financing costs. AIP funds cannot be used for this purpose, except under the AIP Innovative Finance Pilot Program.
d. Eligible projects under the AIP are also eligible for PFC funding. Therefore, future changes to the AIP in regard to project eligibility also apply to the PFC program. However, PFC eligibility also differs from AIP eligibility in that gates and related areas not eligible for AIP at larger airports are PFC-eligible under specific provisions of the PFC statute, as are noise projects eligible under 49 U.S.C. §47504, even if a Part 150 program for those projects has not been approved.
e. As a distinct requirement of the PFC program, PFC projects must meet one or more of the objectives of §158.15(a) of the regulation. Specifically, PFC projects must: (1) preserve or enhance safety, security, or capacity of the national air transportation system; (2) reduce noise or mitigate noise impacts resulting from an airport; or (3) furnish opportunities for enhanced competition between or among air carriers.
Additional requirements for imposition of PFC’s at a level above $3 are discussed in chapter 10.
f. Projects must also be adequately justified. This latter requirement was added to the PFC statute after the original PFC regulation was issued although justification has always been required under §158.25(b)(7). The current version of Part 158 explicitly states this requirement.
g. The authorization to collect PFC's provides that, if the FAA determines a public agency is collecting an excessive amount of PFC revenue or the revenue is not being used as approved, the FAA may reduce the amount of funds otherwise payable to the public agency under the AIP by the amount of the excess collected or not used as approved.
h. Reduction in AIP apportionments at large and medium hub airports that impose a PFC is discussed in section 5 of this chapter.
i. PFC’s constitute a special form of local airport revenue, subject to restrictions imposed by the PFC statute and regulation. Accordingly, some Federal statutory and regulatory requirements that apply to projects funded with AIP monies do not apply to projects funded solely with PFC’s. Most importantly, projects funded totally with PFC revenue or with financing other than Federal funds are not subject to the labor minimum wage rates under the Davis-Bacon Act, Disadvantaged Business Enterprise (DBE) requirements, Buy-American Preferences, or the Uniform Relocation Assistance and Real Property Acquisition Policy Act requirements. However, in cases where PFC funds are commingled with AIP funds to complete a project, all AIP requirements apply. In addition, the AIP requirements may apply if the PFC funded project is part of a past, current, or future FAA grant funded program or project. Finally, in cases where a public agency may have distinct projects to accomplish a similar objective (particularly relocation assistance), one solely PFC funded and one solely AIP grant funded, both projects may adhere to the AIP requirements to preclude perceived inequities among those affected by the projects. Any questions on applicable Federal standards must be addressed on a case-by-case basis in consultation with APP-530.
1-23 to 1-25. RESERVED.
SECTION 5. REDUCTION IN AIP APPORTIONMENTS
1-26. APPORTIONMENT REDUCTION FOR COLLECTION LEVELS OF $3 OR BELOW. The Statute prescribes that funds apportioned under 49 U.S.C. 47114 to large and medium hub primary airports that impose a PFC of $1, $2, or $3 be reduced by an amount equal to 50 percent of the projected revenues from the PFC in the fiscal year. However, this amount cannot exceed 50 percent of the passenger entitlements otherwise due the airport. The reduced apportionment takes effect in the first fiscal year following the year in which the collection of the PFC begins.
1-27. APPORTIONMENT REDUCTION FOR COLLECTION LEVELS ABOVE $3. AIR-21 provides that, in the case of a medium or large hub airport collecting a PFC at a level above $3, AIP funds apportioned must be reduced by an amount equal to the lesser of 75 percent of the projected revenues from the PFC in the fiscal year or 75 percent of the passenger entitlements otherwise due the airport. The reduced apportionment takes effect in the first fiscal year following the year in which the collection of the higher PFC level begins.
AIR-21 provides that certain small hub airports transitioning to medium hub airport status are protected through FY 2003 against a loss in combined year-to-year AIP apportionment and PFC revenues caused by entitlement reductions under 49 U.S.C. 47114(f). The sum of the amount that would be apportioned under 49 U.S.C. 47114 to the public agency controlling that airport in a fiscal year, after application of the apportionment reduction, and the projected PFC revenues to be collected in such fiscal year, shall not be less than the sum of the apportionment to such airport for the preceding fiscal year and the PFC revenues collected in the preceding fiscal year (see paragraph 10-26).
1-28. IMPLEMENTATION OF APPORTIONMENT REDUCTION. Annually, the Office of Airport Planning and Programming (APP) gathers information regarding enplaned passengers and computes the apportionment for each primary airport for the following fiscal year (see paragraph 7-7). The apportionment for each large and medium hub airport imposing a PFC will be recomputed starting in the first fiscal year following the fiscal year in which collections of a PFC begin at that airport and for each ensuing fiscal year that the public agency imposes a PFC. In October of each such fiscal year, APP will notify each FAA Airports office of the amount of each apportionment reduction by airport. The FAA Airports office will notify each public agency controlling an airport subject to reduction of the amount of the reduction. The FAA Airports office should remind a public agency which is considering requesting a PFC level above $3 that the reduced AIP apportionment will be implemented at the beginning of the fiscal year following the charge effective date of the higher collection level, as this may influence the public agency’s choice of the charge effective date (see paragraph 10-26).
1-29. ADJUSTMENTS TO APPORTIONMENT REDUCTION. In the event that PFC revenues are less than or greater than estimated, the reduction may be increased or decreased in the following fiscal year. Any increase in the reduction, however, will not cause the reduction to exceed 50 percent for public agencies collecting PFC’s at a level of $3 or less, or 75 percent for those public agencies collecting at a PFC level above $3, of the amount of AIP entitlement funds that would otherwise be apportioned in any fiscal year.
1-30 to 1-35. RESERVED.
Page 14 (thru 20) Par 1-27
Chapter 2. Advance Coordination
CHAPTER 2. ADVANCE COORDINATION
SECTION 1. BACKGROUND
2-1. OVERVIEW. The public agency's PFC application formulation process includes the following actions: (a) development of a project(s) and a project schedule; (b) preparation of a comprehensive financial plan including the proposed PFC share of project costs; (c) consultation with the air carriers operating at the airport at which the PFC is to be imposed; (d) drafting of the PFC application; and (e) submission of the application to the FAA. In addition, any environmental, ALP, and airspace actions required for projects for which use authority is requested must be completed prior to application submittal. This chapter discusses three processes for advance coordination:
(a) the application formulation meeting, which is optional;
(b) the carrier consultation meeting, which is required by statute; and
(c) the draft PFC application review, which is optional.
The formulation stage is complete when the PFC application is submitted to the FAA.
2-2 to 2-5. RESERVED.
SECTION 2. OPTIONAL APPLICATION FORMULATION MEETING
2-6. OVERVIEW. An application formulation meeting between the public agency and the FAA may identify critical issues that can be resolved in advance of the consultation process and the application submission. Such a meeting is optional on the part of the public agency but, in all but the most routine applications, should be encouraged. Resolution of problems at this level will greatly expedite the PFC process and improve the quality of the final decision. Key points to review at the application formulation meeting include:
(a) Project description, eligibility, objectives, and justification;
(b) Project cost and funding strategies;
(c) Project schedules;
(d) ALP, airspace, and environmental requirements;
(e) Alternative project(s) (for impose-only projects);
(f) Carriers to be excluded from requirement to collect PFC’s;
(g) Consultation process, including the list of air carriers to be consulted; and
(h) Additional requirements for imposing a PFC level above $3, if applicable (see chapter 10)
Although this meeting can yield substantial benefits for the public agency, FAA personnel should be careful not to issue statements that predetermine the application review process. In particular, the FAA can identify problems and suggest corrections, but cannot make any assurances to the public agency that would constrain the FAA’s discretion during the formal evaluation of the application. Upon request, the FAA may provide the public agency with a good example of a PFC application submitted by another airport of comparable size and/or with comparable projects to serve as a model for the public agency.
2-7. PROJECT DESCRIPTION, ELIGIBILITY, OBJECTIVES, AND JUSTIFICATION. The FAA's evaluation of a PFC application may be impeded due to imprecise, inaccurate, or incomplete project descriptions, misunderstandings about project objectives, inadequate justification of projects, or inadequate description of the significant contribution of a project(s) for a $4 or $4.50 PFC (at large or medium hub airports). A failure to identify these weaknesses prior to the consultation and Federal Register comment processes can lead to procedural problems and/or the inability of the FAA to approve a project that otherwise could have been approved. Accordingly, the FAA should make the public agency familiar with the evaluation criteria specified in chapters 4 and 10 of this order at the application formulation meeting.
The FAA Airports office should advise the public agency that each project must be supported by the following information: (a) a concise description that identifies the work to be performed and where the project is located; (b) one or more clearly stated objectives that conform to the objectives in the PFC statute; (c) and an explanation, documented by specific information, of why the project is needed and justified. The FAA should also take this opportunity to identify for the public agency any projects that are clearly not PFC eligible or those projects for which eligibility is determined on a case-by-case basis. Particularly in the case of a proposed terminal development project, the FAA should emphasize the need for the public agency to address the effects of the project on air carrier competition at the airport. Information relevant to the competitive effects of a terminal development project is discussed in sections 3-18, 4-7 and 4-8.
2-8. PROJECT COST AND FUNDING STRATEGIES. The financial plan for a given project must address the period from charge effective date through financial completion. While a financial plan for impose only applications may be preliminary, a detailed financial plan is mandatory for an impose and use application or an application for use. The financial plan for each project must be presented at the airline consultation meeting, and in the PFC application. The financial plan must meet the requirements specified in chapter 4. The FAA should confirm that the public agency: (a) has reasonable cost estimates for each project (availability of project operation and maintenance costs may be beneficial, but are not mandatory, for air carrier consultation purposes); (b) understands which portions of these costs are eligible costs; (c) has correctly
reflected existing AIP entitlement and discretionary grants and has made reasonable assumptions about future AIP entitlement and discretionary funds; and (d) has identified credible sources of other non-PFC funds if needed. If AIP discretionary funds are anticipated in the financial plan, the FAA should advise the public agency that it must develop an alternate funding plan that does not rely on AIP discretionary funding so that interested parties may have some assurance that the project will go forward if approved for PFC funding even if AIP discretionary funds are not forthcoming. In the case of a $4 or $4.50 PFC level, particular attention must be given to expected AIP funding for the project, as the FAA cannot approve $4 or $4.50 PFC funding for projects that it reasonably expects can be funded with AIP funds (see paragraph 10-7). In addition, if the use of a PFC-funded project depends on the completion of a non-PFC funded project, the public agency must present information demonstrating that it has the funding necessary to complete the non-PFC project.
2-9. PROJECT SCHEDULES AND ENVIRONMENTAL, AIRSPACE, AND ALP REQUIREMENTS. Project schedules must consider regulatory requirements for both subsequent use applications and project implementation as provided in chapter 4. The public agency's schedule should be carefully reviewed to ensure it is realistic and consistent with other milestones. For instance, if it appears unlikely the public agency will be able to seek use authority within 3 years of the charge effective date for a project (see paragraph 3-7(b)), the public agency should be discouraged from submitting that project for impose authority. Similarly, the status of ALP, airspace, and environmental actions should be reviewed if the public agency intends to submit projects for "use" approval. Every effort should be made to have all environmental, ALP, and airspace determinations/approvals required for use or impose and use projects completed prior to application submission. Use or impose and use applications are not "substantially complete" until these actions are completed.
PFC projects are coordinated with other FAA offices in the same manner as other non- Federal projects. The public agency should be informed that it will be responsible for any required coordination of construction activities with the appropriate FAA offices (Airports, Airway Facilities, Air Traffic, Security, and Flight Standards) after the FAA has granted project approval.
2-10. ALTERNATIVE PROJECTS (for impose only projects). The public agency must provide and consult with its air carriers on eligible alternative uses to cover at least 5 years of collection or the value of the impose only projects, whichever is less (see paragraph 4-14).
2-11. PREPARATION FOR AND TIMING OF CARRIER CONSULTATION. The application formulation meeting presents an opportunity to discuss the consultation experiences of other public agencies.
The FAA should advise the public agency that the carrier consultation meeting should take place at least 30 days prior to the planned submission of the PFC application (see paragraph 2-21). In the case of a "use only" application, where a meeting may not be
required (see paragraph 2-22), the written notice to air carriers should be issued at least 30 days prior to submission. In addition, the public agency may need to allow additional time to prepare its required responses to carriers' comments, to be included in the application package.
The public agency, with the consent of air carriers, may seek to expedite the consultation/application process. In some instances, the FAA has agreed to a reduction in the 30-day notification time before and/or after a consultation meeting provided that all the air carriers serving the airport concur in writing with the reduced time frame. However, the public agency should be discouraged from basing its planned submission on an assumption that air carriers will waive the notification times. The objection or non-response of only one air carrier would mandate that the full notification periods be provided.
Although the regulation is silent on just how far in advance of the application submission a carrier consultation can occur, it is advisable that it be no more than 6 months in advance (some exceptions will apply). Longer time periods between consultation and application submission increase the risk that the public agency will be required to reconsult due to a change in project cost, scope, or other developments. For instance, the FAA has determined that a public agency must re-consult with air carriers prior to submission of an application if one or more air carriers not invited to the initial consultation begin service at the airport during the period between the consultation and the submission of the application. The longer the time period between consultation and application, the greater is the risk.
Finally, the public agency should be reminded that the FAA has no active role in carrier consultations. The FAA may attend the consultation meeting as an observer; however, this attendance is not mandatory.
2-12. APPLICATION FORMS. The PFC application must be submitted in the form specified in section 3-6. The FAA Airports office should discuss the procedures and format with the public agency. These forms are located in the FAA PFC Branch, APP-530 public access internet site, referred to as the PFC internet document site.
2-13. PUBLIC AGENCY PFC ASSURANCES. The FAA should review the PFC assurances with the public agency, paying particular attention to the linkage between PFC collection authority and the public agency's compliance with 49 U.S.C. 47524 and 47526 (see paragraph 4-12), formerly known as the Airport Noise and Capacity Act of 1990 (ANCA), and revenue diversion assurances (see paragraph 4-13). In addition, if the application includes terminal construction or rehabilitation projects, the public agency should be informed that it will have to assure the FAA that the terminal or portion of the terminal funded with PFC’s will comply with the assurances pertaining to nonexclusivity of contractual agreements, carryover provisions, and competitive access assurances (see paragraphs 15-10 to 15-12). The public agency should be informed that it may need to provide the FAA with a copy of the lease for PFC-funded terminal areas which will be leased to air carriers, and that submission of these documents to the FAA in advance of
the submission of the application will minimize PFC processing time. It should also be pointed out to the public agency that by signing the Passenger Facility Charge Application, FAA Form 5500-1, it has agreed to comply with all assurances.
2-14. EXEMPTION OF A CLASS OR CLASSES OF CARRIERS. Any proposed class of carrier exemption definition should be discussed with the public agency prior to the air carrier consultation meeting. This is especially important if the public agency chooses not to consult with carriers listed in the proposed excluded class(es). In particular, if the carriers in an excluded class are not consulted and that class is subsequently disapproved by the FAA, the entire application could be disapproved or substantially delayed. Moreover, the public agency should be warned that the FAA cannot offer a final determination on the eligibility of the class until the application has been formally submitted--thus emphasizing the value of a fully inclusive consultation. Each class exemption must not exceed 1 percent of the airport's total annual enplanements and should otherwise conform to the requirements described in chapter 4.
2-15. ADDITIONAL REQUIREMENTS FOR IMPOSING A PFC LEVEL ABOVE $3. Any public agency requesting a PFC level above $3 is required to provide additional information for the FAA to make specified findings beyond those required under the PFC statute and regulation for PFC levels of $3 or less (see chapter 10).
2-16. IDENTIFICATION OF ADDITIONAL INFORMATION. Additional project information which may be needed for the FAA's review of PFC project eligibility once the application is formally submitted should be identified at this time. Additional information that may be useful or necessary for the inclusion in the application includes:
a. Sketch(es) depicting proposed projects;
b. Part 150 studies;
c. Noise contours supporting noise mitigation projects;
d. Pavement condition surveys;
e. Documentation of demand by critical aircraft, including haul length;
f. List of Federally funded/PFC financed equipment;
g. Snow removal plan;
h. Airport leases for terminals;
i. Airport capacity information for ground access projects (see paragraph 4-8);
j. Information on existing air carrier competition at the airport (see paragraph 4-8); and
k. Competition plans for a qualifying airport (see paragraph 10-27).
2-17 to 2-20. RESERVED.
SECTION 3. CONSULTATION MEETING
2-21. REQUIREMENT TO CONSULT. Section 158.23 of the PFC regulation states that, prior to submitting an application to the FAA for authority to impose a PFC, the public agency shall provide written notice of the consultation meeting to all air carriers and foreign air carriers operating at the airport (see paragraph 4-15), except those carriers that the public agency may choose to request not to collect PFC's (see paragraph 4-11). This notice shall specify the date and location of a consultation meeting at which the public agency will present projects being considered for impose or impose and use authority to air carriers and foreign air carriers operating at the airport. This meeting should be held no sooner than 30 days nor later than 45 days after issuance of the written notice, although a meeting may be held sooner than 30 days from issuance with unanimous air carrier concurrence (see paragraph 2-11). For a use application, a meeting is not required if there are no significant changes from the original impose only application.
2-22. CONTENT OF NOTICE TO CARRIERS. The written notice to air carriers shall include the following information:
a. Description of project(s) being considered for funding by PFC's (including alternative project(s) in the case of impose only project(s));
b. The PFC charge level, the proposed charge effective date, the estimated charge expiration date, and the estimated total PFC revenue;
c. For a request by a public agency that any class or classes of carriers not be required to collect the PFC:
(1) The designation of each class,
(2) The names of the carriers belonging to each class (to the extent the names are known),
(3) The estimated number of passengers enplaned annually by each class, and
(4) The public agency's reasons for requesting that carriers in each class not be required to collect the PFC; and
d. For an impose only, impose and use, or use application for which a consultation meeting is required, the date and location of a meeting at which the public agency will present such projects to air carriers and foreign air carriers operating at the airport.
For a use application, a meeting is not required unless there are significant changes from the original impose only application; a letter notice will suffice. In this case, the carriers have 30 days from the date of issuance of the letter to submit their certificate of agreement/disagreement to the public agency. However, if the use application includes changes that would otherwise require consultation under the requirements for processing amendments (e.g., a significant change in project scope or increase in cost), then a consultation meeting is required (see paragraph 12-6).
Public agencies should send a copy of the notice to carriers to the FAA Airports office.
2-23. CARRIER WRITTEN ACKNOWLEDGMENT. Within 30 days following issuance of the written notice from the public agency to the air carriers, each carrier must provide the public agency with a written acknowledgment that it received the notice. If the air carrier does not provide written acknowledgment of the notice, it will be assumed that it has received notification. The public agency is strongly encouraged to send its notice "return receipt requested." The returned signed receipt is adequate carrier acknowledgment and is invaluable for verifying carrier notification in the event that one or more carriers should later challenge the thoroughness of the notification procedure. Such a challenge could complicate and/or delay a decision on the PFC application.
2-24. CONSULTATION MEETING. In addition to the information contained in the written notice, the public agency is required to provide the explanatory information to the air carriers at the consultation meeting. However, the FAA Airports office should strongly encourage the public agency to include as much of the required information as possible prior to the meeting in its “Notice to Carriers” to allow carriers sufficient time to review the proposals in-depth, and yield a more useful exchange at the consultation meeting itself. Supplemental information may also be sent after the notice, but prior to the meeting, preferably allowing the carriers sufficient time to review it.
In addition to the information required in the notice, the public agency is required to provide the air carriers and foreign air carriers with the following information in sufficient detail to allow for carrier review and evaluation:
a. A description of each project (and alternative projects in the case of impose only projects);
b. An explanation of the justification for each project (and alternative projects in the case of impose only projects); and
c. A detailed financial plan for the projects including
(1) The estimated allowable project costs to be paid for with PFC revenue allocated to each project,
(2) The anticipated total amount of PFC revenue that will be used to finance the project(s), and
(3) The source and amount of other funds, if any, needed to finance the project(s).
The requirement for a detailed financial plan does not apply to alternative projects submitted with an impose-only project.
The consultation meeting should be viewed as an opportunity for the public agency and the carriers to discuss issues surrounding the scope, financing, and timing of the proposed projects. In this context, while acceptable as meeting the regulatory requirements for consultation, a public hearing is not the recommended forum for consultation.
2-25. CARRIER WRITTEN CERTIFICATION OF AGREEMENT OR DISAGREEMENT. Within 30 days following the consultation meeting, each carrier must provide the public agency with a written certification of its agreement or disagreement with each proposed project. Conditional agreements and agreements with comments are generally considered an agreement. However, the public agency should be advised to address any substantive issues raised in these comments in that these comments may raise issues of concern to the FAA. A certification of disagreement shall contain the reasons for such disagreement. The absence of such reasons shall void a certification of disagreement.
2-26. CARRIER FAILURE TO PROVIDE WRITTEN ACKNOWLEDGMENT OR CERTIFICATION OF AGREEMENT/DISAGREEMENT. The regulation states that if a carrier fails to provide the public agency with timely acknowledgment of the written notice or timely certification of agreement or disagreement with each proposed project, the carrier is considered to have certified its agreement. Any comments of disagreement received from an air carrier within the 30 days following the consultation meeting must be addressed in the public agency's application (see paragraph 2-27), even if that air carrier neglected to acknowledge the public agency's written notice. Although not required, the FAA should encourage a public agency receiving a certification of disagreement after the 30 day comment period to address the carrier's objections. This practice assures that the FAA has all information needed to evaluate comments that may be received through the Federal Register review process.
2-27. SUMMARY OF MEETING. Section 158.25(b)(11) requires the public agency to provide a summary of the consultation process in its PFC application. Although a format for the summary is not specified, the regulation states that the summary shall include:
a. A list of carriers operating at the airport and those carriers notified;
b. A list of carriers that acknowledged receipt of the notice;
c. Lists of carriers that certified agreement and that certified disagreement with each project; and
d. A summary of substantive comments made by carriers in any certifications of disagreement with the project, and the public agency's reasons for proceeding in the face of this disagreement.
The public agency must address all air carrier adverse comments. This analysis and summary is to be provided in the attachment B of the PFC application. Although not required by regulation, the public agency should be encouraged to keep a transcript or detailed notes of the meeting in the event a question is later raised as to whether a specific project was discussed at the meeting.
2-28. CHANGES BY PUBLIC AGENCY AFTER THE CONSULTATION. A public agency may decide to change project descriptions, scopes, and/or estimates of allowable project costs after the consultation is completed. These changes could be necessitated by new engineering studies, changes in aviation demand, responses to air carrier concerns, or new cost information, particularly if there is a long period between the time of the consultation and the time the application is ready to be submitted to the FAA. In such cases (other than as a result of air carrier consultation), procedures and guidelines specified for consultation on amendments are applicable (see paragraph 12-7). As a general rule, an increase in allowable costs for projects in the application of 15 percent or more, or a significant change in the scope of any project, would require a new consultation and a new meeting before the application could be submitted. Adding new projects or changing a project's status from "alternative" to "primary" always requires reconsultation and a new meeting.
2-29 to 2-35. RESERVED.
SECTION 4. DRAFT PFC APPLICATION REVIEW
2-36. OVERVIEW. The public agency may submit a draft of the PFC application to the FAA Airports office for review and comment. The completeness of the carrier notification list, the adequacy of the public agency's response to carrier disagreements, the timeliness of project schedules, the status of required ALP, environmental, or airspace approvals, and the acceptability of any carrier class exemption definitions deserve particular attention. If substantive questions remain, a working meeting with the public agency can be scheduled to resolve issues prior to formal submittal. The public agency should be informed that any opinions expressed by the FAA during the draft application
process are preliminary and could be modified based on new information or further analysis prior to the final decision being issued.
2-37 to 2-40. RESERVED.
Page 30 (thru 34) Par 2-36
Chapter 3. Application Submittal
CHAPTER 3. APPLICATION SUBMITTAL
SECTION 1. GENERAL
3-1. OVERVIEW. This chapter provides information on the PFC application, its availability, the public agency's timing considerations for submitting an application, the processing of the application from the time FAA receives it through the issuance of the Federal Register notice requesting public comment on the application, and the official application file requirements.
The FAA may request clarification of any information received from the public agency at any time during the review process. A written record of any such request and the public agency's response should be maintained in the official file. However, the public agency should not use such a request as an opportunity to present additional arguments including new justifications, as opposed to clarifying information. Submission of a new justification, rather than clarifying information, may cause procedural problems requiring the need for additional Federal Register comment periods (see Air Transport Association v. FAA, 169 F. 3d 1 (D.C. Cir., 1999)).
3-2. FLOW CHART OF APPROVAL/DISAPPROVAL PROCESS. A flow chart of the approval/disapproval process from the time of the FAA Airports office’s receipt of application through approval/disapproval is provided in appendix 1.
3-3 to 3-5. RESERVED.
SECTION 2. PROCEDURES FOR SUBMITTAL
3-6. FORM. The PFC application form, FAA Form 5500-1, including instructions for preparing the attachments and the format for Attachment B, is provided in the PFC internet document site and is also available at the FAA Airports office. This form must be used by all public agencies that submit applications. Failure to use the prescribed format may result in a determination that the application is not substantially complete. Three copies of the completed application should be submitted to the FAA as indicated on FAA Form 5500-1: two copies to the FAA Airports office and one copy to APP-530. If the FAA Airports office advises the public agency to submit all copies to it, the FAA Airports office is required to immediately forward one copy to APP-530. The FAA strongly encourages the electronic submission of Form 5500-1 and the associated attachments to facilitate the processing of applications.
3-7. TIMING OF SUBMISSION.
a. Initial application. The regulation requires that the air carriers be provided with a 30-day comment period following the consultation. Accordingly, the application cannot be submitted until at least 30 days after the consultation meeting with the
carriers (see also paragraph 2-11). In the case of use applications for which a meeting is not required, the application can be submitted no sooner than 30 days after the written notice to air carriers concerning the application. In addition, the public agency may need to allow additional time to prepare its required responses to carriers' comments which must be included in the application package. There is no regulatory time limit on submitting an application after conclusion of consultation, but a lengthy period may result in the need for re-consultation (see paragraph 2-11).
b. Subsequent use applications. In the case of an impose only project, once the FAA approves an application, the public agency has up to 3 years from the charge effective date to submit an application to use PFC revenue for the project.
An important exception to this requirement occurs when the public agency obtains additional impose only (collection) authority for new projects in subsequent application(s) before previously granted impose collection authority has expired. In this case, the use application(s) for these latter impose only projects must be submitted to the FAA within 3 years of the date that the FAA approves the application authorizing those impose only project(s).
For example, the first application approved for the public agency controlling the airport TMS, 95-01-I-00-TMS, authorized 20 years of impose only collections and was signed on January 25, 1995 with a charge effective date of April 1, 1995. The public agency for TMS would be required to submit a use application for this approval by April 1, 1998, three years after the charge effective date. Later, on June 5, 1997, the FAA approved a second impose only application, 97-02-I-00-TMS, with a charge effective date of April 1, 2015 (the date when the 20 year collection authority for 95-01-I-00-TMS terminates). The use application for 97-02-I-00-TMS would be required to be submitted by June 5, 2000, 3 years after the approval date of 97-02-I-00-TMS — not April 1, 2018, 3 years after the charge effective date for that application.
If the public agency has several impose only projects, it may elect to file one combined application or several separate use applications during the 3-year timeframe allowed for the use application(s). In addition, the public agency may request an extension (the extension may be for up to 2 years for a maximum impose only time not to exceed 5 years) to submit an application for project use approval, if progress toward implementation of an impose only project has been delayed for valid reasons (subject to other time restrictions, see chapter 9). The FAA Airports office will assist the public agency in monitoring this requirement for submission of use applications (see chapter 8).
c. Subsequent impose only or impose and use applications. The public agency may submit a new impose only or impose and use application at any time. However, the new application should be submitted at least 180 days prior to the charge expiration date of the previous application if the public agency wishes to maintain PFC collections without interruption. The FAA Airports office and the public agency should monitor the rate of collections and the estimated charge expiration date, although the
ultimate responsibility resides with the public agency. If another PFC application is expected, the FAA Airports office should advise the public agency the best practice is to begin work on that application at least 1 year before the collection for the current application is projected to expire. This will allow for the orderly development, consultation, and evaluation of the new application.
If the subsequent application is not submitted in a timely manner, the public agency puts itself at risk of having to stop and restart collections. These brief interruptions in PFC collections are administratively burdensome to the air carriers, the FAA, and the public agencies. The public agency should make every effort to avoid brief interruptions in collections.
3-8. APPLICATION FILE. An application file is a collection of documents pertinent to a particular PFC application. The PFC file system is established and maintained by the FAA Airports office. File information includes documents tracking a project from receipt of the PFC application (and any official correspondence to or from the FAA leading up to the application) through PFC application closeout. Files of disapproved PFC applications contain all information through item k. below. At a minimum, the application file must include the following information (document sources or references are indicated):
a. PFC application (PFC internet document site) including attachments;
b. Checklist for Review of Application (PFC intranet document site for FAA access);
c. Letter to the public agency on application completeness (PFC intranet document site);
d. Public agency notice of application supplement, if applicable (see paragraph 3-18(c));
e. Application supplement, if applicable (see paragraph 3-18(c));
f. Federal Register notice, as published (see paragraph 3-18(d) or 3-19(b));
g. Public comments resulting from Federal Register notice (see paragraph 5-13);
h. Additional information/clarification requested by the FAA Airports office used to assist in preparing a recommendation;
i. Determination of Delegation (see paragraph 5-6(a));
j. Recommendation package including a copy of the Attachment(s) B and G with the "FOR FAA USE" portions completed (PFC internet document site), PFC Application Recommendation Form (PFC intranet document site), PFC Alternative Project
Recommendation Form (PFC intranet document site), if applicable, and any memoranda or similar documentation supporting the FAA Airports office’s recommendation for approval/disapproval. The recommendation package submitted to APP-530 will also contain a copy of the comments identified in item g. above;
k. A copy of the signed determination package, including the letter to the public agency and the record of decision (ROD) (PFC intranet document site);
l. Public agency notification to carriers to begin collection of PFC's (see paragraph 6-2);
m. Public agency quarterly reports (see paragraph 7-6);
n. Public agency annual August 1st report, if applicable (see paragraph 7-7);
o. Documents associated with amendments and extensions (see chapters 11, 12 and 9);
p. Documents associated with termination proceedings (see chapter 13);
q. Public agency annual audit(s), if requested (see paragraph 7-18);
r. Termination protection documentation for stand-alone PFC financing, if applicable (see paragraph 13-33);
s. Close out project completion certificate (see paragraph 14-11); and
t. PFC application closeout report (see paragraph 14-18).
An application file should be maintained until all projects within it have been physically and financially completed and the application has been closed out. Following close out, it is suggested that the file be reduced to include only the signed determination package, amendments, extensions, and the letter sent by the FAA to the public agency to confirm application close out. However, the FAA Airports office should use discretion and retain materials that may be relevant to future evaluations of projects completed under the application, particularly if there is known controversy concerning those projects.
3-9 to 3-15. RESERVED.
SECTION 3. APPLICATION COMPLETENESS REVIEW
3-16. OVERVIEW. This section covers the regulatory requirements and procedural guidance for making a determination of application completeness, preparing a Federal Register notice, and processing an application supplement, if applicable.
3-17. RECEIPT OF APPLICATION. Upon receipt of the application, the FAA Airports office will write the date received in the appropriate box on the application form and will notify APP-530 (and the FAA Airports Regional Office, if appropriate) promptly of the date of receipt.
3-18. DETERMINATION OF COMPLETENESS.
a. Review checklist. The PFC application will be reviewed for completeness using the checklist (PFC intranet document site) and by completing the appropriate "FOR FAA USE" portions of Attachment(s) B. This checklist and FAA-completed Attachment(s) B serve as the official FAA record for the determination of completeness.
Within 30 days after receipt of an application, the FAA Airports office will determine whether the application substantially complies with the requirements of the PFC statute and regulation. During review of the application for completeness, the FAA Airports office should determine if:
(1) The application contains the required information in sufficient detail that a determination on each project can be made;
(2) Sufficient eligible alternatives have been provided for impose only projects;
(3) Environmental, ALP, and airspace requirements are complete for impose and use or use projects; and
(4) Air carrier consultation was conducted properly.
The FAA’s objective should be to notify public agencies of concerns as soon as possible in the review process, although ideally, such concerns would have been anticipated in the application formulation meeting (see paragraph 2-6). The project description, justification, and financial plan must provide sufficient detail that a person not familiar with the airport will be able to understand the project.
In addition, depending on the specifics of the project, a terminal development project may require additional detailed information. This additional information is necessary in order to meet the regulatory requirement calling for public agencies to discuss any existing conditions that limit competition between and among air carriers, any initiatives the public agency proposes to foster opportunities for enhanced competition between or among such carriers, and the expected results of such initiatives. See section 4-7(d) for specifics regarding the type and specificity of additional information needed. This information is required for all airport sizes and is independent of the requirement that some airports must have a current competition plan (see paragraph 10-27).
Projects for which impose only PFC authority is requested must address the issue of alternative PFC uses (see paragraph 4-14). If sufficient eligible alternatives are not
included in an application that contains impose only projects, the application must be found not substantially complete. In such cases, the public agency will have to consult with the air carriers on new or additional alternatives. Alternatively, the public agency could move sufficient primary projects, which were included in the consultation, to alternative status to provide the needed coverage. The public agency could also choose to withdraw, by letter to the FAA, some or all of the proposed impose only projects from the application. Either of these approaches would eliminate the need for reconsultation. The requirement for consultation on alternatives is a result of a court decision on an early PFC decision (see Northwest Airlines, Inc. v. Federal Aviation Administration, 14 F. 3d 64 (D.C. Cir. 1994)).
Assuring environmental, ALP, and airspace requirements are completed for impose and use or use projects warrants special attention. A notice that the FAA has found an impose and use or use application to be substantially complete, published in the Federal Register is acknowledgment that the FAA has completed actions and issued findings in these areas.
If the FAA reviewer determines an item(s) on the checklist does not meet requirements or is not included in the application, this deficiency will be noted on the checklist and the application determined to be not substantially complete. An exception to this, however, may be the lack of certain general items, such as a telephone number, which do not impair the FAA's ability to render a decision.
The FAA reviewer must verify certain dates which are stipulated by regulation. One such date is the consultation meeting with carriers, which is to be held no earlier than 30 days nor later than 45 days from the date of written notice to the carriers. The other date requirement is that at least 30 days must have passed from the date of the consultation meeting to the date of the public agency submitted its application to the FAA, to allow for carrier certification of agreement or disagreement (see paragraph 4 15(a)(2)). If the public agency has not complied with these timeframes, the application will be determined to be not substantially complete. An exception would be where the public agency has moved a date to accommodate an accelerated schedule and/or an air carrier and the air carriers affected by the change, once advised of it, register an affirmative agreement (see paragraph 2-11). If more than one carrier is affected, agreement must be unanimous.
If the FAA Airports office is aware of any ongoing investigations or findings with regard to non-compliance with ANCA (see paragraph 4-12) or revenue diversion (see paragraph 4-13), APP-530 and APP-600 and/or AAS-400 must be consulted. Depending on the status of the ANCA or revenue diversion issue, the application may be found not substantially complete, in that the FAA would lack sufficient information to make a positive determination of compliance.
The reviewing FAA official shall make a finding of completeness, sign, and date the checklist.
b. Preparation of letter. After the checklist is completed, the FAA Airports office shall advise the public agency, in writing, of the application's completeness. The format for a "substantially complete" letter and a "not substantially complete" letters are shown in the PFC intranet document site. The appropriate letter must be signed by the regional Airports Division Manager or designee.
c. Supplement to application. When the FAA determines the application is not substantially complete, the public agency is afforded one opportunity to formally supplement its application. However, a request by the FAA Airports office for clarification of an item during the review process is not a formal supplement to the application.
The public agency has 15 days from the date the FAA issues a not substantially complete letter to provide written notice that it intends to supplement its application, or it may choose to withdraw any project(s) which has been found to be not substantially complete. Note that only a written notice of intent to supplement is required, not the actual supplement to the application.
Once the public agency has indicated it intends to supplement, the regulation provides no specific time period in which the supplement must be submitted to the FAA. If a significant change is made in the application, reconsultation with the carriers may be needed. Apply guidance contained in chapter 12 concerning amendments in determining what application changes necessitate re-consultation with the carriers. If the public agency declines to supplement the application, the FAA Airports office should follow the procedures for processing an application as set forth in paragraph d. of this section.
If the public agency supplements its application, the statutory 120-day approval period restarts at day 1 when the FAA receives the supplemental information. Section 3-19 provides guidance for processing a supplemented application.
d. Preparation of Federal Register notice.
(1) Substantially complete application. The FAA Airports office prepares a Federal Register notice in accordance with the instructions and format provided in the PFC intranet document site. The Federal Register notice should be prepared at the same time as the "completeness" letter. This simultaneous preparation will save time in the 120-day approval process.
(2) An application found not substantially complete which the public agency does not intend to supplement. If the public agency does not respond in writing within the 15-day period following a "not substantially complete" determination, the FAA Airports office prepares a Federal Register notice in accordance with the instructions and format provided in PFC intranet document site. This notice includes the reason(s) the application was found not substantially complete.
(3) Processing. The Federal Register notice should be sent to the Office of the Docket, AGC-10, for publication in the Federal Register. Appropriate procedures should be established to verify that the notice has been forwarded to and/or received by AGC-10 in a timely manner. If transmitting several Federal Register notices in the same package, special effort should be made to highlight each notice.
3-19. PROCESSING OF APPLICATION SUPPLEMENT.
a. Review of previous checklist. When it receives a supplement to an application, the FAA Airports office will review the previously prepared "completeness" checklist and FAA-completed Attachment(s) B to determine if the supplement provides the information necessary to complete the application.
The FAA Airports office may prepare another letter to the public agency acknowledging receipt of the supplement. This letter may be similar to the substantially complete letter described in section 3-18(b). This letter is not required by regulation, but provides useful documentation to the public agency and the application file.
b. Preparation of Federal Register notice.
(1) Supplemented application complete. The FAA Airports office will prepare a Federal Register notice as shown in the PFC intranet document site.
(2) Supplemented application with unresolved deficiencies. The FAA Airports office will prepare a Federal Register notice as shown in the PFC intranet document site. This notice will include the reason(s) the application was found not substantially complete and why the supplement did not successfully resolve the issue(s).
(3) Processing. The Federal Register notice is sent to the Office of the Docket, AGC-10, for inclusion in the Federal Register. If transmitting several Federal Register notices in the same package, special effort should be made to highlight each notice.
c. Washington coordination. As discussed in section 3-6, the public agency is required to send a copy of the application to APP-530. If the application is supplemented, the FAA Airports office will send a copy of the application supplement to APP-530.
3-20. PUBLIC AGENCY COORDINATION. The FAA Airports office will forward a copy of the published Federal Register notice to the public agency. The public agency shall make available for inspection by the public, upon request, a copy of the application, Federal Register notice, and other documents germane to the application. The public agency may also opt to publish the Federal Register notice in a local newspaper of general circulation.
3-21 to 3-25. RESERVED.
Page 42 (thru 48) Par 3-18
Chapter 4. Project and Application Review
CHAPTER 4. PROJECT AND APPLICATION REVIEW
SECTION 1. GENERAL
4-1. OVERVIEW. This chapter contains the criteria and procedures for evaluating all applications and projects. See chapter 10 for additional requirements that apply to projects at the $4 and $4.50 PFC level of collection.
4-2. APPLICATION EVALUATION. The FAA Airports office will evaluate the application and prepare its recommendations for PFC revenue collection and project approval, partial approval, or disapproval based on the regulatory criteria and procedural guidelines for the following items:
a. Project eligibility;
b. Project objective;
c. Project justification;
d. Amount and duration of the PFC;
e. Collection process;
f. Exclusion of a class of carriers;
g. Compliance with the ANCA;
h. Compliance with airport revenue use requirements;
i. Alternative uses;
j. Consultation requirements;
k. Air carrier and public comments;
l. ALP/airspace/NEPA requirements;
m. Schedule for project implementation; and
n. Financial viability.
Each of these criteria is discussed in the following paragraphs. These criteria may vary in applicability depending on whether an application is to impose or to use. Accordingly, where the criteria apply to approving projects with only authority to impose but not use a PFC, "(impose only)" is indicated after the criteria heading. Where the criteria apply to approving impose authority, with or without accompanying use authority, "(impose)" is
indicated. Where the criteria apply to approving use authority, with or without accompanying impose authority, "(use)" is indicated. Where the criteria apply uniformly to all types of authority, "(all)" is indicated.
4-3 to 4-5. RESERVED.
SECTION 2. EVALUATION CRITERIA
4-6. PROJECT ELIGIBILITY. (All)
a. Eligibility criteria. Each project in an application must qualify under one of the following criteria:
(1) Airport development eligible under subchapter I of 49 U.S.C. chapter 471;
(2) Airport planning eligible under subchapter I of 49 U.S.C. chapter 471;
(3) Terminal development as described in 49 U.S.C. 47110(d);
(4) Airport noise compatibility planning as described in 49 U.S.C. 47505;
(5) Noise compatibility measures eligible for Federal assistance under 49 U.S.C. 47504, without regard to whether the measures have been approved under §47504, (as implemented by 14 CFR Part 150);
(6) Construction of gates and related areas at which passengers are enplaned or deplaned and other areas directly related to the movement of passengers and baggage in air commerce within the boundaries of the airport. These areas do not include restaurants, car rental facilities, automobile parking facilities, or other concession space; or
(7) Air Traffic Modernization Cost Sharing program.
In addition to the eligibility project types listed above, debt service and financing costs associated with projects meeting the above criteria are also eligible.
The description of the project should define the project to the extent that a person unfamiliar with the airport can understand what the project will accomplish and determine the project’s scope. A project within some PFC applications may consist of two or more project elements grouped into a single, larger project (e.g., terminal construction or rehabilitation). A detailed description of the elements of such projects should be provided in order for the FAA to determine the eligibility of each project
element. Applications which lack sufficient details about each project element could lead to a qualified eligibility determination that mandates additional FAA review of project plans for eligible items prior to project implementation or PFC expenditure (see paragraph 5-12(c)).
Eligibility can only be determined by the FAA, therefore, the public agency portion of the Attachment B should not state the eligibility, thereby prejudging the determination.
b. PFC/AIP eligibility. The FAA Airports office will make its eligibility recommendation for items (1) through (4) above based on the latest edition of FAA Order 5100.38, AIP Handbook, as supplemented by PGL's and other guidance. AIP and PFC eligibility of projects is identical for projects within these categories--if it is not AIP eligible, it is not PFC eligible. AIP funding priorities do not affect project eligibility.
Special attention should be given to safety and security projects specified in item (a)(1) above. Section 308, Authority To Use Certain Funds for Airport Security Programs and Activities, of the Federal Aviation Reauthorization Act of 1996 (codified at 49 U.S.C 44901 note) states that "Notwithstanding any other provision of law, funds referred to in subsection (b) may be used for the improvement of facilities and the purchase and deployment of equipment to enhance and ensure the safety and security of passengers and other persons involved in air travel." The referenced subsection (b) includes project grants made under the AIP and application approvals made under the PFC program. The FAA interprets this provision to mean that there is potential AIP or PFC eligibility for some security equipment and facility projects that may not have been formerly eligible under FAA Order 5100.38. However, there are other requirements such as FAA standards for equipment design or FAA standards for whether an airport qualifies for such equipment/facilities, that must be met for eligibility purposes. Therefore, to the extent that a public agency proposes a project that would not otherwise be eligible under FAA Order 5100.38 or other FAA guidance, a determination as to whether the project is an eligible security project should be deferred to APP-510 after coordination with the appropriate Civil Aviation Security Division or Civil Aviation Security Field Office (CASFO) at the regional level, and the Federal Security Manager at selected airports who will consult with the appropriate Headquarters security personnel.
c. Noise eligibility. For item (a)(5) above, noise project eligibility under the PFC program is the same as described in FAA Order 5100.38 except that the project need not be included in an approved Part 150 Noise Compatibility Plan (NCP).
AIP eligible noise projects, which are also PFC eligible, include: projects in an approved Part 150 NCP (but not including costs related to the development of new flight procedures, operational and administrative costs of an airport for ongoing noise mitigation programs, and demonstration programs to test the effectiveness of new noise mitigation technology); and noise insulation projects at public buildings used primarily for educational or medical purposes even if the associated airport does not participate in the Part 150 program. Projects identified in an approved EIS to mitigate the noise impacts of an airport infrastructure project are also eligible for funding as allowable
costs of the infrastructure project under the AIP and PFC. However, the eligibility of these projects is established by the eligibility of the infrastructure project (e.g., capacity) and not on the basis of noise mitigation.
PFC eligible noise projects which are not AIP eligible include any project that would qualify for inclusion in a Part 150 NCP, even though the public agency has not undertaken and/or completed a Part 150 study or the project is not included in an implemented NCP. However, the eligibility of any proposed PFC noise project not in an approved Part 150 NCP must be supported by noise contours, which could be prepared in conjunction with a Part 150 study, airport master plan, environmental assessment, or other suitable planning analysis.
On April 3, 1998, FAA issued the "Final Policy on Part 150 Approval of Noise Mitigation Measures: Effect on the Use of Federal Grants for Noise Mitigation Projects" (Federal Register, Volume 63, Number 64, pp. 16409-16414). Under this policy, the FAA will approve under Part 150 only remedial noise mitigation measures for existing noncompatible development and only preventive noise mitigation measures in areas of potential new non-compatible development. The FAA will not approve remedial noise mitigation measures for new non-compatible development that occurs in the vicinity of airports after the effective date of the final policy even though such remedial projects are technically eligible for inclusion in a Part 150 program. Because the latter projects will not, as a matter of policy, be approved under Part 150, they cannot be AIP funded. However, because they remain technically eligible for inclusion, they remain eligible for PFC funding.
d. Terminal eligibility. PFC eligibility of terminal development projects encompasses and expands upon the types of terminal development eligible under the AIP. AIP eligibility and, consequently, PFC eligibility varies according to the airport hub size.
(1) Hub airports. At large, medium, and small hub primary airports, terminal facilities directly related to the movement of passengers and baggage in air commerce that are not revenue-producing (i.e. multi-modal terminal facilities; public-use areas associated with baggage claim delivery; automated baggage handling equipment; public-use corridors to boarding areas; central waiting rooms; restrooms; holding areas (not exclusively leased to an air carrier); foyers and entryways; and loading bridges are eligible under the AIP program. A flight information display system, which is available for use by all air carriers, is eligible. Under AIP eligibility for hub airports, gates and airline ticketing areas, including passenger check-in facilities and other revenue producing areas are not eligible for AIP funding.
The PFC statute and regulation incorporate AIP eligibility and expand PFC eligibility to include non-concession areas directly related to the movement of passengers and baggage in air commerce regardless of their revenue producing status. Thus, gates, airline ticketing areas, and passenger check-in facilities at hub airports are PFC eligible even though they are not AIP eligible. Because a gate facility cannot function without
the access to passenger and baggage movement services, eligible gate-related areas include ticket counters, incoming and outgoing bag facilities (including baggage makeup areas), and baggage carousels.
Public seating for a food court is not eligible, because the food court seating is a concession facility. The FAA Airports office should consult with APP-530 on the eligibility of any item not covered in the above description.
(2) Expanded eligibility under AIR-21. Section 151 of AIR-21, codified under 49 U.S.C 40117(a)(3)(F), expanded the PFC eligibility of gates and related areas. A project for constructing gates and related areas may include structural foundations and floor systems, exterior building walls and load-bearing interior columns or walls, windows, door and roof systems, building utilities (including heating, air conditioning, ventilation, plumbing, and electrical service), and aircraft fueling facilities adjacent to the gate if the project is required to enable additional air service by an air carrier with less than 50 percent of the annual passenger boardings at an airport. Costs associated with providing the tenant finishes are not eligible.
Section 40117(a)(3)(F) effectively expands eligibility of gates and related areas to include air carrier or airport operations space, concession space, and aircraft fueling facilities directly under or adjacent to a gate and its associated hold room or ticket counter. However, those otherwise ineligible facilities not in the footprint of gates or related areas would not be eligible.
(3) At non-hub primary, non-primary commercial service, and reliever airports, public use terminal development comprising those areas which are eligible at larger hub airports as well as space for gates, airline ticketing areas, passenger check-in areas, restaurants, car rental facilities, and other concessions are AIP eligible regardless of their revenue-producing status. PFC eligibility at these small airports, as well as airports participating in the Military Airport Program, mimics AIP eligibility. However, while the space for concession facilities is eligible, the build-out of the facilities themselves is not.
(4) Terminal operational areas and maintenance. Consistent with AIP provisions, no project in the terminal that is appropriately categorized as operational areas for airports and air carriers, or maintenance, is eligible for PFC funding, subject to the exception created under §40117(a)(3)(F). For example, carpet replacement and painting, as stand-alone projects, are not PFC eligible. However, carpet replacement or painting necessitated by a major eligible project would be eligible as an incidental part of that project.
e. Ground access/Intermodal eligibility. As stated in the Preamble to Part 158, the FAA determines the eligibility and justification for ground access projects, no matter the technology proposed (e.g., road, heavy or light rail, water), on a case-bycase basis after a review of the particulars associated with each unique proposal. In general, an airport access project must be eligible for funding under the AIP and must
Continue reading ↓ 120 of 502 passages shown