Amazon has pulled 21 Air, the all-cargo carrier whose aircraft crashed off a Miami runway, from its contracted freighter network, according to a KGW report surfaced Monday.

The suspension removes 21 Air from Amazon Air's roster of third-party cargo operators in the immediate aftermath of the runway excursion, the dispatch said. The report carried no date for the crash, no aircraft type, no airport designation, and no update on the crew. Length of the Amazon suspension was not stated.

What the KGW report says

The dispatch identified 21 Air as the operator of the aircraft that departed the runway in Miami. Amazon moved to pull the carrier in the immediate aftermath, the report added, without elaborating on the mechanism. Not clear whether Amazon initiated the suspension, 21 Air grounded itself, or both acted in parallel.

What's still missing

The story carries no specifics on the runway excursion: no tail number, no aircraft type, no injury count, no NTSB or FAA reference number. It does not name the airport — Miami International, Miami Executive, or Opa-locka, all of which host cargo operations — and does not say when the crash occurred.

Neither Amazon nor 21 Air had been quoted in the KGW dispatch.

What the suspension signals for Amazon Air

Amazon Air runs one of the largest dedicated e-commerce air networks in the world, with capacity sourced from a mix of Amazon-owned freighters and third-party carriers under long-term contracts. The network moves next-day and two-day parcels across the U.S. and on transborder and Latin America lanes.

Pulling a contracted operator typically forces Amazon to swap in backup lift from its partner pool — a one-for-one aircraft substitution — and absorb any rerouting cost on the affected routes. The size of 21 Air's Amazon commitment is not disclosed.

Block-space deals between Amazon Air and contracted carriers typically run in the low single digits of aircraft per partner, though the KGW dispatch did not confirm 21 Air's specific exposure.

What shippers and forwarders should watch

Three data points will decide the commercial fallout, and none have been published yet: duration of the Amazon suspension, cause of the Miami runway excursion, and any NTSB preliminary findings. A short suspension with no hull loss or injuries would amount to a brief capacity hiccup absorbed inside the existing Amazon Air pool.

A long suspension, a write-off, or an NTSB finding of crew or maintenance fault would cascade into 21 Air's broader customer book and force Amazon to re-tender capacity at a moment when freight demand is firming into year-end peak. 21 Air's other customers — forwarders, postal operators, charter clients — are now on watch.

What regulators will examine

The NTSB leads investigations into U.S. cargo accidents of this scope, with FAA oversight running in parallel. Investigators will pull the flight data and cockpit voice recorders, review maintenance logs, and interview the crew.

Runway excursion findings historically cluster around three causes: unstable approach, weather-related landing issues, or mechanical failure such as brake or thrust reverser problems. The NTSB typically publishes a preliminary report within 7 to 14 days of an incident — the earliest point at which Amazon, 21 Air, and the wider freight market get a clean read on liability and recurrence risk.

Waybill Wire will update this story as the NTSB, FAA, Amazon, and 21 Air publish further detail.