Flight profile · SkyWest Airlines
OO3413
San Jose (SJC) to Boise (BOI) · scheduled 7:22 PM – 7:44 PM
How OO3413 performs
370 operations, 2025-05-15 to 2026-06-30.
OO3413 arrived on time 86.7% of the time, against 84.6% for all SJC → BOI flights — this specific departure is 2.1 percentage points better than the route as a whole. Against SkyWest Airlines’s own flights on this route it is 1.6 points better.
Source: US DOT Bureau of Transportation Statistics · 370 operations between 2025-05-15 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| OO3413 | 86.7% | 0.27% | -15 min | 4.1% | 370 |
| SkyWest Airlines on SJC → BOI | 85.1% | 0.12% | -10 min | 4.1% | 855 |
| All SJC → BOI flights | 84.6% | 0.10% | -7 min | 3.5% | 1,992 |
Source: FlyerIntel analysis of US DOT BTS data · 2025-05-15 to 2026-06-30
Other routes OO3413 has flown
A flight number is a slot in a schedule, and carriers reassign it. These are the other city pairs this number served in the analysis period.
| Route | Operated | Flights | On time |
|---|---|---|---|
| PHX→BOI Phoenix to Boise | 2025-02-13 – 2025-05-14 | 91 | 81.3% |
| BOI→PHX Boise to Phoenix | 2025-04-22 – 2025-05-14 | 23 | — |
| GTF→SEA Great Falls to Seattle | 2025-01-07 – 2025-02-12 | 37 | — |
| SEA→GTF Seattle to Great Falls | 2025-01-07 – 2025-02-12 | 37 | — |
| PDX→SJC Portland to San Jose | 2025-01-05 – 2025-01-05 | 1 | — |
| SEA→PSC Seattle to Pasco | 2024-12-19 – 2025-01-04 | 17 | — |
| SFO→SAN San Francisco to San Diego | 2024-10-27 – 2024-12-16 | 16 | — |
| BUR→SFO Burbank to San Francisco | 2024-12-12 – 2024-12-15 | 2 | — |
| GEG→SEA Spokane to Seattle | 2024-12-13 – 2024-12-13 | 1 | — |
| STS→LAX Santa Rosa to Los Angeles | 2024-12-08 – 2024-12-08 | 1 | — |
| SJC→SEA San Jose to Seattle | 2024-12-07 – 2024-12-07 | 1 | — |
| BOI→BUR Boise to Burbank | 2024-12-04 – 2024-12-06 | 2 | — |
| BUR→BOI Burbank to Boise | 2024-12-05 – 2024-12-05 | 1 | — |
| SFO→BUR San Francisco to Burbank | 2024-12-03 – 2024-12-03 | 1 | — |
| RDM→SEA Redmond to Seattle | 2024-12-02 – 2024-12-02 | 1 | — |
| PDX→SFO Portland to San Francisco | 2024-10-01 – 2024-10-25 | 25 | — |
| SEA→BOI Seattle to Boise | 2024-08-20 – 2024-09-29 | 40 | — |
| BOI→SEA Boise to Seattle | 2024-06-15 – 2024-08-19 | 54 | — |
| LAX→LAS Los Angeles to Las Vegas | 2024-05-16 – 2024-06-11 | 27 | — |
| SMF→SEA Sacramento to Seattle | 2024-04-16 – 2024-05-15 | 30 | — |
| SMF→PDX Sacramento to Portland | 2024-01-08 – 2024-04-15 | 81 | — |
| MSO→SEA Missoula to Seattle | 2023-12-14 – 2024-01-07 | 25 | — |
| SEA→MSO Seattle to Missoula | 2023-12-14 – 2024-01-07 | 25 | — |
| BOI→PDX Boise to Portland | 2023-11-29 – 2023-12-13 | 15 | — |
| PDX→BOI Portland to Boise | 2023-11-29 – 2023-12-13 | 15 | — |
| OAK→SEA Oakland to Seattle | 2023-11-18 – 2023-11-25 | 2 | — |
| SEA→OAK Seattle to Oakland | 2023-11-18 – 2023-11-25 | 2 | — |
| RDD→SEA Redding to Seattle | 2023-07-02 – 2023-11-16 | 98 | 82.7% |
| SEA→RDD Seattle to Redding | 2023-07-02 – 2023-11-16 | 98 | 77.6% |
Because the same number has served different journeys, the statistics above describe only the route OO3413 currently operates. Blending them would produce an average of two different flights.
Why OO3413 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding, fuelling — within the carrier’s control
airspace and airport capacity, including weather-driven flow control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for OO3413 on SJC → BOI. A single late flight can carry more than one cause, and only delays of fifteen minutes or more are attributed at all.
Data and methodology
Calculated by FlyerIntel from 370 records of OO3413 operating SJC → BOI, published by the US DOT Bureau of Transportation Statistics. A flight counts as delayed when it arrives 15 or more minutes after schedule. Cancelled and diverted flights are excluded from the on-time rate and reported separately. Flight numbers are resolved as carrier plus number plus route, because the same number serves different routes over time.