The first thing that caught his attention was not the fire. It was not the smoke, the emergency vehicles or the terrible scene that would unfold seconds later. It was the airplane itself.
From where he stood near Miami International Airport on Sunday afternoon, September 6, 2026, a witness watched an Amazon Air cargo jet approaching the runway after a flight from San Juan, Puerto Rico. At first, there was little reason to believe that the Boeing 767 was only moments away from becoming the center of a deadly aviation disaster. Then he noticed something about the way the aircraft was moving that struck him as unusual.
Minutes later, the plane had traveled beyond the end of the runway, crossed Northwest 67th Avenue, struck vehicles and erupted in flames. Five people were killed and five others were hospitalized, three of them critically injured. More than 200 emergency personnel descended on the area as Miami International Airport temporarily came to a standstill.
What investigators still do not know is why the aircraft failed to stop. Yet the witness account has provided another piece of the puzzle, describing what one person on the ground believed he saw immediately before the crash.
A Routine Arrival Suddenly Looked Wrong
The aircraft involved was 21 Air Flight 7598, a Boeing 767-300 freighter operating for Amazon Air. It had departed Luis Muñoz Marín International Airport in Puerto Rico and was arriving in Miami shortly before 2 p.m. when the landing went catastrophically wrong.
One of the most striking details to emerge afterward was that the pilots apparently had not declared an emergency before touchdown. Air-traffic-control recordings reviewed in early coverage contained no mayday call suggesting the crew knew they were about to face a major problem.
That makes the final moments before touchdown especially important.
Witness Alberto Medina was in the area and later described seeing the aircraft coming in. According to his account, the plane appeared to be moving unusually fast as it approached the runway. He told reporters that something about the landing immediately seemed abnormal.
He would soon understand why.
The aircraft touched down but did not stop within the runway. Instead, it continued toward the airport perimeter at tremendous speed, eventually leaving airport property and entering an area where vehicles were traveling.
What Medina saw cannot establish the cause of the accident. Eyewitness observations are only one small part of an aviation investigation, and perceptions of an aircraft’s speed or position from the ground can differ significantly depending on viewing angle and distance. But his description has become notable because investigators themselves are now examining the aircraft’s speed, touchdown point and stopping performance.
The Boeing Was Still Moving at Enormous Speed
Preliminary flight-tracking information cited in reporting after the accident suggested the Boeing was traveling at close to 130 mph as it left the runway area. Investigators will need the aircraft’s flight-data recorder and physical evidence from the runway to establish its precise speed and configuration during those critical seconds.
A large commercial aircraft does not stop immediately after its wheels touch pavement. Pilots depend on a combination of aerodynamic drag, wheel brakes, spoilers and reverse thrust to reduce speed. The amount of runway remaining after touchdown therefore matters enormously.
Investigators are expected to reconstruct the landing almost second by second, determining exactly where the aircraft touched down, how quickly it was moving, when braking began and whether its braking and reverse-thrust systems operated as expected.
Until that work is complete, the witness’s impression that the landing “wasn’t normal” remains exactly that — an observation, rather than an explanation.
Seconds later, however, there was no ambiguity about what was happening.
The Boeing was running out of runway.
The Plane Didn’t Stop at the Airport Fence
Flight 7598 continued beyond the normal runway environment and crossed Northwest 67th Avenue. In doing so, the aircraft struck vehicles on the ground, dramatically expanding the emergency from an aircraft accident into a mass-casualty scene involving people who had not been aboard the plane.
Emergency-radio recordings captured responders attempting to understand what had happened as they arrived.
One responder reported that the plane had crossed 67th Avenue and struck a truck. Crews then began searching for additional victims while simultaneously confronting the burning aircraft.
The situation deteriorated rapidly.
Firefighters found people trapped in vehicles. Others were injured outside the airplane. The pilot and co-pilot were reportedly trapped in the damaged cockpit, forcing rescue crews to work around the wreckage while fire and leaking fuel created additional danger.
At least one engine reportedly continued operating after the crash, further complicating efforts to approach the aircraft safely.
The quiet Sunday afternoon Medina had been watching was suddenly filled with smoke, flames and sirens.
“Plane’s on Fire”
The dispatch recordings released after the accident capture the transformation more vividly than almost anything else.
“The plane’s on fire,” one responder warned as crews approached the wreckage, before telling colleagues to prepare themselves for what they were about to encounter.
Those few words revealed how little time rescuers had to assess the situation.
They were dealing not simply with an aircraft that had rolled beyond a runway but with a large commercial freighter carrying significant amounts of fuel, damaged vehicles, trapped occupants and victims spread across an unusually wide scene.
Miami-Dade Fire Rescue ultimately dispatched more than 60 units, with roughly 200 personnel involved in the response.
Firefighters fought the flames while technical-rescue teams attempted to reach trapped victims. Paramedics established triage areas. Police closed roads around the airport. Meanwhile, airport officials halted flights as emergency vehicles moved through areas normally occupied by aircraft.
The accident had gone from touchdown to mass-casualty emergency in moments.
Five People Never Made It Home
As firefighters gained control of the scene, the human cost slowly became clear.
Authorities eventually confirmed five deaths.
Another five people were transported to hospitals. Three were initially reported in critical condition, while two suffered injuries described as less severe.
Officials did not immediately release a complete public account identifying where every victim had been at the moment of impact, and early reports cautioned against assuming that all of the fatalities had been aboard the aircraft. Because Flight 7598 struck vehicles after leaving airport property, investigators had to reconstruct several separate impact areas.
For families waiting for information, those hours were agonizing.
For investigators, the location of each victim would also help reconstruct the aircraft’s path after it left the runway.
The Witness Account Is Only the Beginning
In the hours after a major aviation accident, eyewitness testimony often attracts enormous attention because it provides an immediate human description of something investigators may take months to explain. Yet aviation investigators rarely depend on any single person’s memory.
The Boeing itself contains far more precise witnesses.
Its flight-data recorder can preserve information about speed, altitude, braking, engine performance and aircraft configuration. The cockpit voice recorder can reveal what the pilots were discussing and whether they noticed anything unusual during the approach or landing.
Investigators will also examine tire marks and other evidence along the runway, weather observations, maintenance records and air-traffic-control communications.
Taken together, those pieces should eventually reveal whether Flight 7598 landed too far down the runway, approached at an abnormal speed, experienced a mechanical problem, encountered difficult runway conditions or suffered from some combination of factors.
At this stage, none of those possibilities has been established as the cause.
The Absence of a Mayday May Become an Important Clue
One particularly intriguing question is why the pilots apparently did not issue an emergency call before landing.
If a major mechanical failure had already been obvious during the approach, investigators might expect some communication with air-traffic controllers. The absence of such a warning raises the possibility that whatever went wrong became apparent only during or after touchdown.
But even that conclusion would be premature.
Pilots facing rapidly developing emergencies sometimes have little time to communicate, and cockpit recordings will provide a much clearer picture of what the crew knew.
The final approach will therefore receive extraordinary scrutiny.
Investigators will compare what the pilots experienced inside the cockpit with what Medina believed he saw from outside.
Somewhere between those two perspectives lies the answer.
The Aircraft Had Been Flying for More Than Three Decades
The Boeing 767 involved in the crash was approximately 32 years old and had originally operated as a passenger aircraft before being converted into a freighter. It was operated by 21 Air for Amazon Air.
Its age has inevitably attracted attention online, but aircraft age alone does not establish anything about the cause of an accident. Commercial aircraft routinely remain in service for decades when maintained according to required standards.
What matters to investigators will be the actual condition of this particular airplane.
Maintenance records will be reviewed. Components involved in braking and deceleration will be examined. Investigators will look for evidence of mechanical abnormalities and compare physical findings with data stored aboard the aircraft.
Only then will they know whether the airplane itself contributed to what happened.
The Images Afterward Barely Resembled a Runway Accident
Photographs taken after firefighters extinguished the flames showed the Boeing resting outside the normal runway area, its fuselage surrounded by emergency equipment and investigators.
The images explain why the accident stunned witnesses.
A cargo jet designed to travel thousands of miles had somehow crossed from the controlled environment of an international airport into a roadway occupied by ordinary vehicles.
The distance between those two worlds is normally protected by layers of procedures, runway space and airport infrastructure.
On Sunday, Flight 7598 crossed that boundary in seconds.
For Medina, the transformation happened almost too quickly to process. One moment he was watching an airplane arrive. The next, he was witnessing a disaster.
What He Saw May Eventually Make More Sense
The most compelling part of Medina’s account is not that it solves the mystery.
It doesn’t.
It is that he appears to have noticed something unusual before he knew there had been an accident.
His description of the aircraft’s apparent speed now sits alongside flight-tracking information, runway evidence, cockpit recordings and the wreckage itself as investigators reconstruct the final moments.
Perhaps the eventual explanation will show why the aircraft looked unusual from where he stood.
Perhaps it will reveal something completely different.
For now, the National Transportation Safety Board and Federal Aviation Administration have the difficult task of separating observation from evidence and evidence from cause.
That process will take time.
A Few Seconds Separated an Ordinary Landing From Disaster
The tragedy of Flight 7598 can ultimately be measured in an astonishingly short period.
The aircraft had successfully traveled from Puerto Rico to South Florida. Miami was beneath it. The runway was ahead. There had apparently been no dramatic emergency declaration during the approach.
Then the wheels touched down.
Something went wrong.
The Boeing continued forward.
The remaining runway disappeared beneath it, followed by the airport boundary and then Northwest 67th Avenue.
Vehicles were struck. Fire erupted. Emergency dispatchers began calling for additional units. Within minutes, responders were confronting trapped victims and a mass-casualty incident.
Five people would not survive.
Medina could not have known any of that when the airplane first caught his attention. He simply saw something about its approach that made him think the landing did not look right.
Investigators now have to determine whether what he noticed was connected to the reason Flight 7598 never stopped.
For more on the tragic incident, read about the chilling dispatch audio that emerged after the Amazon cargo Boeing crashed in Miami. Or, for a change of pace, check out Madonna at 68: Decades of Photos Show Her Constant Reinvention and how ’90s teen crush Mike Vitar left Hollywood behind.
