San Diego caused national knock‑ons

Flight delays at San Diego International on Sunday, April 12, spilled far beyond Southern California, stranding connecting passengers and pushing late aircraft into airline networks across the country. (thetraveler.org) Public flight-tracking reports cited 46 delayed flights and one cancellation at San Diego on April 12, with United Airlines, Southwest Airlines and Alaska Airlines among the carriers hit. Those delays affected both arrivals and departures, turning short slips at the gate into missed onward connections. (thetraveler.org) The Federal Aviation Administration’s National Airspace System dashboard showed active delay programs elsewhere on April 12, including a ground delay at San Francisco International Airport averaging 31 minutes and forecast disruption risks later in the day for Denver, Houston and Dallas-area traffic. That meant San Diego’s problems were feeding into a system already under strain. (faa.gov) FlightAware’s MiseryMap showed 455 delays and 13 cancellations nationwide at the time of the snapshot on April 12. Large hubs including Atlanta, Chicago, Denver, New York and Seattle were on the map, the same kind of connection points where a late inbound jet from San Diego can disrupt the next leg. (flightaware.com) San Diego is especially vulnerable to knock-on delays because it is a constrained airport with a single main runway and heavy peak-hour demand. The Federal Aviation Administration’s airport capacity profiles define capacity as the hourly number of flights an airport’s runways can sustain, and San Diego has less room to absorb slippage than multi-runway hubs. (faa.gov, faa.gov) That is why a day with relatively few cancellations can still become a national problem. When one aircraft arrives late in San Diego, the same plane, crew and gate assignment can reach Los Angeles, Phoenix, Denver, Dallas or Chicago behind schedule and carry the delay forward. (thetraveler.org, faa.gov) The Federal Aviation Administration’s live status page did not show a systemwide ground stop for San Diego itself on the morning snapshot, and San Diego International’s public flight-status page remained open for travelers to check individual arrivals. That points to a rolling operational slowdown, not a full airport shutdown. (faa.gov, san.org) For travelers, the practical effect on April 12 was simple: a delay that began in San Diego did not stay in San Diego. By the time the national maps lit up, the missed connection was already the story. (flightaware.com, thetraveler.org)