Amazon Pauses 21 Air After Miami Overrun

Amazon has paused operations with cargo carrier 21 Air following a runway overrun at Miami International Airport on 6 September 2026 that killed five people on the ground. The aircraft involved, a 32-year-old Boeing 767-300 freighter operating under the Amazon Air network, overran the runway during landing and came to rest beyond the paved surface. The pause was described by Amazon as a commercial decision rather than a regulatory action, but it removes a meaningful slice of capacity from the e-commerce operator's freighter network while the National Transportation Safety Board (NTSB) investigation continues.

What the flight data shows

Preliminary NTSB data released in the days after the accident outlines a landing sequence that deteriorated rapidly in its final seconds. The aircraft touched down at 158 knots groundspeed — a figure well above typical touchdown reference speeds for a 767-300F at normal landing weights, where Vref generally sits in the 130-to-145-knot range depending on configuration and weight.

The sequence reconstructed from flight data recorder information is as follows:

1. Brakes were applied after touchdown, then released.
2. The throttles were advanced toward go-around thrust, then returned to idle.
3. Speed brakes did not deploy.
4. Thrust reversers did not deploy.

The combination meant the aircraft crossed the runway threshold fast, touched down long, and then spent several critical seconds generating very little deceleration. Cockpit voice recorder information indicates one of the pilots called out the excessive speed before touchdown — a warning that did not translate into a rejected landing or an effective go-around before the aircraft departed the paved surface.

The aircraft was on its third flight of the day, and the NTSB will almost certainly examine crew duty time, fatigue, and the decision dynamics on the flight deck as part of its human factors work. The board's investigation into the decision to apply and then release the brakes, and to advance and then retard the throttles, will look at whether the crew initiated a go-around and abandoned it, or whether the throttle movement reflected a momentary control input that was never fully carried through.

The ground fatalities

The most severe dimension of this accident is on the ground. Five people on the ground were killed — a rare and catastrophic outcome for a runway excursion, and one that recalls the risks airport workers face near active runways and taxiways. The Flight Brief covered a similar ground-worker fatality during a pushback operation in Montreal earlier this year, an accident that drew attention to procedural protections for ramp and manoeuvring-area workers (Montreal airport worker fatality during pushback).

Runway excursions are the most common accident category in commercial aviation by a wide margin, and most end without fatalities. When aircraft depart the runway end near airports with dense ground infrastructure, vehicle traffic, or work areas, the ground risk profile changes entirely. The NTSB will document where the five victims were relative to the aircraft's path and what barriers, if any, existed between the runway safety area and the location where the aircraft stopped.

Amazon's decision and the Part 121 operator landscape

Amazon characterised the pause as a commercial decision, not a regulatory one. The distinction matters. The FAA has the authority to act against an air carrier's certificate through the Part 121 certification framework under which 21 Air operates, and it has emergency authority when an operator presents an unacceptable risk. A voluntary commercial pause by the network's customer — Amazon — sits outside that regulatory machinery, even if it produces a similar operational outcome.

For the freighter operator, a pause of this kind has immediate consequences. Aircraft that are not flying generate no revenue while their costs continue, and any aircraft that is pulled from service for inspections can quickly find itself declared AOG — awaiting parts or maintenance action — if the pause coincides with required checks. Freighters of this vintage sit at the heart of the current MRO demand cycle, where older widebody feedstock is being kept flying longer precisely because new-production freighter slots are sold out for years (aviation MRO super cycle).

The 767-300F at issue was 32 years old. Amazon Air's network has historically leaned heavily on older converted freighters operated by contracted carriers, a model that mixes cost efficiency with the maintenance demands of ageing airframes. Whether the age of the aircraft played any role in this accident is a question the NTSB will answer — the preliminary data points to landing performance and decision-making, not mechanical failure — but the accident will nonetheless sharpen scrutiny of how older freighters are dispatched across multiple sectors in a single duty day.

What happens next

The NTSB investigation will proceed along several tracks in parallel. The flight data recorder and cockpit voice recorder have already yielded the preliminary sequence. The investigative work ahead includes:

• Reconstructing the landing performance data: approach speed, threshold crossing height, touchdown point, and the deceleration profile against the runway's available landing distance.
• Examining the braking logic — why brakes were applied and released, and whether the antiskid and autobrake systems behaved as designed.
• Analysing the throttle and thrust reverser sequence — whether a go-around was commanded, and whether the reverser non-deployment was a procedural omission or a system interlock.
• Reviewing the crew's duty day, rest, and cumulative fatigue across the three sectors flown.
• Documenting the ground victims' locations and the airport's runway safety area characteristics.

A preliminary report is expected within weeks. Probable cause determinations typically take 12 to 18 months. In the meantime, Amazon faces its own calculus: how long it keeps the pause in place, whether it shifts capacity to other contracted carriers, and what it does if the NTSB's findings point toward procedures that need reinforcement across its network.

For an industry watching, the accident is a reminder that landing accidents remain the highest-frequency serious event category in commercial aviation, and that the margin between a long landing that ends in a brake-cooling pause and one that ends in fatalities can be measured in seconds and knots. Readers can follow how airworthiness directives and inspection mandates ripple through fleets in our airworthiness directive compliance guide — though in this case, the early evidence points to the flight deck, not the maintenance hangar.

The Flight Brief will update this story as the NTSB releases its preliminary report.