Live · checked FAA national advisories 5 minFAA NAS status 1 minForecast cycle 71 minLightning 2 minWeather observations 3 minFAA surface data 5 minFAA flight data 5 min
Observed Significant Resolved Inbound aircraft SFO departures

SFO aircraft turns back near normal: 1 of 24 departures in the next 90 min are tight

Current state
Resolved at 2:22 PM PDT
Started
Latest activity
Updates
2
Create monitor View SFOFlights at SFO

Tailodds reports what the FAA publishes, what we measure and what our model forecasts. It doesn’t control airport operations or change bookings; check with your airline about your trip.

Updates oldest first

  1. Initial Observed

    SFO: 8 of 32 departures in the next 90 min have their aircraft due in with under 35 min to turn

    Of the 57 departures scheduled from SFO (SFO) between 9:42 AM and 11:12 AM PDT, FAA flight plans name the aircraft for 32. For 8 of those, the aircraft’s previous flight into SFO is due at the gate less than 35 minutes before the scheduled departure, or after it (FAA arrival times or estimates plus the airport’s typical taxi time); 1 of those inbound flights have not taken off yet. Measured by Tailodds from FAA flight data; it does not mean each of these departures will leave late.

    Evidence for this update
    Departures scheduled9:42 AM–11:12 AM PDT · 57 departures, aircraft known for 32
    Tight turns8 (25%) with the inbound due under 35 min before departure
    Inbound not yet in1 not taken off · 4 in the air
    MethodSFDPS flight-plan aircraft (flight_aircraft) -> previous flight into this airport; FAA wheels-on or arrival estimate + median taxi-in (taxi_times) vs the FAA-filed airline schedule (flight_odds)
    TightestOO 6007 to MRY at 10:00 AM: aircraft N947SW, inbound OO 385 from SMF (not departed), -37 min to turn
    TightestWN 1647 to SAN at 10:56 AM: aircraft N8866H, inbound WN 4303 from DEN (airborne), -15 min to turn
    TightestOO 4708 to ACV at 10:15 AM: aircraft N610UX, inbound OO 4639 from BOI (airborne), 17 min to turn
    TightestWN 3288 to AUS at 10:33 AM: aircraft N8961K, inbound WN 3471 from PHX (airborne), 23 min to turn
    TightestWN 4311 to BUR at 10:38 AM: aircraft N429WN, inbound WN 1146 from BUR (airborne), 25 min to turn
    Source event time
    Ingested
    Published here (2026-10-26 16:42 UTC)
    SourcesTailodds measurement of FAA flight plans and arrival estimates against airline schedules
    Provenanceinbound_aircraft inbound-v1 · config 2026-10-17.1 · writer template-v1
    Was this useful?
  2. Recovery Observed

    SFO aircraft turns back near normal: 1 of 24 departures in the next 90 min are tight

    What changed: tight share 29% at worst → 4% now

    Of the 32 departures scheduled from SFO (SFO) between 2:22 PM and 3:52 PM PDT, FAA flight plans name the aircraft for 24. For 1 of those, the aircraft’s previous flight into SFO is due at the gate less than 35 minutes before the scheduled departure, or after it (FAA arrival times or estimates plus the airport’s typical taxi time); 1 of those inbound flights have not taken off yet. Measured by Tailodds from FAA flight data; it does not mean each of these departures will leave late. The tight share has stayed at or below 12% for 31 minutes across 16 checks, each with current data.

    Evidence for this update
    Departures scheduled2:22 PM–3:52 PM PDT · 32 departures, aircraft known for 24
    Tight turns1 (4%) with the inbound due under 35 min before departure
    Inbound not yet in1 not taken off · 0 in the air
    MethodSFDPS flight-plan aircraft (flight_aircraft) -> previous flight into this airport; FAA wheels-on or arrival estimate + median taxi-in (taxi_times) vs the FAA-filed airline schedule (flight_odds)
    TightestWN 4313 to DAL at 3:31 PM: aircraft N8866H, inbound WN 473 from SAN (not departed), -24 min to turn
    Source event time
    Ingested
    Published here (2026-10-26 21:22 UTC)
    SourcesTailodds measurement of FAA flight plans and arrival estimates against airline schedules
    Provenanceinbound_aircraft inbound-v1 · config 2026-10-17.1 · writer template-v1
    Was this useful?