Partly stale · checked FAA NAS status 224 h staleForecast cycle 1 hLightning 224 h staleWeather observations no data staleFAA surface data 6 minFAA flight data 6 min

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

Lightning is stale (224 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 Inbound aircraft BNA departures

Nashville aircraft turns back near normal: 0 of 17 departures in the next 90 min are tight

Current state
Resolved at 4:42 AM CDT
Started
Latest activity
Updates
4
Create monitor View BNAFlights at BNA

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

    Nashville: 10 of 26 departures in the next 90 min have their aircraft due in with under 35 min to turn

    Of the 31 departures scheduled from Nashville (BNA) between 10:55 AM and 12:25 PM CDT, FAA flight plans name the aircraft for 26. For 10 of those, the aircraft’s previous flight into BNA 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 scheduled10:55 AM–12:25 PM CDT · 31 departures, aircraft known for 26
    Tight turns10 (38%) with the inbound due under 35 min before departure
    Inbound not yet in1 not taken off · 8 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 2136 to DAL at 11:18 AM: aircraft N497WN, inbound WN 3355 from PHX (airborne), 2 min to turn
    TightestWN 660 to MSY at 12:05 PM: aircraft N1805U, inbound WN 2837 from TUL (airborne), 16 min to turn
    TightestWN 968 to GRR at 11:33 AM: aircraft N293WN, inbound WN 3199 from LGA (airborne), 24 min to turn
    TightestWN 322 to DCA at 11:28 AM: aircraft N8649A, inbound WN 1544 from DEN (airborne), 26 min to turn
    TightestWN 3250 to OMA at 12:08 PM: aircraft N8803L, inbound WN 2511 from RDU (airborne), 26 min to turn
    Source event time
    Ingested
    Published here (2026-10-23 15:55 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. Escalation Observed

    More tight aircraft turns at Nashville: 16 of 35 departures in the next 90 min

    What changed: tight share 38% → 46%

    Of the 44 departures scheduled from Nashville (BNA) between 6:22 PM and 7:52 PM CDT, FAA flight plans name the aircraft for 35. For 16 of those, the aircraft’s previous flight into BNA 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); 2 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 scheduled6:22 PM–7:52 PM CDT · 44 departures, aircraft known for 35
    Tight turns16 (46%) with the inbound due under 35 min before departure
    Inbound not yet in2 not taken off · 13 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 573 to JAN at 6:27 PM: aircraft N257WN, inbound WN 2838 from MDW (not departed), -114 min to turn
    TightestWN 165 to AUS at 6:45 PM: aircraft N8914Q, inbound WN 1936 from SJC (airborne), -62 min to turn
    TightestF9 3051 to DFW at 6:23 PM: aircraft N437FR, inbound F9 3052 from DFW (airborne), -26 min to turn
    TightestWN 611 to MCI at 6:56 PM: aircraft N8670A, inbound WN 275 from AUS (airborne), -16 min to turn
    TightestWN 724 to SFO at 7:33 PM: aircraft N8527Q, inbound WN 2701 from PHX (airborne), -11 min to turn
    Source event time
    Ingested
    Published here (2026-10-23 23: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?
  3. De-escalation Observed

    Fewer tight aircraft turns at Nashville: 11 of 27 departures in the next 90 min, still high

    What changed: tight share 46% → 41%

    Of the 34 departures scheduled from Nashville (BNA) between 6:51 PM and 8:21 PM CDT, FAA flight plans name the aircraft for 27. For 11 of those, the aircraft’s previous flight into BNA 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); 0 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 scheduled6:51 PM–8:21 PM CDT · 34 departures, aircraft known for 27
    Tight turns11 (41%) with the inbound due under 35 min before departure
    Inbound not yet in0 not taken off · 8 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 611 to MCI at 6:56 PM: aircraft N8670A, inbound WN 275 from AUS (airborne), -16 min to turn
    TightestWN 724 to SFO at 7:33 PM: aircraft N8527Q, inbound WN 2701 from PHX (airborne), -11 min to turn
    TightestWN 662 to MSY at 7:39 PM: aircraft N8719Q, inbound WN 3700 from SAT (airborne), -7 min to turn
    TightestWN 569 to HOU at 7:22 PM: aircraft N8737L, inbound WN 3317 from ORF (airborne), 1 min to turn
    TightestWN 1088 to MCO at 6:54 PM: aircraft N8817L, inbound WN 4614 from MSP (airborne), 2 min to turn
    Source event time
    Ingested
    Published here (2026-10-23 23:51 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?
  4. Recovery Observed

    Nashville aircraft turns back near normal: 0 of 17 departures in the next 90 min are tight

    What changed: tight share 55% at worst → 0% now

    Of the 23 departures scheduled from Nashville (BNA) between 4:42 AM and 6:12 AM CDT, FAA flight plans name the aircraft for 17. For 0 of those, the aircraft’s previous flight into BNA 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); 0 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 30 minutes across 16 checks, each with current data.

    Evidence for this update
    Departures scheduled4:42 AM–6:12 AM CDT · 23 departures, aircraft known for 17
    Tight turns0 (0%) with the inbound due under 35 min before departure
    Inbound not yet in0 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)
    Source event time
    Ingested
    Published here (2026-10-24 09: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?