Partly stale · checked FAA NAS status 222 h staleForecast cycle 1 hLightning 222 h staleWeather observations no data staleFAA surface data 3 minFAA flight data 3 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 Developing Delay SAN departures

San Diego departure delays ease: 63% late in the last hour, still above normal

Current state
Developing
Started
Latest activity
Updates
5
Create monitor View SANFlights at SAN

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

    San Diego departures running late: 56% left 15+ min late in the last hour

    Of 18 departures that took off between 11:50 AM and 12:50 PM PST, 10 left at least 15 minutes late. San Diego typically sees 29% of departures in this hour leave that late (US DOT on-time data, last 12 published months, departures in the 12 PM hour). Measured by Tailodds from FAA flight data against airline schedules.

    Evidence for this update
    Measurement window11:50 AM–12:50 PM PST
    Sample18 flights, 10 late (56%)
    Comparison29% typical · US DOT on-time data, last 12 published months, departures in the 12 PM hour
    Median delay33.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-12 20:50 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. Escalation Observed

    San Diego departure delays worsen: 77% late in the last hour

    What changed: late share 56% → 77%

    Of 22 departures that took off between 1:26 PM and 2:26 PM PST, 17 left at least 15 minutes late. San Diego typically sees 34% of departures in this hour leave that late (US DOT on-time data, last 12 published months, departures in the 1 PM hour). Measured by Tailodds from FAA flight data against airline schedules.

    Evidence for this update
    Measurement window1:26 PM–2:26 PM PST
    Sample22 flights, 17 late (77%)
    Comparison34% typical · US DOT on-time data, last 12 published months, departures in the 1 PM hour
    Median delay35.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-12 22:27 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. De-escalation Observed

    San Diego departure delays ease: 59% late in the last hour, still above normal

    What changed: late share 77% → 59%

    Of 17 departures that took off between 4:29 PM and 5:29 PM PST, 10 left at least 15 minutes late. San Diego typically sees 37% of departures in this hour leave that late (US DOT on-time data, last 12 published months, departures in the 4 PM hour). Measured by Tailodds from FAA flight data against airline schedules.

    Evidence for this update
    Measurement window4:29 PM–5:29 PM PST
    Sample17 flights, 10 late (59%)
    Comparison37% typical · US DOT on-time data, last 12 published months, departures in the 4 PM hour
    Median delay18.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 01:29 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?
  4. Escalation Observed

    San Diego departure delays worsen: 79% late in the last hour

    What changed: late share 59% → 79%

    Of 19 departures that took off between 7:33 PM and 8:33 PM PST, 15 left at least 15 minutes late. San Diego typically sees 36% 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 window7:33 PM–8:33 PM PST
    Sample19 flights, 15 late (79%)
    Comparison36% typical · US DOT on-time data, last 12 published months, departures in the 8 PM hour
    Median delay30.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:33 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?
  5. De-escalation Observed

    San Diego departure delays ease: 63% late in the last hour, still above normal

    What changed: late share 79% → 63%

    Of 19 departures that took off between 8:16 PM and 9:16 PM PST, 12 left at least 15 minutes late. San Diego typically sees 36% 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:16 PM–9:16 PM PST
    Sample19 flights, 12 late (63%)
    Comparison36% typical · US DOT on-time data, last 12 published months, departures in the 8 PM hour
    Median delay18.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:16 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?