Eight Dead in a Minute: New Video Sharpens Mystery of Philly Medevac Crash

What is now established is spare and brutal. On January 31, 2025, a twin-engine Learjet 55 operating as a medevac flight crashed along Cottman Avenue near Rupert Street in Northeast Philadelphia.⁠2⁠7 The jet had just departed Northeast Philadelphia Airport.⁠7 About one minute after takeoff, it went down in a densely built area, killing everyone aboard and two people on the ground.⁠7⁠4 The fire and debris field injured at least two dozen more.⁠4

For more than a year, the public record on the crash was thin. That changed on Tuesday, August 18, 2026, when the National Transportation Safety Board released hundreds of pages of investigative records, including surveillance, doorbell and dashcam video, photographs, and flight data capturing the moments before and after the crash.⁠3⁠4⁠5⁠7 The release did not answer why the jet fell. It made the brevity and violence of the sequence visible in a way written summaries never had.⁠3⁠7

The new material comes from ordinary cameras that happened to be pointed in the right direction. Doorbell lenses, storefront surveillance systems, and vehicle dashcams each caught fragments of the jet's brief climb and sudden dive, and together with photographs and recorded flight data they form the backbone of the public docket.⁠3⁠7 Coverage of the release ran from August 18 to 21, 2026, from CNN, NBC10 Philadelphia, ABC and 6abc, the Philadelphia Inquirer, PhillyVoice, AVweb, FlightGlobal, and PennLive.⁠5⁠4⁠3⁠7⁠10⁠2⁠6⁠8⁠9⁠11

Federal investigators are examining possible human error and gaps in FAA oversight, including the pilots' workload and readiness and the agency's oversight of the Mexican medical jet operator.⁠2⁠11 That line of inquiry does not assign blame. It describes where investigators are looking more than 18 months after the crash: at the people in the cockpit and at the system that put them there.⁠2⁠11

PhillyVoice, reviewing the same trove, distilled the focus to three possible factors under study: pilot fatigue, gaps in oversight, and faulty settings.⁠6 Each points to a different kind of failure, one physiological, one institutional, one technical. None has been identified as the cause.⁠6⁠5⁠7

Aviation publication FlightGlobal reported that investigators are exploring the significance of trim settings and the effects of spatial orientation, but added that their significance was yet to become clear.⁠9 In the language of crash investigation, that phrase matters. Trim shapes how an aircraft holds its attitude without constant control input, and disorientation can overwhelm even experienced crews in seconds, especially at night and just after takeoff.⁠9 To say the significance is yet to become clear is to say these are threads, not findings.⁠9

The central fact remains that the cause is undetermined. The NTSB is still trying to figure out what caused the crash.⁠5⁠7 That uncertainty is not a footnote. It is the story after the video, because a visual record of a steep, rapid loss of control does not by itself explain why control was lost.⁠3⁠7⁠5

What the docket does not provide is as important as what it does. No verbatim official explanation of the dive appears in the reported excerpts, and the provided source texts do not confirm precise figures for altitude, speed, or cockpit recorder history that have circulated alongside the footage.⁠2⁠3⁠4⁠5⁠6⁠7⁠8⁠9⁠10⁠11 Readers should treat any such numbers as unconfirmed unless and until they appear in NTSB material itself.⁠3⁠5⁠7