Miami Airport Disruption Continues After Boeing 767 Cargo Crash Kills Five

A Boeing 767-300 cargo aircraft operated by North Carolina-based 21 Air, flying under contract for Amazon, overran the runway at Miami International Airport on Sunday, September 6, after arriving from San Juan, Puerto Rico. The freighter failed to stop on landing, overshot the runway end, crashed through the perimeter fence, skidded across a public road bordering the airfield and struck multiple vehicles before coming to rest in flames near an airport logistics area. Five people were killed, including crew members aboard the jet and occupants of vehicles on the road, with at least five survivors transported to area hospitals, several in critical condition.

Miami International Airport ordered a full ground stop immediately after the accident, closing all runways and taxiways while emergency crews fought an intense fuel-fed fire and investigators documented the scene. At least one main runway remained closed into Monday as recovery teams prepared to move the burned-out aircraft. By Monday morning commercial operations were resuming only gradually, with dozens of departures and arrivals delayed or canceled as airlines worked around the blocked runway and residual congestion; flights bound for Miami on Sunday were diverted to other airports in Florida and the southeastern United States.

Several major carriers issued travel advisories urging passengers to check flight status and consider flexible rebooking, with some offering fee-free changes for itineraries touching Miami early in the week. Amazon issued a statement expressing sorrow over the loss of life and said it was cooperating with the operating airline and investigators, describing the aircraft as operating a 21 Air cargo service on behalf of its Prime Air freight network. Federal safety investigators dispatched a team to Miami to examine the wreckage and review physical evidence along the runway and overrun area, with the inquiry expected to focus on the approach and landing, braking systems, thrust reversers and runway surface conditions at touchdown; investigators will also review radar data, cockpit voice and flight data recorders, and air traffic control communications. Weather at the time included scattered showers typical for late-summer South Florida, with no indication of severe storms on the airfield.

A runway overrun at a major international gateway illustrates how a single accident involving one cargo operator can cascade into system-wide disruption, since a hub airport typically has only a limited number of runways available and closing even one forces arriving and departing traffic from every carrier onto reduced capacity. That is why Miami's ground stop produced diversions across the southeastern United States and prompted fee-free rebooking from multiple airlines rather than just 21 Air or Amazon's freight network.

Cargo contract flying for large shippers like Amazon typically runs on tight, repeatable schedules with limited buffer, so an accident involving one aircraft in that network can affect downstream package flows even though the disruption at the airport itself is being felt mainly by passenger carriers sharing the same runways and taxiways. Braking performance, thrust reverser function and runway surface conditions are standard areas of focus in overrun investigations, and the presence of a public road immediately beyond the runway end is now part of what investigators will need to account for.

The next milestones are the runway's return to full operation and any preliminary findings federal investigators release on approach speed, braking and reverser performance. Until those are published, the cause of the overrun remains undetermined and airlines' advisories for Miami-bound itineraries are likely to stay in effect.