Background and Need for Legislation
On January 29, 2025, American Airlines Flight 5342 departed
from Dwight D. Eisenhower National Airport (ICT) in Wichita,
Kansas to Ronald Reagan Washington National Airport (DCA). Air
traffic controllers at DCA instructed American Airlines Flight
5342 to land on runway 33. While on final approach, an Army UH-
60 ``Black Hawk'' helicopter collided with American Airlines
Flight 5342 resulting in both aircraft impacting the Potomac
River. The two pilots, two flight attendants, the 60 passengers
onboard the airplane, and three crew members on the
helicopter--67 people--tragically died. This mid-air collision
was the deadliest aviation accident in the United States since
2001. Immediately following the collision, Federal authorities,
alongside state and local first responders from Maryland,
Virginia, and Washington, D.C., launched an aggressive search
and rescue mission on the Potomac River. Furthermore, the
National Transportation Safety Board (NTSB) launched an
immediate investigation into the collision to determine the
probable cause, contributing factors and findings, and issue
recommendations to the appropriate Federal agencies.
On March 7, 2025, the NTSB issued an urgent recommendation
report containing two urgent recommendations on mitigating the
risk of mid-air collisions at DCA.\1\ The NTSB's urgent safety
recommendations cautioned the Federal Aviation Administration
(FAA) to prohibit operations on helicopter Route 4 between
Hains Point and the Wilson Bridge while Runways 15/33 were
being used at DCA.\2\ The NTSB successfully closed this urgent
recommendation, determining the FAA's response ``exceeded
recommendation action'' on May 2, 2025.\3\ Additionally, the
NTSB cautioned the FAA to designate an alternative helicopter
route that could be used to facilitate travel between Hains
Point and the Wilson Bridge when that segment of helicopter
Route 4 was closed.\4\ To date, the NTSB classifies this urgent
safety recommendation as ``open-acceptable response.''\5\
Following the NTSB's urgent safety recommendations, the FAA
took immediate action to improve safety around DCA, including
by: (1) permanently restricting non-essential helicopter
operations around DCA and eliminating helicopter and fixed-wing
mixed traffic, (2) permanently closing helicopter Route 4
between Hains Point and the Wilson Bridge and evaluated
alternative helicopter routes, (3) keeping traffic at specific
distances from fixed-wing aircraft in the event a helicopter
needed to transit through the airspace on an urgent mission
(e.g., lifesaving medical evacuations, priority law enforcement
missions, or Presidential transport), (4) prohibiting the
simultaneous use of Runways 15/33 and 4/22 when helicopters are
conducting those urgent missions around DCA airspace, and (5)
limiting the use of visual separation to certain Coast Guard,
Marine Corps, and Park Police helicopter operations outside of
the restricted airspace.\6\ Additionally, the FAA conducted a
deeper analysis of other airports in the National Airspace
System (NAS) with high volumes of mixed traffic operations,
utilizing machine learning and language modeling.\7\
---------------------------------------------------------------------------
\1\Nat'l transp. safety board, deconflict airplane and helicopter
traffic in the vicinity of Ronald Reagan Washington national airport
(2025), available at https://www.ntsb.gov/investigations/
AccidentReports/Reports/AIR2501.pdf. [hereinafter Urgent Safety
Recommendations].
\2\Id.
\3\nat'l transp. safety board, Safety Recommendation A-25-001 (last
updated May 2, 2025), available at https://data.ntsb.gov/carol-main-
public/sr-details/A-25-001.
\4\Urgent Safety Recommendations, supra note 1.
\5\nat'l transp. safety board, Safety Recommendation A-25-002 (last
updated March 11, 2025), available at https://data.ntsb.gov/carol-main-
public/sr-details/A-25-002.
\6\Press Release, FAA, FAA Statement on NTSB Recommendations for
DCA (March 14, 2025), available at https://www.faa.gov/newsroom/faa-
statement-ntsb-recommendations-dca.
\7\Id.
---------------------------------------------------------------------------
During the NTSB's Board meeting on January 27, 2026, the
Board adopted a final report, which was subsequently published
on February 17, 2026, that contained the probable cause of the
collision, findings, and 50 new safety recommendations.\8\ Of
the 50 safety recommendations: 33 recommendations were directed
to the FAA, eight recommendations were directed to the United
States Army, five recommendations were directed to the
Department of Defense's (DoD's) Policy Board on Federal
Aviation, two recommendations were directed to the Department
of Transportation (DOT), one recommendation was directed to the
DOT Office of Inspector General, and one recommendation was
directed to the Radio Technical Commission for Aeronautics
(RTCA) Program Management Committee.\9\
---------------------------------------------------------------------------
\8\nat'l transp. safety board, midair collision over the Potomac
river PSA airlines flight 5342, Mitsubishi heavy industries (mhi) rj
aviation cl-600-2C10 (crj700), and u.s. army priority air transport
flight 25, sikorsky uh-60l (2026), available at https://www.ntsb.gov/
investigations/AccidentReports/Reports/AIR2602.pdf. [hereinafter Final
Report].
\9\Id.
---------------------------------------------------------------------------
In the final report, the NTSB determined that the probable
cause of the collision was primarily the FAA's placement of
helicopter Route 4 near the runway approach path, the FAA's
failure to regularly review helicopter routes and available
data, and the overreliance on visual separation. Causal factors
were determined to be ineffective application of the see-and-
avoid concept within visual separation procedures, air traffic
controllers' loss of situational awareness and high workload,
lack of alerts to both flight crews, and the helicopter crew's
lack of awareness of their altimeter tolerances.\10\
Additionally, the Board identified contributing factors which
included: (1) the limitations of traffic awareness, collision
avoidance technology, and alerts, (2) an unsustainable aircraft
arrival rate at DCA, (3) the Army's inadequate safety
management system (SMS), (4) the FAA's failure to fully
integrate SMS, and (5) the absence of effective data sharing
among the FAA, aircraft operators, and others.\11\ The
culmination of the NTSB's year-long investigation revealed the
need for systemic reform across several areas of aviation
safety, including: enhancing situational awareness for flight
crews and air traffic controllers, improving helicopter route
safety and separation around airports, improving air traffic
control processes and procedures, addressing the shortcomings
in the FAA's and Army's safety culture and data sharing
mechanisms, reducing conflict in and around the airspace of
DCA, and overhauling cooperation between the military and the
FAA.
---------------------------------------------------------------------------
\10\Id.
\11\Id.
---------------------------------------------------------------------------
To advance adoption of NTSB's safety recommendations, on
February 20, 2026, the leaders of the House Committee on
Transportation and Infrastructure and House Committee on Armed
Services introduced the Airspace Location and Enhanced Risk
Transparency Act of 2026 (ALERT Act).\12\ The ALERT Act, as
amended, is a comprehensive package that addresses all 50
safety recommendations issued by the NTSB in its final
report.\13\ Specifically, the ALERT Act takes important steps
to improve safety throughout the NAS by ensuring civil aircraft
are equipped and operating with technology to enhance flight
crew alerting and controller situational awareness, requiring
updates to helicopter route safety and separation requirements,
requiring updates to air traffic control processes and
procedures to promote safety, investigating the shortcomings in
safety culture and data sharing at the FAA and the DoD,
strengthening safety standards for military aircraft and
enhancing cooperation between the FAA and the DoD, enhancing
the requirements and guidance for collision avoidance
technology for military aircraft operating in the NAS, and
requiring flight data sharing between the FAA and the DoD.\14\
---------------------------------------------------------------------------
\12\ALERT Act, H.R. 7613, 119th Cong. (2026). [hereinafter ALERT].
\13\NTSB Safety Analysis, Nat'l Transp. Safety Board, Analysis of
H.R. 7613 ALERT Act, Titles I & II: A Side-by-Side Review of Amendment
in the Nature of a Substitute (ANS) to H.R. 7613 (ALERT Act), as posted
Mar. 24, 2026, compared with NTSB Safety Recommendations from NTSB
Aviation Investigation Report AIR-26-02 on the DCA Midair Collision
(Mar. 24, 2026) (on file with Comm.).
\14\ALERT, supra note 12.
---------------------------------------------------------------------------
On March 26, 2026, the Transportation and Infrastructure
and Armed Services Committees of the House of Representatives
marked up their respective titles of the ALERT Act. Title I of
the ALERT Act pertains to civil aviation matters, and is within
the Transportation and Infrastructure Committee's jurisdiction,
while Title II pertains to DoD matters, which is under the
Armed Services Committee's jurisdiction. Both Committees
ordered their respective Titles to be reported to the House
with a favorable recommendation, with amendment, by unanimous
recorded vote. The House Armed Services Committee will file a
separate Bill Report for Title II of the ALERT Act. This Bill
Report covers Title I.
Hearings
For the purposes of rule XIII, clause 3(c)(6)(A) of the
119th Congress--
The following hearing was used to develop or consider H.R.
7613: On Tuesday, December 16, 2025, the Subcommittee on
Aviation held a hearing entitled, ``The State of American
Aviation.'' At the hearing, Members received testimony from the
Honorable Bryan Bedford, Administrator, FAA. The hearing
examined the general state of aviation in America and Members
had the opportunity to discuss recent regulatory actions taken
by the FAA, including changes to the Washington, DC airspace in
response to the January 29, 2025 crash, air traffic control
modernization, air traffic controller hiring and training, the
continued implementation of the FAA Reauthorization Act of 2024
(P.L. 118-63), and other current issues in aviation.
Legislative History and Consideration
H.R. 7613, the ``ALERT Act,'' was introduced in the United
States House of Representatives on February 20, 2026, by
Representative Sam Graves (R-MO), with Representatives Rick
Larsen (D-WA), Mike Rogers (R-AL), and Adam Smith (D-WA) along
with 44 other members as original cosponsors and was referred
to the Committee on Transportation and Infrastructure and the
Committee on Armed Services. Within the Committee on
Transportation and Infrastructure, H.R. 7613 was referred to
the Subcommittee on Aviation. The Subcommittee on Aviation was
discharged from further consideration of H.R. 7613 on March 26,
2026.
The Committee considered H.R. 7613 on March 26, 2026, and
ordered the measure to be reported to the House with a
favorable recommendation, with amendment, by a recorded vote of
62 yeas to 0 nays.
The following amendments were offered:
An Amendment in the Nature of a Substitute to H.R. 7613,
offered by Chairman Graves of Missouri; was AGREED TO, as
amended, by voice vote.
A Manager's Amendment to the Amendment in the Nature of a
Substitute to H.R. 7613, offered by Chairman Graves of Missouri
(Graves MGRS 01): Page 6, line 6, strike ``March 11'' and
insert ``March 7''. Page 20, line 16, insert ``a second
independent source of target aircraft data, such as'' after
``and''. Page 27, line 21, strike ``civil'' and insert ``non-
military''. Page 28, line 4, strike ``civil'' and insert ``non-
military''. Page 28, after line 17, insert the following (and
redesignate the subsequent paragraphs accordingly): ``(2) Air
carriers operating under part 121 of title 14, Code of Federal
Regulations.'' Page 34, line 6, strike ``civil'' and insert
``non-military''. Page 47, strike lines 6 through 10 and insert
the following: ``(3) the frequency of the recurrent and
refresher training described in subsection (a), including--(A)
whether such frequency should be increased for air traffic
controllers in facilities managing high-complexity or high-
volume airspace; and (B) the need for advance training and
guidance ahead of any changes to FAA visual separation
policies;''. Page 50, line 17, strike ``and''. Page 50, after
line 17, insert the following (and redesignate the subsequent
paragraph accordingly): ``(5) organizations representing
operators of Federal contract towers pursuant to section 47124
of title 49, United States Code; and''. Page 53, after line 21,
insert the following (and redesignate the subsequent paragraphs
accordingly): ``(2) Air carriers operating under parts 91,
including subpart K, and 135 of title 14, Code of Federal
Regulations, authorized to conduct non-scheduled operations at
Ronald Reagan Washington National Airport.'' Page 90, line 13,
insert ``the Air Traffic Safety Action Plan,'' after
``Reporting System,''. Page 90, line 21, insert ``and the
Aviation Safety Management Organization'' after ``Air Traffic
Organization''. Page 91, line 2, insert ``and the Aviation
Safety Management Organization'' after ``Traffic
Organization''. Page 91, line 15, insert ``and the Aviation
Safety Management Organization'' after ``Air Traffic
Organization''. Page 91, line 21, insert ``and the Aviation
Safety Management Organization'' after ``Air Traffic
Organization''. Page 92, line 1, insert ``and the Aviation
Safety Management Organization'' after ``Air Traffic
Organization''. Page 92, line 10, insert ``and the Aviation
Safety Management Organization'' after ``Air Traffic
Organization''. Page 93, line 3, insert ``and the Aviation
Safety Management Organization'' after ``Organization''. Page
93, line 18, insert ``and the Aviation Safety Management
Organization'' after ``Air Traffic Organization''. Page 93,
line 22, insert ``and the Aviation Safety Management
Organization'' after ``Traffic Organization''. Page 94,
beginning on line 16, strike ``regulations and standard
operating''. Page 94, line 24, strike ``regulations'' and
insert ``procedures''. Page 95, line 1, strike ``standard
operating procedures,'' and insert ``procedures and''. Page 95,
line 2, strike ``, and regulations''. Page 95, beginning on
line 12, strike ``submit a rationale for atypical occurrences''
and insert ``report on deviations from the standard operating
procedures''. Page 97, beginning on line 5, strike ``in FAA
Order JO 7210.3EE, titled `Facility Operation and
Administration' (or any successor document)'' and insert ``and
procedures''. Page 97, beginning on line 23, strike ``in FAA
Order JO 7210.3EE, titled `Facility Operation and
Administration' (or any successor document)'' and insert ``and
procedures''. Page 97, line 25, insert ``and procedures'' after
``such standards''. Page 99, after line 15, insert the
following: ``SEC. 127. CLOSURE OF HELICOPTER ROUTE 4. (a) IN
GENERAL.--Operations on Helicopter Route 4, as such Route
existed on January 29, 2025, on the segment located between
Hains Point and the Woodrow Wilson Memorial Bridge in the
District of Columbia shall be prohibited. (b) SEGMENT
ELIMINATION.--The segment of Helicopter Route 4 described in
subsection (a) shall remain eliminated from helicopter charts.;
was AGREED TO by voice vote.
An Amendment to the Amendment in the Nature of a Substitute
to H.R. 7613, offered by Mr. Carbajal of California (Carbajal
061): Strike section 105 (and redesignate subsequent sections
accordingly). Page 44, line 23, strike ``109'' and insert
``108''. Page 60, line 12, strike ``115'' and insert ``114''.
Page 76, line 4, strike ``120'' and insert ``119''. Page 76,
line 22, strike ``119(d)'' and insert ``118(d)''. Page 86, line
24, strike ``122'' and insert ``121''. Page 89, line 22, strike
``122'' and insert ``121''.; was NOT AGREED TO by a recorded
vote of 27 Yeas and 36 Nays (RC#71).
An Amendment to the Amendment in the Nature of a Substitute
to H.R. 7613, offered by Ms. Hoyle of Oregon (Hoyle 042): At
the end of title I of the bill, insert the following: SEC. 127.
ENHANCED NOTIFICATION AND ALERTING FOR SLACKLINES. Not later
than 180 days after the date of enactment of this Act, the
Administrator shall implement enhanced notification and
alerting requirements for slacklines and similar temporary
aerial hazards that--(1) exceed existing regulatory notice
requirements; and (2) provides pilots with a warning, similar
to a temporary flight restriction, that is--(A) not limited to
an airport-specific notice (NOTAM); and (B) displayed on pilot-
facing tools for aircraft operating in the vicinity of the
affected airspace.; was WITHDRAWN.
An Amendment to the Amendment in the Nature of a Substitute
to H.R. 7613, offered by Ms. Friedman of California (Friedman
035): Page 34, strike line 22 through line 3 on page 35 (and
redesignate the subsequent paragraph accordingly).; was NOT
AGREED TO by a recorded vote of 27 Yeas and 36 Nays (RC#72).
An Amendment to the Amendment in the Nature of a Substitute
to H.R. 7613, offered by Ms. Hoyle of Oregon (Hoyle 043): Page
2, strike lines 3 through 11 and insert the following
paragraphs (and redesignate subsequent paragraphs accordingly):
TITLE I--REQUIREMENTS AS TO COMMERCIAL DRIVERS' LICENSES Add,
at the end of the bill, the following: TITLE II--VERIFICATION
ENHANCEMENT AND RELIABILITY FOR IMMIGRATION FIDELITY SEC. 101.
SAVE PROGRAM MODERNIZATION. (a) GENERAL REQUIREMENT.--The
Secretary of Homeland Security, acting through United States
Citizenship and Immigration Services, shall modernize the SAVE
program to ensure accurate, timely, and reliable verification
response, including by--(1) upgrading query processing
infrastructure to reduce response latency; (2) implementing
automated data reconciliation with source systems; (3)
expanding API access for authorized querying agencies; and (4)
establishing a user feedback mechanism for agencies to report
suspected data errors. (b) TIMELINESS OF UPDATES.--To the
maximum extent practicable and consistent with applicable law,
the Secretary shall ensure that changes to an individual's
immigration status, including grants, extensions, expirations,
revocations, or terminations of lawful status or parole, are
reflected in the SAVE program not later than 24 hours after
such changes are recorded in the originating system. (c)
INTEROPERABILITY AND DATA SHARING.--The Secretary, consistent
with the Privacy Act of 1974, the E Government Act of 2002, the
Computer Matching and Privacy Protection Act of 1988, and other
applicable Federal law, shall--(1) integrate the SAVE program
into relevant Department of Homeland Security systems,
including arrival and departure information systems; (2)
establish or update memoranda of understanding with the Social
Security Administration and other Federal agencies, as
appropriate, to improve verification accuracy using data-
sharing arrangements authorized under applicable Federal law,
including section 6103 of the Internal Revenue Code, the
Computer Matching and Privacy Protection Act of 1988, and
memoranda of understanding in effect as of the date of
enactment of this Act; and (3) encourage voluntary data-sharing
agreements with State vital records agencies for verification
of birth and death information, where legally permissible. (d)
POST-VERIFICATION STATUS CHANGE ALERTS.--The SAVE program shall
notify querying agencies when an individual's immigration
status materially changes after a prior verification, when such
notification is relevant to continued eligibility.
Notifications shall comply with applicable Federal privacy
laws, including the Privacy Act of 1974, and with additional
administrative safeguards established by the Secretary and
include only information necessary for eligibility
determinations. (e) DATA SCOPE LIMITATIONS.--Information used
or displayed through the SAVE program shall be limited to data
necessary for eligibility verification purposes. Nothing in
this Act may be construed to authorize--(1) the expansion of
the SAVE program to include non-immigration criminal history
databases; and (2) the use of the SAVE program for general law
enforcement or surveillance purposes. (f) USE OF AUTOMATED
TOOLS.--The Secretary may use automated or algorithmic tools
within the SAVE program solely for data reconciliation, error
reduction, and identity matching, provided that--(1) no adverse
eligibility determination is made solely on the basis of
automated processing; (2) human review is required for
contested or negative determinations; and (3) the Secretary
implements regular testing for accuracy and bias and submits
summary results annually to Congress. SEC. 102. PROHIBITION ON
USER ACCESS AND FEES. No fee may be charged to a Federal,
State, local, or Tribal government agency for submitting a
verification query through the SAVE program. SEC. 103.
IMPLEMENTATION AND OVERSIGHT. (a) MODERNIZATION PLAN.--Not
later than 180 days after enactment of this Act, the Secretary
shall submit to Congress a SAVE modernization plan that
includes--(1) a description of technological upgrades to the
SAVE program; (2) user training improvements; and (3)
performance metrics related to accuracy and response time,
including error rates and average query completion time
benchmarks. (b) INSPECTOR GENERAL AUDITS.--The Inspector
General of the Department of Homeland Security shall conduct
annual audits of the SAVE program's accuracy, timeliness, and
compliance with this Act, and submit reports to Congress. (c)
CORRECTIVE ACTION.--If the Inspector General identifies
material non-compliance, the Secretary shall submit a
corrective action plan to Congress within 90 days. Continued
non-compliance may be addressed through limitations on the use
of funds for non-SAVE discretionary activities, as determined
by Congress, and may trigger suspension of SAVE queries until
compliance is restored. SEC. 104. DEFINITION. For purposes of
this title, the term ``SAVE program'' means the Systematic
Alien Verification for Entitlements program, established
pursuant to section 121 of the Immigration Reform and Control
Act of 1986. SEC. 105. EFFECTIVE DATE. This title shall take
effect one year after the date of enactment, except that
planning and reporting requirements under section 103 shall
take effect immediately upon enactment. SEC. 106. SEVERABILITY.
If any provision of this title, or the application thereof, is
held invalid, the remainder of this title shall not be
affected.; was WITHDRAWN.
An Amendment to the Amendment in the Nature of a Substitute
to H.R. 7613, offered by Mr. Figures of Alabama (Figures 052):
Page 34, line 24, insert ``(except a State or local government
for the assessment of taxes and preventing tax evasion)'' after
``governmental agency''. Page 35, line 14, strike ``State,
local,''. Page 35, line 15, insert ``, and no State or local
official may, except for the assessment of taxes or preventing
tax evasion,''. After ``may''.; was NOT AGREED TO by a recorded
vote of 25 Yeas and 38 Nays (RC#73).