Partly stale · checked FAA NAS status 222 h staleForecast cycle 79 minLightning 222 h staleWeather observations no data staleFAA surface data 2 minFAA flight data 4 min

FAA NAS status is stale (222 h old). No FAA restriction can start or end on the wire until it is fresh again.

Lightning is stale (222 h old). Lightning items are paused; thunderstorm items still come from official observations.

Weather observations is stale. Weather items are paused until it is fresh again; missing observations never end a weather event.

Observed Significant Resolved Delay SFO departures

SFO departures back near normal: 22% late in the last hour

Current state
Resolved at 9:48 PM PST
Started
Latest activity
Updates
3
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 departures running late: 70% left 15+ min late in the last hour

    Of 23 departures that took off between 7:13 PM and 8:13 PM PST, 16 left at least 15 minutes late. SFO typically sees 25% of departures in this hour leave that late (US DOT on-time data, last 12 published months, departures in the 7 PM hour). Measured by Tailodds from FAA flight data against airline schedules.

    Evidence for this update
    Measurement window7:13 PM–8:13 PM PST
    Sample23 flights, 16 late (70%)
    Comparison25% typical · US DOT on-time data, last 12 published months, departures in the 7 PM hour
    Median delay19.0 min
    MethodFAA wheels-off/on +/- median taxi (taxi_times) vs the FAA-filed airline schedule (flight_odds)
    Source event time
    Ingested
    Published here (2026-11-13 04:13 UTC)
    SourcesTailodds measurement of FAA flight data against airline schedules
    Provenanceobserved_ops observed-ops-v1 · config 2026-10-17.1 · writer template-v1
    Was this useful?
  2. De-escalation Observed

    SFO departure delays ease: 50% late in the last hour, still above normal

    What changed: late share 70% → 50%

    Of 16 departures that took off between 8:04 PM and 9:04 PM PST, 8 left at least 15 minutes late. SFO typically sees 32% of departures in this hour leave that late (US DOT on-time data, last 12 published months, departures in the 8 PM hour). Measured by Tailodds from FAA flight data against airline schedules.

    Evidence for this update
    Measurement window8:04 PM–9:04 PM PST
    Sample16 flights, 8 late (50%)
    Comparison32% typical · US DOT on-time data, last 12 published months, departures in the 8 PM hour
    Median delay17.0 min
    MethodFAA wheels-off/on +/- median taxi (taxi_times) vs the FAA-filed airline schedule (flight_odds)
    Source event time
    Ingested
    Published here (2026-11-13 05:04 UTC)
    SourcesTailodds measurement of FAA flight data against airline schedules
    Provenanceobserved_ops observed-ops-v1 · config 2026-10-17.1 · writer template-v1
    Was this useful?
  3. Recovery Observed

    SFO departures back near normal: 22% late in the last hour

    What changed: late share 83% at worst → 22% now

    Of 23 departures that took off between 8:48 PM and 9:48 PM PST, 5 left at least 15 minutes late. SFO typically sees 27% of departures in this hour leave that late (US DOT on-time data, last 12 published months, departures in the 9 PM hour). Measured by Tailodds from FAA flight data against airline schedules. The late share has stayed at or below 30% for 30 minutes across 16 checks, each with at least 12 flights and current data.

    Evidence for this update
    Measurement window8:48 PM–9:48 PM PST
    Sample23 flights, 5 late (22%)
    Comparison27% typical · US DOT on-time data, last 12 published months, departures in the 9 PM hour
    Median delay3.0 min
    MethodFAA wheels-off/on +/- median taxi (taxi_times) vs the FAA-filed airline schedule (flight_odds)
    Source event time
    Ingested
    Published here (2026-11-13 05:48 UTC)
    SourcesTailodds measurement of FAA flight data against airline schedules
    Provenanceobserved_ops observed-ops-v1 · config 2026-10-17.1 · writer template-v1
    Was this useful?