@TheIntelFrog - TheIntelFrog
An "aircraft emergency" has Reagan National Airport (DCA) in Washington D.C. closed as of 0155z. Will update this thread with more details as we find out. 1/
@TheIntelFrog - TheIntelFrog
US Park Police's N11PP as EAGLE1 is circling just off the end of one of the runways, and an airport operations vehicle, OPS 3, is parked at the end of the runway. 2/
@TheIntelFrog - TheIntelFrog
DC FEMS confirms a small plane has gone into the Potomac River. Unknown if it came from the airport or if this is the reason the airport is closed. 3/
@TheIntelFrog - TheIntelFrog
From reviewing playback on @ADSBex it appears that JIA5342, operated by PSA Airlines (regional carrier for American Airlines) collided midair with PAT25. PAT25 is possibly a US Army aircraft. 4/
@TheIntelFrog - TheIntelFrog
Current look at aerial activity over the scene. N911DC is the DC Metro Police Department's helicopter N11PP is the US Park Police's helicopter 6/
@TheIntelFrog - TheIntelFrog
Listening to the radio traffic on @liveatc, JIA5342 as BLUESTREAK5342 was directed to runway 33 and cleared to land. US Army Helicopter PAT25 was last asked if they had a Cherokee in sight. Per ADSB playback the accident happened at approximately 01:48:10z. 7/
@TheIntelFrog - TheIntelFrog
It does not appear that JIA5342 made it to the runway. 8/
@TheIntelFrog - TheIntelFrog
JIA5342 was a regularly scheduled service between Wichita, KS and Reagan National Airport in Washington D.C. It's a CRJ701-ER which has a maximum capacity of 70 passengers. 9/
@TheIntelFrog - TheIntelFrog
Confirmation from American Airlines it was a regional subsidiary aircraft involved in the crash. 10/
@TheIntelFrog - TheIntelFrog
Media reports confirm 64 souls on board the CRJ-700. Unknown who/what was on the US Army UH-60. 11/
@TheIntelFrog - TheIntelFrog
Correcting a previous post, the radio traffic to the blackhawk was "do you have the CRJ in sight" and was told to go behind the CRJ, to which PAT25 advises "in sight...visual separation." 12/
@TheIntelFrog - TheIntelFrog
Media reports confirm 3 souls on board the US Army UH-60 Blackhawk for a total of 67 souls involved in this accident. 13/
@TheIntelFrog - TheIntelFrog
Several helicopters still ovehead of the accident site. N22PP US Park Police EAGLE2 N913PG as GARDNR3 Prince Georges County, MD N191NR MD Natural Resources Dept. 14/
@TheIntelFrog - TheIntelFrog
American Airlines has setup a hotline for families of the passengers on board the CRJ. 15/
@TheIntelFrog - TheIntelFrog
US Army confirms it was a US Army UH-60 Blackhawk helicopter that was involved in the crash. It appeared to have come from the Langley, VA area and may have been returning to Fort Belvoir, VA. 16/
@TheIntelFrog - TheIntelFrog
Press conference with officials is expected to start soon at 0630z. 20/
@TheIntelFrog - TheIntelFrog
Press conference has begun at 0654z. Per Mayor Bowser: - A passenger plane collided with a military helicopter. - Fire departments from throughout the region are executing a rescue operation. - We expect to have another briefing at daylight. 22/
@TheIntelFrog - TheIntelFrog
Per Chief John Donnelly: - 300 responders on scene conducting rescue operations. - Operating under a unified command. - Highly complex operation, water is rough and it is windy. 23/
@TheIntelFrog - TheIntelFrog
24/
@TheIntelFrog - TheIntelFrog
DCA airport will be closed until at least 1100L tomorrow. No impact at Dulles or Baltimore-Washington airports. Per Airport Management. 25/
@TheIntelFrog - TheIntelFrog
30/ Updates from today’s NTSB briefing.
@flightradar24 - Flightradar24
There has been an incident at DCA airport in Washington. The airfield is currently closed until further notice. We will share more details as we learn them. https://www.flightradar24.com/airport/dca
@flightradar24 - Flightradar24
ATC audio captured by @liveatc notes a collision between a CRJ and a helicopter over the Potomac River. The aircraft fitting the description at that time is #AA5342 operated by PSA Airlines for American Airlines. https://www.flightradar24.com/2025-01-30/01:48/1x/JIA5342/38ecc36f
@joeyshep11 - joey shep
@TheIntelFrog American airlines JIA5342 and US military PAT25 cross paths at similar altitude. Hope I'm wrong 😞 https://t.co/P7IK6Q4YdA
@bricaul - Brian McGuigan
.@flightradar24 recording as #AA5342 approached. Looks like another American flight was just ahead of them on final to runway 1. Possible 5342 sidestepped to runway 13, got low, and collided with a helicopter flying low on the east bank of the Potomac. The helicopter is not on ADSB.
@bricaul - Brian McGuigan
It is worth noting that – without casting any blame – the east bank of the Potomac is a published helicopter route that is generally only used by police and military helicopters given the restricted airspace. Not an unusual location for a police helicopter to be.
@bricaul - Brian McGuigan
I have DCA tower audio from the time of the #AA5342 incident. Hear 5342 check in and tower call out a traffic advisory to PAT25. Link below if you want to take a listen, but believe one of the impacted aircraft taps their mic at the time of the incident, so beware. https://drive.google.com/file/d/19E15JPah72EquQDlpyEJWctxJnPTY3kH/view?usp=sharing
@bricaul - Brian McGuigan
Really good thread on PAT25 broadcasting and 5342’s TCAS.
@ADSBex - ADSBexchange
Following developments of what appears to be a collision between a CRJ arriving from Wichita and a military VIP transport helicopter just east of DCA. The military aircraft was not broadcasting ADSB. https://globe.adsbexchange.com/?icao=ae313d,a97753&lat=38.851&lon=-77.036&zoom=13.4&showTrace=2025-01-30&trackLabels
@WayneTechSPFX - WayneTech SPFX®️
AIRPLANE OPS: MASS CASUALTY EVENT: 🚨An airplane crashed into a helicopter over the Reagan National Airport in DC. The impact was caught on tower cam Search & Rescue teams are searching the Potomac River for survivors. Developing... https://t.co/9X9kNZH1Mn
@WayneTechSPFX - WayneTech SPFX®️
UPDATE: American Airlines Flight 5342 From Wichita, Kansas Inbound To Reagan National was the plane involved that crashed into a government helicopter.
@WayneTechSPFX - WayneTech SPFX®️
Flight data: No confirmation on how many were on the plane as of yet. https://t.co/NihfSdRJry
@WayneTechSPFX - WayneTech SPFX®️
According to the official ADSB Exchange. The heli wasn't broadcasting ADSB. That means its transponder wasn't on. ADSB: "Following developments of what appears to be a collision between a CRJ arriving from Wichita and a military VIP transport helicopter just east of DCA. The military aircraft was not broadcasting ADSB." The heli was triangulated via MLAT but not ADSB. I'm a paid subscriber to them. I trust 100% of what they say. It all checks out.
@WayneTechSPFX - WayneTech SPFX®️
UPDATE: New dashcam footage captured by a couple driving near Reagan. https://t.co/Pjb0AaMuyx
@WayneTechSPFX - WayneTech SPFX®️
UPDATE: NTSB has launched a go-team to the aviation accident involving a PSA Airlines Bombardier CRJ700 airplane and a Sikorsky H-60 military helicopter near Ronald Reagan Washington National Airport.
@WayneTechSPFX - WayneTech SPFX®️
UPDATE: The plane was found in the river in pieces. The Black Hawk helicopter was found upside-down at the bottom of the Potomic River. -CBS 19 bodies have been recovered so far. No survivors have been found as of yet. President Trump took to Truth to issue a response: https://t.co/PskwgxMVmy
@ClayTravis - Clay Travis
Helicopter and plane crash in DC. Video here. Pilots can respond, but how is this possible? https://t.co/OiTsLCDWJa
@Marteljr - Ray Martel
Here is a track of the helicopter from VA that would eventually crash into the CRJ at National Airport. Terrible accident. Helicopter came from Langley area. #planecrash https://t.co/NEBFzMG1SN
@newsmidlee - MIDDLE EAST NEWS
BREAKİNG The CA is “Collision Alert” which is not imminent collision, rather a tool used to bring extra attention from the Air Traffic Controllers. #DC @avgeekjake 🎥 https://t.co/USckqBUt8F
@rawsalerts - R A W S A L E R T S
🚨#BREAKING: Shared to me anonymously shows the Playback from official Air Traffic Control radar 📌#Washington | #DC Watch as exclusive playback, sent anonymously by @avgeekjake to Rawsalerst, reveals official Air Traffic Control radar footage displaying the Collision Alert. This alert is not for an imminent collision but serves as a tool to draw heightened attention from the controllers to potential risks. The footage then captures the critical moment when both aircraft collided, emphasizing the urgency of the controllers' split-second decisions. The radar data provides a detailed view of the events leading up to the crash, offering valuable insight into the sequence of actions and how the situation ultimately unfolded
@clashreport - Clash Report
Official Air Traffic Control radar captures today’s collision near Washington, DC between a passenger aircraft and a US Army Black Hawk helicopter. CA (Collision Alert) signals heightened ATC attention, not imminent impact. Source: @avgeekjake https://t.co/Tg2er8s36p
@texan_angler - Texan Angler
Audio of ATC (air traffic control) from the DC #planecrash can be heard asking the Blackhawk PAT25 if it has the American Airlines CRJ-700 in sight. Moments later the two aircraft collide and crash into the Potomac river - audible gasps can be heard in the control tower. https://t.co/t29xmcfSV4
@texan_angler - Texan Angler
Audio courtesy of the fine folks at @liveatc
@Jes_J_Bel - Jes_J_Bel
@DraftDonks Listen to this; the Blackhawk pilot said to air traffic control "there's an aircraft in sight, visual separation." Means he saw it and flew straight into it, sure feels like a suicidal act of mass murder to me. https://t.co/qzZ4p6JXUR
@Bubblebathgirl - Paul A. Szypula 🇺🇸
DC crash official Air Traffic Control radar data playback. Shows the fateful final path. https://t.co/EpvDC28mVO
@Raptorzs1 - Raptorzs
To put things into perspective. It appears that the CRJ700 was on approach to runway 33. This is the gps approach plate for that runway. This is the path fixed wing aircraft have to follow in order to get into that airport. IE the approach corridor. Keep in mind I don’t have all the facts yet but I am curious to see what the helicopter was doing there… Most airlines stick to following the arrivals and approach plates for every flight.
@Brookltnwilliw - Ultra MagaBA🇺🇸
https://t.co/Bx36tgxPye x.com/rawsalerts/sta… 🚨#BREAKING: Shared to me anonymously shows the Playback from official Air Traffic Control radar 📌#Washington | #DC Watch as exclusive playback, sent anonymously by @avgeekjake to Rawsalerst, reveals official Air Traffic Control radar footage displaying the Collision Alert. This alert is not for an imminent collision but serves as a tool to draw heightened attention from the controllers to potential risks. The footage then captures the critical moment when both aircraft collided, emphasizing the urgency of the controllers' split-second decisions. The radar data provides a detailed view of the events leading up to the crash, offering valuable insight into the sequence of actions and how the situation ultimately unfolded. 🔥This sure looks like a terrorist attack🔥
@flight5342 - Flight 5342
🚨#BREAKING: Shared to me anonymously shows the Playback from official Air Traffic Control radar 📌#Washington | #DC Watch as exclusive playback, sent anonymously by @avgeekjake to Rawsalerst, reveals official Air Traffic Control radar footage displaying the Collision Alert. https://t.co/JuFNYDkc3v
@Ttrafiicckaza - Trafficc
Official Air Traffic Control radar captures today's collision near Washington, DC between a passenger aircraft and a US Army Black Hawk helicopter. CA (Collision Alert) signals increased ATC attention, not imminent impact. Source: @avgeekjake https://t.co/CzxjefQyA1
@westerns1978 - Dan Western
🚨#BREAKING: Shared to me anonymously shows the Playback from official Air Traffic Control radar #Washington | #DC Watch as exclusive playback, sent anonymously by @avgeekjake to @Rawsalerst reveals official Air Traffic Control radar footage displaying the Collision Alert. https://t.co/0tA2lR4HHV
@rawsalerts - R A W S A L E R T S
🚨#BREAKING: Shared to me anonymously shows the Playback from official Air Traffic Control radar 📌#Washington | #DC Watch as exclusive playback, sent anonymously by @avgeekjake to Rawsalerst, reveals official Air Traffic Control radar footage displaying the Collision Alert. This alert is not for an imminent collision but serves as a tool to draw heightened attention from the controllers to potential risks. The footage then captures the critical moment when both aircraft collided, emphasizing the urgency of the controllers' split-second decisions. The radar data provides a detailed view of the events leading up to the crash, offering valuable insight into the sequence of actions and how the situation ultimately unfolded
@PlutooXr - Theo☀️
@In2ThinAir @rawsalerts @avgeekjake Not only zig zaging but attempting to crash into other planes. He shouldn't get that close at all. https://t.co/nX8AxaOeSx
@CitizenFreePres - Citizen Free Press
NEW VIDEO OF DC BLACKHAWK COLLISION AND PLANE CRASH These are the clearest images of the collision we've seen so far. How is it possible the Blackhawk pilots did not see the AA jet. https://t.co/mqY2Lnhn0K
@_Tyrant_Slayer - Ken Smith
@Matt_Bracken48 So based off this image the reports of the helicopters not being allowed to travel above 200' are true, and that means the helicopter that took out the plane appears to have done this on purpose. As the helicopter didn't climb until the plane was in sight. https://t.co/r04iZYjFDF
@MichelleMaxwell - Michelle Maxwell
Another perspective. I am going to call my Dad tonight and get his perspective as well since he spent his whole 40 year career working with the FAA and dealing with ATC and flight patterns. Will let you know what he thinks as well. https://t.co/3u07sWEIZj
@prodreamer1 - pro dreamer
#Blackhawk #flight5342 collision NTSB: helicopter flight recorder revealed the female pilot thought their altitude was 100 feet below the altitude that the instructor pilot believed them to be. https://t.co/STXnsbK5bd
@retirednavypm - RetiredNavyPM
I remain convinced there was a miscalculation in the error budget that led the FAA to determine helicopter pilots could safely operate at 200 feet at the location of the collision. A pilot relying on a barometric altimeter could reasonably conclude that staying below an indicated 200 feet ensured safety. This assumption was flawed. Altimeters based on barometric pressure are subject to errors that, when compounded, can be significant enough to guarantee a collision in some instances. Yes, there were contributing secondary factors. The helicopter crew twice reported having the jet in sight. The forthcoming visual studies will confirm the physics and probabilities of this claim and its implications. If they truly saw and heard the warnings about the jet’s location, they should have recognized they had 90–120 seconds before it reached the intersection point—ample time to deconflict, slow down, or change direction. Yet, there was no recorded conversation about deconfliction. To me, this suggests that standard practice did not emphasize identifying and reacting to a collision intersection point within roughly 100 seconds when the ATC Tower alerted the helicopter team that a jet was using Runway 33. Moreover, it’s likely that pilots were too focused on navigating the corridor to perform real-time collision avoidance calculations without prior planning and briefing on major risk areas like this. This raises the question: Did the pre-flight briefing include discussions on how to respond when ATC alerted the crew about Runway 33 landings? Such planning would seem prudent—unless they relied on the FAA’s 200-foot altitude restriction, which brings me back to my central point: FAA engineers failed to properly account for error budget analysis. The altitude restriction at this location should have been set at 75 feet. However, I doubt the military would have accepted such a restriction while flying at night at 100 knots over a dark river. This would have necessitated one of two outcomes: 1.Requiring helicopters to remain under ATC tower control, or 2.Mandating that pilots actively plot and track intersecting aircraft in real time using time-based calculations rather than relying solely on altitude separation. The latter approach—managing collision risk through speed and course adjustments—would have been the only effective way to ensure safety without positive ATC control. There is discussion of future real-time plotting displays in cockpits. Perhaps these could work, provided pilots understand the implications of increased workload and distraction. However, experience suggests this may not be a reliable solution. In Vietnam, pilots often disabled certain warning alarms during critical moments, such as final approaches to drop ordnance, because they could not manage additional distractions. Given the challenges of flying at 100 knots and 200 feet over a river at night, I am not convinced that real-time plotting would be sufficient. Perhaps adding a fourth crew member dedicated to situational awareness and collision avoidance could be a more viable solution.
@prodreamer1 - pro dreamer
@retirednavypm 1. The ATC msg that the CRJ was diverted to runway 33 was not heard by the Blackhawk so they may have moved to the center of the Potomac for separation from a plane they thought was heading North on their left. There were 2 occasions when the instructor corrected the altitude. https://t.co/r407BtCzyI
@retirednavypm - RetiredNavyPM
The visual studies should inform the NTSB what could be seen and what might confuse them. When the CRJ was 1200 feet just south of Woodrow Wilson bridge (about 90 to 120 seconds away), the ATC Tower advised the helicopter of location and that it was going to land on Runway 33. The helicopter replied they had CJR in sight and wanted permission to manage separation based on visibility. I presume that meant they were tracking something (CJR) located just south of that bridge and at 1200 feet elevation for the next 90 seconds or so. I am looking forward to seeing what simulation shows regarding they could see and/or mistake. I was surprised the voice recording showed essentially no discussion of tracking the CJR.
@retirednavypm - RetiredNavyPM
Also, I note your comment that the helicopter flight recorder at this time does not cite the word ‘circle’. I note NTSB does not say that the words “Runway 33” were missing, only that “circle” was missing. They said their recorder team was evaluating. As you suggest, if the helicopter team did not hear CJR was planning Runway 33 verses Runway 1, that would be significant it terms of raising the probability of misidentification. What the helicopter pilots are likely going to see are bright white dots floating in the air and slowly descending. The dot which was the CJR would also have a left horizontal motion as it tracked away from ILS on Runway 1 in order to set up for Runway 33. That would leave the dot for the next jet that was tracking for Runway 1. I would have believed you would be hard pressed to confuse the two. But that was based on initial belief the helicopter heard the CJR was re-aligning for Runway 33. It will interesting to hear what the recorder team concludes on what the helicopter heard.
@prodreamer1 - pro dreamer
@retirednavypm The instructor pilot was primarily there to evaluate the pilot rather than functioning to assist her. This was probably a timed flight with failure resulting from too slow a flight. He may also have been under pressure to not fail her by assuming control due to her incompetence