NTSB Data Show 21 Air's Miami Freighter Touched Down 1,000 Feet Long Before Fatal Overrun

NTSB's investigative update, published Sept. 9, lays out in seconds-level detail how 21 Air Flight 7598 — a Boeing 767-300 freighter (registration N1997A) flying San Juan to Miami on the third leg of an Amazon Air rotation that began in Cincinnati — overran Miami International Airport's Runway 30 on Sept. 6, killing five people and injuring at least five more, all in vehicles struck on the ground. Both pilots were uninjured.

The cockpit voice recorder captured 2-plus hours of four-channel audio; the flight data recorder held roughly 54 hours across 400-plus parameters. Together they show the aircraft, carrying 32,000 pounds of cargo at a landing weight of 231,236 pounds, touching down at 158 knots groundspeed roughly 4,000 feet down the runway — well past the standard 3,000-foot touchdown zone on a runway that measures 9,360 feet total. Seven seconds later, brakes were applied. Eleven seconds after initial touchdown, the left main gear came down at 134 knots and the crew called for a go-around; four seconds later, throttles moved toward go-around thrust before being pulled back to idle and brakes reapplied at 117 knots. NTSB found no indication that speed brakes or thrust reversers were deployed at any point. The aircraft crossed a public road roughly 1,300 feet past the runway end and came to rest in a parking lot about 1,500 feet beyond that.

Both fatal impacts were on the ground: a 2012 Ford Econoline van operated by Professional Ocean Service Corporation, an aircraft cleaning contractor, was struck inside the airport perimeter with seven people aboard, and a Toyota Corolla Cross was hit on Northwest 67th Avenue outside the fence. "I would describe it in one word: devastating, utter devastation. The Econoline van is torn apart," NTSB Chair Jennifer Homendy said, according to CBS Miami's coverage of the response.

What happens to the airport, and to 21 Air, next

Two of MIA's four runways closed immediately after the crash; one reopened once NTSB finished documenting the scene, and full restoration of the fourth was still pending fuel-spill remediation and evidence collection as of this filing. NTSB says a written CVR transcript is next, a preliminary report is expected within roughly 30 days, and the full investigation will take a year or more. 21 Air, a North Carolina-based cargo carrier, operates as a contractor within the Amazon Air network rather than as an Amazon-owned entity — a distinction that matters for anyone tracking whose insurance, whose maintenance program and whose operating certificate is now under NTSB scrutiny.

What forwarders and air cargo buyers do differently

• MIA capacity is constrained, not just delayed. With one runway only recently reopened and a fourth still closed for remediation, forwarders routing perishables, pharma or other time-critical freight through MIA — one of the busiest freighter and belly-cargo gateways for Latin American and Caribbean trade — should confirm current runway status and build in schedule buffer rather than assuming normal turnaround times have resumed.
• 21 Air is a named counterparty risk, not an abstract one. Any forwarder or 3PL with visibility into which contract carrier operates a given Amazon Air leg should ask directly whether 21 Air aircraft or crews are involved, particularly on Puerto Rico–Miami and other short-haul legs similar to the accident routing, until NTSB's preliminary findings narrow the causal question to aircraft, crew or airport-specific factors.
• The unstabilized-approach pattern here is a fleet-wide watch item, not a one-off. A touchdown 1,000 feet past the normal zone with no recorded speed brake or reverser deployment, followed by a go-around call after the aircraft was already down, points toward an approach-stabilization and go-around-decision question that regulators and other 767 freighter operators will be watching closely — worth monitoring for any FAA safety alert or operator bulletin in the weeks ahead, since those can affect freighter scheduling reliability well before the final NTSB report.