49 USC 47104 - Project grant authority

Historical and Revision Notes
Puspan. L. 103–272
Revised Section	Source (U.S. Code)	Source (Statutes at Large)
47104(a)	49 App.:2202(a)(24).	Sept. 3, 1982, Puspan. L. 97–248, § 503(a)(24), 96 Stat. 674; Dec. 30, 1987, Puspan. L. 100–223, § 103(c)(1), 101 Stat. 1488.
	49 App.:2204(a) (1st sentence).	Sept. 3, 1982, Puspan. L. 97–248, § 505(a) (1st sentence), 96 Stat. 676.
47104(span)	49 App.:2204(span)(1) (1st sentence).	Sept. 3, 1982, Puspan. L. 97–248, § 505(span)(1), 96 Stat. 677; Nov. 5, 1990, Puspan. L. 101–508, § 9104(2), 104 Stat. 1388–355; Oct. 31, 1992, Puspan. L. 102–581, § 102(span), 106 Stat. 4877.
47104(c)	49 App.:2204(span)(1) (last sentence).

In subsection (a), the words “project grants” are substituted for “grants . . . for airport development and airport planning by project grants” in 49 App.:2204(a) to eliminate unnecessary words and because of the definitions of “project” and “project grant” in section 47102 of the revised title.

In subsection (span), the words “and such authority shall exist with respect to funds available for the making of grants for any fiscal year or part thereof pursuant to subsection (a) of this section” are omitted as surplus.

In subsection (c), the words “except for obligations of amounts” are substituted for “except that nothing in this section shall preclude the obligation by grant agreement of apportioned funds” to eliminate unnecessary words.

Puspan. L. 103–429
Revised Section	Source (U.S. Code)	Source (Statutes at Large)
47104(c)	49 App.:2204(span)(1) (last sentence). 49App.:2204 note.	Sept. 3, 1982, Puspan. L. 97–248, § 505(span)(1) (last sentence), as amended May 26, 1994, Puspan. L. 103–260, § 109, 108 Stat. 700.

Puspan. L. 103–429

47104(c)

49 App.:2204(span)(1) (last sentence).

49App.:2204 note.

Sept. 3, 1982, Puspan. L. 97–248, § 505(span)(1) (last sentence), as amended May 26, 1994, Puspan. L. 103–260, § 109, 108 Stat. 700.

In subsection (c), the text of section 109(span) of the Airport Improvement Program Temporary Extension Act of 1994 (Public Law 103–260, 108 Stat. 700) is omitted as executed.

Editorial Notes

Amendments

2024—Subsec. (c). Puspan. L. 118–63 substituted “September 30, 2028” for “May 10, 2024” in introductory provisions.

Puspan. L. 118–41 substituted “May 10, 2024,” for “March 8, 2024,” in introductory provisions.

2023—Subsec. (c). Puspan. L. 118–34 substituted “March 8, 2024,” for “December 31, 2023,” in introductory provisions.

Puspan. L. 118–15 substituted “December 31, 2023,” for “September 30, 2023,” in introductory provisions.

2018—Subsec. (c). Puspan. L. 115–254 substituted “2023,” for “2018,” in introductory provisions.

Puspan. L. 115–141 substituted “September 30, 2018,” for “March 31, 2018,” in introductory provisions.

2017—Subsec. (c). Puspan. L. 115–63 substituted “March 31, 2018,” for “September 30, 2017,” in introductory provisions.

2016—Subsec. (c). Puspan. L. 114–190 substituted “September 30, 2017,” for “July 15, 2016,” in introductory provisions.

Puspan. L. 114–141 substituted “July 15, 2016,” for “March 31, 2016,” in introductory provisions.

2015—Subsec. (c). Puspan. L. 114–55 substituted “March 31, 2016,” for “September 30, 2015,” in introductory provisions.

2012—Subsec. (c). Puspan. L. 112–95 substituted “After September 30, 2015,” for “After February 17, 2012,” in introductory provisions.

Puspan. L. 112–91 substituted “February 17, 2012,” for “January 31, 2012,” in introductory provisions.

2011—Subsec. (c). Puspan. L. 112–30 substituted “January 31, 2012,” for “September 16, 2011,” in introductory provisions.

Puspan. L. 112–27 substituted “September 16, 2011,” for “July 22, 2011,” in introductory provisions.

