AA5342 Down DCA

[Musician]

Originally Posted by WillFlyForCheese

It appears as though the CRJ crew saw the Blackhawk at the last second and pulled up in an attempt to miss it. Was that evident in any other videos?

It could be concluded from the pitch and roll data.

Edit: From the final report, section 1.1:

At 2047:58.0, the airplane’s control column moved from 3° to 11° nose up, and the elevators moved from a deflection of 1° to a maximum of 24° nose up in less than 1 second. At this point, the airplane’s recorded radio altitude was 313 ft.
At 2047:58.6, the CVR recorded an exclamation by the captain, followed by the FO.
At 2047:59.3, a significant longitudinal deceleration was recorded, consistent with impact. The airplane’s attitude at this time was 7° nose up with an 11° left roll.
The recording ended at 2048:04.

[nachtmusak]

It was also mentioned/could be concluded from the preliminary report (page 8), though the pitch was corrected (?) in the final report

At 2047:58, or 1 second before impact, flight 5342 began to increase its pitch. FDR data showed the airplane’s elevators were deflected near their maximum nose up travel.

At 2047:58, the controller issued a landing clearance to another airplane. During this transmission, audible reactions could be heard from the other tower controllers as they observed the collision, which occurred about 2047:59 while flight 5342 was over the Potomac River and on final approach for runway 33.

The flight 5342 FDR indicated that the airplane’s last recorded radio altitude was 313 ft, 2 seconds before the collision. The airplane’s pitch at the time of the collision was 9º nose up and roll was 11º left wing down. The airplane was descending at 448 ft per minute.

The PAT25 FDR indicated that the radio altitude of the helicopter at the time of the collision was 278 ft and had been steady for the previous 5 seconds. The helicopter’s pitch at the time
of the collision was about 0.5º nose up with a left roll of 1.6º.

So this is information that has been available for over a year, albeit now in video.

Considering that most people don't really do much more than skim these reports (if they read them at all) on top of smaller details slipping out of memory quite easily, I expect media and bloggers alike will continue to farm clicks off already-known facts about this accident for a long time yet.

[scard08]

Originally Posted by WillFlyForCheese

It appears as though the CRJ crew saw the Blackhawk at the last second and pulled up in an attempt to miss it. Was that evident in any other videos?

If you look at the last ten seconds of the NTSB right-seat cockpit view simulation then I would say yes, that shows a pitch up and the runway moves sharply down as PAT25 comes into view. I trust that the NTSB have reasons to show that in the simulation. No comment on whether this new video is real or AI slop based on published data. I cannot tell.

[WillowRun 6-3]

Legislation passed by House of Representatives

From a press release issued by the House Transportation and Infrastructure Committee (April 14)

"Washington, D.C. -

The House of Representatives today overwhelmingly approved the Airspace Location and Enhanced Risk Transparency (ALERT) Act of 2026 (H.R. 7613), the bipartisan comprehensive legislative response to the tragic 2025 midair collision between American Airlines Flight 5342 and a UH-60 Army Black Hawk helicopter at Ronald Reagan Washington National Airport (DCA).

The ALERT Act was introduced on February 20, 2026, following the conclusion of the National Transportation Safety Board’s (NTSB) full investigation of the accident. The legislation is a comprehensive package of improvements that respond to the broad scope of safety issues raised by the NTSB’s investigation and addresses all 50 of the NTSB’s final recommendations.

The ALERT Act was introduced in the House by Transportation and Infrastructure (T&I) Committee Chairman Sam Graves (R-MO), Transportation and Infrastructure Committee Ranking Member Rick Larsen (D-WA), Armed Services Committee (HASC) Chairman Mike Rogers (R-AL), and Armed Services Committee Ranking Member Adam Smith (D-WA). The bill was approved today by a vote of 396 to 10.

[Quotations from Committee leaders omitted]

The ALERT Act:

Takes important steps to improve safety throughout the nation’s airspace for every user of the airspace and the flying public;

Ensures the utilization of technology to enhance flight crew alerting and controller situational awareness;

Requires ADS-B (Automatic Dependent Surveillance–Broadcast) In and a corresponding collision prevention technology to be equipped and operating on virtually all aircraft that are required to have ADS-B Out, by December 31, 2031;

Establishes a public dashboard to ensure transparency and accountability throughout the rulemaking processes;

Makes updates to helicopter route safety and separation requirements;

Requires necessary updates to air traffic control training, processes, and procedures to promote safety;

Seeks to objectively define a close proximity encounter and requires the Federal Aviation Administration (FAA) to establish a database to effectively monitor such encounters and other data for trends;

