More news on this day
Labor Day travelers across Florida faced a chaotic end to the holiday weekend as a deadly Amazon-branded cargo plane crash at Miami International Airport, combined with rounds of intense storms, fueled hundreds of delays and cancellations at some of the state’s busiest airports.
Get the latest news straight to your inbox!
Runway overrun at Miami disrupts peak holiday traffic
The disruption began on Sunday, September 6, when a Boeing 767 operated for Amazon’s Prime Air network by 21 Air overran Runway 30 while landing at Miami International Airport and crashed beyond the airfield perimeter. Publicly available accounts indicate the jet struck at least two vehicles, including a passenger van, before coming to rest in a parking area and catching fire. Five people were killed and five others injured in one of the most serious cargo aviation accidents in the United States in recent years.
According to published coverage, the accident forced Miami International to suspend operations on all runways for several hours on Sunday afternoon, right as the Labor Day rush peaked. Subsequent notices from the airport and aviation outlets show that two runways remained closed into Monday while investigators documented the scene and recovery crews worked around the wreckage, meaning reduced capacity at one of the country’s busiest international gateways during a prime travel window.
Flight-tracking and airport status data cited in multiple reports point to hundreds of delayed and canceled flights into and out of Miami on Sunday and Monday, as airlines struggled to reposition aircraft and crews that had been held out of the airport during the initial shutdown. The resulting ripple effects left passengers facing missed connections, extended tarmac waits and last-minute rebookings, even on flights that were not directly linked to Miami.
Aviation analysis pieces note that the aircraft involved had been converted from a passenger jet to a freighter and was flying a route between Miami and San Juan, Puerto Rico, as part of Amazon’s domestic air network. Industry observers say the accident will likely prompt renewed scrutiny of runway overrun risks and wet-weather procedures at busy hub airports.
Stormy Labor Day skies compound Florida delays
At the same time, unsettled weather across South Florida added another layer of complexity for airlines and passengers. Forecasters in the Miami and Fort Lauderdale area flagged an unusually active pattern heading into the long weekend, with rounds of heavy rain and scattered thunderstorms projected each day from Friday through Labor Day. Local meteorologists reported roadway flooding and crash-clogged commutes as early bands of rain moved through on Saturday, signaling the kind of unstable conditions that often slow air traffic.
Television and online forecasts for the holiday period highlighted a return to a classic wet-season pattern, with storms flaring in the afternoon and early evening. For aviation, that meant periodic ground stops, holds and reroutes whenever lightning moved near terminals or storm cells built along approach and departure paths. Even without the Miami crash, those conditions were poised to make for a challenging travel weekend.
Weather discussions shared among pilots and aviation enthusiasts suggest that winds and rain were factors around the time of the crash, though investigators have not yet issued a formal finding on the role of weather in the accident itself. Regardless of the cause, the combination of reduced runway availability and intermittent convective storms significantly constrained the number of arrivals and departures Miami could safely handle per hour in the days that followed.
The impact was not limited to Miami. Storm clusters periodically affected Fort Lauderdale-Hollywood International and Palm Beach International as well, producing additional delays and diversions along Florida’s southeast coast. Travelers already rerouted away from Miami by the cargo jet investigation often found that nearby airports were also wrestling with weather-related slowdowns.
Ripple effects felt in Orlando and across Florida’s network
The timing of the Miami disruption and the storm pattern was especially problematic because Florida had been preparing for one of its busiest Labor Day travel periods in years. Orlando International Airport projected that more than 840,000 passengers would pass through its terminals between Thursday and Tuesday, with Labor Day itself expected to be the single busiest day of the stretch. Travel organizations again ranked Orlando among the top national holiday destinations for air travelers in 2026.
Central Florida did not experience the same level of operational shock as Miami, but the state’s interconnected air network meant Orlando and other airports still felt the knock-on effects. Flights originating in or routed through Miami sometimes arrived late or with crew-time limitations, forcing schedule shuffles that left Orlando passengers facing longer lines at ticket counters and security checkpoints.
Statewide, data from flight-tracking services and media tallies show that Florida airports collectively recorded elevated delay and cancellation rates compared with a typical September weekend. Carriers moved to consolidate lightly booked flights, swap aircraft between routes and encourage travelers to accept voluntary rebookings. For many passengers, the result was a day or more of uncertainty about when and where they would actually depart.
Travel analysts point out that holiday periods leave airlines with less slack in their systems. With aircraft and crews already heavily utilized, an incident like the Miami cargo crash, layered on top of active weather, can quickly overwhelm contingency plans and propagate problems far beyond the immediate region.
Investigators probe causes as travelers weigh future plans
Federal investigators are now focused on reconstructing the final minutes of the flight and understanding how an apparently routine approach ended in disaster. Early summaries of publicly released flight data suggest the crew may have attempted to abort an unstable landing before the aircraft ran off the end of the runway. Analysts note that such maneuvers require split-second decisions and precise execution, particularly when runway surfaces are damp or winds are shifting.
Reports indicate that the National Transportation Safety Board has recovered flight data and cockpit voice recorders and is examining them alongside radar tracks and weather observations. The investigation is expected to take months, with preliminary findings likely to address questions about landing distance, braking performance, crew actions and any environmental or mechanical factors that may have contributed.
For Amazon and its contracted cargo operators, the crash marks a significant setback for a network that has grown rapidly over the past decade. Industry coverage notes that the aircraft involved was one of the early jets brought into service for Amazon’s air operation and that the company has relied heavily on third-party carriers to expand its overnight delivery capacity. Safety experts say the findings in Miami could influence training requirements, oversight practices and infrastructure investments for cargo operations at major hubs.
In the near term, airlines serving Florida are urging passengers to build extra time into itineraries and to remain flexible about connections and routing. Travel advisors recommend closely monitoring flight status notifications, considering earlier departures when possible and being prepared for schedule adjustments if storms flare or if Miami’s runway configuration remains constrained while recovery work and inspections continue.
New York Times: Miami cargo plane crash coverage
FreightWaves: Runways closed after Amazon cargo jet accident