Boston Logan and Miami International Face Separate Disruptions in Week of September 11
Why It MattersRunway-capacity losses show how planned safety upgrades and sudden accident investigations impose similar operational strain, even though one is scheduled and controllable while the other is not.
What happened
Boston Logan International Airport and Miami International Airport (MIA) are each dealing with major runway disruptions this week, though the causes are unrelated. At Logan, airport operator Massport ordered a planned closure of Runway 9/27 to allow installation of additional Engineered Materials Arresting System (EMAS) protection at a runway end. The closure, scheduled to run until mid-November — a window of approximately 75 days — has produced a recurring pattern of 60–75 minute average afternoon delays under certain wind and traffic configurations. Massport has described the work as a deliberate trade of reduced short-term capacity for a long-term safety improvement.

At MIA, the disruption stems from the fatal crash of 21 Air Flight 7598 on Sunday, September 6. The Boeing 767-300 freighter, operating under contract for Amazon Prime Air on a flight arriving from San Juan, Puerto Rico, overran Runway 30 at approximately 2:00 PM, struck multiple vehicles in a nearby parking area, and came to rest with catastrophic results. Five people on the ground were killed: Rolando Aleman Leon, 55; Yoel Rodriguez Narajo, 53; Julio C. Pineda, 75; Carlos Acosta Fajardo, 53; and Javierkys Reyes Quevedo, 47, identified by Miami-Dade County officials.
As of Tuesday, September 8, two of MIA's four runways remained closed while the NTSB continued its on-site investigation, leaving the airport operating at half its normal runway capacity into the second week following the crash. On the Monday immediately after the accident, 129 domestic flights were delayed and 65 were cancelled at MIA. No timeline has been announced for when all four runways will return to service.
Industry impact & what to watch
Both cases illustrate how concentrated a single runway or runway pair is within an airport's total capacity: losing one asset at Logan or two at MIA does not scale down operations proportionally, it produces disproportionate afternoon delay banking and cancellations because arrival and departure flows cannot simply redistribute across the remaining runways without absorbing wait time. The Logan closure is the more predictable version of this dynamic — a scheduled, safety-driven tradeoff with a known mid-November end date that lets carriers and passengers plan around a defined window. The MIA situation is the opposite: an unscheduled loss of half of a four-runway field with no announced restoration timeline, driven by an active NTSB investigation into a fatal freighter accident.
What differs is the exit path. Logan's disruption ends when the EMAS installation is complete, a construction timeline Massport already controls. MIA's runway restoration depends on when the NTSB clears the affected runways for use, a process with no fixed schedule until investigators determine it is safe to reopen them. The next verifiable markers are Massport's progress reports on the EMAS work at Logan, and any NTSB statement on when the two closed MIA runways might return to service.

















































