Is WN2389 delayed?
No, WN2389 landed in Columbus 6 min early, at 12:03 on Nov 15 (as of Nov 15, 17:03 UTC).
Usually on time: 20 of its last 26 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.
6 min early
Official source · Updated
Departure
Baltimore
BWI
Actual
Scheduled 10:50
Nov 15
Arrival
Columbus
CMH
Actual
Scheduled 12: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.
- 6 min early
Baltimore → Columbus
- 5 min early
Baltimore → Columbus
- On schedule (7 min behind)
Baltimore → Columbus
- 25 min early
Baltimore → Columbus
- 8 min early
Baltimore → Columbus
Is WN2389 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
- 45 delayed, 8 cancelled of 95 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 | Baltimore | Columbus | -6 | |
| Nov 13, 2026Arrived | Baltimore | Columbus | -5 | |
| Nov 12, 2026Arrived | Baltimore | Columbus | 7 | |
| Nov 11, 2026Arrived | Baltimore | Columbus | -25 | |
| Nov 10, 2026Arrived | Baltimore | Columbus | -8 | |
| Nov 9, 2026Arrived | Baltimore | Columbus | -3 | |
| Nov 8, 2026Arrived | Baltimore | Columbus | -12 | |
| Nov 6, 2026Arrived | Baltimore | Columbus | 12 | |
| Nov 5, 2026Arrived | Baltimore | Columbus | 7 | |
| Nov 4, 2026Arrived | Baltimore | Columbus | -6 | |
| Nov 3, 2026Arrived | Baltimore | Columbus | -6 | |
| Nov 2, 2026Arrived | Baltimore | Columbus | -7 | |
| Oct 31, 2026Arrived | Raleigh/Durham | Orlando | -12 | |
| Oct 30, 2026Arrived | Las Vegas | Reno | -10 | |
| Oct 29, 2026Arrived | Las Vegas | Reno | 13 | |
| Oct 28, 2026Arrived | Las Vegas | Reno | -8 | |
| Oct 27, 2026Arrived | Las Vegas | Reno | 39 | |
| Oct 26, 2026Arrived | Las Vegas | Reno | -5 | |
| Oct 25, 2026Arrived | Las Vegas | Reno | 24 | |
| Oct 23, 2026Arrived | Las Vegas | Reno | 107 | |
| Oct 22, 2026Arrived | Las Vegas | Reno | 26 | |
| Oct 21, 2026Arrived | Las Vegas | Reno | 1 | |
| Oct 20, 2026Arrived | Las Vegas | Reno | -19 | |
| Oct 19, 2026Arrived | Las Vegas | Reno | -22 | |
| Oct 18, 2026Arrived | Las Vegas | Reno | 16 | |
| Oct 16, 2026Arrived | Las Vegas | Reno | 19 |