767 

Federal Aviation Administration, DOT 

§ 158.30 

(ii) A description of how this project 

meets one of the PFC objectives in 
§ 158.15(a), and 

(iii) A description of how this project 

meets the adequate justification re-
quirement in § 158.15(c). 

(4) A copy of any comments received 

by the public agency during the air 
carrier consultation and public com-
ment processes (§§ 158.23 and 158.24) and 
the public agency’s response to any dis-
agreements. 

(5) If applicable, a request to exclude 

a class of carriers from the require-
ment to collect the PFC (§ 158.11). 

(6) A signed statement certifying 

that the public agency will comply 
with the assurances set forth in Appen-
dix A to this part. 

(7) Any additional information the 

Administrator may require. 

(c) 

Notice of intent to use PFC revenue. 

A public agency may use PFC revenue 
only for projects included in notices 
filed under this paragraph or approved 
under § 158.29. This paragraph sets forth 
the information that a public agency 
must file, unless otherwise authorized 
by the Administrator, in its notice of 
intent to use PFC revenue to finance 
specific projects under this section. 

(1) A notice of intent to use PFC rev-

enue filed concurrently with a notice of 
intent to impose a PFC must include: 

(i) The information required under 

paragraphs (b)(1) through (7) of this 
section; 

(ii) A completed FAA Form 5500–1, 

Attachment G, Airport Layout Plan, 
Airspace, and Environmental Findings 
(latest edition) for all projects not in-
cluded in an existing Federal airport 
program grant. 

(2) A notice of intent to use PFC rev-

enue where the FAA has previously ac-
knowledged a notice of intent to im-
pose a PFC must: 

(i) Be preceded by further consulta-

tion with air carriers and the oppor-
tunity for public comment under 
§§ 158.23 and 158.24 of this part. How-
ever, a meeting with the air carriers is 
optional if all information is the same 
as that provided with the impose au-
thority notice; 

(ii) Include a copy of any comments 

received by the public agency during 
the air carrier consultation and public 
comment processes (§§ 158.23 and 158.24) 

and the public agency’s response to any 
disagreements or negative comments; 
and 

(iii) Include any updated and changed 

information: 

(A) Required by paragraphs (b)(1), (2), 

(5), (6), and (7) of this section; and 

(B) Required by paragraph (c)(1)(ii) of 

this section. 

(d) 

FAA review of notices of intent. 

(1) 

The FAA will review the notice of in-
tent to determine that: 

(A) The amount and duration of the 

PFC will not result in revenue that ex-
ceeds the amount necessary to finance 
the project(s); 

(B) Each proposed project meets the 

requirements of § 158.15; 

(C) Each project proposed at a PFC 

level above $3.00 meets the require-
ments of § 158.17(a)(2) and (3); 

(D) All applicable airport layout 

plan, airspace, and environmental re-
quirements have been met for each 
project; 

(E) Any request by the public agency 

to exclude a class of carriers from the 
requirement to collect the PFC is rea-
sonable, not arbitrary, nondiscrim-
inatory, and otherwise complies with 
the law; and 

(F) The consultation and public com-

ment processes complied with §§ 158.23 
and 158.24. 

(2) The FAA will also make a deter-

mination regarding the public agency’s 
compliance with 49 U.S.C. 47524 and 
47526 governing airport noise and ac-
cess restrictions and 49 U.S.C. 47107(b) 
governing the use of airport revenue. 
Finally, the FAA will review all com-
ments filed during the air carrier con-
sultation and public comment proc-
esses. 

(e) 

FAA acknowledgment of notices of 

intent. 

Within 30 days of receipt of the 

public agency’s notice of intent about 
its PFC program, the FAA will issue a 
written acknowledgment of the public 
agency’s notice. The FAA’s acknowl-
edgment may concur with all proposed 
projects, may object to some or all pro-
posed projects, or may object to the no-
tice of intent in its entirety. The 
FAA’s acknowledgment will include 
the reason(s) for any objection(s). 

VerDate Sep<11>2014 

08:20 May 17, 2019

Jkt 247048

PO 00000

Frm 00777

Fmt 8010

Sfmt 8010

Y:\SGML\247048.XXX

247048