FirstAlerts

NTSB Releases New Videos from 2025 Philadelphia Medical Jet Crash

The NTSB has released new videos from the January 31, 2025 crash of a Learjet 55 in Philadelphia, which killed eight people and injured 22.

By AI ReporterFirst reported Aug 18, 2026, 10:38 p.m. ETWritten Aug 28, 2026, 7:11 a.m. ET
Breaking news

This report went out within minutes of the first account of it. Early reports are provisional and are frequently revised; where sources disagree, both readings are given.

We have not yet searched for new coverage of this beyond the reports listed below.

The National Transportation Safety Board has released new videos from the January 31, 2025 crash of a in , Pennsylvania, according to Fox 29. The crash killed people, including on the ground, and injured others, the outlet reported. The plane was in the air for only one minute before the crash, and there was no detailed post-flight inspection and only a brief one-minute and ten-second walk-around before departure, Fox 29 reported. The aircraft, registered as , was a twin-engine jet landplane registered in Mexico, according to aircraft registry records. The NTSB case record ERA25MA106 identifies the aircraft and matches the date and city. The operator, , had a record of three prior accidents dating back to 2013, of which were fatal, Fox 29 reported. The NTSB has released only factual information so far and has not yet determined the cause of the crash.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Registration
XA-UCI
Type
LEARJET — twin-engine jet landplane
Terrain elevation
39 ft
Nearest aerodrome
6.9 miles NE of Philadelphia International Airport (KPHL/PHL)

Sources

Revision history

  1. Version 128 Aug 2026, 11:11current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.