Is WN1956 delayed?
No delay reported yet — WN1956 is scheduled to leave Boise at 15:42 on Sep 29 and reach San Diego at 16:45 (as of Sep 29, 19:42 UTC).
Usually on time: arrived within 15 min of schedule on 40 of the last 57 flights.
No live update yet
Showing the published schedule until live times are reported.
Update time unavailable
Departure
Boise
BOI
Scheduled
Sep 29
Arrival
San Diego
SAN
Scheduled
Sep 29
Times shown in airport local time
Service date: · Scheduled departure date (America/Boise)
Think WN1956 runs late today? Delayed is trading at 24¢ — pays out x4.10.
Will Southwest Airlines SWA 1956 from Boise to San Diego arrive on time, be delayed, or be cancelled on Sep 29?Flight details
Departure · UTC
- Scheduled
- Estimated
- Not available
- Actual
- Not available
Arrival · UTC
- Scheduled
- Estimated
- Not available
- Actual
- Not available
Market prices express trading expectations about a contract’s stated threshold. They do not confirm airline status. The linked market shows its terms and activity.
Recent arrivals
Dates below are arrival dates in the destination airport’s time zone. The detailed history uses service dates.
- 26 min early
Fort Lauderdale → Baltimore
- 9 min early
Dallas → Fort Lauderdale
- 15 min early
Kansas City → Dallas
- 17 min early
Denver → Kansas City
- 4 min early
Kansas City → Dallas
Is WN1956 usually late?
Observation window: Aug 30, 2026 – Sep 29, 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. Results compare scheduled and actual arrival times. Cancelled or diverted flights are excluded. Some flights may be missing from the history.
At the airports today
San Diego (SAN) departures
- Left more than 15 min late
- 23 of 115
- Cancelled today
- 1
Related flights
Flight history and details
| Service date | Departure | Arrival | Actual | Arrival delay (minutes) |
|---|---|---|---|---|
| Sep 28, 2026Arrived | Fort Lauderdale | Baltimore | -26 | |
| Sep 28, 2026Arrived | Dallas | Fort Lauderdale | -9 | |
| Sep 28, 2026Arrived | Kansas City | Dallas | -15 | |
| Sep 28, 2026Arrived | Denver | Kansas City | -17 | |
| Sep 27, 2026Arrived | Kansas City | Dallas | -4 | |
| Sep 27, 2026Arrived | Denver | Kansas City | -14 | |
| Sep 26, 2026Arrived | Boise | San Diego | -14 | |
| Sep 25, 2026Arrived | Fort Lauderdale | Baltimore | 8 | |
| Sep 25, 2026Arrived | Dallas | Fort Lauderdale | 4 | |
| Sep 25, 2026Arrived | Kansas City | Dallas | -12 | |
| Sep 25, 2026Arrived | Denver | Kansas City | -9 | |
| Sep 24, 2026Arrived | Fort Lauderdale | Baltimore | 38 | |
| Sep 24, 2026Arrived | Dallas | Fort Lauderdale | 21 | |
| Sep 24, 2026Arrived | Kansas City | Dallas | -2 | |
| Sep 24, 2026Arrived | Denver | Kansas City | -15 | |
| Sep 23, 2026Arrived | Boise | San Diego | 20 | |
| Sep 22, 2026Arrived | Boise | San Diego | -17 | |
| Sep 21, 2026Arrived | Fort Lauderdale | Baltimore | 45 | |
| Sep 21, 2026Arrived | Dallas | Fort Lauderdale | 46 | |
| Sep 21, 2026Arrived | Kansas City | Dallas | 4 | |
| Sep 21, 2026Arrived | Denver | Kansas City | 9 | |
| Sep 20, 2026Arrived | Kansas City | Dallas | -16 | |
| Sep 20, 2026Arrived | Denver | Kansas City | -10 | |
| Sep 19, 2026Arrived | Boise | San Diego | 0 | |
| Sep 18, 2026Arrived | Fort Lauderdale | Baltimore | 76 | |
| Sep 18, 2026Arrived | Dallas | Fort Lauderdale | 41 | |
| Sep 18, 2026Arrived | Kansas City | Dallas | -11 | |
| Sep 18, 2026Arrived | Denver | Kansas City | -6 | |
| Sep 17, 2026Arrived | Fort Lauderdale | Baltimore | 25 | |
| Sep 17, 2026Arrived | Dallas | Fort Lauderdale | 23 | |
| Sep 17, 2026Arrived | Kansas City | Dallas | 9 | |
| Sep 17, 2026Arrived | Denver | Kansas City | -12 | |
| Sep 16, 2026Arrived | Boise | San Diego | -8 | |
| Sep 14, 2026Arrived | Fort Lauderdale | Baltimore | -13 | |
| Sep 14, 2026Arrived | Dallas | Fort Lauderdale | -5 | |
| Sep 12, 2026Arrived | Boise | San Diego | -7 | |
| Sep 11, 2026Arrived | Fort Lauderdale | Baltimore | 43 | |
| Sep 11, 2026Arrived | Dallas | Fort Lauderdale | 20 | |
| Sep 11, 2026Arrived | Kansas City | Dallas | -7 | |
| Sep 11, 2026Arrived | Denver | Kansas City | -17 | |
| Sep 10, 2026Arrived | Fort Lauderdale | Baltimore | 11 | |
| Sep 10, 2026Arrived | Dallas | Fort Lauderdale | 13 | |
| Sep 10, 2026Arrived | Kansas City | Dallas | -4 | |
| Sep 9, 2026Arrived | Boise | San Diego | 21 | |
| Sep 8, 2026Arrived | Boise | San Diego | 63 | |
| Sep 7, 2026Arrived | Fort Lauderdale | Baltimore | 100 | |
| Sep 7, 2026Arrived | Dallas | Fort Lauderdale | 15 | |
| Sep 7, 2026Arrived | Kansas City | Dallas | -17 | |
| Sep 7, 2026Arrived | Denver | Kansas City | -10 | |
| Sep 6, 2026Arrived | St Louis | Jacksonville | 20 | |
| Sep 5, 2026Arrived | Boise | San Diego | -2 | |
| Sep 4, 2026Arrived | Fort Lauderdale | Baltimore | 4 | |
| Sep 4, 2026Arrived | Dallas | Fort Lauderdale | 8 | |
| Sep 4, 2026Arrived | Kansas City | Dallas | -20 | |
| Sep 4, 2026Arrived | Denver | Kansas City | -19 | |
| Sep 3, 2026Cancelled | Denver | Kansas City | Not available | Not available |
| Aug 31, 2026Arrived | Fort Lauderdale | Baltimore | 38 | |
| Aug 31, 2026Arrived | Denver | Kansas City | -15 |
Email me if WN1956 runs late
We email you if your next WN1956 flight in the coming day is more than 15 minutes late, cancelled or diverted. Alerts last 30 days. No account needed.