Flight profile · SkyWest Airlines
OO3404
Santa Ana (SNA) to San Francisco (SFO) · scheduled 2:00 PM – 3:20 PM
How OO3404 performs
525 operations, 2023-07-01 to 2026-06-09.
OO3404 arrived on time 66.5% of the time, against 72.3% for all SNA → SFO flights — this specific departure is 5.8 percentage points worse than the route as a whole. Against SkyWest Airlines’s own flights on this route it is 5.3 points worse.
Source: US DOT Bureau of Transportation Statistics · 525 operations between 2023-07-01 to 2026-06-09
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| OO3404 | 66.5% | 0.95% | 0 min | 8.9% | 525 |
| SkyWest Airlines on SNA → SFO | 71.8% | 1.38% | -3 min | 9.7% | 9,843 |
| All SNA → SFO flights | 72.3% | 1.23% | -4 min | 9.5% | 13,393 |
Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-06-09
Other routes OO3404 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 |
|---|---|---|---|
| SFO→SNA San Francisco to Santa Ana | 2023-07-01 – 2026-06-09 | 491 | 71.1% |
| SJC→SNA San Jose to Santa Ana | 2024-05-01 – 2026-06-06 | 12 | — |
| OAK→SNA Oakland to Santa Ana | 2024-04-29 – 2026-06-05 | 5 | — |
| STS→LAS Santa Rosa to Las Vegas | 2026-03-18 – 2026-05-12 | 56 | — |
| BUR→STS Burbank to Santa Rosa | 2025-12-02 – 2025-12-17 | 16 | — |
| SAN→SFO San Diego to San Francisco | 2025-01-13 – 2025-02-10 | 5 | — |
| SAN→BOI San Diego to Boise | 2024-12-19 – 2025-01-05 | 18 | — |
| SFO→SEA San Francisco to Seattle | 2024-12-18 – 2024-12-18 | 1 | — |
| SJC→PDX San Jose to Portland | 2024-12-05 – 2024-12-16 | 8 | — |
| SFO→LAX San Francisco to Los Angeles | 2024-12-03 – 2024-12-03 | 1 | — |
| PDX→SEA Portland to Seattle | 2024-11-22 – 2024-12-02 | 11 | — |
| SFO→PDX San Francisco to Portland | 2024-10-29 – 2024-11-20 | 8 | — |
| SJC→SEA San Jose to Seattle | 2024-11-02 – 2024-11-16 | 3 | — |
| PDX→LAS Portland to Las Vegas | 2024-03-16 – 2024-04-13 | 5 | — |
| SEA→LAX Seattle to Los Angeles | 2024-04-02 – 2024-04-10 | 4 | — |
| SEA→BOI Seattle to Boise | 2024-03-13 – 2024-03-13 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route OO3404 currently operates. Blending them would produce an average of two different flights.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
55 min late
against a median of 0 min early
Percentiles over 525 operations. Cancelled and diverted flights have no arrival time and are counted separately rather than as very late arrivals.
Why OO3404 runs late
Where US DOT attributed the delay minutes on this flight.
airspace and airport capacity, including weather-driven flow control
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding, fuelling — within the carrier’s control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for OO3404 on SNA → SFO. A single late flight can carry more than one cause, and only delays of fifteen minutes or more are attributed at all.
Other departures on SNA → SFO
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| OO5873 | SkyWest Airlines | 68.4% | 4 min early | 632 |
| OO3440 | SkyWest Airlines | 62.1% | 3 min late | 664 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. Schedules change; confirm the departure still operates before booking around this.
Data and methodology
Calculated by FlyerIntel from 525 records of OO3404 operating SNA → SFO, 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.
Full methodology · Report a problem
Analysis last recomputed