Model lowers MCO departure delay risk 6–9 PM Monday to 53%
- Current state
- Resolved: closed without a new report (The forecast window has started; measured delays are reported separately as observed items.)
- Started
- Latest activity
- Updates
- 4
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
-
Initial Forecast
Model forecasts 44% delay risk for MCO departures 6–9 PM Monday
Tailodds’ model gives the 123 departures scheduled from MCO 6–9 PM Monday an average 44% chance of leaving 15+ minutes late. With calm weather the same flights would average 27%. From the 7:00 AM EST forecast (model famA-fc-v3+famB-sd-v4i). This is a forecast, not a report of delays.
Evidence for this update
Target MCO departures 6–9 PM 2026-11-16 (15+ min late) Probability (calibrated, mean per flight) 44% over 123 flights Forecast cycle · horizon Mon Nov 16, 7:00 AM EST · 9.5 h ahead Model version famA-fc-v3+famB-sd-v4i Source event time Ingested Published here (2026-11-16 13:27 UTC) Sources Tailodds forecast Provenance forecast_blocks forecast-blocks-v1 · config 2026-10-17.1 · writer template-v1 Was this useful? -
Escalation Forecast
Updated model puts MCO departure delay risk 6–9 PM Monday at 55%
What changed: 44% → 55% since the 7:00 AM EST forecast (model changed)
Tailodds’ model gives the 123 departures scheduled from MCO 6–9 PM Monday an average 55% chance of leaving 15+ minutes late. With calm weather the same flights would average 29%. From the 3:00 PM EST forecast (model famB-sd-v4i). The model changed since the previous item (from famA-fc-v3+famB-sd-v4i), so some or all of this change comes from the new model rather than new information. This is a forecast, not a report of delays.
Evidence for this update
Target MCO departures 6–9 PM 2026-11-16 (15+ min late) Probability (calibrated, mean per flight) 55% over 123 flights Forecast cycle · horizon Mon Nov 16, 3:00 PM EST · 2.1 h ahead Model version famB-sd-v4i (changed since the previous update) Source event time Ingested Published here (2026-11-16 20:56 UTC) Sources Tailodds forecast Provenance forecast_blocks forecast-blocks-v1 · config 2026-10-17.1 · writer template-v1 Was this useful? -
Escalation Forecast
Model raises MCO departure delay risk 6–9 PM Monday to 59%
What changed: 55% → 59% since the 3:00 PM EST forecast (same model, same window)
Tailodds’ model gives the 123 departures scheduled from MCO 6–9 PM Monday an average 59% chance of leaving 15+ minutes late. With calm weather the same flights would average 29%. From the 4:00 PM EST forecast (model famB-sd-v4i). This is a forecast, not a report of delays.
Evidence for this update
Target MCO departures 6–9 PM 2026-11-16 (15+ min late) Probability (calibrated, mean per flight) 59% over 123 flights Forecast cycle · horizon Mon Nov 16, 4:00 PM EST · 1.1 h ahead Model version famB-sd-v4i Source event time Ingested Published here (2026-11-16 21:56 UTC) Sources Tailodds forecast Provenance forecast_blocks forecast-blocks-v1 · config 2026-10-17.1 · writer template-v1 Was this useful? -
De-escalation Forecast
Model lowers MCO departure delay risk 6–9 PM Monday to 53%
What changed: 59% → 53% since the 4:00 PM EST forecast (same model, same window)
Tailodds’ model gives the 123 departures scheduled from MCO 6–9 PM Monday an average 53% chance of leaving 15+ minutes late. With calm weather the same flights would average 31%. From the 5:00 PM EST forecast (model famB-sd-v4i). This is a forecast, not a report of delays.
Evidence for this update
Target MCO departures 6–9 PM 2026-11-16 (15+ min late) Probability (calibrated, mean per flight) 53% over 123 flights Forecast cycle · horizon Mon Nov 16, 5:00 PM EST · 0.0 h ahead Model version famB-sd-v4i Source event time Ingested Published here (2026-11-16 22:57 UTC) Sources Tailodds forecast Provenance forecast_blocks forecast-blocks-v1 · config 2026-10-17.1 · writer template-v1 Was this useful?
Closed Mon Nov 16, 6:01 PM EST: The forecast window has started; measured delays are reported separately as observed items.