More news on this day
Federal safety investigators reached Miami International Airport on Monday to begin examining how an Amazon-branded Boeing 767 cargo jet barreled off a runway, crossed a perimeter road and struck vehicles, leaving at least five people dead and several others injured.
Get the latest news straight to your inbox!
Investigators Focus on Late Landing and Runway Overrun
Initial accounts from national and local coverage indicate that the widebody cargo aircraft, painted in Amazon Air livery and reportedly operated by North Carolina based carrier 21 Air, was attempting to land at Miami International Airport on Sunday, September 6, when it failed to stop on the runway. The jet continued beyond the pavement, crossed an airport perimeter area and a roadway, and collided with multiple vehicles before coming to rest in flames near the airport’s western boundary.
Published reports describe a chaotic scene, with the aircraft’s fuselage heavily damaged and thick black smoke visible from surrounding neighborhoods and nearby expressways. Early tallies from public reports indicate that at least five people were killed, including occupants of vehicles struck beyond the runway, and around five others were transported for medical care.
Coverage citing preliminary aviation data suggests investigators are examining whether the Boeing 767 touched down significantly farther along the runway than normal, raising questions about landing speed, braking effectiveness, and the influence of shifting wind conditions at the time of arrival. Analysts following flight tracking data have noted indications of a quartering tailwind near the time of landing, a factor that can lengthen landing distance if not fully accounted for in approach planning.
According to publicly available information about similar runway events, a landing that occurs even a few thousand feet beyond the typical touchdown zone can sharply reduce the stopping margin, especially on a busy international airport runway where operational and weather conditions can change rapidly.
NTSB Launches Go-Team and Secures Wreckage
The National Transportation Safety Board dispatched a multidisciplinary team to Miami soon after the crash, in keeping with its practice for major commercial aviation accidents. Publicly posted information indicates that the group includes specialists in aircraft operations, human performance, structures, systems, and airport factors, along with technical staff responsible for recorders and flight data.
On arrival at Miami International Airport, investigators began the process of documenting the accident scene, coordinating with airport personnel and other agencies to map the wreckage trail from the point where the jet departed the runway to the final resting position of the fuselage. High resolution photography, drone imagery, and detailed measurements of runway markings, tire tracks, and ground scars are expected to form part of the initial factual record.
The NTSB team is also expected to locate and recover the aircraft’s flight data recorder and cockpit voice recorder, which are typically housed in the tail section of a Boeing 767. Once retrieved, the devices are transported to NTSB laboratories in Washington, where specialists download and analyze the information to reconstruct flight parameters, cockpit communications, and the timing of key events during the landing roll.
Based on the agency’s prior investigations of cargo operations, the early field phase generally lasts several days, after which investigators continue interviews, data analysis, and component examinations off site before any conclusions are reached about causes or contributing factors.
Miami International Operations and Travel Disruptions
The crash occurred at one of the nation’s busiest international gateways, a key hub for flights across the Americas and to Europe. Public advisories from airport and airline channels in the hours after the accident pointed to temporary runway closures and ground stops affecting both passenger and cargo operations, creating delays that rippled through the schedule on Sunday evening and into Monday.
Travel industry tracking platforms showed flight diversions and cancellations as emergency crews responded and investigators began securing the site. While Miami International Airport maintained limited operations on unaffected runways, airlines warned travelers to expect extended wait times, last minute gate changes, and potential missed connections.
For travelers arriving or departing Miami in the coming days, publicly available guidance emphasizes monitoring airline messages closely, checking flight status before leaving for the airport, and allowing additional time for security and check in. Depending on how long the damaged runway and adjacent areas remain closed, some carriers may temporarily retime or reroute services, particularly on long haul or widebody flights that normally rely on the affected pavement.
Airport ground access has also been affected. Local traffic reports describe intermittent closures or restrictions on roads skirting the western edge of the airfield, where emergency vehicles, cranes, and heavy recovery equipment have been operating near the wreckage.
Amazon Air and 21 Air in the Spotlight
The accident places fresh scrutiny on Amazon’s fast growing air cargo network and the contractors that fly under its brand. Public records indicate that the crashed aircraft was a Boeing 767 freighter painted in Amazon’s distinctive blue Prime Air livery and operating a scheduled cargo service into Miami, part of a system that links fulfillment centers with major airports across the United States.
Industry databases and previous regulatory filings show that Amazon does not operate its own airline certificate, instead relying on carriers such as Atlas Air, Air Transport International, and 21 Air to provide aircraft, crews, and maintenance. In this case, early reporting from aviation focused outlets attributes the flight to 21 Air, a cargo specialist based in Greensboro, North Carolina, which has flown Amazon branded routes for several years.
According to publicly available economic and safety analyses, Amazon’s rapid expansion in air logistics has reshaped the U.S. domestic cargo market, with older widebody passenger jets converted to freighters and deployed on high frequency overnight routes. The Miami crash is expected to renew discussion about training, scheduling, and oversight structures across a network where aircraft may carry the branding of a tech and retail giant but operate under the certificates of multiple carriers.
Past investigations into other Amazon related cargo accidents, including the 2019 crash of Atlas Air Flight 3591 in Texas, have already prompted recommendations on pilot screening, training, and performance monitoring in outsourced cargo operations. Safety advocates are likely to follow how those earlier findings inform the lines of inquiry in the new Miami case.
What Investigators Will Examine in the Weeks Ahead
While it is too early for any findings about what caused the Amazon branded cargo jet to overrun the runway in Miami, previous accident reports offer a guide to the issues investigators may explore. These typically include pilot decision making during approach and landing, adherence to stabilized approach criteria, configuration and speed management, and the possibility of mechanical or systems malfunctions affecting braking or thrust reversers.
Weather conditions at the time of landing are expected to receive close attention, particularly reports of shifting winds and potential tailwind components on the active runway. Investigators will compare real time meteorological observations, air traffic control data, and cockpit inputs to determine whether the crew had full and timely information, and how that information was used in deciding whether to continue or break off the landing.
The investigation is also likely to examine runway characteristics at Miami International Airport, including available landing distance, surface condition, lighting, and any ongoing construction or operational constraints. Detailed performance calculations can show whether the landing, as flown, left adequate stopping margin given the aircraft’s weight, configuration, and the reported winds.
In parallel, attention will focus on the human impact of the crash on people using roads and facilities around the airfield, an aspect that has drawn increasing scrutiny as airports worldwide see development and traffic grow around their perimeters. For an airport that handles tens of millions of passengers and significant cargo each year, the Miami overrun marks a stark reminder of how on airport events can rapidly extend beyond the fence line.
Associated Press overview of the Miami Amazon cargo crash and NTSB response
Initial AP report on fatalities and disruptions at Miami International Airport