In the final approach to Miami International Airport, a Boeing 767 carrying Amazon cargo descended faster and hotter than safety demanded, while one pilot's repeated warnings went unanswered and automated alarms filled the cockpit air. The plane overshot the runway and struck a van carrying five workers whose only connection to the flight was the ordinary labor of keeping aircraft clean. What the flight data now reveals is not merely a sequence of mechanical failures, but a portrait of how warnings — human and electronic alike — can exist in a system and still go unheeded, with irreversible co
Amazon cargo plane was going too fast before Miami crash, pilot warnings show
a doomed approach, confirmed by the data
So the pilot knew they were coming in too fast. Why didn't they just slow down?
That's the question everyone's asking. One pilot was saying it repeatedly, but the other pilot wasn't responding consistently. By the time they realized how bad it was, they were already committed to landing.
We should be careful here. We don't know what "inconsistent verbal response" actually means. The NTSB summary doesn't tell us if the other pilot heard the warning, disagreed, was distracted, or something else entirely.
What about the flaps? The article mentions they deployed late.
Flaps are what slow the plane down and help it land gently. If they went out late, it suggests the pilots were scrambling to fix a speed problem that was already developing.
Right, but that's inference. The data shows late deployment. We don't have the pilots' explanation for why yet. It could be procedural, it could be a system issue, it could be pilot error. We just don't know.
And five people died because of this.
Five members of a ground crew in a van. They had no warning, no way to know the plane was coming at them.
The human cost is real and tragic. But we should be precise about causation. The crash killed them. Whether it was pilot error, a system failure, or something else—that's still being investigated.
What happens now?
The NTSB keeps digging. They'll want the full audio, they'll interview the pilots, they'll look at training records, maintenance logs, everything.
And we'll know more when they release their findings. Right now we have data points and one attorney's interpretation. That's important, but it's not the whole story yet.
Il Polso
- One pilot warned repeatedly that the aircraft was moving too fast, yet the other offered no consistent reply as the descent continued to deteriorate.
- Automated alarms cascaded through the cockpit — sink rate too steep, terrain proximity too close — painting a picture of an approach already slipping beyond recovery.
- The plane touched down at 158 knots, on the high edge of acceptable landing speed, and could not stop before the runway ran out.
- Five members of a plane-cleaning crew — men ranging in age from 47 to 75 — were killed when the overrunning aircraft struck their van beyond the runway's end.
- Late flap deployment suggests the pilots may have been scrambling to correct excessive speed rather than executing a controlled approach, pointing investigators toward possible procedural and communication failures.
- The NTSB investigation continues, seeking to understand not why the safety systems failed, but why the warnings they produced were not enough to change what happened.
In the final approach to Miami International Airport, a Boeing 767 carrying Amazon cargo descended faster and hotter than safety demanded, while one pilot's repeated warnings went unanswered and automated alarms filled the cockpit air. The plane overshot the runway and struck a van carrying five workers whose only connection to the flight was the ordinary labor of keeping aircraft clean. What the flight data now reveals is not merely a sequence of mechanical failures, but a portrait of how warnings — human and electronic alike — can exist in a system and still go unheeded, with irreversible consequence.
In the final minutes before Amazon Prime Air Flight 7598 struck the ground in Miami, one pilot kept repeating the same warning: the plane was going too fast. The other pilot did not respond consistently. By the time the automated alarms joined the chorus — announcing a dangerous sink rate and dangerously close terrain — the approach had already become, in the words of one aviation attorney, a doomed one.
Flight data released by the National Transportation Safety Board this week shows the Boeing 767-300 touched down at 158 knots, a speed aviation experts describe as sitting at the high end of acceptable. The plane overshot the runway, struck ground equipment, and then collided with a white Ford van carrying five members of a plane-cleaning crew. The aircraft tore through a perimeter fence, struck another vehicle, and finally came to rest roughly 1,300 feet past where it should have stopped. The five men in the van — Rolando Aleman Leon, Yoel Rodriguez Naranjo, Julio C Pineda, Carlos Acosta Fajardo, and Javierkys Reyes Quevedo — were killed. Five others were injured.
Aviation attorney Pablo Rojas noted that the flight data raises difficult questions about cockpit dynamics. Without the actual audio recording, the precise meaning of an "inconsistent verbal response" remains open to interpretation — but the broader pattern is legible. The data also shows the plane's flaps were deployed far later than standard procedure calls for, suggesting the pilots may have been reacting to a speed problem that had already taken hold rather than preventing one from developing.
The NTSB has not yet determined what caused the excessive speed or why repeated human warnings failed to produce the correction the approach required. What is already clear is that the safety systems performed as designed — the alarms sounded, the data was captured, the warnings were spoken aloud. The harder question, and the one the investigation must now answer, is why none of it was enough.
In the final minutes before Amazon Prime Air Flight 7598 struck the ground in Miami on Sunday, one pilot in the cockpit kept saying the same thing: the plane was going too fast. The other pilot did not respond consistently, even as electronic alarms began to sound. By then, it was too late to stop what was coming.
Flight data released this week by the National Transportation Safety Board reveals the sequence of a descent that went wrong in ways both obvious and subtle. The Boeing 767-300 touched down at 158 knots—292 kilometers per hour—a landing speed that aviation experts have flagged as being on the high end of acceptable. But the numbers alone do not capture what the pilots were experiencing in real time. Throughout the approach, one pilot issued repeated cautions about the aircraft's excessive speed. The NTSB's summary of their conversation notes there was "not a consistent verbal response" from the other pilot, even as the plane's instruments were screaming warnings. An automated callout announced the sink rate—the speed at which the plane was descending—was too steep. Another electronic voice warned that the aircraft was flying too close to the ground without being properly configured for landing.
What happened next unfolded in seconds. The plane overshot the runway. It struck ground equipment, then collided with a white Ford van carrying five members of a plane-cleaning crew. The aircraft continued forward, tore through a perimeter fence, hit a Toyota Corolla, and finally came to rest about 1,300 feet beyond where it should have stopped. The five people in the van—Rolando Aleman Leon, 55; Yoel Rodriguez Naranjo, 53; Julio C Pineda, 75; Carlos Acosta Fajardo, 53; and Javierkys Reyes Quevedo, 47—were killed. Five others were injured.
Aviation attorney Pablo Rojas told CBS News that the flight data raises hard questions about what was happening in the cockpit. Without access to the actual audio recording, he said, it is difficult to know exactly what the NTSB means by an "inconsistent verbal response." But the pattern is clear enough. "It really confirms that this was, in a way, a doomed approach," Rojas said. The data also shows that the plane's flaps—the movable surfaces on the wings that help slow an aircraft and allow for a gentler descent—were deployed much later than they should have been. Rojas suggested this late deployment may indicate the pilots were reacting to the fact that they were already going too fast, trying to correct a problem that had already taken hold.
The NTSB is continuing its investigation into the crash. The agency has not yet determined what caused the excessive speed or why one pilot's repeated warnings did not prompt the consistent response needed to correct the approach. What is known is that multiple safety systems worked as designed—the alarms sounded, the data was recorded, the warnings were issued. What remains unclear is why those warnings were not heeded in time.
Citazioni salienti
It really confirms that this was, in a way, a doomed approach.— Aviation attorney Pablo Rojas, speaking to CBS News