Investigates shortcomings in both safety culture and data sharing that contributed to the collision;

Tackles mismanagement within the FAA that contributed to the fatal collision;

Strengthens safety standards for military aircraft and cooperation between the military and the FAA;

Enhances requirements and guidance for collision avoidance technology for military aircraft;

Strengthens oversight of flight operations in congested airspace; and

Requires greater flight data sharing between the Secretary of Defense and the FAA."

[Capn Bloggs]

Requires ADS-B (Automatic Dependent Surveillance–Broadcast) In and a corresponding collision prevention technology to be equipped and operating on virtually all aircraft that are required to have ADS-B Out, by December 31, 2031;

Will probably cause more problems than it will solve. Pilots will become self-ATCs as they see aircraft going every which way and start bleating to ATC about the impending collision, not knowing that ATC had actually planned to avoid it. It might have been helpful in this case but the last thing I want to be doing at 700ft on final at night is peering at the ND looking at all the ADS-B In returns wondering if they are on a collision course.

As for...

corresponding collision prevention technology

It's took decades to get TCAS to a "good" standard. I would be very surprised if this new "technology" will be mission-ready in 5 years without costing a truckload.

The fundamental problem had nothing to do with cockpit displays.

[Propellerhead]

Originally Posted by Capn Bloggs

Will probably cause more problems than it will solve. Pilots will become self-ATCs as they see aircraft going every which way and start bleating to ATC about the impending collision, not knowing that ATC had actually planned to avoid it. It might have been helpful in this case but the last thing I want to be doing at 700ft on final at night is peering at the ND looking at all the ADS-B In returns wondering if they are on a collision course.

As for...

It's took decades to get TCAS to a "good" standard. I would be very surprised if this new "technology" will be mission-ready in 5 years without costing a truckload.

The fundamental problem had nothing to do with cockpit displays.

How is that any different to TCAS in terms of peering at a screen and seeing if it’s on a collision course. Surely the whole point is you don’t have to as it will tell you.

[Musician]

Originally Posted by Capn Bloggs

It's took decades to get TCAS to a "good" standard. I would be very surprised if this new "technology" will be mission-ready in 5 years without costing a truckload.

Isn't the legislation describing TCAS?

[ATC Watcher]

Capn Bloggs has it right when he says L

The fundamental problem had nothing to do with cockpit displays.

