Partly stale · checked FAA NAS status 222 h staleForecast cycle 85 minLightning 222 h staleWeather observations no data staleFAA surface data 4 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 Major Resolved Delay MDW departures

Midway departures back near normal: 17% late in the last hour

Current state
Resolved at 9:41 PM CST
Started
Latest activity
Updates
3
Create monitor View MDWFlights at MDW

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

    Midway departures running late: 74% left 15+ min late in the last hour

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

    Evidence for this update
    Measurement window6:28 PM–7:28 PM CST
    Sample23 flights, 17 late (74%)
    Comparison42% typical · US DOT on-time data, last 12 published months, departures in the 6 PM hour
    Median delay21.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 01:28 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

    Midway departure delays worsen: 100% late in the last hour

    What changed: late share 74% → 100%

    Of 15 departures that took off between 6:49 PM and 7:49 PM CST, 15 left at least 15 minutes late. Midway typically sees 41% 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 window6:49 PM–7:49 PM CST
    Sample15 flights, 15 late (100%)
    Comparison41% typical · US DOT on-time data, last 12 published months, departures in the 7 PM hour
    Median delay25.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 01:49 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

    Midway departures back near normal: 17% late in the last hour

    What changed: late share 100% at worst → 17% now

    Of 23 departures that took off between 8:41 PM and 9:41 PM CST, 4 left at least 15 minutes late. Midway typically sees 51% 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 31 minutes across 16 checks, each with at least 12 flights and current data.

    Evidence for this update
    Measurement window8:41 PM–9:41 PM CST
    Sample23 flights, 4 late (17%)
    Comparison51% typical · US DOT on-time data, last 12 published months, departures in the 9 PM hour
    Median delay4.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 03:41 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?