MEBRO

DISINFO DESK

Conspiracy & Hoaxes

D.C. Mid-Air Collision Misinfo

Fact-check of misinformation narratives surrounding the January 2025 D.C. mid-air collision near Reagan National Airport. DEI-blame claims and sabotage conspiracy theories are unsupported; FAA staffing shortages are real. Updated with the NTSB's final findings, released January 2026.

MISLEADING

FILED AUG 22, 2026 · UPDATED AUG 22, 2026 · 9 SOURCES

The Tragedy: What We Know

The collision occurred on the evening of January 29, 2025, as American Eagle Flight 5342, a Bombardier CRJ700 regional jet operated by PSA Airlines, approached Reagan National Airport around 9 p.m. [2][3]

A U.S. Army UH-60 Black Hawk helicopter from B Company, 12th Aviation Battalion, based at Fort Belvoir, Virginia, was on a training flight in the same airspace. The aircraft collided over the Potomac River, and both went down in the water, killing all 67 people aboard the two aircraft — 64 on the jet and three soldiers on the helicopter. [3]

Key confirmed facts from official sources:

The NTSB led the investigation, with the FAA supporting. The NTSB's board meeting to determine probable cause was held January 27, 2026, about a year after the crash. [1][2]

False Narrative #1: DEI Hiring Blamed

Within hours of the crash, President Trump and others claimed that diversity, equity, and inclusion (DEI) hiring practices at the FAA were responsible for the tragedy, alleging unqualified air traffic controllers were hired to meet diversity quotas. [5]

There is no evidence linking DEI policy to this incident. FactCheck.org found the FAA's diversity hiring programs had been in place since at least 2013 — years before the change in administration that Trump blamed — undercutting the claim that a recent policy shift was responsible. [5]

The NTSB's completed investigation, concluded in January 2026, attributed the crash to systemic failures in airspace design, equipment, and air-traffic-control procedures. It did not cite controller hiring practices or DEI policy as a factor. [1][4]

The National Air Traffic Controllers Association (NATCA) did not address the DEI claims by name in its official statement. Instead it stood behind controllers as a "highly trained, highly skilled" workforce and pledged cooperation with the investigation. [6]

False Narrative #2: Deliberate Sabotage

Conspiracy theories claiming the collision was a deliberate act spread on social media, including claims the aircraft were intentionally directed into each other and comparisons to an assassination plot. [7]

One widely shared claim held that CNN reported the crash roughly five hours before it happened, implying advance knowledge. Lead Stories traced this to a mistimestamped screenshot and confirmed CNN's first report came about 40 minutes after the roughly 8:50 p.m. collision, around 9:31 p.m. [7]

There is no evidence of deliberate action. The NTSB's final report found the Black Hawk crew, flying a night proficiency check ride with night-vision goggles, had degraded visibility and likely never saw the approaching jet, and traced the crash to a faulty altimeter reading combined with airspace-design and air-traffic-control failures — not intent. [1][4]

Verified Concerns: FAA Staffing Issues

While the DEI-blame and sabotage claims are unsupported, concerns about FAA air traffic controller staffing are legitimate and were documented well before this crash. [8]

A DOT Inspector General audit released in June 2023 found 20 of 26 critical FAA facilities — 77% — staffed below the agency's own 85% target, citing high attrition and training backlogs. [8]

A subsequent GAO report found the national controller workforce had shrunk about 6% since 2015 even as flight volume rose roughly 10%, and that the FAA's hiring pipeline can take two to six years per controller. [9]

At Reagan National specifically, the FAA's own account of the crash lists the tower's authorized strength as 30 certified controllers, with 22 working the position at the time, eight in training, and four temporarily assigned from other facilities. [2]

What the Investigation Actually Found

Major NTSB accident investigations typically take a year or more to complete; this one concluded roughly a year after the crash, when the board met on January 27, 2026 to determine probable cause. [1]

NTSB Chair Jennifer Homendy said the board found "deep, underlying systemic failures — system flaws — [that] aligned to create the conditions that led to the devastating tragedy," adding that "the conditions for this tragedy were in place long before the night of Jan. 29." [1]

The board did not identify a single cause. It cited the FAA's failure to act on more than 80 reported close calls between helicopters and airplanes near the airport, a faulty altimeter reading aboard the Black Hawk, a single controller handling both helicopter and airplane traffic, and gaps in the Army's own safety-reporting system — and issued 50 safety recommendations. [1][4]

Conclusion

The D.C. mid-air collision was a genuine tragedy, and the year-long federal investigation has since produced its answer. Our assessment, updated to reflect the NTSB's final findings:

FALSE: Claims blaming DEI hiring policies or alleging deliberate sabotage have no evidentiary support. The completed NTSB investigation attributes the crash to airspace design, equipment failure, and air-traffic-control and safety-oversight lapses — not hiring practices or intent. [1][4][5]

TRUE: FAA air traffic controller staffing shortages are real and were documented years before this crash, though investigators did not identify DCA tower staffing itself as a cause of the collision. [1][8][9]

RESOLVED: The NTSB investigation that was ongoing when this piece first published has since concluded; the board's January 2026 findings are summarized above. [1]

The families of the 67 victims deserve factual reporting, not speculation and misinformation.

MEBRO · DISINFO DESK · mebro.app

Investigative report — not a user-submitted fact-check.

AI-built, source-verified. Every claim here was checked against the sources cited above before publishing — but don't just trust us: follow any citation to its source and confirm it yourself. That's the whole point.