American Eagle Flight 5342 and the Army PAT25 Midair Collision at Reagan National Airport (2025)

What Happened at Reagan National Airport on January 29, 2025, and What the Record Confirms for Families

The official record of the Reagan National Airport crash is the NTSB's Aviation Investigation Final Report - Accident Number: DCA25MA108. The report lists the date and time as January 29, 2025, 20:48 local time, and the location as Washington, District of Columbia. Its "defining event" is a midair collision.

The report's analysis states that a Sikorsky UH-60L operated by the US Army under the callsign PAT25 (Priority Air Transport Flight 25) and a CRJ700 regional jet operated by PSA Airlines as American Airlines flight 5342, the flight many people search for as American Eagle 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 NTSB records the highest injury level as fatal. In the report's words, "The 2 pilots, 2 flight attendants, and 60 passengers on board the airplane and all 3 crewmembers on board the helicopter died." The report lists 64 fatal injuries for the airplane and 3 for the helicopter, and states that both aircraft were destroyed.

The report also records the conditions. It states that night visual meteorological conditions prevailed, with clear skies, 10 miles of visibility, and wind from 300 degrees at 14 knots gusting to 23, as observed at the airport at 20:52.

For a family, these details are the fixed points of the official record: the time, the place, which aircraft your loved one was aboard, and the conditions that night. Some families find it useful to note the accident number, DCA25MA108, since it is how the NTSB identifies this record and how later questions about it are usually framed. What the NTSB concluded about why it happened is covered below, in the agency's own language.

Which Aircraft and Operators Were Involved, and Why the Difference Matters to Families

The NTSB report separates the two aircraft, labeling the airplane "A1" and the helicopter "A2." Keeping them apart matters, because each was flying under a different set of rules.

The airplane is listed as a BOMBARDIER INC CL-600-2C10, registration N709PS, built in 2004, serial number 10165, with 80 seats and two engines. The report describes it as an MHI (Mitsubishi Heavy Industries) RJ Aviation (formerly Bombardier) CRJ700. It lists the registered owner as UMB BANK NA TRUSTEE, the operator as PSA Airlines, and the operator as doing business as American Airlines flight 5342. The NTSB's American Airlines NTSB records page on this site collects other records naming that airline.

According to the report, 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 in Kansas to DCA. It departed at 18:39 local time on an instrument (IFR) flight plan. Part 121 is the set of Federal Aviation Administration (FAA) rules for airline operations, and the report lists the flight as "Part 121: Air carrier - Scheduled." An air carrier, in plain words, is a company that carries passengers or cargo by air as a business, under a certificate from the FAA. The report lists PSA Airlines' certificate as "Flag carrier (121)."

For families of the helicopter crew, the record describes a very different aircraft. The report identifies it as a Sikorsky UH60 L, serial number 702614, with a GE T700-GE-701D turboshaft engine, and it was not on the civil register. The Army Department of Defense is listed as both its owner and its operator, and it held no FAA operating certificate. The report lists it as flying under "Armed Forces" rather than a civil part of the federal rules. It departed Davison Army Airfield at Fort Belvoir, Virginia, at 18:45 on a military VFR flight plan, for "the pilot's annual standardization evaluation flight with the use of night vision goggles."

The report places both aircraft in Class B airspace, the controlled airspace around a busy airport. The practical point is that a civil airline flight and a military flight sit under different authorities, which can affect which questions arise later and against whom. If you lost someone on one aircraft rather than the other, it can help to keep track of which aircraft that was and who operated it, since that is often where an attorney's questions begin.

The NTSB Investigation: Status and What the Final Report Covers

This investigation is closed in the NTSB's sense: a final report has been issued. The report shows an original publish date of February 17, 2026, lists the investigation as Class 1, and notes that the NTSB traveled to the scene. The NTSB dataset read on 2026-10-17 carries the agency's probable-cause statement for DCA25MA108.

A few terms help here. A preliminary report is an early, short summary the NTSB may release soon after an accident; it states initial facts and is not a conclusion. A final report is the agency's completed account, with its factual information, its findings and its probable cause. A probable cause is the NTSB's own determination of what caused or contributed to the accident.

What a probable cause is not matters just as much. The final report states that the NTSB "does not assign fault or blame for an accident or incident," and quotes its own regulation: investigations "are fact-finding proceedings with no formal issues and no adverse parties … and are not conducted for the purpose of determining the rights or liabilities of any person." So the report is a safety finding, not a legal judgment about who owes what to whom.

Federal law adds a second limit. Under 49 U.S.C. § 1154(b), "No part of a report of the Board, related to an accident or an investigation of an accident, may be admitted into evidence or used in a civil action for damages resulting from a matter mentioned in the report." The NTSB's report adds that "A factual report that may be admissible under 49 United States Code section 1154(b) is available."

