The Amazon Air cargo aircraft involved in a fatal accident at Miami International Airport overflew nearly half of the runway before touching down, the National Transportation Safety Board said in its preliminary account of the accident.

The figure is the most concrete data point yet in an investigation that began immediately after the crash. A landing that consumes close to half of a runway's available length before the wheels reach the pavement leaves a narrow margin for stopping, and Miami's main arrival surfaces — among the busiest in the United States for both passenger and freight traffic — leave little room for error once that margin is spent.

The NTSB's statement establishes the geometry of the accident sequence: the aircraft passed a substantial portion of the runway before completing the landing. What remains unresolved, and what the board's continuing work will address, is why the approach continued to a touchdown that far down the runway rather than prompting a go-around. Investigators will examine the approach profile, the crew's decision-making, aircraft performance data, weather conditions at the time of arrival, and any air traffic control communications that preceded the landing.

A long landing is among the most closely scrutinized events in commercial operations because it compresses every subsequent margin — braking distance, spoiler and thrust-reverser effectiveness, and the runway remaining before the paved surface ends. On a fully loaded freighter, where landing weights typically run higher than on comparable passenger aircraft, the stopping-distance arithmetic become less forgiving still. Cargo operators fly dense, heavy payloads on schedules that push aircraft utilization, and the consequences of a touchdown point drifting deep into the landing distance available scale directly with weight.

For Amazon Air, the accident places its contracted cargo network under the same investigative spotlight that passenger carriers face after a hull loss. The carrier's fleet — a mix of Boeing 767s and ATRs operated by contracted airlines including Atlas Air and Silver Airways feeder operations — moves freight through hub airports where runway capacity, arrival rates and freighter turnaround times are tightly coupled. An NTSB finding that points toward crew procedure, aircraft systems or airport factors will carry operational consequences across that network, not just for the operator whose aircraft was involved.

The preliminary statement from the board also frames the timeline ahead. NTSB investigations of this type typically run 12 to 24 months to a probable-cause determination, with urgent safety recommendations issued earlier if investigators identify an immediate hazard. Interim factual reports will add the aircraft's actual touchdown point, its speed at landing, the runway condition reports in effect at the time, and the crew's experience and duty history — each a data point that either supports or complicates the early picture of a landing begun too far down the runway to be recoverable.

The board has not yet stated a probable cause, and the preliminary findings do not assign fault. What they do establish is where the aircraft was when the landing finally occurred — past nearly half the runway's length — and that the sequence ended in a fatal outcome. The investigation's next factual releases will determine whether that touchdown point reflected a stabilized approach that should have been broken off, a performance shortfall in the aircraft, or conditions at Miami that reduced the margin the crew believed it had.

Until then, the confirmed facts stand: an Amazon Air freighter landed deep on a Miami runway, and people died. The NTSB's final report will decide what the industry must change in response.