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

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

Lightning is stale (223 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 LAS departures

Las Vegas aircraft turns back near normal: 0 of 16 departures in the next 90 min are tight

Current state
Resolved at 5:14 AM PST
Started
Latest activity
Updates
4
Create monitor View LASFlights at LAS

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

    Las Vegas: 8 of 28 departures in the next 90 min have their aircraft due in with under 35 min to turn

    Of the 42 departures scheduled from Las Vegas (LAS) between 1:50 PM and 3:20 PM PST, FAA flight plans name the aircraft for 28. For 8 of those, the aircraft’s previous flight into LAS 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 scheduled1:50 PM–3:20 PM PST · 42 departures, aircraft known for 28
    Tight turns8 (29%) with the inbound due under 35 min before departure
    Inbound not yet in0 not taken off · 4 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 2383 to MKE at 2:51 PM: aircraft N8535S, inbound WN 204 from AMA (airborne), 11 min to turn
    TightestWN 2118 to LAX at 2:16 PM: aircraft N8948Q, inbound WN 2554 from LBB (airborne), 16 min to turn
    TightestWN 2674 to IND at 2:46 PM: aircraft N9033W, inbound WN 2508 from LAX (airborne), 23 min to turn
    TightestWN 1786 to PSP at 2:14 PM: aircraft N932WN, inbound WN 1786 from COS (landed), 26 min to turn
    TightestWN 2397 to FAT at 2:51 PM: aircraft N236WN, inbound WN 2397 from SAN (airborne), 27 min to turn
    Source event time
    Ingested
    Published here (2026-11-01 21:50 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 Las Vegas: 17 of 31 departures in the next 90 min

    What changed: tight share 29% → 55%

    Of the 45 departures scheduled from Las Vegas (LAS) between 5:24 PM and 6:54 PM PST, FAA flight plans name the aircraft for 31. For 17 of those, the aircraft’s previous flight into LAS 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); 4 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 scheduled5:24 PM–6:54 PM PST · 45 departures, aircraft known for 31
    Tight turns17 (55%) with the inbound due under 35 min before departure
    Inbound not yet in4 not taken off · 11 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 513 to TUS at 5:34 PM: aircraft N8966S, inbound WN 513 from BUR (not departed), -67 min to turn
    TightestWN 2400 to OMA at 5:49 PM: aircraft N936WN, inbound WN 598 from LAX (not departed), -57 min to turn
    TightestWN 2853 to SAT at 5:39 PM: aircraft N8872Q, inbound WN 2853 from LGB (not departed), -55 min to turn
    TightestWN 239 to OAK at 5:47 PM: aircraft N7752B, inbound WN 1010 from DEN (airborne), -52 min to turn
    TightestWN 662 to LGB at 5:45 PM: aircraft N295WN, inbound WN 2136 from ONT (not departed), -43 min to turn
    Source event time
    Ingested
    Published here (2026-11-02 01:24 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 Las Vegas: 12 of 23 departures in the next 90 min, still high

    What changed: tight share 55% → 52%

    Of the 30 departures scheduled from Las Vegas (LAS) between 6:00 PM and 7:30 PM PST, FAA flight plans name the aircraft for 23. For 12 of those, the aircraft’s previous flight into LAS 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 scheduled6:00 PM–7:30 PM PST · 30 departures, aircraft known for 23
    Tight turns12 (52%) with the inbound due under 35 min before departure
    Inbound not yet in1 not taken off · 5 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 4244 to OKC at 6:04 PM: aircraft N8542Z, inbound WN 4401 from OAK (airborne), -47 min to turn
    TightestWN 2047 to BUR at 6:14 PM: aircraft N929WN, inbound WN 2047 from ABQ (airborne), -40 min to turn
    TightestWN 4510 to BNA at 6:19 PM: aircraft N8958Q, inbound WN 424 from SEA (airborne), -39 min to turn
    TightestOO 4179 to SNA at 6:01 PM: aircraft N301SY, inbound OO 3916 from SAN (landed), 4 min to turn
    TightestWN 4335 to MCI at 6:29 PM: aircraft N8890Q, inbound WN 4335 from SLC (airborne), 12 min to turn
    Source event time
    Ingested
    Published here (2026-11-02 02:00 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

    Las Vegas aircraft turns back near normal: 0 of 16 departures in the next 90 min are tight

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

    Of the 26 departures scheduled from Las Vegas (LAS) between 5:14 AM and 6:44 AM PST, FAA flight plans name the aircraft for 16. For 0 of those, the aircraft’s previous flight into LAS 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 31 minutes across 16 checks, each with current data.

    Evidence for this update
    Departures scheduled5:14 AM–6:44 AM PST · 26 departures, aircraft known for 16
    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-11-02 13:14 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?