NTSB's Preliminary Report on the Fatal Miami 767 Cargo Overrun: Speed Warnings, No Wind Information, No Cause Yet

Rajkumar Agarwal3 October 20269 min read0 viewsSafety & Regulation
NTSB's Preliminary Report on the Fatal Miami 767 Cargo Overrun: Speed Warnings, No Wind Information, No Cause Yet

The first public narrative of how a Boeing 767 freighter ended up beyond the end of a Miami runway, killing five people in a van, arrived on October 1. The National Transportation Safety Board's preliminary report on the September 6 crash of 21 Air Flight 7598 describes an approach that was fast from the start, a first officer who said so repeatedly, a touchdown far down the runway, and a go-around attempt that began with almost no pavement left. It also says the tower did not pass wind information to the crew even though the rules call for it when a tailwind is present.

What the report does not do is say why it happened. The NTSB stated no conclusion on cause. Under the international convention that governs accident investigation, that is how a preliminary report is supposed to read: a collection of facts, not a verdict. This article sticks to what the NTSB and the outlets that have read the report have put on the record, and it flags where accounts differ.

What happened on September 6

Flight 7598 was a cargo flight flown by 21 Air, a Greensboro, North Carolina-based freight airline, on behalf of Amazon. The aircraft was a Boeing 767-33A freighter returning to Miami International Airport from San Juan, Puerto Rico. According to CBS News Miami's reading of the report, the jet landed on Runway 30 at about 1:53 p.m. local time with thunderstorms near the airport.

The aircraft did not stop on the runway. It left the paved surface and, per the NTSB's September investigative update, travelled about 1,300 feet beyond the pavement. On the way it struck a 2012 Ford Econoline van owned by Professional Ocean Services Corp., a contract cleaning company that serves airlines. The van carried seven people. Five of them died. CBS Miami reports two van occupants were seriously injured, and that one occupant of a Toyota Corolla Cross was also seriously hurt. The captain and first officer escaped with minor injuries.

Reports from the days after the crash described the scene in stark terms. NTSB Chair Jennifer Homendy characterized it as "utter devastation," according to FreightWaves, which also reported damage to navigational aids and fencing and said two of Miami's four runways were closed indefinitely at that stage for fuel remediation and investigative needs.

One discrepancy is worth noting. At least one outlet gave the date as Sunday, September 7. The NTSB's own investigative update and CBS Miami give September 6, which fell on a Sunday this year, and that is the date used here.

The approach: warnings that went unanswered

The most consequential material in the report concerns the final minutes. The NTSB's September 9 update established the outline: the cockpit voice recorder held more than two hours of good-quality audio across four channels, and the flight data recorder held about 54 hours of data covering more than 400 parameters. When flaps were set to 20 degrees, one pilot cautioned the other that they were too fast, and kept commenting on the excessive speed for the rest of the recording. The NTSB said at that stage that there was not a consistent verbal response to those comments.

The preliminary report adds numbers. CBS Miami, summarising it, says the first officer repeatedly warned about excessive speed throughout the approach and that flight recorders captured more than 10 electronic warnings. The jet crossed the runway threshold at roughly 204 mph. It touched down about 3,750 feet past the threshold at roughly 184 mph, which is consistent with the NTSB's earlier figure of 158 knots groundspeed.

Reported speed of the 21 Air 767 at the runway threshold and at touchdown on September 6
Reported speed of the 21 Air 767 at the runway threshold and at touchdown on September 6

For a heavy jet landing near thunderstorms in gusty conditions, a touchdown that far down the runway at that speed leaves little margin. The report is explicit about what the recorders did not show. The recorded data contained no indication that speed brakes or thrust reversers deployed. Those are the two systems that, together with wheel brakes, shed energy after touchdown on a freighter this size.

A go-around too late to work

The NTSB's September update said that four seconds after the nose and right main gear touched down, the brakes were released and the throttles increased to values consistent with a go-around. The aircraft left the paved surface roughly ten seconds later.

CBS Miami reports a related detail from the preliminary report: the captain called for a go-around only 15 seconds after touchdown, when approximately 415 feet of runway remained. At that point, the report as summarised describes the attempt as too late to execute safely. The aircraft then continued off the end of the runway, struck the van and the SUV, and came to rest with major damage, including a post-crash fire on the right wing, partial separation of the right wing and engine, and wreckage scattered across roughly 158 feet.

