Is WN1914 delayed?
No, WN1914 landed in Sacramento 25 min early, at 12:59 on Nov 15 (as of Nov 15, 21:00 UTC).
Usually on time: 21 of its last 29 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.
25 min early
Official source · Updated
Departure
Baltimore
BWI
Actual
Scheduled 10:35
Nov 15
Arrival
Sacramento
SMF
Actual
Scheduled 13:24
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.
- 25 min early
Baltimore → Sacramento
- 219 min late
San Antonio → El Paso
- 34 min early
Baltimore → Sacramento
- 14 min early
Baltimore → Sacramento
- 20 min early
Baltimore → Sacramento
Is WN1914 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
Baltimore (BWI) departures
Too few departures on record with a known outcome so far today to judge: 0 of 20 needed.
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 | Sacramento | -25 | |
| Nov 14, 2026Arrived | San Antonio | El Paso | 219 | |
| Nov 13, 2026Arrived | Baltimore | Sacramento | -34 | |
| Nov 12, 2026Arrived | Baltimore | Sacramento | -14 | |
| Nov 11, 2026Arrived | Baltimore | Sacramento | -20 | |
| Nov 10, 2026Arrived | Baltimore | Sacramento | 48 | |
| Nov 9, 2026Arrived | Baltimore | Sacramento | -10 | |
| Nov 8, 2026Arrived | Baltimore | Sacramento | -2 | |
| Nov 7, 2026Arrived | San Antonio | El Paso | 7 | |
| Nov 6, 2026Arrived | Baltimore | Sacramento | -21 | |
| Nov 5, 2026Arrived | Baltimore | Sacramento | -2 | |
| Nov 4, 2026Arrived | Baltimore | Sacramento | -24 | |
| Nov 3, 2026Arrived | Baltimore | Sacramento | -23 | |
| Nov 2, 2026Arrived | Baltimore | Sacramento | -15 | |
| Nov 1, 2026Arrived | Baltimore | Sacramento | -6 | |
| Oct 29, 2026Arrived | Fort Lauderdale | Dallas | 17 | |
| Oct 28, 2026Arrived | Fort Lauderdale | Columbus | -13 | |
| Oct 27, 2026Arrived | Fort Lauderdale | Columbus | -14 | |
| Oct 26, 2026Arrived | Fort Lauderdale | Dallas | -2 | |
| Oct 25, 2026Arrived | Columbus | St Louis | 21 | |
| Oct 25, 2026Arrived | Fort Lauderdale | Columbus | 22 | |
| Oct 23, 2026Arrived | Fort Lauderdale | Dallas | 21 | |
| Oct 22, 2026Arrived | Fort Lauderdale | Dallas | 32 | |
| Oct 21, 2026Arrived | Fort Lauderdale | Columbus | 0 | |
| Oct 20, 2026Arrived | Fort Lauderdale | Columbus | -1 | |
| Oct 19, 2026Arrived | Fort Lauderdale | Dallas | -13 | |
| Oct 18, 2026Arrived | Columbus | St Louis | 13 | |
| Oct 18, 2026Arrived | Fort Lauderdale | Columbus | 14 | |
| Oct 17, 2026Arrived | Fort Lauderdale | Columbus | 62 |