A Boeing 767 cargo jet operated by 21 Air for Amazon overran Runway 30 at Miami International Airport on September 6 and struck occupied vehicles beyond the runway. Five people on the ground were killed and five others were injured, according to information released by federal investigators and reported by The Associated Press.

The National Transportation Safety Board said the people who died were in a van and an SUV hit by the aircraft. That corrects the earlier version of this story, which incorrectly described fatalities among the flight crew and vehicle operators. The pilots survived.

What investigators have established

Flight information released after the crash indicated that one pilot repeatedly warned that the aircraft was approaching too fast. Investigators also said the crew appeared to consider or attempt a go-around. Those findings are preliminary and do not establish the probable cause.

The cockpit voice recorder and flight data recorder were recovered. Investigators are expected to examine the touchdown point, approach stability, aircraft maintenance and ownership history, weather, crew actions and 21 Air's operation of the flight.

What remains unknown

The NTSB, not the airline or early eyewitness accounts, will determine probable cause after reviewing the full record. Casualty details, sequence-of-events findings and safety recommendations can change as the docket develops. Readers should distinguish preliminary updates from the agency's eventual final report.

How this account was assessed

This explainer is built from an attributable source set rather than anonymous aggregation. The references used for the current version are: Associated Press: NTSB investigation and corrected victim details; Associated Press: preliminary flight information; NTSB accident docket search. Each source has a different evidentiary role. A public record can establish what an institution filed or announced, while independent reporting can add chronology, interviews and context. Neither should be stretched beyond what it directly supports.

What the sources can—and cannot—show

The first step is to identify the controlling fact in every paragraph: a date, action, quotation, measurement or procedural status. That fact should be traceable to a named record. Statements about motive, cause or future impact require separate evidence and should not be inferred merely because two events occurred close together. Early official information can also change. Preliminary findings, emergency statements and initial court or agency summaries should be described as preliminary until the complete record is available.

A source’s existence is not proof of every detail in a story. Readers should check whether the linked page actually contains the quoted language or number, whether it covers the same time and place and whether a newer version has replaced it. When several reports all depend on the same original statement, they count as multiple publications but only one evidentiary origin.

Reading chronology and numbers carefully

Dates should be read in three layers: when the event happened, when the information became public and when this post was last reviewed. Keeping those moments separate prevents a later update from being projected backward. Numerical claims need the same discipline. Confirm the unit, denominator, comparison period, geographic scope and whether a figure is seasonally adjusted, inflation adjusted, estimated or final. A percentage change without its starting value can exaggerate practical significance.

Independent checks for readers

Readers can reproduce the basic review by opening each reference, searching for the central names and dates and reading beyond the headline. For government or court material, find the docket, order, transcript or downloadable dataset. For company statements, compare the announcement with a filing or regulator’s record when one exists. For scientific or technical claims, prefer the underlying paper, protocol or evaluation and check whether outside specialists have examined the method.

Why this context matters

Aviation reports matter first for safety, operations and the people directly affected; the cause should remain open until investigators publish evidence. Authority comes from showing the path from evidence to conclusion, not from confident tone. That is why this post keeps reference links visible, states the limits of the available material and avoids treating an unresolved question as settled.

What to watch next

Look for an investigation docket, recorder analysis, verified casualty updates and any operational directive from the relevant aviation authority. A useful update should name the new record, summarize the change and explain whether it confirms, narrows or contradicts the earlier account. If a correction changes a central fact, the correction should remain visible instead of being silently folded into the text.

This process does not eliminate uncertainty; it makes uncertainty legible. Readers should leave with a clear understanding of what is documented, what is attributed, what is analysis and what still requires evidence. That separation is the foundation of a durable, useful blog post.