The deadly crash of an Amazon cargo jet at Miami International Airport has sharpened a familiar aviation debate: was the decisive failure in the cockpit, on the runway, or in the safeguards that should have limited the damage?

The aircraft overshot the runway, struck vehicles and killed five people, injuring five others. A conservative account emphasizes flight data indicating that the pilots tried to abort the landing before the crash, placing the focus on the final approach and the difficult decisions made in its last moments.¹ That framing does not necessarily settle responsibility, but it directs attention toward whether the crew recognized the danger soon enough and whether the attempted go-around came too late.

A broader account stresses that the crash’s consequences were shaped by airport design as well as pilot action. Officials said the evidence suggested the pilots had considered aborting the landing, but Miami’s runway was not equipped with “arresting beds”—crushable-material systems intended to slow or stop aircraft that run beyond the pavement.¹ The Federal Aviation Administration says such systems have been installed at more than 120 airports nationwide, making their absence at Miami a central safety question rather than a technical footnote.

The two perspectives overlap on the immediate sequence: a landing deteriorated, an abort was considered, and the aircraft left the runway. They diverge over what deserves the greatest scrutiny. The pilot-centered interpretation asks whether cockpit decisions failed at the critical moment. The infrastructure-centered view asks whether a known risk was left without a final layer of protection—especially for people on the ground who had no role in the approach.

The crash therefore resists a single-cause explanation. Determining accountability will require separating the crew’s options in real time from the airport’s preparedness for an overrun—and examining why both vulnerabilities could converge in one fatal event.