Amendments
2024—Subsec. (c). [Pub. L. 118–63] substituted “September 30, 2028” for “May 10, 2024” in introductory provisions.
[Pub. L. 118–41] substituted “May 10, 2024,” for “March 8, 2024,” in introductory provisions.
2023—Subsec. (c). [Pub. L. 118–34] substituted “March 8, 2024,” for “December 31, 2023,” in introductory provisions.
[Pub. L. 118–15] substituted “December 31, 2023,” for “September 30, 2023,” in introductory provisions.
2018—Subsec. (c). [Pub. L. 115–254] substituted “2023,” for “2018,” in introductory provisions.
[Pub. L. 115–141] substituted “September 30, 2018,” for “March 31, 2018,” in introductory provisions.
2017—Subsec. (c). [Pub. L. 115–63] substituted “March 31, 2018,” for “September 30, 2017,” in introductory provisions.
2016—Subsec. (c). [Pub. L. 114–190] substituted “September 30, 2017,” for “July 15, 2016,” in introductory provisions.
[Pub. L. 114–141] substituted “July 15, 2016,” for “March 31, 2016,” in introductory provisions.
2015—Subsec. (c). [Pub. L. 114–55] substituted “March 31, 2016,” for “September 30, 2015,” in introductory provisions.
2012—Subsec. (c). [Pub. L. 112–95] substituted “After September 30, 2015,” for “After February 17, 2012,” in introductory provisions.
[Pub. L. 112–91] substituted “February 17, 2012,” for “January 31, 2012,” in introductory provisions.
2011—Subsec. (c). [Pub. L. 112–30] substituted “January 31, 2012,” for “September 16, 2011,” in introductory provisions.
[Pub. L. 112–27] substituted “September 16, 2011,” for “July 22, 2011,” in introductory provisions.
[Pub. L. 112–21] substituted “July 22, 2011,” for “June 30, 2011,” in introductory provisions.
[Pub. L. 112–16] substituted “June 30, 2011,” for “May 31, 2011,” in introductory provisions.
[Pub. L. 112–7] substituted “May 31, 2011,” for “March 31, 2011,” in introductory provisions.
2010—Subsec. (c). [Pub. L. 111–329] substituted “March 31, 2011,” for “December 31, 2010,” in introductory provisions.
[Pub. L. 111–249] substituted “December 31, 2010,” for “September 30, 2010,” in introductory provisions.
[Pub. L. 111–216] substituted “September 30, 2010,” for “August 1, 2010,” in introductory provisions.
[Pub. L. 111–197] substituted “August 1, 2010,” for “July 3, 2010,” in introductory provisions.
[Pub. L. 111–161] substituted “July 3, 2010,” for “April 30, 2010,” in introductory provisions.
[Pub. L. 111–153] substituted “April 30, 2010,” for “March 31, 2010,” in introductory provisions.
2009—Subsec. (c). [Pub. L. 111–116] substituted “March 31, 2010,” for “December 31, 2009,” in introductory provisions.
[Pub. L. 111–69] substituted “December 31, 2009,” for “September 30, 2009,” in introductory provisions.
[Pub. L. 111–12] substituted “September 30, 2009,” for “March 31, 2009,” in introductory provisions.
2008—Subsec. (c). [Pub. L. 110–330] substituted “March 31, 2009,” for “September 30, 2008,” in introductory provisions.
[Pub. L. 110–253] substituted “September 30, 2008,” for “June 30, 2008,” in introductory provisions.
[Pub. L. 110–190] substituted “June 30, 2008,” for “September 30, 2007,” in introductory provisions.
2003—Subsec. (c). [Pub. L. 108–176] substituted “September 30, 2007” for “September 30, 2003” in introductory provisions.
2000—Subsec. (c). [Pub. L. 106–181] substituted “September 30, 2003,” for “September 30, 1999,” in introductory provisions.
1999—Subsec. (c). [Pub. L. 106–59] substituted “September 30, 1999” for “August 6, 1999” in introductory provisions.
[Pub. L. 106–31] substituted “August 6, 1999” for “May 31, 1999” in introductory provisions.
[Pub. L. 106–6] substituted “May” for “March” in introductory provisions.
1998—Subsec. (c). [Pub. L. 105–277] substituted “March 31, 1999” for “September 30, 1998” in introductory provisions.
1996—Subsec. (c). [Pub. L. 104–264] substituted “1998” for “1996” in introductory provisions.
1994—Subsec. (c). [Pub. L. 103–429] reenacted heading without change and amended text generally. Prior to amendment, text read as follows: “After September 30, 1996, the Secretary may not incur obligations under subsection (b) of this section, except for obligations of amounts remaining available after that date under section 47117(b) of this title.”
[Pub. L. 103–305] substituted “After September 30, 1996, the Secretary” for “After September 30, 1993, the Secretary”.
Remote Tower Pilot Program for Rural and Small Communities
[Pub. L. 115–254, div. B, title I, § 161], Oct. 5, 2018, [132 Stat. 3221], as amended by [Pub. L. 118–15, div. B, title II, § 2202](o), Sept. 30, 2023, [137 Stat. 83]; [Pub. L. 118–34, title I, § 102](o), Dec. 26, 2023, [137 Stat. 1114]; [Pub. L. 118–41, title I, § 102](o), Mar. 8, 2024, [138 Stat. 22]; [Pub. L. 118–63, title VI, § 621(d)], May 16, 2024, [138 Stat. 1237], provided that:“(a)
Pilot Program.—
“(1)
Establishment.—
The Administrator of the Federal Aviation Administration shall establish—
“(A)
in consultation with airport operators and other aviation stakeholders, a pilot program at public-use airports to construct and operate remote towers in order to assess their operational benefits;
“(B)
a selection process for participation in the pilot program; and
“(C)
a clear process for the safety and operational certification of the remote towers.
“(2)
Safety considerations.—
“(A)
Safety risk management panel.—
Prior to the operational use of a remote tower under the pilot program established in subsection (a), the Administrator shall convene a safety risk management panel for the tower to address any safety issues with respect to the tower. The panels shall be created and utilized in a manner similar to that of the safety risk management panels previously convened for remote towers and shall take into account existing best practices and operational data from existing remote towers in the United States.
“(B)
Consultation.—
In establishing the pilot program, the Administrator shall consult with operators of remote towers in the United States and foreign countries to design the pilot program in a manner that leverages as many safety and airspace efficiency benefits as possible.
“(3)
Applications.—
The operator of an airport seeking to participate in the pilot program shall submit to the Administrator an application that is in such form and contains such information as the Administrator may require.
“(4)
Program design.—
In designing the pilot program, the Administrator shall—
“(A)
to the maximum extent practicable, ensure that at least 2 different vendors of remote tower systems participate;
“(B)
identify which air traffic control information and data will assist the Administrator in evaluating the feasibility, safety, costs, and benefits of remote towers;
“(C)
implement processes necessary to collect the information and data identified in subparagraph (B);
“(D)
develop criteria, in addition to considering possible selection criteria in paragraph (5), for the selection of airports that will best assist the Administrator in evaluating the feasibility, safety, costs, and benefits of remote towers, including the amount and variety of air traffic at an airport; and
“(E)
prioritize the selection of airports that can best demonstrate the capabilities and benefits of remote towers, including applicants proposing to operate multiple remote towers from a single facility.
“(5)
Selection criteria for consideration.—
In selecting airports for participation in the pilot program, the Administrator, after consultation with representatives of labor organizations representing operators and employees of the air traffic control system, shall consider for participation in the pilot program—
“(B)
3 airports that are not primary airports and that do not have existing air traffic control towers;
“(C)
1 airport that participates in the Contract Tower Program; and
“(D)
1 airport selected at the discretion of the Administrator.
“(6)
Data.—
The Administrator shall clearly identify and collect air traffic control information and data from participating airports that will assist the Administrator in evaluating the feasibility, safety, costs, and benefits of remote towers.
“(7)
Report.—
Not later than 1 year after the date the first remote tower is operational, and annually thereafter, the Administrator shall submit to the appropriate committees of Congress [Committee on Commerce, Science, and Transportation of the Senate and Committee on Transportation and Infrastructure of the House of Representatives] a report—
“(A)
detailing any benefits, costs, or safety improvements associated with the use of the remote towers; and
“(B)
evaluating the feasibility of using remote towers, particularly in the Contract Tower Program, for airports without an air traffic control tower, to improve safety at airports with towers, or to reduce costs without impacting safety at airports with or without existing towers.
“(8)
Deadline.—
Not later than 1 year after the date of enactment of this Act [Oct. 5, 2018], the Administrator shall select airports for participation in the pilot program.
“(9)
Definitions.—
In this subsection:
“(A)
Contract tower program.—
The term ‘Contract Tower Program’ has the meaning given the term in
section 47124(e) of title 49, United States Code, as added by this Act.
“(B)
Remote tower.—
The term ‘remote tower’ means a remotely operated air navigation facility, including all necessary system components, that provides the functions and capabilities of an air traffic control tower whereby air traffic services are provided to operators at an airport from a location that may not be on or near the airport.
“(C)
Other definitions.—
The terms ‘nonhub airport’, ‘primary airport’, and ‘public-use airport’ have the meanings given such terms in
section 47102 of title 49, United States Code.
“(10)
Sunset.—
This subsection, including the report required under paragraph (8), shall not be in effect after September 30, 2028.
“(b)
Remote Tower Program.—
Concurrent with the establishment of the process for safety and operational certification of remote towers under subsection (a)(1)(C), the Administrator shall establish a process to authorize the construction and commissioning of additional remote towers that are certificated under subsection (a)(1)(C) at other airports.
“(c)
AIP Funding Eligibility.—
For purposes of the pilot program under subsection (a), and after certificated remote towers are available under subsection (b), constructing a remote tower or acquiring and installing air traffic control, communications, or related equipment specifically for a remote tower shall be considered airport development (as defined in
section 47102 of title 49, United States Code) for purposes of subchapter I of chapter 471 of that title if the components are installed and used at the airport, except, as needed, for off-airport sensors installed on leased towers.”