Five people were killed and five others were injured on September 6, 2026, after 21 Air Flight 7598, a Boeing 767-300AER BDSF cargo aircraft, overran Runway 30 after landing at Miami International Airport in Miami, Florida. The aircraft, registered as N1997A, had departed from San Juan-Luis Muñoz Marín International Airport and was landing in Miami when the accident occurred.
Initial information from the NTSB indicates the aircraft did not make a normal stabilized touchdown on all landing gear. The plane touched down at high speed, with the nose gear and right main gear contacting the runway before the left main gear. During the landing roll, the crew applied braking, briefly advanced power as if attempting to continue or recover from the landing, and then reduced power again.
The aircraft was unable to stop on the runway. It struck airport equipment, overran the paved surface, traveled across grass, crossed NW 67th Avenue, and hit vehicles outside the runway environment. The aircraft was destroyed after colliding with ground objects, and a post-crash fire erupted. The No. 2 engine attachment appears to have been compromised during the accident sequence.
Five people on the ground were killed. Five others were injured, including three who were reported to be in critical condition. Thunderstorm activity was in the area at the time, with gusting winds reported. The NTSB is investigating the cause of the crash.
Runway overruns can become catastrophic
A runway excursion occurs when an aircraft leaves the runway surface during takeoff or landing. In a large cargo aircraft, an overrun can become catastrophic because of the aircraft’s speed, weight, fuel load, and distance required to stop.
Here, the aircraft reportedly left the paved surface, crossed grass, impacted airport equipment, crossed a public roadway, and struck vehicles. That sequence raises major questions about touchdown point, braking delay, landing configuration, runway conditions, crew decision-making, wind, weather, and whether a rejected landing or go-around attempt was initiated too late to succeed.
Runway overruns are rarely explained by one fact alone. Investigators will likely examine whether the aircraft touched down long, fast, or misaligned, whether all landing gear were firmly on the runway, when braking and spoilers became effective, and why power was briefly advanced before being reduced again.
The touchdown and braking sequence matters
The initial NTSB data makes the aircraft’s touchdown sequence especially important. The aircraft reportedly touched down first on the nose gear and right main gear, with the left main gear touching down several seconds later. That is an unusual and important detail.
A large aircraft depends on proper landing attitude, firm weight-on-wheels, braking, spoilers, reverse thrust, and directional control to stop safely. If all landing gear are not fully on the runway, braking and stopping performance may be delayed or reduced. A delay of even several seconds can matter when an aircraft is moving at high speed.
The reported 13-second delay before braking will likely be a central issue. Investigators may review cockpit voice recorder information, flight data, autobrake settings, manual brake inputs, spoiler deployment, thrust reverser status, tire condition, runway surface conditions, and crew callouts. They may also evaluate whether the crew recognized the runway overrun risk early enough.
Thunderstorm, wind, and crosswind concerns
Weather may be one of the most important parts of the investigation. At the time of the accident, a thunderstorm was in the area, and winds were reported from 190 degrees at 17 knots, gusting to 26 knots. Landing on Runway 30 under those wind conditions may have involved a significant crosswind component and gusts.
Adverse weather can affect approach stability, touchdown speed, aircraft alignment, braking performance, and pilot workload. A thunderstorm near the airport may also create rapidly changing wind, heavy rain, reduced visibility, turbulence, and wind shifts.
A crosswind landing in a heavy cargo aircraft requires precise control. Gusts can cause drift, bank, wing-low touchdown, crab-angle issues, or delayed main gear contact. If one main gear touched down significantly later than the other, investigators may consider whether wind, aircraft attitude, runway alignment, or control inputs contributed.
Wind shear may also be examined if thunderstorm outflow or sudden wind changes affected the final approach or flare. No cause has been determined, but storm conditions and gusting winds must be carefully reviewed.
Go-around and rejected landing questions
The application of TOGA power after braking began is one of the most important reported facts. A go-around is normally used to discontinue an unsafe approach or landing attempt. However, once an aircraft is on the runway at high speed and braking has begun, the decision to continue stopping or attempt to fly again can become extremely time-sensitive.
The reported sequence indicates that TOGA power was applied at about 120 knots after the left main gear touched down, then engine power was brought back to idle four seconds later. Investigators will need to determine why power was advanced, whether the crew intended to reject the landing, whether aircraft configuration allowed a safe go-around, and why that attempt was discontinued.
A late transition between stopping and attempting to go around can consume critical runway distance. The cockpit voice recorder and flight data recorder should help explain the crew’s decision-making, callouts, automation status, thrust settings, and aircraft response.
Ground impacts and post-crash fire
After overrunning the runway, the aircraft struck the localizer antenna array, crossed grass, crossed NW 67th Avenue, and struck vehicles. The No. 2 engine attachment reportedly appears to have been compromised, and a fire erupted at that point.
Post-crash fire can greatly increase the severity of an aircraft accident. Fire may threaten crew members, people in vehicles, first responders, and anyone trapped near the wreckage. It can also destroy important evidence, including wiring, cockpit components, engine structures, and systems that may help explain the accident.
Investigators may review fuel release, engine separation or damage, fire origin, emergency response timing, airport perimeter protection, roadway exposure, and why vehicles were in the aircraft’s path after it left the airport boundary. A runway overrun that reaches a public roadway raises serious questions about airport safety zones, ground infrastructure, and protection of people outside the aircraft.
Flight recorders and investigation evidence
The NTSB’s investigation will likely rely heavily on flight data and cockpit voice information. In this accident, the timing of touchdown, braking, left main gear contact, TOGA power, idle thrust, overrun speed, and impact sequence will be central.
The flight data recorder may show airspeed, groundspeed, vertical acceleration, pitch, bank, yaw, brake pressure, spoiler deployment, thrust reverser activity, engine power, flap settings, landing gear status, and control inputs. The cockpit voice recorder may show crew communications, warnings, checklists, callouts, and decision-making during the final seconds.
A black box review can be critical after a runway overrun because the physical wreckage alone may not explain why the aircraft did not stop or why power settings changed during the landing roll.
Maintenance, systems, and aircraft performance
Mechanical and systems issues must also be ruled in or out. Aircraft maintenance may become relevant if there were problems with braking, antiskid, spoilers, thrust reversers, landing gear, tires, hydraulics, flight controls, or warning systems.
Investigators may examine whether the braking system responded properly, whether spoilers deployed, whether thrust reversers activated, whether any system generated alerts, and whether the aircraft had recent maintenance or unresolved discrepancies. Compliance with any applicable Airworthiness Directive may also be reviewed.
Because the aircraft was a converted freighter operating commercial cargo service, the investigation may also consider weight, balance, landing performance calculations, dispatch decisions, crew training, company procedures, and whether landing performance margins were adequate for the conditions.
Legal issues after a cargo-plane runway overrun
A fatal cargo aircraft overrun may involve multiple potentially responsible parties. Depending on the evidence, legal issues may include crew decision-making, company procedures, cargo operator training, aircraft maintenance, runway conditions, air traffic control communications, airport safety zones, emergency response, and protection of vehicles or workers near the airport perimeter.
An aviation accident attorney can help families evaluate flight recorder evidence, aircraft records, company procedures, airport layout, roadway impacts, and potential claims against responsible parties. Ground victims may have different legal issues than crew members because they were not passengers on the aircraft but were injured or killed after the aircraft left the runway environment.
The key questions are why the aircraft did not stop, whether the landing should have been rejected earlier, whether weather or runway conditions made the landing unsafe, and whether people on the ground were exposed to preventable danger.
Speak With an Aviation Accident Attorney
Spagnoletti Law Firm represents people and families affected by serious aviation accidents and other catastrophic events. When a cargo aircraft overruns a runway, strikes ground vehicles, or catches fire, it is important to determine whether weather, landing performance, aircraft systems, maintenance, airport layout, or operational decisions contributed to the tragedy.
We offer a free consultation, and we handle aviation accident cases on a contingency fee basis, meaning there are no upfront attorney’s fees and we are paid only if we recover compensation for you.
If you or a loved one has been impacted by a plane crash, call Spagnoletti Law Firm at 713-804-9306 or contact us online.