Is WN2234 delayed?
Yes, WN2234 landed in Las Vegas 299 min late, at 22:36 on Nov 13 (as of Nov 14, 06:36 UTC).
Usually on time: arrived within 15 min of schedule on 16 of the last 29 flights.
299 min late
Official source · Updated
Departure
Cleveland
CLE
Actual
Scheduled 16:12
Nov 13
Arrival
Las Vegas
LAS
Actual
Scheduled 17:38
Nov 13
Times shown in airport local time
Service date: · Scheduled departure date (America/New_York)
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.
- 299 min late
Cleveland → Las Vegas
- 9 min early
Cleveland → Las Vegas
- On schedule (2 min behind)
Kansas City → Washington
- On schedule (5 min behind)
Los Angeles → Kansas City
- 11 min early
Kansas City → Washington
Is WN2234 usually late?
Period: Oct 15, 2026 – Nov 14, 2026
On time means arriving no more than 15 minutes after the scheduled time; late means more than 15 minutes after. Cancelled and diverted flights are counted apart from arrivals. Compares scheduled and actual arrival times. Cancelled and diverted flights are left out. Some flights may be missing.
At the airports today
Cleveland (CLE) departures
- Left more than 15 min late
- 10 of 19
- Cancelled today
- 30
Las Vegas (LAS) departures
- Left more than 15 min late
- 19 of 47
- Cancelled today
- 38
Related flights
Flight history and details
| Service date | Departure | Arrival | Actual | Arrival delay (minutes) |
|---|---|---|---|---|
| Nov 13, 2026Arrived | Cleveland | Las Vegas | 299 | |
| Nov 12, 2026Arrived | Cleveland | Las Vegas | -9 | |
| Nov 11, 2026Arrived | Kansas City | Washington | 2 | |
| Nov 11, 2026Arrived | Los Angeles | Kansas City | 5 | |
| Nov 10, 2026Arrived | Kansas City | Washington | -11 | |
| Nov 10, 2026Arrived | Los Angeles | Kansas City | -20 | |
| Nov 9, 2026Arrived | Cleveland | Las Vegas | -23 | |
| Nov 8, 2026Arrived | Cleveland | Las Vegas | -9 | |
| Nov 6, 2026Arrived | Cleveland | Las Vegas | -2 | |
| Nov 5, 2026Arrived | Cleveland | Las Vegas | -10 | |
| Nov 4, 2026Arrived | Kansas City | Washington | 18 | |
| Nov 4, 2026Arrived | Los Angeles | Kansas City | 28 | |
| Nov 3, 2026Arrived | Kansas City | Washington | 16 | |
| Nov 3, 2026Arrived | Los Angeles | Kansas City | 7 | |
| Nov 2, 2026Arrived | Cleveland | Las Vegas | -23 | |
| Nov 1, 2026Arrived | Cleveland | Las Vegas | -8 | |
| Oct 30, 2026Arrived | Seattle | Las Vegas | 130 | |
| Oct 29, 2026Arrived | Seattle | Las Vegas | 24 | |
| Oct 28, 2026Arrived | Myrtle Beach | Baltimore | -7 | |
| Oct 26, 2026Arrived | Seattle | Las Vegas | -11 | |
| Oct 25, 2026Arrived | Seattle | Las Vegas | 33 | |
| Oct 23, 2026Arrived | Seattle | Las Vegas | 58 | |
| Oct 22, 2026Arrived | Seattle | Las Vegas | 76 | |
| Oct 21, 2026Arrived | Myrtle Beach | Baltimore | 0 | |
| Oct 20, 2026Arrived | Myrtle Beach | Baltimore | 2 | |
| Oct 19, 2026Arrived | Seattle | Las Vegas | 29 | |
| Oct 18, 2026Arrived | Seattle | Las Vegas | 111 | |
| Oct 16, 2026Arrived | Seattle | Las Vegas | 57 | |
| Oct 15, 2026Arrived | Seattle | Las Vegas | 98 |