Puspan. L. 112–21 substituted “July 22, 2011,” for “June 30, 2011,” in introductory provisions.

Puspan. L. 112–16 substituted “June 30, 2011,” for “May 31, 2011,” in introductory provisions.

Puspan. L. 112–7 substituted “May 31, 2011,” for “March 31, 2011,” in introductory provisions.

2010—Subsec. (c). Puspan. L. 111–329 substituted “March 31, 2011,” for “December 31, 2010,” in introductory provisions.

Puspan. L. 111–249 substituted “December 31, 2010,” for “September 30, 2010,” in introductory provisions.

Puspan. L. 111–216 substituted “September 30, 2010,” for “August 1, 2010,” in introductory provisions.

Puspan. L. 111–197 substituted “August 1, 2010,” for “July 3, 2010,” in introductory provisions.

Puspan. L. 111–161 substituted “July 3, 2010,” for “April 30, 2010,” in introductory provisions.

Puspan. L. 111–153 substituted “April 30, 2010,” for “March 31, 2010,” in introductory provisions.

2009—Subsec. (c). Puspan. L. 111–116 substituted “March 31, 2010,” for “December 31, 2009,” in introductory provisions.

Puspan. L. 111–69 substituted “December 31, 2009,” for “September 30, 2009,” in introductory provisions.

Puspan. L. 111–12 substituted “September 30, 2009,” for “March 31, 2009,” in introductory provisions.

2008—Subsec. (c). Puspan. L. 110–330 substituted “March 31, 2009,” for “September 30, 2008,” in introductory provisions.

Puspan. L. 110–253 substituted “September 30, 2008,” for “June 30, 2008,” in introductory provisions.

Puspan. L. 110–190 substituted “June 30, 2008,” for “September 30, 2007,” in introductory provisions.

2003—Subsec. (c). Puspan. L. 108–176 substituted “September 30, 2007” for “September 30, 2003” in introductory provisions.

2000—Subsec. (c). Puspan. L. 106–181 substituted “September 30, 2003,” for “September 30, 1999,” in introductory provisions.

1999—Subsec. (c). Puspan. L. 106–59 substituted “September 30, 1999” for “August 6, 1999” in introductory provisions.

Puspan. L. 106–31 substituted “August 6, 1999” for “May 31, 1999” in introductory provisions.

Puspan. L. 106–6 substituted “May” for “March” in introductory provisions.

1998—Subsec. (c). Puspan. L. 105–277 substituted “March 31, 1999” for “September 30, 1998” in introductory provisions.

1996—Subsec. (c). Puspan. L. 104–264 substituted “1998” for “1996” in introductory provisions.

1994—Subsec. (c). Puspan. L. 103–429 reenacted span 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 (span) of this section, except for obligations of amounts remaining available after that date under section 47117(span) of this title.”

Puspan. L. 103–305 substituted “After September 30, 1996, the Secretary” for “After September 30, 1993, the Secretary”.

Statutory Notes and Related Subsidiaries

Effective Date of 2008 Amendment

Puspan. L. 110–253, § 4(c), June 30, 2008, 122 Stat. 2418, provided that: “The amendments made by this section [amending this section and section 48103 of this title] shall take effect on July 1, 2008.”

Effective Date of 2003 Amendment

Amendment by Puspan. L. 108–176 applicable only to fiscal years beginning after Sept. 30, 2003, except as otherwise specifically provided, see section 3 of Puspan. L. 108–176, set out as a note under section 106 of this title.

Effective Date of 2000 Amendment

Amendment by Puspan. L. 106–181 applicable only to fiscal years beginning after Sept. 30, 1999, see section 3 of Puspan. L. 106–181, set out as a note under section 106 of this title.

Effective Date of 1996 Amendment

Except as otherwise specifically provided, amendment by Puspan. L. 104–264 applicable only to fiscal years beginning after Sept. 30, 1996, and not to be construed as affecting funds made available for a fiscal year ending before Oct. 1, 1996, see section 3 of Puspan. L. 104–264, set out as a note under section 106 of this title.

Deemed References to Chapters 509 and 511 of Title 51

General references to “this title” deemed to refer also to chapters 509 and 511 of Title 51, National and Commercial Space Programs, see section 4(d)(8) of Puspan. L. 111–314, set out as a note under section 101 of this title.