Readers should be careful with the timeline numbers. The four-second and fifteen-second figures come from different publications describing different moments, one from the NTSB's September update and one from a summary of the October report. They are not necessarily in conflict, since they may mark the brake release, the go-around call, and the commitment point, but only the NTSB's full documents settle that. The investigation is identified as DCA26MA352, and the board said it would convene a cockpit voice recorder group to produce a written transcript.

The crew and the aircraft

The preliminary report gives a profile of both. The captain had 7,267 total flight hours and had been with 21 Air since April. The first officer had about 2,800 hours and joined the airline in February 2025. According to CBS Miami, the two were flying together for the first time that day, having flown Miami to San Juan earlier before the return leg that ended in the crash. FreightWaves reported it was the crew's third flight of the day.

The aircraft was built in June 1994 as a passenger plane and converted to a freighter in June 2016. It had logged approximately 110,077 flight hours and 24,505 flight cycles. Neither the NTSB nor the outlets reviewed here connect the aircraft's age or conversion history to the accident, and nothing in the preliminary material suggests a mechanical cause. Age is context, not a finding.

The tower and the wind

A separate thread in the report concerns air traffic control. CBS Miami reports that the tower cleared the flight to land at about 1:49 p.m., when the aircraft was roughly 12 nautical miles out, and that controllers did not give the pilots wind information. The report notes that FAA regulations require controllers to state wind direction and speed when a tailwind component exists. Wind at the time was reported from the south, with gusts of roughly 17 to 26 knots, depending on the observation.

What this means for the outcome is not established. A crew that is already high and fast can misjudge a tailwind, but the first officer was already cautioning about speed well before touchdown, and the report as summarised does not claim the missing wind call caused the overrun. Accident investigations commonly examine contributing factors alongside the sequence of events, and the NTSB has not said how it will weigh this one. The omission is a documented procedural gap, and it is the sort of item that tends to draw FAA attention regardless of the final cause.

The runway end: no arrestor bed

The report also records that no system existed at the end of Runway 30 designed to slow an aircraft that runs beyond the pavement. FreightWaves put it in terms of engineered materials arresting systems, the crushable-concrete beds installed at the ends of some US runways, noting that roughly 72 US airports have them and that Miami does not at this runway end.

That fact cuts two ways in the public debate. Arresting beds are built to stop aircraft that overrun at modest speeds. An aircraft that leaves the pavement at the speed reported here is outside what many such systems are designed for, though only the investigation can say what difference one would have made. The more immediate lesson for the people who died is simpler: a large jet ended up beyond the pavement, among people in vehicles, in a place it was never meant to be.

What 21 Air and the survivors' lawyers say

21 Air said it will continue to work closely with the NTSB as a party to the investigation and review its safety and operational protocols, according to CBS Miami. An attorney representing a surviving van occupant, Sebastian Perdomo Torres, acknowledged the report's value but said it does not answer all the questions about the broader airline operation, the same outlet reported.

Those statements frame the next phase. As a party to the investigation, the operator participates in factual work under NTSB direction. Questions about training, crew pairing, procedures for unstabilised approaches, and company oversight are typically examined in that phase, and some will become the subject of civil litigation that runs on a separate track.

What happens next

The NTSB says a full investigation of this kind takes between one and two years. Between now and then, expect a CVR transcript, interviews with the crew and the controller, examination of company procedures, and, if the board sees an urgent safety issue, interim recommendations that can be issued long before the final report. A preliminary report, by design, leaves the hardest question open.

For travellers, it is worth being plain about the scope. This was a cargo flight, with no passengers aboard, and every death was on the ground. It is still a fatal accident involving a large jet, and the questions it raises, about stabilised approaches, controller phraseology, and what stands beyond a runway, apply to every airline that lands at a busy airport in convective weather.

The facts as of October 3: a heavy freighter landed fast and long, the recorders show no speed brake or reverser deployment, a go-around began with little runway left, and five people in a van died. Whether this was a decision, a miscue, a system gap, or a combination is exactly what the NTSB has not yet said.

Sources

#21 Air#NTSB#Miami#runway overrun#cargo#Boeing 767
Share:

Comments

Leave a comment

← All posts