Amazon Prime Air 767 Freighter Overruns Miami Runway, Leaving 5 Dead and Forcing Ground Stop

A widebody Boeing 767-300 freighter touches down at approximately 150 knots, carrying enough kinetic energy to require over a mile of clear pavement to safely halt. On Sunday, September 6, 2026, an Amazon Prime Air flight operating on that physical basis failed to stop within the confines of Miami International Airport, overrunning the diagonal runway, breaching the airfield boundary, and colliding with civilian vehicles on a nearby roadway.[1][2]

The runway excursion resulted in at least five fatalities and left five others injured, with three in critical condition and two hospitalized with less severe injuries, according to Miami-Dade County officials. The aircraft, operating as 21 Air Flight 7598, crossed into the 2100 block of Northwest 42nd Avenue at approximately 2:00 p.m. local time, striking two semi-trucks and multiple passenger vehicles before coming to rest on its belly and igniting.[2][3][5]

Emergency response protocols were activated immediately, drawing more than 60 Miami-Dade Fire Rescue units to the perimeter. "Units arrived to find an airplane that had caught fire as a result of this crash, with heavy flames and smoke showing," the fire department stated in a public release. "Firefighters are working on extinguishing the fire and assessing patients." Rescue crews faced a complex extraction environment, with victims trapped inside crushed vehicles and the flight crew trapped inside the cockpit while aviation fuel leaked onto the roadway.[3][4]

The aircraft involved was a 32-year-old Boeing 767-300 originally built for passenger service and converted to a freighter configuration in 2015. It had arrived from Luis Muñoz Marín International Airport in San Juan, Puerto Rico. Rather than operating the aircraft directly, Amazon utilizes a contracted logistics model; the flight was operated by 21 Air, a North Carolina-based cargo carrier that flies within the Prime Air network.[1][3][4]

Amazon acknowledged the structural arrangement in its immediate response. "We can confirm that an Amazon Air plane operated by 21 Air experienced an incident while attempting to land at Miami International Airport," Amazon spokesperson Kelly Nantel said. "This is a fast-moving situation and we're still gathering details. We're working closely with local authorities and officials to understand exactly what happened."[3][5]

The incident triggered an immediate systemic contraction across the regional airspace. The Federal Aviation Administration's Air Traffic Control System Command Center issued a full ground stop for Miami International Airport at 2:30 p.m., halting all inbound and outbound traffic. By late afternoon, the disruption had cascaded into more than 250 flight delays, according to tracking data, before airport authorities managed to reopen a single runway at 4:50 p.m.[3][4][5]

Transportation Secretary Sean Duffy directed federal investigators to the site, initiating a dual-track inquiry. The National Transportation Safety Board launched a specialized "go team" led by Chairwoman Jennifer Homendy, who is scheduled to deliver a preliminary briefing on Monday. The investigation will focus on retrieving the flight data and cockpit voice recorders to determine whether the overrun was caused by mechanical failure, such as locked brakes or thrust reverser malfunction, meteorological factors, or pilot error.[3][4][5]

Runway overruns, while statistically rare, represent one of the most severe kinetic events in commercial aviation because they transfer the aircraft's remaining energy into unyielding ground infrastructure. Safety systems like Engineered Material Arresting Systems—crushable concrete blocks placed at runway ends—are designed to absorb this energy, but their installation depends on available perimeter space, which is severely limited at landlocked facilities like Miami International.[1]

The NTSB's forthcoming analysis will dictate whether the Federal Aviation Administration mandates new operational margins for heavy freighters landing on diagonal runways, or whether the failure was isolated to this specific 32-year-old airframe. The recovery of the aircraft and the reconstruction of the perimeter fence will dictate the timeline for restoring full capacity to the airport's intersecting runway network.[1][3]