Is WN1559 delayed?
No, WN1559 landed in San Antonio on schedule (10 min behind), at 14:44 on Nov 19 (as of Nov 19, 20:50 UTC).
Usually on time: 20 of its last 30 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.
On schedule (10 min behind)
Official source · Updated
Departure
Orlando
MCO
Scheduled
Nov 19
Arrival
San Antonio
SAT
Actual
Scheduled 14:34
Nov 19
Times shown in airport local time
Service date: · Scheduled departure date (America/New_York)
Market settled: On time.
Flight details
Departure · UTC
- Scheduled
- Estimated
- Not available
- Actual
- Not available
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.
- On schedule (10 min behind)
Orlando → San Antonio
- 20 min early
Orlando → San Antonio
- 25 min late
Orlando → San Antonio
- 142 min late
Denver → Columbus
- 249 min late
Orlando → San Antonio
Is WN1559 usually late?
Period: Oct 20, 2026 – Nov 19, 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
Orlando (MCO) departures
- Delayed: left more than 15 min after schedule
- 90 delayed, 0 cancelled of 162 departures on record
Counts cover the departures on record at each airport, not its full schedule.
Related flights
More flights of the same airline observed landing recently: WN9016
Flight history and details
| Service date | Departure | Arrival | Actual | Arrival delay (minutes) |
|---|---|---|---|---|
| Nov 19, 2026Arrived | Orlando | San Antonio | 10 | |
| Nov 17, 2026Arrived | Orlando | San Antonio | -20 | |
| Nov 16, 2026Arrived | Orlando | San Antonio | 25 | |
| Nov 15, 2026Arrived | Denver | Columbus | 142 | |
| Nov 14, 2026Arrived | Orlando | San Antonio | 249 | |
| Nov 13, 2026Arrived | Denver | Columbus | 6 | |
| Nov 12, 2026Arrived | Denver | Columbus | -4 | |
| Nov 11, 2026Arrived | Orlando | San Antonio | -3 | |
| Nov 10, 2026Arrived | Orlando | San Antonio | 58 | |
| Nov 9, 2026Arrived | Denver | Columbus | 0 | |
| Nov 8, 2026Arrived | Denver | Columbus | 33 | |
| Nov 7, 2026Arrived | Orlando | San Antonio | 10 | |
| Nov 6, 2026Arrived | Denver | Columbus | 0 | |
| Nov 5, 2026Arrived | Denver | Columbus | 31 | |
| Nov 4, 2026Arrived | Orlando | San Antonio | 3 | |
| Nov 3, 2026Arrived | Orlando | San Antonio | 2 | |
| Nov 2, 2026Arrived | Denver | Columbus | -17 | |
| Nov 1, 2026Arrived | Denver | Columbus | -2 | |
| Oct 31, 2026Arrived | Las Vegas | San Diego | -19 | |
| Oct 31, 2026Arrived | Oakland | Las Vegas | -22 | |
| Oct 30, 2026Arrived | Chicago | Kansas City | 65 | |
| Oct 29, 2026Arrived | Chicago | Kansas City | -1 | |
| Oct 28, 2026Arrived | Chicago | Kansas City | 19 | |
| Oct 27, 2026Arrived | Chicago | Kansas City | -23 | |
| Oct 26, 2026Arrived | Chicago | Kansas City | 9 | |
| Oct 25, 2026Arrived | Chicago | Kansas City | 45 | |
| Oct 23, 2026Arrived | Chicago | Kansas City | 1 | |
| Oct 22, 2026Arrived | Chicago | Kansas City | 19 | |
| Oct 21, 2026Arrived | Chicago | Kansas City | -12 | |
| Oct 20, 2026Arrived | Chicago | Kansas City | -20 |