, it also complement what I said in my early post one month ago ( #1965 of 13 march) We always are pushing and looking for magic new technical solutions to mitigate basic organization or human errors .​​​​​​​ Some are easy to do ( like red lights and alerts to prevent runways incursions ) some other are far , far more complex , TCAS was a good example, and it is still not perfect 40 years after its mandate . Regarding this "corresponding collision prevention technology" ADS-B in is simple technology putting it on a display is easy however how to integrate it in an existing older aircraft cockpit a bit less. , But it is how to use it that will be far more complex.. Giving info is one thing , interpreting and acting on the info will be the issue. And even it it all works out on paper ,are we going to have now 2 anti collisions systems in an aircraft ? or is TCAS going to be removed ? (good luck with that one )
.
That said this ALERT bill goes into the right direction . even if only 20% of its recommendations are followed in the end ( my wild guess) it is helpful , would it be alone to push the FAA out of its comfort zone.

[SINGAPURCANAC]

It is way cheaper to spend bilions on tecnical solutions working improperly than to fire debil managers and employ enough operational workers.


N.B. it is better 10% from 1b€ contract than nothing from salary of ATCO..

[MechEngr]

Originally Posted by Musician

Isn't the legislation describing TCAS?

No - TCAS is a system that waits for a problem to become nearly catastrophic before issuing a coordinated emergency demand for action,

ADS-B is for situational awareness to avoid even nearing catastrophe, but it can be expanded to include avoidance alerts for obstacles, such as firetrucks, which TCAS cannot manage.

If automation is not to be trusted, can aircraft get flight engineers back to monitor all aspects of the turbojet engines and ditch FADEC?

[Musician]

This is the definition, directly from the ALERT act as it passed the House:
https://www.congress.gov/bill/119th-...ouse-bill/7613

(4) Collision prevention technology.—
The term “collision prevention technology” means equipment, or a combination of equipment, that—

(A) has ADS–B In;

(B) uses ADS–B data to provide the pilot and flight crew with situational awareness of surrounding traffic and traffic advisories; and

(C) provides, and is configured to provide, alerting that is audible to the pilot and flight crew.

.
To my layman's understanding, both TCAS and ADS-B in use data provided by a Mode S transponder, so in that sense, I expect that TCAS fits this definition.

I also think it's unlikely that Congress would set a 5-year ultimatum to install technology that doesn't exist yet, so it'd be interesting to look at other existing technology that uses ADS-B and provides audible alerts.

[Musician]

Ok, more text from the bill:
https://www.congress.gov/bill/119th-...ouse-bill/7613
.

SEC. 102. AIRBORNE COLLISION AVOIDANCE SYSTEM UPGRADES.

(a) In general.—Not later than 45 days after the date of enactment of this Act, the Administrator shall establish an aviation rulemaking committee (in this section referred to as the “Committee”) to review and develop findings and recommendations to require selected aircraft to be equipped and operating with ACAS Xa that is—

(1) integrated and uses both ADS–B In and transponder interrogations, as required under the RTCA minimum operational performance standards for the Airborne Collision Avoidance System (DO–385A, issued June 22, 2023); and

(2) is configured to provide visual and audible alerting to the pilot and flight crew.

[...]
(h) Selected aircraft defined.—In this section, the term “selected aircraft” means aircraft that are required to be equipped with traffic alert and collision avoidance systems as required in sections 121.356, 135.180, and 91.1045 of title 14, Code of Federal Regulations.

.
ACAS X is the successor to TCAS II:
https://skybrary.aero/articles/acas-x

The FAA has funded research and development of a new approach to airborne collision avoidance (which has become known as ACAS X - pronounced “Ay-cas eks” rather than “Ay-cas ten") since 2008. This new approach takes advantage of recent advances in ‘dynamic programming’ and other computer science techniques (which were not available when TCAS was first developed) to generate alerts using an off-line optimisation of resolution advisories. It is the intention that ACAS X will eventually replace TCAS II (ACAS II).

.

ACAS XA – The general purpose ACAS X that makes active interrogations to detect intruders. ACAS XA is the baseline system, the successor to TCAS II. ACAS XA /XO standards were published by RTCA DO-385 and EUROCAE ED-256 in September 2018. Amendments to ICAO provisions and regulatory approval for ACAS XA /XO are pending.

.

The ACAS XA system will use the same hardware (antennas and displays) as the current TCAS II system and the same range of RAs – as in TCAS II version 7.1 – will be used. There will be no change in the way how RAs are displayed and announced to the pilots. Consequently, pilots and controllers would perceive no change with the transition to the new system, which will be fully compatible with current TCAS II systems. It is the intention that ACAS XAwill eventually replace TCAS II.

Two of the key differences between TCAS II and the current concept for ACAS XA are the collision avoidance logic and the sources of surveillance data.

.
In essence, the bill mandates a timeline for the replacement of TCAS II with ACAS X, with potentially reduced inhibition altitudes.

[Musician]

Originally Posted by Musician

This is the definition, directly from the ALERT act as it passed the House:
https://www.congress.gov/bill/119th-...ouse-bill/7613

(4) Collision prevention technology.—
The term “collision prevention technology” means equipment, or a combination of equipment, that—

(A) has ADS–B In;

(B) uses ADS–B data to provide the pilot and flight crew with situational awareness of surrounding traffic and traffic advisories; and

(C) provides, and is configured to provide, alerting that is audible to the pilot and flight crew.

.

More text from the bill:
https://www.congress.gov/bill/119th-...ouse-bill/7613
.

SEC. 104. COLLISION PREVENTION SYSTEMS.

(a) Final rule.—Not later than 2 years after the date of enactment of this Act, the Administrator shall issue a final rule with an effective date not later than December 31, 2031, to require covered aircraft to be equipped and operating with collision prevention technology.
[...]
(e) Equivalent level of safety.—In issuing the final rule required under this section, the Administrator shall allow for the use of any collision prevention technology (including technology that uses portable ADS–B In receivers or other equipment that displays on an existing or future portable device, electronic flight bag, or panel mounted display) available for use at the time of the effective date established in subsection (d)(4), if the Administrator determines it provides an equivalent level of safety as the requirements of the final rule issued pursuant to subsection (a).
[...]
(g) Covered aircraft defined.—In this section, the term “covered aircraft”—

(1) means any non-military aircraft, except a selected aircraft as defined in section 102, that is required to be equipped with ADS–B Out under section 91.225 of title 14, Code of Federal Regulations; [...]

.
The FAA has 2 years to make rules for all aircraft that now must have ADS-B to require a collision prevention system by the end of 2031. This could run on a tablet.

[WillowRun 6-3]

There is more to the statute's means and method of dealing with "collision prevention technology" than has been revealed so far. (Caveat: there are quite a lot of things worth noting in this legislation - and in so stating, I am not disagreeing with any pro pilot's or ATCO's assessment of whether or not any specific technological or process change would be good, bad or indifferent. There are many other types of reforms and changes set up by the ALERT Act.)

First, it is necessary to recognize there are two "Titles" in the legislation. Title II deals with Department of Defense provisions (sorry to any WH Administration worthies - this post deals with legislation, and thus unless and until the Congress changes the name of the DoD, it's status quo, all day long.) And I've noted Title II first because it is set forth first in the CRS (Congressional Research Service) legislative information. Title I deals with civil aviation provisions.

The definition cited by Musician is from Title II, Sec. 2655(6). Of interest is that where, in Title II, this term is used, it also is followed by the phrase "or successor technologies". For example (and I think, importantly), in Sec. 2656(b) - which deals with a Memorandum of Agreement assigned to the Secretary of Defense, language provides that "sole control over the determination of which specific collision prevention technology is appropriate for installation and operation...".

Without having read the entire enactment as passed by the House, the conclusion I believe it is reasonable to draw is that notwithstanding the Title II definition, the specific technology or technical system mandated by this Title of the Act is not limited to one system or type of hardware.

But there's more; there is Title I.
Which has its own definition:
"(4) Collision prevention technology.—The term “collision prevention technology” means equipment, or a combination of equipment, that—

(A) has ADS–B In;

(B) uses ADS–B data to provide the pilot and flight crew with situational awareness of surrounding traffic and traffic advisories; and

(C) provides, and is configured to provide, alerting that is audible to the pilot and flight crew." (Section 2, Definitions)

It gets statutorily dense hereafter.

Section 101 deals with changing the inhibit levels of collision avoidance systems.

Section 102 deals with upgrades of collision avoidance systems.

Section 103 deals with same for rotorcraft.

These both are extensive statutory provisions dealing with the process to be followed, and the information and reports to be provided to Congress. Very briefly, Sec. 101 requires an evaluation by the Administrator; Sections 102 and 103 require the process undertaken by an Aviation Advisory Committee.

But then, have a look at Section 104. It does not require the adoption or implementation of specific technology or systems; instead it mandates a broad review and study conducted by the Administrator. The initiative is directed to include input from 20 identified stakeholder groups or organizations, and to consider 15 specific factors.

[Crossed w/ posts by Musician .... and power outage this morning has been unhelpful w/r/t posting useful info]

[Musician]

Originally Posted by WillowRun 6-3

The definition cited by Musician is from Title II, Sec. 2655(6).

It was at first, but I corrected it 15 minutes later. Sorry about that.

It gets statutorily dense hereafter.

Section 101 deals with changing the inhibit levels of collision avoidance systems.

Section 102 deals with upgrades of collision avoidance systems.

Section 103 deals with same for rotorcraft.

These both are extensive statutory provisions dealing with the process to be followed, and the information and reports to be provided to Congress. Very briefly, Sec. 101 requires an evaluation by the Administrator; Sections 102 and 103 require the process undertaken by an Aviation Advisory Committee.

But then, have a look at Section 104. It does not require the adoption or implementation of specific technology or systems; instead it mandates a broad review and study conducted by the Administrator. The initiative is directed to include input from 20 identified stakeholder groups or organizations, and to consider 15 specific factors.

[Crossed w/ posts by Musician]

Sections 101, 102 and 103 deal with TCAS upgrades. As I understand it, Aircraft that don't already have TCAS are not affected. 103 applies to any civilian helicopter operating in class B airspace, i.e. near a major airport.

Section 104 is the contentious one, where the ADS-B in mandate is established for aircraft that must have ADS-B out now (minus some exceptions).
As I understand it, the FAA has 2 years to adopt a set of rules. It would then certify equipment that conforms to these rules. Starting in 2032 at the latest, pilots would be required to use that equipment.

Title II essentially mandates ADS-B in and collision avoidance equipment for military craft, except fighters, bombers, and drones.

[21600HRS]

Over a year and yet there is only ADS-B and other technical solutions considered. During the accident there was warning in tower, ”traffic” in CRJ but still this happened. Reason was visual separation in the dark. All visual separations in dark or poor visibility should be banned, no human can for sure name a target in the dark.

[MechEngr]

Originally Posted by 21600HRS

Over a year and yet there is only ADS-B and other technical solutions considered. During the accident there was warning in tower, ”traffic” in CRJ but still this happened. Reason was visual separation in the dark. All visual separations in dark or poor visibility should be banned, no human can for sure name a target in the dark.

Consistent use of ADS-B is like turning on the lights.

[Musician]

Originally Posted by 21600HRS

Over a year and yet there is only ADS-B and other technical solutions considered. During the accident there was warning in tower, ”traffic” in CRJ but still this happened. Reason was visual separation in the dark. All visual separations in dark or poor visibility should be banned, no human can for sure name a target in the dark.

a) as a non-technical solution, the bill also abolishes heli route 4 operations.
b) visual separation when you can't see the traffic is already banned

More from the bill:
https://www.congress.gov/bill/119th-...bill/7613/text

SEC. 109. CONTROLLER VISUAL SEPARATION TRAINING.

(a) In general.—Not later than 270 days after the date of enactment of this Act, the Administrator shall, in coordination with the exclusive bargaining representative of air traffic controllers certified under section 7111 of title 5, United States Code, develop and implement initial, recurrent, and refresher training for air traffic controllers on tower-applied and pilot-applied visual separation procedures that is instructor-led and scenario-based.

SEC. 119. REQUIRING VERTICAL SEPARATION NEAR AIRPORTS DURING CRITICAL PHASES OF FLIGHT.

.
Section 119 concerns criteria for helicopter routes.

The "findings" section says:

(8) The NTSB held a public meeting on January 27, 2026, where the NTSB determined that the probable cause of the accident was the FAA’s placement of a helicopter route in close proximity to a runway approach path; their failure to regularly review and evaluate helicopter routes and available data, and their failure to act on recommendations to mitigate the risk of a midair collision near DCA; as well as the air traffic system’s overreliance on visual separation in order to promote efficient traffic flow without consideration for the limitations of the see-and-avoid concept.

(9) The NTSB determined that the lack of effective pilot-applied visual separation by the helicopter crew, the tower team’s loss of situation awareness and degraded performance due to the high workload of the combined helicopter and local control positions and the absence of a risk assessment process to identify and mitigate real-time operational risk factors, and the Army’s failure to ensure pilots were aware of the effects of error tolerances on barometric altimeters in their helicopters, were also causal to the collision.

[WillowRun 6-3]

1) props and thanks to Musician for plowing through the actual legislation. As an example of the federal administrative state growimg to behemoth proportions, the sections defining FAA rule-making processes, including factors to be considered and reports to Congress among other terms, are pretty complicated (but then, I'm not legislative counsel on any committee or Member's staff).

