Is WN1247 delayed?
No, WN1247 landed in Baltimore on schedule (2 min behind), at 14:11 on Nov 15 (as of Nov 15, 19:11 UTC).
Usually on time: 19 of its last 20 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 (2 min behind)
Official source · Updated
Departure
Columbus
CMH
Actual
Scheduled 13:07
Nov 15
Arrival
Baltimore
BWI
Actual
Scheduled 14:09
Nov 15
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
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 (2 min behind)
Columbus → Baltimore
- 10 min early
Columbus → Baltimore
- On schedule (12 min behind)
Columbus → Baltimore
- 15 min early
Fort Myers → Columbus
- 28 min early
Columbus → Baltimore
Is WN1247 usually late?
Period: Oct 16, 2026 – Nov 15, 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
Baltimore (BWI) departures
- Delayed: left more than 15 min after schedule
- 46 delayed, 9 cancelled of 97 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 | Columbus | Baltimore | 2 | |
| Nov 13, 2026Arrived | Columbus | Baltimore | -10 | |
| Nov 12, 2026Arrived | Columbus | Baltimore | 12 | |
| Nov 11, 2026Arrived | Fort Myers | Columbus | -15 | |
| Nov 10, 2026Arrived | Columbus | Baltimore | -28 | |
| Nov 10, 2026Arrived | Fort Myers | Columbus | -21 | |
| Nov 9, 2026Arrived | Columbus | Baltimore | 2 | |
| Nov 8, 2026Arrived | Columbus | Baltimore | -13 | |
| Nov 6, 2026Arrived | Columbus | Baltimore | 15 | |
| Nov 5, 2026Arrived | Columbus | Baltimore | -4 | |
| Nov 4, 2026Arrived | Columbus | Baltimore | -7 | |
| Nov 4, 2026Arrived | Fort Myers | Columbus | -14 | |
| Nov 3, 2026Arrived | Columbus | Baltimore | -26 | |
| Nov 3, 2026Arrived | Fort Myers | Columbus | -7 | |
| Nov 2, 2026Arrived | Columbus | Baltimore | -13 | |
| Nov 1, 2026Arrived | Columbus | Baltimore | 3 | |
| Oct 26, 2026Arrived | Columbus | Denver | -10 | |
| Oct 25, 2026Arrived | Tucson | Las Vegas | 12 | |
| Oct 22, 2026Arrived | Columbus | Denver | 0 | |
| Oct 18, 2026Arrived | Tucson | Las Vegas | 74 |