Pilots Missed CRITICAL Warning Before Deadly Crash

Photo: Tada Images / Shutterstock

A tower controller’s silence on wind conditions is the kind of finding that makes for a clean headline, but the deeper truth about runway overruns is that they are almost never caused by one missing radio call — they are the product of several small failures stacking up in the final ninety seconds of flight.

Key Points

The NTSB’s preliminary report on the September 2026 crash of Amazon-contracted cargo flight 7598 at Miami International Airport found that the tower controller did not relay wind information before clearing the Boeing 767 to land, despite an FAA rule requiring it when a tailwind component exists.
A different aircraft received a wind advisory just four minutes earlier, showing the data was available in the tower when the Amazon flight was cleared.
Flight-data and cockpit evidence separately show the first officer repeatedly warned the pilot flying that the aircraft was coming in too fast, and the jet touched down roughly 3,750 feet past the runway threshold.
Five people died when the plane overran the runway and struck vehicles; the investigation remains preliminary, with probable cause likely a year or more away.
The case illustrates a pattern well established in aviation safety research: runway excursions are almost always multi-factor events, not single-cause failures.

What the Preliminary Report Actually Found

The NTSB’s preliminary account of DCA26MA352 is narrow by design — preliminary reports exist to establish a factual timeline, not to assign blame. Within that timeline, one detail stands out: the controller handling arrivals and departures did not issue wind direction and velocity to the Amazon-contracted flight before authorizing its landing, even though FAA procedure requires that information whenever a tailwind component is present on the runway in use. Investigators noted that winds at the time were blowing from the south at roughly 20 mph, gusting to 30, while the aircraft landed to the northwest — a configuration that put a tailwind component squarely into play.

What makes the omission harder to wave off as an isolated lapse is timing. About four minutes before clearing the Amazon flight, the same controller had advised a separate aircraft of gusts up to 25 mph from the south. The information existed in the tower environment; it simply was not passed along to the crew that needed it most on this approach. That detail has driven most of the headline coverage, and for good reason — it describes a specific, documented procedural failure rather than speculation.

Why Runway Overruns Rarely Have a Single Cause

Aviation safety literature has studied runway excursions for decades, and the pattern is remarkably consistent: excess approach speed, landing beyond the intended touchdown zone, delayed deceleration, and incomplete wind or runway-condition information tend to arrive together rather than alone. Reviews by the Flight Safety Foundation and the Government Accountability Office have repeatedly found that pilot misjudgment of speed or distance is the most common single factor in overruns, frequently compounded by inadequate weather or runway-condition information reaching the flight deck. A missing wind advisory fits neatly into that known pattern — it is the kind of early, legible failure that coexists with, rather than substitutes for, the harder-to-see breakdowns in cockpit decision-making that often follow.

The Cockpit Evidence Investigators Are Also Weighing

Separate from the wind-advisory question, NTSB flight-data and cockpit summaries describe a landing sequence that was already in trouble before the aircraft touched down. The first officer warned the pilot flying more than once that the plane was coming in too fast, and investigators found no consistent verbal response to those warnings. Flight data showed one pilot briefly advanced the throttles toward takeoff power — the start of a go-around — then pulled them back to idle four seconds later and continued the landing. The aircraft crossed the runway threshold at roughly 172 knots, well above the recommended approach speed, floated an extended distance down the runway, and touched down nose-gear first in a way that delayed the weight-on-wheels signal spoilers and reverse thrust depend on. By the time it left the pavement, it had traveled past nearly half the runway’s usable length and come to rest roughly 3,750 feet beyond the threshold.

Aviation safety consultant Mary Schiavo, reviewing available video, described the aircraft as floating above the runway for an extended period without the nose-up flare maneuver pilots use to force the main gear down promptly — a detail that, if accurate, points toward a landing-technique problem independent of anything the tower did or did not say. Former airline pilot Steve Arroyo, reviewing the same cockpit data, characterized the exchange between the two pilots as reflecting a lack of teamwork under pressure, with the pilot flying possibly too focused on salvaging the landing to register the speed warnings. None of this evidence rebuts the controller’s omission; it exists alongside it, which is exactly the multi-factor picture the preliminary report’s broader context — speed, braking, runway length, and weather — was already gesturing toward.

First officer warned that Amazon cargo plane was coming in too fast before deadly Miami crash, NTSB says. https://t.co/Og5VxGx1HY

— CBS News (@CBSNews) October 1, 2026

What Comes Next, and What It Means

Final NTSB probable-cause determinations typically take a year or more, and this case will likely need that full window: cockpit voice recorder transcripts, thrust-reverser and spoiler system data, braking-action analysis on a runway that may have been wet, and a precise calculation of the tailwind component at the moment of touchdown all remain to be fully documented in the public docket. Amazon has already paused its use of 21 Air, the operator flying the route under contract, a step that suggests the company is not waiting for final findings to act on what preliminary data has shown. For the traveling and shipping public, the lesson embedded in this case is an old one dressed in new details: a missing wind call is a real and documented failure worth fixing, but treating it as the whole story would repeat the same mistake investigators are now working methodically to avoid.