2) leaving aside the various initiatives and reports assigned to the Defense Department and the Secretary, and just looking at the work given to FAA, it's worth considering whether the agency will be able to perform. Among other reasons, does it have the professional and technical staff depth to conduct the required work? Having said that, I admit perhaps bias - the impression made by FAA at the NTSB hearing on this accident was a pretty negative impression. Not directed at any specific person, with exceptions for some few standouts during the hearing, including but not limited to the reprimand by Board Chair Homendy. The bureaucratic resistance to, and ultimate failure to implement, chart notations about so-called "hot spots" strikes at least this one non-pilot as a pretty good example of a federal agency's gears stuck in bureaucratic neutral.

3) layer on top the new air traffic control system and the disruption the ongoing work may bring. Ironically, the advent of the new system should provide a vehicle for implementing much of the legislative requirements. It could be very interesting and informative for House Transportation and Infrastructure Committee staff to interact with the architects of the European ATM Master Plan - not because the airspace of Europe and the NAS are so similar, I recognize there are significant differences. Rather because the ATM Master Plan is built upon a service-oriented architecture. What says the forum community, has FAA provided the expected and required quality of service at the expected and required level of consistency? If the answer is anything other than an unqualified "yes, FAA has done so" then perhaps the ATM Master Plan can yield useful guidance for fixing what's broken. This is definitely not a situation where there ain't something broke.

4) and maybe, possibly, looking to international best practices, including the future-focus of SESAR and the ATM Master Plan, will create organizational and practical space to move forward swiftly and aggressively to improve ATCO terms and conditions across the board. "Well folks, something's gotta change" (as stated by "Ben" in the classic United Airlines tv spot, "the Speech" (1990)). Again the inertia of the status quo engenders plenty of doubt that current efforts will get anywhere close to sufficient.

[Capn Bloggs]

Originally Posted by Propellerhead

How is that any different to TCAS in terms of peering at a screen and seeing if it’s on a collision course. Surely the whole point is you don’t have to as it will tell you.

Precisely my point. You don't peer at your TCAS screen trying to decide what to do. You shouldn't have to peer at your Nav Display looking at the ADS-B In returns to work out whether you're on a collision course. But that is exactly what ADS-B In will do/mean imply, unless/until it is fully integrated into the aircraft systems. Maybe the pollies (or whoever is feeding them this nonsense) think it can be bolted onto the TCAS, overnight job, done... problem solved.