Five dead in Miami cargo crash were in vehicles on ground

All five people killed when an Amazon-branded cargo jet crashed on landing at Miami International Airport were in two vehicles on the ground that were struck as the aircraft overran its runway, according to published coverage and newly released investigative details.

Victims were riding in airport van and SUV

Publicly available information indicates the Boeing 767-300 freighter, operating under contract to Amazon, was arriving from San Juan, Puerto Rico, on Sunday, September 6, when it failed to stop after touching down on Runway 30 at Miami International Airport. The aircraft broke through the runway end area and perimeter fencing and collided with two vehicles before coming to rest in a storage area beyond the airport boundaries.

Reports indicate the five people who died were all in the two vehicles that were hit. Most accounts describe a Ford Econoline passenger van used by a cleaning contractor to shuttle workers around the airfield and a second vehicle, identified in some local coverage as a Toyota SUV, traveling outside the fence line. Seven people were in the van, which took the brunt of the impact.

Miami-Dade County officials and local media have published the names of the five victims as Rolando Aleman Leon, 55, Yoel Rodriguez Naranjo, 53, Julio C. Pineda, 75, Carlos Acosta Fajardo, 53, and Javierkys Reyes Quevedo, 47. They were described as members of an airport cleaning crew and other workers being transported near the runway environment at the time of the crash.

According to multiple reports, five additional people were injured. Three of them remained hospitalized as of Tuesday, including two men listed in critical condition, while two others had been treated and released.

Unsteady landing and aborted stop under review

Early investigative summaries released by the National Transportation Safety Board (NTSB) and described in media reports focus on the aircraft’s landing sequence. Flight tracking data and preliminary information indicate the freighter may have floated above the runway and touched down farther along the pavement than typical for a standard landing.

Analyses shared by aviation specialists in public coverage suggest the crew may have attempted to salvage the landing before an apparent decision to abort and go around, with engine power increasing late on the rollout. By that point, the remaining distance is believed to have been too short for the aircraft to either safely stop or gain sufficient speed to climb away.

Drone and ground imagery published since the crash show long tire marks leading off the end of Runway 30, heavy damage to an airport security fence and perimeter road, and wrecked vehicles lying near the aircraft’s final position. Debris photographs highlight shredded airport infrastructure, scattered cargo containers and personal effects from the vehicles.

The cockpit voice recorder and flight data recorder were recovered from the wreckage and transported to Washington for analysis. Investigators are expected to use those records, along with radar, weather and maintenance data, to reconstruct the crew’s decisions and the exact timing of events in the seconds before the aircraft left the runway.

Ground operations and vehicle access under scrutiny

Beyond the flight crew’s actions, the Miami crash has drawn attention to how service vehicles and employee shuttles move around active runways and perimeter roads. According to publicly available information from the NTSB briefing and local reporting, one of the vehicles struck was traveling on an internal airport service route while the second was on a public road just outside the fence.

Investigators are expected to review airfield diagrams, access procedures and communications between the control tower, ground operations and the companies that manage support crews. The circumstances raise questions about how close ground traffic should be permitted to runway ends and what barriers or engineered safety areas are in place to mitigate runway overruns at busy commercial airports.

Accounts from the crash scene describe what one report termed “utter devastation,” with vehicle air bags, cabin equipment, aircraft debris and fencing scattered along the aircraft’s path. The force of impact pushed the struck vehicles hundreds of feet, a pattern visible in aerial imagery released during the investigation.

Airport management has stated through public channels that it will cooperate fully with the federal safety inquiry. Any recommendations that emerge could affect ground-transport policies for airport workers, including how cleaning crews, maintenance staff and other contractors are routed between aircraft stands and terminal facilities.

Impact on Miami air traffic and cargo operations

The incident occurred at one of the United States’ busiest international gateways and a major hub for both passenger and cargo flights. Following the crash, Miami International Airport temporarily closed two of its four runways, including the one where the overrun occurred, while investigators documented the site and removal of wreckage was coordinated.

Airport status advisories cited in media reports note that the closures and associated restrictions have caused delays and cancellations, particularly for flights operating in the late afternoon and evening bank. Disruptions have been most pronounced on routes that rely on the affected runway configuration and for airlines with tightly timed connections through Miami.

The cargo sector has also faced knock-on effects. The aircraft involved was part of a dedicated Prime Air network that moves e-commerce shipments across the Americas. Published tracking data show other freighters being rerouted to alternate airports or retimed as the operator adjusts its schedules around the loss of one aircraft and temporary constraints at Miami.

Industry analysts quoted in public coverage say cargo networks can generally recover quickly from single-aircraft losses but that localized infrastructure restrictions, such as runway closures at a key hub, can add complexity and costs as carriers reposition aircraft and crews.

Ongoing investigation and safety context

Formal findings on the cause of the Miami crash are likely to take many months. The NTSB typically issues a preliminary report within weeks that summarizes factual information without assigning blame, with a final report and any safety recommendations following after a more detailed technical analysis.

Runway overrun events involving large jets are relatively rare, but they remain a recurring focus for regulators and airport planners. International safety bodies have long encouraged the use of engineered materials arresting systems and extended runway safety areas where space permits, specifically to reduce the risk of catastrophic outcomes if an aircraft fails to stop in time.

Published coverage of the Miami investigation indicates that federal and local agencies are already examining how existing protections at the airport performed and whether additional measures could further separate ground vehicles from potential overrun paths. Any proposed changes could influence design standards and operating practices at other large airports that handle a mix of passenger and cargo traffic.

For the families and colleagues of those killed, the technical inquiry is unfolding alongside memorials and workplace remembrances. Travel and aviation communities are watching closely as investigators piece together how a landing that began uneventfully on a sunny afternoon ended with a cargo jet crushing two vehicles and causing one of the deadliest runway accidents in Miami’s recent history.

Five killed in Miami plane crash were in two vehicles on ground, investigators say

Identities of victims in Amazon cargo plane crash released

All 5 killed in Miami cargo jet crash were in a van used by plane cleaners

Amazon cargo plane crash victims were in vehicles that were hit