19990103021799I

Incident · Minor damage

FAA incident report · Cessna 172M · San Jose, CA · January 3, 1999

Date
January 3, 1999 · 13:46 local
Place
San Jose, CA
Airport
Reid-Hillview Of Santa Clara
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N9668Q
Reported as
Cessna 172M
People aboard
1
Fatal injuries
0
Pilot’s flight hours
89 total10 in this make and model9 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-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

As the FAA filed it

(-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^