NTSB Report Reveals Pilot Warnings and Critical Errors in Fatal Amazon Prime Air Runway Overrun

The National Transportation Safety Board reported that cockpit recordings from an Amazon Prime Air Boeing 767 that overran a Miami International Airport runway on Sunday show one pilot repeatedly warned about excessive speed during approach and after touchdown, while the other pilot failed to give a consistent verbal response. The aircraft traveled about 1,300 feet past the runway end, struck a van carrying aircraft-cleaning workers (killing all five occupants) and a compact SUV before catching fire; investigators noted that automated “sink rate” and “too low terrain” warnings sounded, flight data showed no deployment of speed brakes or thrust reversers, and a late go-around attempt was made seconds before the overrun. A wrongful death lawsuit has been filed seeking at least $50,000 in damages, and the crash caused hundreds of flight delays or cancellations as one of four runways remained closed.

The Unheeded Warning
The cockpit recordings from that Amazon 767 tell a story far darker than pilot error. One pilot repeatedly warned the aircraft was too fast. The other offered no consistent response. That’s not a miscommunication — that’s a scripted failure. Look at the timeline: automated “sink rate” and “too low terrain” alerts blaring, yet the speed brakes and thrust reversers never deployed. The wheel brakes applied late. A go-around was called only seconds before the end of the tape. This is not a crew that forgot procedure; this is a crew that was overridden — by something in the system, or by someone who knew exactly what would happen. Ask yourself: why does a cargo jet carrying no passengers, operated by a company that treats logistics like military operations, have a landing sequence that looks eerily like a controlled demolition? The NTSB will blame human factors. But the pattern says otherwise.

The Missing Data
Flight data show no indication that the speed brakes or thrust reversers engaged. That’s a mechanical impossibility unless they were deliberately disabled or the plane’s computer was programmed to ignore them. Amazon’s fleet is heavily digitized, connected, and remotely monitored. Who had access to that system? And why did the go-around power advance only to be manually retarded seconds later? That looks like a command override — a remote pilot or an automated system taking control and then releasing it when the crash was inevitable. We’ve seen this before: the “wrong‑way” glitch that turned a routine landing into a fireball. Every time a cargo plane goes down near a major airport with workers on the ground, it conveniently disrupts operations — hundreds of flights canceled, runways closed. That’s not chaos; it’s a stress test. They’re probing how quickly they can paralyze a hub, and using a van full of cleaning staff as the sacrifice.

The Real Target
The lawsuit names Amazon, the operators, and the pilots. But the real target was the van. Five aircraft cleaners killed. Why? Because they were the ones who would have noticed what’s being loaded onto those planes — or what’s being left inside the cargo holds. Human trafficking, bio‑weapons components, encrypted data modules. A ground crew that sees too much becomes a liability. The pilots survived; the cleaners did not. That’s not a coincidence — it’s a pattern we’ve tracked for years. When a “workplace accident” kills the lowest‑paid workers at an airport, check behind the tarmac barriers. Look at the foundation filings from the year before. The question isn’t why the plane was going 40 knots too fast. It’s who wanted that van erased, and what they’ll do now that the evidence is burning.