Flight profile · United Airlines
UA1763
San Diego (SAN) to San Francisco (SFO) · scheduled 1:50 PM – 3:35 PM
How UA1763 performs
396 operations, 2024-02-15 to 2026-06-30.
UA1763 arrived on time 73.7% of the time, against 67.6% for all SAN → SFO flights — this specific departure is 6.1 percentage points better than the route as a whole.
Source: US DOT Bureau of Transportation Statistics · 396 operations between 2024-02-15 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| UA1763 | 73.7% | 0.00% | -3 min | 6.6% | 396 |
| United Airlines on SAN → SFO | 74.5% | 1.08% | -5 min | 8.1% | 7,097 |
| All SAN → SFO flights | 67.6% | 1.14% | 0 min | 10.8% | 19,381 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-02-15 to 2026-06-30
Other routes UA1763 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→OMA San Francisco to Omaha | 2026-06-25 – 2026-06-29 | 4 | — |
| SFO→ORD San Francisco to Chicago | 2025-12-02 – 2026-06-24 | 46 | — |
| SFO→SEA San Francisco to Seattle | 2026-03-29 – 2026-05-20 | 53 | — |
| SEA→ORD Seattle to Chicago | 2026-04-02 – 2026-05-20 | 37 | — |
| IAH→PHL Houston to Philadelphia | 2026-03-05 – 2026-03-28 | 24 | — |
| SFO→EWR San Francisco to Newark | 2026-01-08 – 2026-02-09 | 20 | — |
| MSY→DEN New Orleans to Denver | 2025-12-18 – 2026-01-05 | 19 | — |
| SFO→XNA San Francisco to Fayetteville/Springdale/Rogers | 2025-06-01 – 2025-06-01 | 1 | — |
| JAX→EWR Jacksonville to Newark | 2025-05-01 – 2025-05-21 | 17 | — |
| SFO→RDU San Francisco to Raleigh–Durham | 2025-01-07 – 2025-04-30 | 90 | 95.5% |
| DEN→RIC Denver to Richmond | 2025-03-06 – 2025-03-29 | 24 | — |
| IAH→LAX Houston to Los Angeles | 2024-12-19 – 2025-01-06 | 19 | — |
| SFO→SNA San Francisco to Santa Ana | 2024-09-26 – 2024-12-02 | 68 | — |
| ABQ→SFO Albuquerque to San Francisco | 2024-11-01 – 2024-12-02 | 27 | — |
| MCI→SFO Kansas City to San Francisco | 2023-07-01 – 2024-09-25 | 258 | 94.1% |
| SFO→MFR San Francisco to Medford | 2024-06-27 – 2024-08-18 | 53 | — |
| SFO→PIT San Francisco to Pittsburgh | 2023-10-29 – 2024-06-26 | 211 | 86.7% |
| RSW→CLE Fort Myers to Cleveland | 2023-12-21 – 2024-01-08 | 19 | — |
| RNO→SFO Reno to San Francisco | 2023-10-29 – 2023-11-27 | 29 | — |
| SFO→AUS San Francisco to Austin | 2023-07-01 – 2023-09-04 | 47 | — |
| CLE→EWR Cleveland to Newark | 2023-08-06 – 2023-09-03 | 5 | — |
| EWR→LAS Newark to Las Vegas | 2023-08-06 – 2023-09-03 | 5 | — |
Because the same number has served different journeys, the statistics above describe only the route UA1763 currently operates. Blending them would produce an average of two different flights.
Why UA1763 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 UA1763 on SAN → 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 SAN → SFO
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| UA2117 | United Airlines | 79.7% | 9 min early | 1,000 |
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 396 records of UA1763 operating SAN → 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