H.R. 7613

ALERT Act

Sponsor: Sam Graves

87 cosponsors
Follow this bill

Official summary

Written by the Congressional Research Service.

Airspace Location and Enhanced Risk Transparency Act of 2026 or the ALERT Act

This bill addresses aviation safety by increasing requirements for aircraft tracking and communication using Automatic Dependent Surveillance-Broadcast (ADS-B) technology and expanding oversight. As background, ADS-B for broadcasting (Out) and receiving (In) transmits information (e.g., location and weather) among aircraft and air traffic control (ATC).

The bill requires the Department of Defense (DOD) and the Department of Transportation (DOT) to enter into an agreement regarding the use of collision prevention technologies on DOD aircraft. The agreement must require the use of ADS-B Out as the default practice for DOD helicopters operating in the national airspace, unless such use would affect operational security. For DOD helicopters that are carrying out special missions in the Washington, DC, metropolitan area and are exempt from ADS-B Out transmission requirements, DOD must coordinate with DOT to conduct a safety risk assessment and implement appropriate mitigations.

By December 31, 2031, DOD aircraft (other than certain special mission aircraft) must be equipped with and operating integrated ADS-B In technology.

With respect to civil aircraft, by December 31, 2031, the Federal Aviation Administration (FAA) must generally require aircraft that are currently required to be equipped with ADS-B Out to also be equipped with ADS-B In.

Additionally, among other requirements, the FAA must

  • establish time-on-position limits for supervisory ATC personnel;
  • establish a process to timely notify parties involved in certain near-miss incidents; and
  • evaluate and revise, as necessary, helicopter routes around Ronald Reagan Washington National Airport.

Text of the bill

Expand all

I Civil Aviation Matters

Sec. 123. Notification of close proximity encounters and analysis of data Changed · Apr 9

Where this section came from

  1. Feb 20, 2026 · Introduced in House Referred to House Committee on Transportation and Infrastructure, Feb 20 Referred to House Committee on Armed Services, Feb 20
  2. Apr 9, 2026 · Reported in House Marked up by House Committee on Transportation and Infrastructure, Mar 26 Marked up by House Committee on Armed Services, Mar 26 Reported by House Committee on Transportation and Infrastructure, Apr 9 Reported by House Committee on Armed Services, Apr 9 Committee members' individual votes aren't in our records.
What changed in the text

(a) In general. Not later than 180 days after the date of enactment of this Act, the Administrator, in accordance with the mandatory occurrence reporting requirements in FAA Order JO 7210.632A, title titled Air Traffic Organization Occurrence Reporting (or any successor document ) ), FAA Order 8020.11D, titled Aircraft Accident and airborne Incident loss Notification, of Investigation, separation and minima Reporting in (or any successor document), and FAA Order Advisory JO Circular 7110.65BB AC 90–120 , titled Air Operational Traffic Use Control of Airborne Collision Avoidance Systems (or any successor document), shall establish a process to— (1) notify , with respect to each event, parties involved with — an (A) airborne a loss near of midair separation collision event ; of (B) such a traffic collision avoidance system resolution advisory event; (C) a close proximity encounter, as defined pursuant to section 122; and (D) any other events, as determined by the Administrator; and

… 2 unchanged passages …

(1) establish a database that tracks the details of airborne events loss described of in separation subsection events; (a)(1);

… 2 unchanged passages …

(4) consider informing, with deidentified or aggregated data, other frequent operators in the airspace of loss events of described separation in events; subsection (a)(1); and

… 3 unchanged passages …

(C) traffic airborne alert loss and of collision avoidance system resolution advisory activations separation ; and

… 2 unchanged passages …

(1) air carriers operating under part 121 of title 14, Code of Federal Regulations ; (2) air carriers operating under part 135 of title 14, Code of Federal Regulations; (3) air carriers operating under part 91 of title 14, Code of Federal Regulations; (4) organizations representing helicopter aviation operators and pilots ; ( 3 5 ) organizations representing the general aviation community; (6) organizations representing business aviation operators; ( 4 7 ) organizations representing experimental aircraft operators; (8) organizations representing powered-lift operators; (9) organizations representing certified collective bargaining representatives of airline pilots; ( 5 10 ) the certified exclusive bargaining representatives of air traffic controllers of the Administration certified under section 7111 of title 5, United States Code; ( 6 11 ) FAA subject matter experts, including aviation safety inspectors; and ( 7 12 ) other aviation safety experts determined appropriate by the Administrator.

