Is WN4491 delayed?
Yes, WN4491 landed in Tulsa 38 min late, at 00:01 on Nov 16 (as of Nov 16, 06:02 UTC).
Usually on time: 18 of its last 22 graded arrivals landed within 15 min of schedule. We say “usually” only from 20 graded arrivals, with two in three or more on one side.
38 min late
Official source · Updated
Departure
Las Vegas
LAS
Actual
Scheduled 19:11
Nov 15
Arrival
Tulsa
TUL
Actual
Scheduled 23:24
Nov 16
Times shown in airport local time
Service date: · Scheduled departure date (America/Los_Angeles)
Market settled: Delayed.
Flight details
Departure · UTC
- Scheduled
- Estimated
- Not available
- Actual
Arrival · UTC
- Scheduled
- Estimated
- Not available
- Actual
The price is the traded chance of the market’s outcome. It doesn’t confirm the flight’s status. See the market for its rules.
Recent arrivals
Dates below are arrival dates in the destination airport’s time zone. The detailed history uses service dates.
- 38 min late
Las Vegas → Tulsa
- 9 min early
Las Vegas → Tulsa
- 4 min early
Las Vegas → Tulsa
- 20 min early
Las Vegas → Tulsa
- 5 min early
Las Vegas → Tulsa
Is WN4491 usually late?
Period: Oct 17, 2026 – Nov 16, 2026
On time means landing no more than 15 minutes after the scheduled arrival, late more than 15 minutes after, both times read to the minute. The percentages share one base: graded arrivals plus cancelled and diverted flights. A cancelled plan another plan of the flight replaced within 12 hours is not counted. Median and “9 in 10” are interpolated over the graded arrivals. Compares scheduled and actual arrival times, read to the minute. Some flights may be missing.
Departures on record at these airports today
Las Vegas (LAS) departures
- Delayed: left more than 15 min after schedule
- 188 delayed, 15 cancelled of 395 departures on record
Counts cover the departures on record at each airport, not its full schedule.
Related flights
Flight history and details
| Service date | Departure | Arrival | Actual | Arrival delay (minutes) |
|---|---|---|---|---|
| Nov 15, 2026Arrived | Las Vegas | Tulsa | 38 | |
| Nov 13, 2026Cancelled | Las Vegas | Tulsa | Not available | Not available |
| Nov 12, 2026Arrived | Las Vegas | Tulsa | -9 | |
| Nov 11, 2026Arrived | Las Vegas | Tulsa | -4 | |
| Nov 10, 2026Arrived | Las Vegas | Tulsa | -20 | |
| Nov 9, 2026Arrived | Las Vegas | Tulsa | -5 | |
| Nov 8, 2026Arrived | Las Vegas | Tulsa | 18 | |
| Nov 6, 2026Arrived | Las Vegas | Tulsa | 1 | |
| Nov 5, 2026Arrived | Las Vegas | Tulsa | 4 | |
| Nov 4, 2026Arrived | Las Vegas | Tulsa | -13 | |
| Nov 3, 2026Arrived | Las Vegas | Tulsa | -3 | |
| Nov 2, 2026Arrived | Las Vegas | Tulsa | 79 | |
| Nov 1, 2026Arrived | Las Vegas | Tulsa | 42 | |
| Oct 30, 2026Arrived | Baltimore | Norfolk | -10 | |
| Oct 29, 2026Arrived | Baltimore | Norfolk | -4 | |
| Oct 26, 2026Arrived | Baltimore | Norfolk | -6 | |
| Oct 25, 2026Arrived | Baltimore | Norfolk | -12 | |
| Oct 24, 2026Arrived | Indianapolis | Fort Myers | -21 | |
| Oct 23, 2026Arrived | Baltimore | Norfolk | -2 | |
| Oct 22, 2026Arrived | Baltimore | Norfolk | 14 | |
| Oct 19, 2026Arrived | Baltimore | Norfolk | 7 | |
| Oct 18, 2026Arrived | Baltimore | Norfolk | -13 | |
| Oct 17, 2026Arrived | Indianapolis | Fort Myers | 11 |