# Incident 19990103021799I: Cessna 172M, San Jose, CA, January 3, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 3, 1999, 13:46 local time
- Place: San Jose, CA
- Airport: Reid-Hillview Of Santa Clara
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 37.3329° N, 121.8198° W: Placed by OpenAirDocs at REID-HILLVIEW OF SANTA CLARA COUNTY (RHV), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.3329&lon=-121.8198&mi=10
- Aircraft: N9668Q, a cancelled registration (https://openairdocs.org/deregistered/N9668Q-2013-05-23) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 89 total, 10 in this make and model, 9 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990103021799I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-5) PILOT STATED THE AIRCRAFT ENTERED THE DOWNWIND LEG OF RWY 31R AT RHV, WHERE PILOT BECAME UNSURE AS TO SEQUENCE FOR LANDING. TWO AIRCRAFT WITH SIMILAR `N' NUMBERS WERE BEING SEQUENCED, AND WERE IN CONTACT WITH RHV ATCT AS "CESSNA 68Q" AND "CESSNA 68B." ATCT DID NOT ADVISE THE AIRCRAFT OF SIMILAR `N' NUMBERS ON THE SAME FREQUENCY. ACCORDING TO THE PILOT, THIS UNCERTAINTY AS TO SEQUENCE CAUSED HIM, IN PART, TO TURN FROM THE DOWNWIND LEG ONTO THE BASE LEG SOONER THAN NORMAL, WHICH CAUSED THE AIRCRAFT TO BE POSITIONED HIGHER THAN NORMAL FOR THE BASE LEG. THE PILOT STATED THE LANDING PATTERN FINAL LEG AS THEN FLOWN TOO HIGH AND APPROXIMATELY TEN-TO-FIFTEEN MILES PER HOUR TOO FAST, AND THE AIRCRAFT TOUCHED DOWN APPROXIMATELY ONE-HALF WAY DOWN THE 3,101 FOOT RUNWAY. THE AIRCRAFT BOUNCED TWICED, ROLLED OUT LONG, HIT A RUNWAY END LIGHT, AND STOPPED IN THE OVERRUN.  SUBSEQUENT TO THE INCIDENT, THE PILOT INITIATED A PROGRAM TO ENSURE HIS FUTURE SAFETY AND COMPLIANCE WITH THE FEDERAL AVIATION REGULATIONS: HE COOPERATED FULLY WITH THE SJC FSDO IN THE INVESTIGATION. HE TOOK REFRESHER FLIGHT TRAINING ON 3-9-99 AND 3-15-99, WITH EMPHASIS ON RADIO PROCEDURES, TRAFFIC PATTERNS, LANDINGS, AND    GO-AROUNDS. HE VISITED THE RHV TOWER AND PARTICIPATED IN CONTINUING WINGS PROGRAM. ^PRIVACY DATA OMITTED^

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.