Amazon cargo plane crash in Miami: Pilot warned it was coming in too fast was recorded by Global Incident Tracker on Friday, 11 September 2026 at 17:48 UTC. The event is classified as a air crash incident with a severity rating of Moderate, and was detected through GNEWS.
Reported in United States (Miami). Found by our incident harvester, which queries each country's press in its own language, one incident category at a time (transport). Original headline: "Amazon cargo plane crash in Miami: Pilot warned it was coming in too fast - WFLX".
Where this happened
The incident is located in United States (North America), whose capital is Washington, D.C.. Historically, United States is most affected by hurricanes, wildfires, tornadoes, earthquakes and floods. You can follow every incident recorded in this country, updated live, on the United States incident tracker.
Approximate coordinates of the reported event are 25.774°, -80.194°. The marker on the map above shows this position; for news-derived reports the location reflects the place named in media coverage and may represent a district or city rather than an exact site.
Understanding air crash events
Aviation accidents involving passenger, cargo, military or light aircraft. Aviation remains the safest form of long-distance travel per kilometre. Modern accidents almost always involve a chain of contributing factors, which is why investigations take months and produce systemic recommendations.
How severity is rated
Global Incident Tracker rates every event on a four-step scale — Minor, Moderate, Severe and Extreme — derived from the source signal: earthquake magnitude, official GDACS alert colour, or the volume of independent media reporting for news-derived incidents. This event is currently rated Moderate. Ratings can change as more information becomes available, and a rating is a monitoring signal rather than an official government assessment.
Safety guidance for air crash situations
- Do not approach a crash site: fuel, composites and pressurised components remain hazardous.
- Preserve the site for investigators; debris position matters for the inquiry.
- Families should use the operator's official information line rather than social media.
- Treat early speculation about causes with heavy scepticism.
- Follow only official instructions from local authorities and emergency services — this page is a monitoring record, not an emergency alert.
Data and verification
This record was generated automatically from GNEWS and de-duplicated against our archive. Early reports for any incident can be revised: locations get refined, magnitudes are recalculated and impact figures change as assessments arrive. We deliberately do not publish casualty numbers unless an official source states them. The original source report is linked at the top of this page.
Keep watching the situation on our live world incident map, browse every plane crashes we track on the Air Crash tracker, or see today's global picture on the incidents today page.
Timeline and sources
Reported
Reported by News reports (Google News). Not independently confirmed. Copies of one syndicated story are counted once.
How statuses are decided · the number of reports is never treated as confirmation.
-
· received · event time 11 Sep 2026, 17:48 UTCFirst report News report
First recorded from News reports (Google News).
-
· receivedAlso reported News report
One more report from News reports (Google News). Links were not kept for reports merged before 13 September 2026.
News reports (Google News)
Times are when this site received each report, in UTC; the event time is shown where the source gave one. 2 reports are attached to this incident. Copies of one syndicated story count as one report.
Conditions at the time
No rainfall was recorded that day, and the temperature peaked at 31°C. Conditions are shown for context only — they do not establish a cause.
Weather reanalysis for this location and date via Open-Meteo.