Amazon-owned Boeing 767 cargo plane crashes after overshooting runway in Miami

9/6/26 Boeing 767 Runway Overrun in Miami, FL - Flight Safety Detectives​

On 9/6/26 at 1:53pm EDT, a Boeing 767 experienced a runway overrun at Miami Intl Airport in Miami, FL. The Flight Safety Detectives discuss the known facts.

John Goglia and Greg Feith dive into what’s known so far about the fatal 21 Air Boeing 767-33A accident in Miami, including the weather, the aircraft’s approach, and whether installation of a runway Engineered Material Arresting System (EMAS) would have made a difference in this event.
 

NTSB B-Roll - Miami, Florida, Boeing 767 Cargo Plane Runway Excursion Accident - NTSBGov​




In the closeup footage the aircraft fuselage looks surprisingly intact, though the right wing and engines are badly damaged. The drone flyover shows a relatively smooth runoff area, with no major obstacles, and clear and flat towards the horizon. At normal speeds this overrun would have been much less serious. In theory a go-around should have been safe until the last second (while still on the runway).

Google says the stall speed for a lightly loaded B767 is surprisingly low, though obviously this is an extreme case:
Light Weight / Landing Configuration (Full Flaps and Gear Down): Down to 90 to 110 KIAS when very light with high-lift devices fully deployed.
 
There have been some insinuations that the pilots first language is not English and that some loophole was used for the paperwork to allow the planes to operate in the US when in fact the company owners were in Canada.

This is one
 

The Pilots Tried to Go Around, Then Changed Their Mind - Taking Off​

The flight data recorder from the Miami cargo plane crash shows something the NTSB hasn't fully explained yet: the throttles came up to go-around power, then went back to idle four seconds later.

Here's the second-by-second breakdown from the September 8th briefing, plus what's actually confirmed, and not confirmed, about the crew and the airline's safety record.

 

Prime Air Crash Update: What the NTSB Just Revealed - Captain Steeeve​

The NTSB has released new information and investigative footage from the deadly Prime Air Boeing 767 crash at Miami International Airport, and Captain Steeeve is taking a closer look at what investigators are now revealing.

Preliminary flight data indicates the aircraft touched down at approximately 158 knots. Investigators say the crew applied the brakes, then increased engine power and released the brakes in what appears to have been an attempted go-around after touchdown. Moments later, the throttles returned to idle and braking resumed.

Perhaps most notably, the NTSB says the aircraft's speed brakes and thrust reversers were not deployed during the landing rollout.

In this update, Captain Steeeve reacts to footage released during the NTSB briefings, walks through the sequence of events, and explains what pilots would normally be thinking and doing during the critical seconds following touchdown.

Five people on the ground were killed when the aircraft overran the runway. Our thoughts and prayers remain with their families and everyone affected by this tragedy.

The NTSB investigation is still ongoing, and no final determination of probable cause has been made. This video discusses publicly available preliminary information and should not be interpreted as assigning blame or determining the cause of the accident.

 

Why This 767 Never Stopped (The Data Is Shocking) - Garybpilot​

Pilot review of the latest NTSB flight-data update on the Miami 767 runway overrun.

In this video I break down the final 30 seconds of the Amazon Prime Air Boeing 767 crash at Miami International Airport — the late/uneven touchdown, brakes on then off, brief go-around thrust, aborted go-around, and why speed brakes and thrust reversers never deployed.

We look at the actual data the NTSB just released and what it means from a pilot’s perspective.

This is an ongoing investigation. Five people on the ground lost their lives. This video is an analysis of the publicly released data only.

 
Latest update from Juan Browne...

NTSB CVR Data Released MIA 21Air 767 Crash - blancolirio​


WOW! CRM failure. I'm still watching now, but Juan points out the cockpit 'gradient' as a big factor. The older captain with less time on type vs the younger co-pilot with more time on type.

Edit: The CVR shows that the aircraft was screaming at them: Sink Rate! Too Low! Terrain!

Hollywood version: Aren't we going a bit fast? Silence. OK BOSS. Then crash...

P.S. Includes NTSB B-roll footage. The only channel you need to watch.
 
Last edited:
And these bastards complain about our pilots

The problem is that cargo always goes to the lowest bidder, and that carries over to their training programs, and the pilots they employ. Do not generalise about US pilots, but rather focus on Amazon and other cost cutters, who outsource everything.
 
The problem is that cargo always goes to the lowest bidder, and that carries over to their training programs, and the pilots they employ. Do not generalise about US pilots, but rather focus on Amazon and other cost cutters, who outsource everything.
The lowest bidder in isolation creates a rush to the bottom.

/ Also, Airlink should hire these guys. The have no fear of flying at 10 feet. :whistling:
 
Time on type might have been a factor in not being anywhere near stable at the stabilized approach point (was the captain PF? Too lazy to check), but it has nothing to do with the daft decision of not simply going around. That gets drilled into you from the early days of flight school already.
 
Calling for landing flaps 30 just above 40 feet is fkn unheard of. The flaps wouldn't even have enough time to run to 30 before touching down at that stage - you're basically already flaring. This incompetent captain belongs in jail.
 
Calling for landing flaps 30 just above 40 feet is fkn unheard of.

Airlink:

monkey-looking-away-meme-template-thumbnail-60662f1a.webp


/runs
 
Top
Sign up to the MyBroadband newsletter
X