For a family, this is a real decision point. The final report can explain what happened, but a civil case would need to prove its points with other evidence. Questions families often weigh at this stage include whether they have read the report itself, what the separate factual report contains, and what other evidence may exist. Whether and how a case can be built depends on the facts and on the law that applies, which is part of what a conversation with an attorney can help sort out.

What the NTSB Record States About Cause: Factual Summary of DCA25MA108

The NTSB opens its conclusions with the words, "The National Transportation Safety Board determines the probable cause(s) of this accident to be:" What follows is quoted from the final report, attributed to the NTSB and published February 17, 2026. This page adds no cause of its own.

The NTSB states the probable cause as: "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."

The report continues that "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," and that "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."

The NTSB then lists contributing factors, including the limitations of the traffic awareness and collision alerting systems on both aircraft; "an unsustainable airport arrival rate, increasing traffic volume with a changing fleet mix, and airline scheduling practices at DCA"; the Army's lack of a fully implemented safety management system; the FAA's failure to implement previous NTSB recommendations, "including Automatic Dependent Surveillance–Broadcast In"; and "the absence of effective data sharing and analysis among the FAA, aircraft operators, and other relevant organizations."

Alongside that narrative, the report attaches short coded findings to both aircraft, and several echo the themes above, such as "Task overload - ATC personnel," "Traffic congestion - Contributed to outcome" and "Dark - Contributed to outcome."

For a family, the stake is that the NTSB names several organizations and conditions, not a single cause. These are safety conclusions, not a court's findings of legal fault. A family reading them may ask which of the named organizations and practices relate to their loss, and an attorney can help explain how the legal questions differ from the safety ones.

What Evidence Families Can Use: What the NTSB Gathers and Why It Matters

A major investigation draws on many participants, and the list shows how many organizations hold knowledge of this accident. The final report names participating parties from the FAA, PSA Airlines, GE Aerospace, Sikorsky, the US Army, the National Air Traffic Controllers Association, the Air Line Pilots Association, the Association of Flight Attendants, the International Association of Machinists and Aerospace Workers, the Metropolitan Washington Airports Authority, the Transportation Safety Board of Canada, Mitsubishi Heavy Industries, Transport Canada and Collins Aerospace. The report also refers to a public investigation docket for the project, which families may consult alongside the report.

Some of the most sensitive evidence in any aviation case is recorder material, and federal law treats it specially. Under 49 U.S.C. § 1154(a), a party in a court case generally may not use discovery to obtain a cockpit recorder recording, or parts of a recorder transcript or still images the NTSB has not made public. A court may allow it only after a private (in camera) review, if it decides the public material does not give the party "sufficient information for the party to receive a fair trial" and more is necessary for one. When a court allows it, the statute requires a protective order limiting its use to the case, and admitting it into evidence requires placing it under seal.

So recorder material is tightly controlled, and, as explained above, the NTSB report itself cannot be used in a civil case. The facts the investigation uncovered often still matter, but they reach a courtroom by other routes.

Families often keep their own records too: death certificates, travel and ticket records, messages and communications with the airline or agencies, and records of a loved one's work and income. If you lost someone on this flight or this helicopter, those are the kinds of papers that usually come up. Limitation periods, fault rules and damages rules differ from state to state, and no single state's rule governs a case like this one. If it would help to talk through which records may matter, you can request a case evaluation.

What Families Affected by a Fatal Aviation Accident May Consider

When a death happens, the claim the law generally recognizes is called wrongful death: a civil claim, brought for a person who died, by the people or the estate the law allows, against someone whose wrongful conduct is alleged to have caused the death. Who may bring it, what must be shown and what it may cover are set by the law that applies, not by the NTSB.

That law varies. Each state writes its own wrongful-death statute, its own limitation period, its own comparative-fault rule and its own list of what damages the law may allow. This site's Texas aviation accident lawyer and California aviation accident lawyer pages show how two states' rules differ, and neither state's rule is the rule everywhere. This accident also involved a civil airline, a military aircraft and a federal air traffic system, which can raise questions about which court hears a case and whose law applies. Those questions can look different for families of the airplane's passengers and crew than for families of the helicopter crew, and they turn on facts and law this page does not resolve.

Whatever framework applies, the basic questions stay the same: whether someone owed a duty of care, whether it was breached, whether that breach caused the death, and what losses followed. The NTSB's probable cause speaks to safety, not to those legal elements, and whether any of them is met depends on the facts.

For a family, the weight here is not abstract. It is about deadlines that differ by place, about which records and witnesses exist, and about getting clear on what questions apply to your loss. A conversation with an attorney can help sort out which jurisdictions may be involved and what each one asks.