What does the July 2026 SJC → SAN data actually show?
The BTS file recorded 478 scheduled reporting-carrier nonstop flight records from Mineta San Jose International Airport (SJC / KSJC) to San Diego International Airport (SAN / KSAN) during 1–31 July 2026. Of completed flights with a known arrival delay, 60.1% were on time by the BTS definition of arriving less than 15 minutes late. Separately, the cancellation rate across all scheduled records was 0.6%, and 0.2% were diverted.
This is a direction-specific historical sample, not a statement that this route operates today, a live operational feed, a forecast, an airline-specific result or a promise for a future booking.
Six measured indicators for this flight direction
Do not add the on-time and cancellation rates: the denominators differ. This sample includes only reporting-carrier domestic nonstop records; other traffic is outside its coverage.
Same airports, reverse flight direction: why the journey order matters
The same July 2026 BTS archive separately recorded 476 scheduled nonstop flight records from SAN to SJC. The reverse direction had 66.0% on-time arrivals, 0.4% cancellations and mean arrival delay of 12.6 minutes.
On-time rate difference (SJC→SAN minus SAN→SJC): -5.8 percentage points. This is a descriptive comparison across two different sets of observed flights, not a causal claim or a reliable future directional advantage.
Open the separately measured reverse-direction report for SAN → SJC →
Scheduled departure-hour cohorts in July 2026
These are local scheduled departure hours at Mineta San Jose International Airport (BTS CRSDepTime). To limit very small samples, only hour groups with at least 30 scheduled flight records are displayed. These are observed past outcomes and must not be used as a recommendation or guarantee about which time to book.
| Scheduled departure time | Flight records | On-time arrivals | Cancelled | Mean arrival delay |
|---|---|---|---|---|
| 07:00–07:59 | 38 | 76.3% | 0.0% | 5.9 min |
| 08:00–08:59 | 31 | 74.2% | 0.0% | 13.6 min |
| 09:00–09:59 | 54 | 75.5% | 0.0% | 8.0 min |
| 10:00–10:59 | 56 | 73.2% | 0.0% | 11.0 min |
| 11:00–11:59 | 31 | 56.7% | 3.2% | 17.5 min |
| 13:00–13:59 | 31 | 67.7% | 0.0% | 13.8 min |
| 15:00–15:59 | 31 | 38.7% | 0.0% | 44.4 min |
| 17:00–17:59 | 63 | 50.8% | 3.2% | 21.1 min |
The displayed groups account for 335 of the 478 monthly scheduled records. Other flight records can belong to suppressed small-hour groups or have missing scheduled-hour information. The largest displayed time group began at 17:00 origin-local time with 63 records; this indicates sample volume, not safety or future punctuality.
Source and measurement boundaries
Source: U.S. DOT Bureau of Transportation Statistics, Reporting Carrier On-Time Performance (July 2026) ↗. Published September 2026 and processed into AeroDue's source-dated historical aggregates in October. The dataset covers reported domestic nonstop scheduled flight records, not every potential airline service.
Verify airport codes independently: SJC / KSJC airport identity ↗ and SAN / KSAN airport identity ↗. Reporting-carrier eligibility, canceled/unknown arrival-delay records and the sample windows determine the denominator for each measure.
For your real flight, check the operating airline, exact flight date and status. These statistics cannot prove a delay cause, eligibility for a refund or fixed compensation.
Continue from the route to a real travel decision
- Verify your flight status and identifying flight number for the correct day.
- Confirm the operating airline's current customer-service commitments for disruptions, and do not confuse them with refund duties.
- Keep the itinerary, receipts and written airline notifications before reviewing any passenger rights.
See measured July 2026 airport-wide arrival performance at SJC →
See measured July 2026 airport-wide arrival performance at SAN →
Compare recorded US airline assistance commitments → · Read US/Canada passenger-rights guidance →
Other high-sample recorded routes sharing this origin or destination
These are linked because they share an origin/destination and have similarly sized historical reporting samples. They are not suggested alternative flights or verified connections.