SFO operational friction

On Friday afternoon, April 3, a fire broke out in SFO’s cargo yard and was contained to five conex storage containers by roughly 3:33 p.m.; no injuries were reported and the airport said passenger flights were not affected. (abc7news.com) Fire crews said the blaze started around 2:15 p.m. near North McDonnell Road and involved pallets and giveaway items such as toiletries and headphones; smoke briefly closed nearby roadways and suspended the AirTrain Blue Line to rental car and long‑term parking. (ktvu.com) Separately, and more consequential for daily airline operations, the Federal Aviation Administration announced policy and procedural changes at SFO at the end of March that cut the airport’s maximum arrival rate from 54 aircraft per hour to 36. (usnews.com) Two elements drove that reduction. First, a six‑month runway rehabilitation has taken one set of north–south runways out of service, concentrating traffic onto the airport’s east–west runway pair and removing runway redundancy during peak periods. (airlinegeeks.com) Second, the FAA has banned simultaneous side‑by‑side visual approaches on SFO’s closely spaced parallel east‑west runways in clear weather, requiring “staggered” approaches where one aircraft is offset from the other. (kqed.org) Parallel, side‑by‑side approaches let two planes land nearly simultaneously and are a primary way busy airports squeeze more arrivals into each hour. Staggered approaches force extra lateral or longitudinal separation between arriving aircraft, which increases the time needed between successive landings and thus lowers hourly throughput. (bloomberg.com) The immediate operational result was visible in early April. Flight‑tracking summaries show SFO logged 224 delays and seven cancellations on April 4 as cascading late arrivals and reduced hourly capacity stacked into the morning and afternoon peaks. (nomadlawyer.org) For airlines and shippers, the two incidents illustrate different vulnerabilities. The cargo‑yard fire was a local disruption that produced smoke, traffic closures, and a brief transit outage but—because it was confined to storage containers—did not force terminal evacuations or runway closures. (nbcbayarea.com) The FAA’s capacity change, by contrast, alters how air traffic is sequenced across months and removes operational slack that absorbs small upstream delays. (cbsnews.com) That difference matters for people who move real assets around the Bay. If arrivals are slower and more volatile, airlines and freight carriers face higher on‑time risk for hub rotations; ground‑handling windows tighten; connecting passengers miss fewer predictable connections but more fragile ones. Those dynamics can shift demand toward warehouses with more flexible receiving hours, induce airlines to reoptimize schedules out of SFO, and raise the value of logistics sites that minimize last‑mile dwell time. (airlinegeeks.com) Operationally, the runway repaving is expected to keep constraints in place for roughly six months, with reopening targeted in October 2026, while the FAA said it does not plan to lift the staggered‑approach restriction once the repaving finishes. (usnews.com) The cargo fire was contained quickly and did not halt passenger service; the FAA’s arrival cap, however, is producing multi‑week ripple effects through April and is scheduled to influence airport throughput through at least October 2026. (abc7news.com)