Five people died last week not because they boarded a plane, but because they were doing ordinary, unglamorous work beside a runway when a 32-year-old cargo jet failed to stop where it was supposed to — a fact that reframes this crash less as an aviation mystery and more as a question of who bears responsibility when a a routine landing goes catastrophically wrong for people who had no seat on the plane at all.
Key Points
- Amazon Prime Air Flight 7598, a Boeing 767 operated by 21 Air LLC, overran Miami International Airport’s runway 30 by roughly 1,300 feet and struck a van carrying cleaning-crew workers, killing five and injuring five more.
- The flight data recorder showed the throttles set to full power seconds before the crash, with no indication that speed brakes or thrust reversers were deployed, according to NTSB investigator Chihoon Shin.
- A wrongful-death lawsuit filed by Yaraisi Santiso Morejon names Amazon, Amazon Air Cargo, 21 Air LLC, and the two pilots, alleging pilot error, inadequate training, and use of an aging aircraft.
- The NTSB has not issued a probable-cause finding, and the investigation remains open — a fact that limits, but does not erase, the strength of the emerging negligence narrative.
- Runway overruns are a well-documented, recurring category of aviation accident, and cargo-carrier liability structures often split responsibility across brand, operator, and lessor in ways that complicate public accountability.
The Sequence of Events on Runway 30
On September 6, Amazon Prime Air Flight 7598, a Boeing 767-33 Alpha operated by 21 Air LLC, came in for a landing at Miami International Airport shortly before 2 p.m. Instead of stopping on the paved surface, the aircraft continued approximately 1,300 feet beyond the runway, according to NTSB Chair Jennifer Homendy. It crossed a service road used by warehouse employees and ground contractors and struck a van carrying seven cleaning-crew workers who were finishing their shift. Five of them died; the survivors, along with others injured on the ground, were hospitalized. The location of the impact — a road meant for airport support traffic, not passengers — is why this crash reads differently from most runway accidents: the fatalities were bystanders, not people who chose to fly.
What the Flight Data Recorder Shows
Early technical findings point toward the landing itself, not an external event, as the operative failure. NTSB investigator Chihoon Shin told reporters the flight data recorder showed the throttles set to full power in the seconds before the crash, and that there was no indication the speed brakes or thrust reversers — the systems that decelerate a landing jet by disrupting lift and reversing engine thrust — had been deployed. Those are precisely the deceleration tools a stabilized landing depends on. Their apparent absence, combined with a nearly quarter-mile overrun, is the kind of physical evidence that tends to anchor a negligence claim, because it describes an aircraft configured for continued flight or a rejected landing rather than one committed to stopping. It does not, on its own, explain why that configuration existed.
Runway Overruns as a Known Aviation Pattern
This is not a novel failure mode. Runway excursions — overruns and veer-offs combined — are among the most frequently recorded runway-safety events worldwide, and a long-running multi-decade study estimated an overrun accident rate near 0.5 per million landings, with contaminated or wet runways, long touchdowns, high approach speeds, and delayed braking consistently cited as contributing anomalies. Cargo operations, notably, account for a smaller share of these events than passenger flights — roughly 15 percent versus 66 percent in one dataset — which makes a cargo-jet overrun statistically less common, though no less consequential when it occurs near ground infrastructure. Canadian transport-safety data shows overruns as a stable, recurring hazard rather than an anomaly, averaging close to ten occurrences a year at that country’s airports alone. The pattern is familiar to investigators; what remains unsettled here is which specific link in the chain broke.
The Lawsuit and the Corporate Structure Behind It
The wrongful-death complaint filed by Yaraisi Santiso Morejon names Amazon, Amazon Air Cargo, 21 Air LLC, and pilots Joseph Carroll and Jaime Felipe Silva Molina, alleging that the crash resulted from pilot error, inadequate training, and reliance on a 32-year-old aircraft. Her attorney’s framing was blunt: this was “not a freak accident, but a foreseeable and preventable disaster caused by negligence.” That theory gains some texture from separate reporting that former 21 Air pilots had previously alleged management suppressed safety reports, pushed crews to fly without adequate rest, and staffed pilots with limited English proficiency — allegations that, if substantiated, would speak directly to a pattern of institutional risk-tolerance rather than a single crew’s isolated mistake. Amazon, for its part, has expressed condolences and pledged cooperation with investigators without conceding fault.
Untangling responsibility among Amazon, the brand under which the flight operated; 21 Air, the certificated operator actually flying and maintaining the jet; and the aircraft’s ownership and leasing chain is not a bureaucratic footnote — it is often the crux of aviation liability litigation. U.S. law generally shields a passive aircraft owner or lessor from liability unless it retained actual possession or operational control, meaning fault tends to concentrate on whoever directed the flight and maintained the plane, not merely whoever branded it. That legal architecture explains why plaintiffs typically name every entity in the chain — operator, lessor, and manufacturer alike — and let discovery sort out who controlled what.
"MY CAREER IS OVER": A cargo plane pilot who escaped a fiery crash near Miami International Airport was visibly shaken and urgently asked a nearby warehouse worker to use his phone to call his wife, a witness said. https://t.co/zDDHrphYMR
— WPLG Local 10 News (@WPLGLocal10) September 9, 2026
What the Investigation Still Owes the Public
The NTSB has not determined probable cause, and that omission matters for what can be asserted with confidence today. The full cockpit voice recorder transcript, maintenance and airworthiness records for the aircraft, and 21 Air’s training and dispatch files have not yet been made public. Those materials — not the early throttle and overrun data alone — will ultimately determine whether this accident traces to pilot decision-making under pressure, a mechanical or configuration failure, environmental conditions, or some combination the investigation has not yet weighted. Litigation discovery, running on its own timeline, may surface internal safety communications faster than the federal probe does. Until then, the physical facts — full power, no deployed reversers, a 1,300-foot overrun, and five people killed in a van on a service road — stand on their own as the clearest record of what happened, even as the harder question of why remains open.
Sources:
washingtontimes.com, cbsnews.com, cnn.com, reuters.com, abcnews.com, miamiherald.com, pbs.org, washingtonpost.com, en.wikipedia.org, foxnews.com