… 2 unchanged passages …

(1) data on number and location of — airborne (A) loss near of midair separation collision events; (B) traffic collision avoidance system resolution advisory events; and (C) close proximity encounters, as defined pursuant to section 122;

… 3 unchanged passages …

(f) Protection of data.

(1) In general. Data collected in response to subsection (a) shall be used solely for safety assurance and safety risk management.

(2) Consistency with existing safety programs. The Administrator shall ensure consistency with existing voluntary safety programs, including the Aviation Safety Action Program, the Aviation Safety Reporting System, the Air Traffic Safety Action Plan, and flight operational quality assurance programs.

What is a markup?

A markup is a committee meeting where members go through a bill and vote on changes before sending it to the full chamber.

(a) In general. Not later than 180 days after the date of enactment of this Act, the Administrator, in accordance with the mandatory occurrence reporting requirements in FAA Order JO 7210.632A, titled Air Traffic Organization Occurrence Reporting (or any successor document), FAA Order 8020.11D, titled Aircraft Accident and Incident Notification, Investigation, and Reporting (or any successor document), and FAA Advisory Circular AC 90–120, titled Operational Use of Airborne Collision Avoidance Systems (or any successor document), shall establish a process to—

(1) notify, with respect to each event, parties involved with—

(A) a near midair collision event;

(B) a traffic collision avoidance system resolution advisory event;

(C) a close proximity encounter, as defined pursuant to section 122; and

(D) any other events, as determined by the Administrator; and

(2) provide deidentified event data to the Aviation Safety Information Analysis and Sharing program.

(b) Requirements. In establishing the process under subsection (a), the Administrator shall—

(1) establish a database that tracks the details of events described in subsection (a)(1);

(2) continuously monitor and review such database to identify areas of potential traffic conflict for safety assurance and safety risk management;

(3) ensure timeliness of notifications to the parties described in subsection (a)(1) so that relevant data remains available before meaningful safety analysis, reporting, or corrective action is no longer practicable;

(4) consider informing, with deidentified or aggregated data, other frequent operators of events described in subsection (a)(1); and

(5) consider the practicality and usefulness of notification requirements for—

(A) airport surface loss of separation;

(B) loss of separation with terrain or obstacles;

(C) airborne loss of separation; and

(D) any other close proximity encounters as determined by the Administrator.

(c) Consultation. In establishing the process under subsection (a), the Administrator shall consult with—

(1) air carriers operating under part 121 of title 14, Code of Federal Regulations;

(2) air carriers operating under part 135 of title 14, Code of Federal Regulations;

(3) air carriers operating under part 91 of title 14, Code of Federal Regulations;

(4) organizations representing helicopter aviation operators and pilots;

(5) organizations representing the general aviation community;

(6) organizations representing business aviation operators;

(7) organizations representing experimental aircraft operators;

(8) organizations representing powered-lift operators;

(9) organizations representing certified collective bargaining representatives of airline pilots;

(10) the certified exclusive bargaining representatives of air traffic controllers of the Administration certified under section 7111 of title 5, United States Code;

(11) FAA subject matter experts, including aviation safety inspectors; and

(12) other aviation safety experts determined appropriate by the Administrator.

(d) Briefing. Not later than 30 days after establishing the process required under subsection (a), the Administrator shall brief the appropriate committees of Congress on the implementation of this section.

(e) Report. Not later than 1 year after establishing the process required under subsection (a), and annually thereafter, the Administrator shall submit to the appropriate committees of Congress a report containing—

(1) data on number and location of—

(A) near midair collision events;

(B) traffic collision avoidance system resolution advisory events; and

(C) close proximity encounters, as defined pursuant to section 122;

(2) the average time of notification to parties involved in such events;

(3) identified locations of concern or other trends; and

(4) actions taken to mitigate identified risks and reduce such events.

(f) Protection of data

(1) In general. Data collected in response to subsection (a) shall be used solely for safety assurance and safety risk management.

(2) Consistency with existing safety programs. The Administrator shall ensure consistency with existing voluntary safety programs, including the Aviation Safety Action Program, the Aviation Safety Reporting System, the Air Traffic Safety Action Plan, and flight operational quality assurance programs.

II Department of Defense Matters