The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB DCA25MA108 · Final report

Bombardier INC CL-600-2C10 and Sikorsky UH60 mid-air collision near Washington, District of Columbia, January 30, 2025

On January 30, 2025 at about 1:48 am local time, 2 aircraft, Bombardier INC CL-600-2C10 (N709PS) and Sikorsky UH60 (UNREG), were involved in a mid-air collision near Washington, District of Columbia. 67 people were killed. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The Federal Aviation Administration’s (FAA) 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 Ronald Reagan Washington National Airport (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. Also causal was the lack of effective pilot-applied visual separation by the helicopter crew, which resulted in a midair collision. Additional causal factors were 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, which resulted in misprioritization of duties, inadequate traffic advisories, and the lack of safety alerts to both flight crews. Also causal was the Army’s failure to ensure pilots were aware of the effects of error tolerances on barometric altimeters in their helicopters, which resulted in the crew flying above the maximum published helicopter route altitude. Contributing factors include: · the limitations of the traffic awareness and collision alerting systems on both aircraft, which precluded effective alerting of the impending collision to the flight crews; · an unsustainable airport arrival rate, increasing traffic volume with a changing fleet mix, and airline scheduling practices at DCA, which regularly strained the DCA air traffic control tower workforce and degraded safety over time; · the Army’s lack of a fully implemented safety management system, which should have identified and addressed hazards associated with altitude exceedances on the Washington, DC, helicopter routes; · the FAA’s failure across multiple organizations to implement previous NTSB recommendations, including Automatic Dependent Surveillance–Broadcast In, and to follow and fully integrate its established safety management system, which should have led to several organizational and operational changes based on previously identified risks that were known to management; and · the absence of effective data sharing and analysis among the FAA, aircraft operators, and other relevant organizations.
The Federal Aviation Administration’s (FAA) 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 Ronald Reagan Washington National Airport (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. Also causal was the lack of effective pilot-applied visual separation by the helicopter crew, which resulted in a midair collision. Additional causal factors were 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, which resulted in misprioritization of duties, inadequate traffic advisories, and the lack of safety alerts to both flight crews. Also causal was the Army’s failure to ensure pilots were aware of the effects of error tolerances on barometric altimeters in their helicopters, which resulted in the crew flying above the maximum published helicopter route altitude. Contributing factors include: · the limitations of the traffic awareness and collision alerting systems on both aircraft, which precluded effective alerting of the impending collision to the flight crews; · an unsustainable airport arrival rate, increasing traffic volume with a changing fleet mix, and airline scheduling practices at DCA, which regularly strained the DCA air traffic control tower workforce and degraded safety over time; · the Army’s lack of a fully implemented safety management system, which should have identified and addressed hazards associated with altitude exceedances on the Washington, DC, helicopter routes; · the FAA’s failure across multiple organizations to implement previous NTSB recommendations, including Automatic Dependent Surveillance–Broadcast In, and to follow and fully integrate its established safety management system, which should have led to several organizational and operational changes based on previously identified risks that were known to management; and · the absence of effective data sharing and analysis among the FAA, aircraft operators, and other relevant organizations.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 30, 2025 · about 1:48 am local time
Place
Washington, District of Columbia · map
Type
Accident · mid-air collision
Injuries
67 people were killed.
Weather
visual conditions (good weather)
Aircraft 1
Bombardier INC CL-600-2C10, built 2004
Registration
N709PS · no longer on the register · serial 10165
Damage
Destroyed
Flight
Flight · scheduled airline rules (Part 121)
Aircraft 2
Sikorsky UH60 L · all UH60s on the register
Registration
UNREG · no longer on the register · serial 702614
Damage
Destroyed
Flight
Flight · military rules

The NTSB's narrative for the Bombardier INC CL-600-2C10 final · quoted from the NTSB record

On January 29, 2025, about 2048 eastern standard time, a Sikorsky UH 60L, operated by the US Army under the callsign PAT25 (Priority Air Transport Flight 25), and an MHI (Mitsubishi Heavy Industries) RJ Aviation (formerly Bombardier) CL-600-2C10 (CRJ700), N709PS, operated by PSA Airlines as American Airlines flight 5342, collided in flight about 0.5 miles southeast of Ronald Reagan Washington National Airport (DCA), Arlington, Virginia, and impacted the Potomac River in southwest Washington, DC. The 2 pilots, 2 flight attendants, and 60 passengers on board the airplane and all 3 crewmembers on board the helicopter died. Both aircraft were destroyed as a result of the accident. Flight 5342 was operating under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from Wichita Dwight D. Eisenhower National Airport, Wichita, Kansas, to DCA. PAT25 originated from Davison Army Airfield, Fort Belvoir, Virginia, for the purpose of the pilot’s annual standardization evaluation flight with the use of night vision goggles. Night visual meteorological conditions prevailed in the area of DCA at the time of the accident.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Sikorsky UH60 final · quoted from the NTSB record

On January 29, 2025, about 2048 eastern standard time, a Sikorsky UH 60L, operated by the US Army under the callsign PAT25 (Priority Air Transport Flight 25), and an MHI (Mitsubishi Heavy Industries) RJ Aviation (formerly Bombardier) CL-600-2C10 (CRJ700), N709PS, operated by PSA Airlines as American Airlines flight 5342, collided in flight about 0.5 miles southeast of Ronald Reagan Washington National Airport (DCA), Arlington, Virginia, and impacted the Potomac River in southwest Washington, DC. The 2 pilots, 2 flight attendants, and 60 passengers on board the airplane and all 3 crewmembers on board the helicopter died. Both aircraft were destroyed as a result of the accident. Flight 5342 was operating under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from Wichita Dwight D. Eisenhower National Airport, Wichita, Kansas, to DCA. PAT25 originated from Davison Army Airfield, Fort Belvoir, Virginia, for the purpose of the pilot’s annual standardization evaluation flight with the use of night vision goggles. Night visual meteorological conditions prevailed in the area of DCA at the time of the accident.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the Bombardier INC CL-600-2C10 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during approach defining event

The NTSB's findings

  • Organizational issues › Development › Design › Policy/procedure development › FAA/Regulator
  • Organizational issues › Support/oversight/monitoring › Enforcement › Regulatory requirements › FAA/Regulator
  • Organizational issues › Support/oversight/monitoring › Oversight › Oversight of operation › FAA/Regulator
  • Organizational issues › Management › Policy/procedure › Adequacy of policy/proc › ATC
  • Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot of other aircraft
  • Environmental issues › Operating environment › Air traffic/operating proc › Airway/route system procedure › Contributed to outcome
  • Personnel issues › Psychological › Attention/monitoring › Monitoring environment › ATC personnel
  • Personnel issues › Task performance › Workload management › Task overload › ATC personnel
  • Organizational issues › Management › Policy/procedure › Availability of policy/proc › ATC
  • Organizational issues › Support/oversight/monitoring › Oversight › Oversight of personnel › Other institution/organization
  • Organizational issues › Support/oversight/monitoring › Oversight › Equipment monitoring › Other institution/organization
  • Aircraft › Aircraft systems › (general) › (general) › Capability exceeded
  • Environmental issues › Operating environment › Air traffic/operating proc › Terminal arrival procedure › Contributed to outcome
  • Environmental issues › Operating environment › Air traffic/operating proc › Traffic congestion › Contributed to outcome
  • Organizational issues › Support/oversight/monitoring › Safety programs › Adequacy of safety program › Other institution/organization
  • Organizational issues › Support/oversight/monitoring › Safety programs › Adequacy of safety program › FAA/Regulator
  • Organizational issues › Management › Communication (organizational) › Between groups/organizations › FAA/Regulator
  • Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Contributed to outcome

The aircraft

  • Seats: 80
  • Landing gear: retractable
  • Engine 3: Ge CF34 SERIES (turbofan); 20,740 hours total
  • Engine 4: Ge CF34 SERIES (turbofan); 17,841 hours total
  • Not recorded
  • Operator: Psa Airlines

The flight

  • Departed from: ICT Wichita KS
  • Destination: DCA Washington DC
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 300° at 14 knots, gusting 23
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 50°F (10°C), dew point 19°F (-7°C)
  • Altimeter: 29.90 inHg
  • Observation at 8:52 pm from KDCA

Weather report (METAR): METAR KDCA 300152Z 30014G23KT 270V330 10SM CLR 10/M07 A2990 RMK AO2 PK WND 30033/0108 SLP126 T01001072=126,135,072

Injuries

FatalSeriousMinorNone
Cabi2
Flig2
Passengers60

The factual record for the Sikorsky UH60 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during enroute defining event

The NTSB's findings

  • Organizational issues › Development › Design › Policy/procedure development › FAA/Regulator
  • Environmental issues › Operating environment › Air traffic/operating proc › Airway/route system procedure › Contributed to outcome
  • Organizational issues › Support/oversight/monitoring › Enforcement › Regulatory requirements › FAA/Regulator
  • Organizational issues › Support/oversight/monitoring › Oversight › Oversight of operation › FAA/Regulator
  • Organizational issues › Management › Policy/procedure › Adequacy of policy/proc › ATC
  • Organizational issues › Management › Policy/procedure › Availability of policy/proc › ATC
  • Aircraft › Aircraft systems › (general) › (general) › Capability exceeded
  • Environmental issues › Operating environment › Air traffic/operating proc › Terminal arrival procedure › Contributed to outcome
  • Environmental issues › Operating environment › Air traffic/operating proc › Traffic congestion › Contributed to outcome
  • Organizational issues › Support/oversight/monitoring › Safety programs › Adequacy of safety program › Other institution/organization
  • Organizational issues › Support/oversight/monitoring › Safety programs › Adequacy of safety program › FAA/Regulator
  • Organizational issues › Management › Communication (organizational) › Between groups/organizations › FAA/Regulator
  • Organizational issues › Support/oversight/monitoring › Oversight › Oversight of personnel › Other institution/organization
  • Organizational issues › Support/oversight/monitoring › Oversight › Equipment monitoring › Other institution/organization
  • Personnel issues › Task performance › Workload management › Task overload › ATC personnel
  • Personnel issues › Psychological › Attention/monitoring › Monitoring environment › ATC personnel
  • Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Flight crew
  • Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Contributed to outcome

The aircraft

  • Landing gear: fixed
  • Engine 1: Ge T700-GE-701D (turboshaft); 0 hours total
  • Engine 2: Ge GE T700-GE-70 (turboshaft); 0 hours total
  • Not recorded
  • Operator: Army Department Of Defense

The flight

  • Departed from: DAA Fort Belvoir VA at 11:45 pm
  • A second pilot was aboard

Injuries

FatalSeriousMinorNone
Flig2
Passengers1

Other NTSB records under N709PS the same tail number, which may have belonged to a different aircraft at the time

2021-03-26ENG21LA023 · incident near North Canton, OH · minor damage · no injuries
2017-02-15DCA17CA064 · accident near Charlotte, NC · substantial damage · no injuries

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA25MA108.