ALLcrimesfood&drugstaxestelecomcommercehealthconservationtransportationagricultureveteransbrowse all titles »
0

49 U.S.C. § 44810Airport safety and airspace hazard mitigation and enforcement

submitted 8 years ago by Pub. L. 115-254 to r/title-49-TRANSPORTATION · 664 words · no verdicts yet

in plain englishAI-generated · not legal advice

The FAA must work with other agencies to test drone-detection technology without harming airport safety. It must run detection and mitigation programs at five airports and let airports later buy approved equipment with grant money. This section ends on September 30, 2028.

(a) Coordination. The FAA must work with the Secretary of Defense, the Secretary of Homeland Security, and other federal agencies so that technology built to detect and stop dangerous or hostile drones does not hurt safe airport operations, navigation, air traffic services, or the national airspace system. (b) Plan. (1) In general: the FAA must build a plan for certifying, permitting, authorizing, or allowing the deployment of drone detection and mitigation technology. (2) Contents: the plan must set policies, procedures, or protocols letting FAA officials use that technology to detect and reduce drone safety risks. (3) Aviation rulemaking committee: the FAA must charter a committee to recommend the plan and any needed standards for the technology; the Federal Advisory Committee Act does not apply to this committee. (4) Non-delegation: the plan cannot hand off the FAA's authority under this section to other federal, state, local, tribal, or territorial agencies, or to an airport sponsor. (c) Airspace Hazard Mitigation Program. To test and evaluate this technology, the FAA must deploy it at 5 airports — including one ranked in the FAA's top 10 for passenger boardings — plus any other location the FAA chooses. (d) Authority. During the testing in subsection (c), the FAA may use the detection and mitigation systems to detect and stop unauthorized drone flights that risk aviation safety. (e) AIP Funding Eligibility. Once such technology is certified, permitted, authorized, or allowed after successful testing, an airport sponsor may apply for an Airport Improvement Program grant under subchapter I of chapter 471 to buy a detection and mitigation system; buying one counts as "airport development" under section 47102. (f) Briefing. The FAA must brief the relevant congressional committees every year, including the House and Senate Judiciary Committees, on how this section is being carried out. (g) Applicability of Other Laws. Several federal laws — the hijacking statute (section 46502), the Aircraft Sabotage Act, the Computer Fraud and Abuse Act, the Wiretap Act, and the Pen/Trap Statute — do not apply to activities the FAA authorizes under subsections (c) and (d). (h) Sunset. This section stops being effective on September 30, 2028. (i) Non-delegation. The FAA cannot delegate its authority under this section to other federal, state, local, tribal, or territorial agencies, or to an airport sponsor. The FAA may still partner with other federal agencies, subject to any limits those agencies have on their own counter-drone authority.
the actual law source: uscode.house.gov ↗public domain
(a)Coordination.—

The Administrator of the Federal Aviation Administration shall work with the Secretary of Defense, the Secretary of Homeland Security, and the heads of other relevant Federal departments and agencies for the purpose of ensuring that technologies or systems that are developed, tested, or deployed by Federal departments and agencies to detect and mitigate potential risks posed by errant or hostile unmanned aircraft system operations do not adversely impact or interfere with safe airport operations, navigation, air traffic services, or the safe and efficient operation of the national airspace system.

(b)Plan.—
(1)In general.—

The Administrator shall develop a plan for the certification, permitting, authorizing, or allowing of the deployment of technologies or systems for the detection and mitigation of unmanned aircraft systems.

(2)Contents.—

The plan shall provide for the development of policies, procedures, or protocols that will allow appropriate officials of the Federal Aviation Administration to utilize such technologies or systems to take steps to detect and mitigate potential airspace safety risks posed by unmanned aircraft system operations.

(3)Aviation rulemaking committee.—

The Administrator shall charter an aviation rulemaking committee to make recommendations for such a plan and any standards that the Administrator determines may need to be developed with respect to such technologies or systems. The Federal Advisory Committee Act (5 U.S.C. App.) 1 shall not apply to an aviation rulemaking committee chartered under this paragraph.

(4)Non-delegation.—

The plan shall not delegate any authority granted to the Administrator under this section to other Federal, State, local, territorial, or tribal agencies, or an airport sponsor, as defined in section 47102 of title 49, United States Code.

(c)Airspace Hazard Mitigation Program.—

In order to test and evaluate technologies or systems that detect and mitigate potential aviation safety risks posed by unmanned aircraft, the Administrator shall deploy such technologies or systems at 5 airports, including 1 airport that ranks in the top 10 of the FAA’s most recent Passenger Boarding Data, and any other location the Administrator determines appropriate.

(d)Authority.—

Under the testing and evaluation in subsection (c), the Administrator shall use unmanned aircraft detection and mitigation systems to detect and mitigate the unauthorized operation of an unmanned aircraft that poses a risk to aviation safety.

(e)Aip Funding Eligibility.—

Upon the certification, permitting, authorizing, or allowing of such technologies and systems that have been successfully tested under this section, an airport sponsor may apply for a grant under subchapter I of chapter 471 to purchase an unmanned aircraft detection and mitigation system. For purposes of this subsection, purchasing an unmanned aircraft detection and mitigation system shall be considered airport development (as defined in section 47102).

(f)Briefing.—

The Administrator shall annually brief the appropriate committees of Congress, including the Committee on Judiciary 2 of the House of Representatives and the Committee on the Judiciary of the Senate, on the implementation of this section.

(g)Applicability of Other Laws.—

Section 46502 of this title, section 32 of title 18, United States Code (commonly known as the Aircraft Sabotage Act), section 1031 of title 18, United States Code (commonly known as the Computer Fraud and Abuse Act of 1986),1 sections 2510–2522 of title 18, United States Code (commonly known as the Wiretap Act), and sections 3121–3127 of title 18, United States Code (commonly known as the Pen/Trap Statute), shall not apply to activities authorized by the Administrator pursuant to subsection 3 (c) and (d).

(h)Sunset.—

This section ceases to be effective September 30, 2028.

(i)Non-delegation.—

The Administrator shall not delegate any authority granted to the Administrator under this section to other Federal, State, local, territorial, or tribal agencies, or an airport sponsor, as defined in section 47102 of title 49, United States Code. The Administrator may partner with other Federal agencies under this section, subject to any restrictions contained in such agencies’ authority to operate counter unmanned aircraft systems.

Source credit: (Added Pub. L. 115–254, div. B, title III, § 383(a), Oct. 5, 2018, 132 Stat. 3321; amended Pub. L. 118–15, div. B, title II, § 2202(d), Sept. 30, 2023, 137 Stat. 83; Pub. L. 118–34, title I, § 102(d), Dec. 26, 2023, 137 Stat. 1113; Pub. L. 118–41, title I, § 102(d), Mar. 8, 2024, 138 Stat. 21; Pub. L. 118–63, title IX, § 904, May 16, 2024, 138 Stat. 1341.)

history & why it existsrecord from the source credit
  • 2018Enacted · Pub. L. 115-254 · 132 Stat. 3321
  • 2023Amended · Pub. L. 118-15 · 137 Stat. 83
  • 2023Amended · Pub. L. 118-34 · 137 Stat. 1113
  • 2024Amended · Pub. L. 118-41 · 138 Stat. 21
  • 2024Amended · Pub. L. 118-63 · 138 Stat. 1341

A history note hasn’t been published yet. The record shows enactment by Pub. L. 115-254 on 2018-10-05.

all 0 arguments · sorted by: best

0/280

no arguments yet — make the first case