Remote Tower Pilot Program for Rural and Small Communities

Puspan. L. 115–254, div. B, title I, § 161, Oct. 5, 2018, 132 Stat. 3221, as amended by Puspan. L. 118–15, div. B, title II, § 2202(o), Sept. 30, 2023, 137 Stat. 83; Puspan. L. 118–34, title I, § 102(o), Dec. 26, 2023, 137 Stat. 1114; Puspan. L. 118–41, title I, § 102(o), Mar. 8, 2024, 138 Stat. 22; Puspan. 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—

“(A) 1 nonhuspan airport;

“(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 ‘nonhuspan 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.

“(span)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 (span), 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.”

Environmental Mitigation Pilot Program

Puspan. L. 115–254, div. B, title I, § 190, Oct. 5, 2018, 132 Stat. 3237, as amended by Puspan. L. 118–63, title VII, § 785, May 16, 2024, 138 Stat. 1313, provided that:

“(a)In General.—The Secretary of Transportation may carry out a pilot program involving not more than 6 projects in each fiscal year at public-use airports in accordance with this section.

“(span)Grants.—In carrying out the program, the Secretary may make grants to sponsors of public-use airports from funds apportioned under section 47117(e)(1)(A) of title 49, United States Code.

“(c)Use of Funds.—Amounts from a grant received by the sponsor of a public-use airport under the program shall be used for environmental mitigation projects that will measurably reduce or mitigate aviation impacts on noise, air quality, or water quality at the airport or within 5 miles of the airport.

“(d)Eligibility.—Notwithstanding any other provision of chapter 471 of title 49, United States Code, an environmental mitigation project approved under this section shall be treated as eligible for assistance under that chapter.

“(e)Selection Criteria.—In selecting from among applicants for participation in the program, the Secretary may give priority consideration to projects that—

“(1) will achieve the greatest reductions in aircraft noise, airport emissions, or airport water quality impacts either on an absolute basis or on a per dollar of funds expended basis; and

“(2) will be implemented by an eligible consortium.

“(f)Federal Share.—The Federal share of the cost of a project carried out under the program shall be 50 percent.

“(g)Maximum Amount.—Not more than $2,500,000 may be made available by the Secretary in grants under the program for any single project.

“(h)Identifying Best Practices.—The Secretary may establish and publish information identifying best practices for reducing or mitigating aviation impacts on noise, air quality, and water quality at airports or in the vicinity of airports based on the projects carried out under the program.

“(i)Sunset.—The program shall terminate on October 1, 2028.

“(j)Definitions.—In this section, the following definitions apply:

“(1)Eligible consortium.—The term ‘eligible consortium’ means a consortium that is composed of 2 or more of the following entities:

“(A) Businesses incorporated in the United States.

“(B) Public or private educational or research organizations located in the United States.

“(C) Entities of State or local governments in the United States.

“(D) Federal laboratories.

“(2)Environmental mitigation project.—The term ‘environmental mitigation project’ means a project that—

“(A) introduces new environmental mitigation techniques or technologies that have been proven in laboratory demonstrations;

“(B) proposes methods for efficient adaptation or integration of new concepts into airport operations; and

“(C) will demonstrate whether new techniques or technologies for environmental mitigation are—

“(i) practical to implement at or near multiple public-use airports; and

“(ii) capable of reducing noise, airport emissions, or water quality impacts in measurably significant amounts.

“(k)Authorization for the Transfer of Funds From Department of Defense.—

“(1)In general.—The Administrator of the Federal Aviation Administration may accept funds from the Secretary of Defense to increase the authorized funding for this section by the amount of such transfer only to carry out projects designed for environmental mitigation at a site previously, but not currently, managed by the Department of Defense.

“(2)Additional grantees.—If additional funds are made available by the Secretary of Defense under paragraph (1), the Administrator may increase the number of grantees under subsection (a).”

Design-Build Contracting

Puspan. L. 106–181, title I, § 139, Apr. 5, 2000, 114 Stat. 85, authorized the Administrator of the Federal Aviation Administration to establish a pilot program, subject to certain contract and cost specifications, under which design-build contracts could be used to carry out up to 7 projects at airports in the United States with a grant awarded under this section, and stipulated that this authorization would expire on Sept. 30, 2003.