19981112034869A

Accident · Substantial damage

FAA accident report · Piper PA-28-150 · Gila Bend, AZ · November 12, 1998

Date
November 12, 1998 · 13:00 local
Place
Gila Bend, AZ
Phase of flight
Fcd/Prec Ldg From Cruise
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N991PK
NTSB investigation
NTSBLAX99LA029
Reported as
Piper PA28150
Reported engine
Lycoming O320E2A
People aboard
1
Fatal injuries
0
Pilot’s flight hours
305 total9 in this make and model1 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.

On November 12, 1998, at 1300 hours mountain standard time, a Piper PA-28-150, N991PK, experienced a loss of engine power, made a forced landing, and struck a sign on the landing rollout on interstate 8 near Gila Bend, Arizona. The aircraft sustained substantial damage and the private pilot was not injured. Visual meteorological conditions existed for the personal flight that departed montgomery field, san diego, California, at 1000 pacific standard time. The flight was scheduled to terminate at the sky harbor airport, phoenix, Arizona. In an interview with the safety board, the pilot reported that no mechanical anomalies existed prior to the loss of engine power. He stated that all instruments were in the "green" and that the engine was running smoothly. The engine then began to sputter and was still running, but it was not developing any power. The pilot contacted albuquerque center and declared an emergency. He stated that the landing was normal, but on the landing rollout he struck a road sign that he had not seen. The aircraft turned 45 degrees and came to rest after sliding on gravel (.4)the pilot said that no engine discrepancies were noted during either the preflight or the initial cruise portion of the flight, and that all engine instrument readings were normal. Between 500 and 1,100 mean sea level, the engine suffered a significant loss of power accompanied by sputtering, vibration, and the RPM fluctuating. He declared an emergency, performed the emergency checklist with no changes, and made a forced landing on a road. During the landing rollout the airplane struck a road sign that he had not seen. Postaccident inspection of the engine revealed the gear at the back of the crankshaft was detached and moving freely between the corresponding gears. The crankshaft gear attaching bolt and threads were undamaged and the bolt appeared to have backed out of the crankshaft and was resting in the crankshaft gear bore. The bolt locking plate remained at the head of the bolt, and exhibited fretting signatures. Fretting signatures were also located around the mating surfaces of the gear and crankshaft bore. The crankshaft gear dowel pin had failed, with fatigue striations visible to the naked eye. An engine overhaul was completed 1 month after an airworthiness dirctive (AD) was published requiring inspection of the crankshaft gear and the bolt to prevent the bolt from backing out and liberating the crankshaft gear. No evidence of compliance with this AD was found in the engine maintenance records.

As the FAA filed it

ON NOVEMBER 12, 1998, AT 1300 HOURS MOUNTAIN STANDARD TIME, A PIPER PA-28-150, N991PK, EXPERIENCED A LOSS OF ENGINE POWER, MADE A FORCED LANDING, AND STRUCK A SIGN ON THE LANDING ROLLOUT ON INTERSTATE 8 NEAR GILA BEND, ARIZONA.THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE AND THE PRIVATE PILOT WAS NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS EXISTED FOR THE PERSONAL FLIGHT THAT DEPARTED MONTGOMERY FIELD, SAN DIEGO, CALIFORNIA, AT 1000 PACIFIC STANDARD TIME. THE FLIGHT WAS SCHEDULED TO TERMINATE AT THE SKY HARBOR AIRPORT, PHOENIX, ARIZONA.IN AN INTERVIEW WITH THE SAFETY BOARD, THE PILOT REPORTED THAT NO MECHANICAL ANOMALIES EXISTED PRIOR TO THE LOSS OF ENGINE POWER. HE STATED THAT ALL INSTRUMENTS WERE IN THE "GREEN" AND THAT THE ENGINE WAS RUNNING SMOOTHLY.THE ENGINE THEN BEGAN TO SPUTTER AND WAS STILL RUNNING, BUT IT WAS NOT DEVELOPING ANY POWER. THE PILOT CONTACTED ALBUQUERQUE CENTER AND DECLARED AN EMERGENCY. HE STATED THAT THE LANDING WAS NORMAL, BUT ON THE LANDING ROLLOUT HE STRUCK A ROAD SIGN THAT HE HAD NOT SEEN. THE AIRCRAFT TURNED 45 DEGREES AND CAME TO REST AFTER SLIDING ON GRAVEL (.4)THE PILOT SAID THAT NO ENGINE DISCREPANCIES WERE NOTED DURING EITHER THE PREFLIGHT OR THE INITIAL CRUISE PORTION OF THE FLIGHT, AND THAT ALL ENGINE INSTRUMENT READINGS WERE NORMAL. BETWEEN 500 AND 1,100 MEAN SEA LEVEL, THE ENGINE SUFFERED A SIGNIFICANT LOSS OF POWER ACCOMPANIED BY SPUTTERING, VIBRATION, AND THE RPM FLUCTUATING. HE DECLARED AN EMERGENCY, PERFORMED THE EMERGENCY CHECKLIST WITH NO CHANGES, AND MADE A FORCED LANDING ON A ROAD. DURING THE LANDING ROLLOUT THE AIRPLANE STRUCK A ROAD SIGN THAT HE HAD NOT SEEN. POSTACCIDENT INSPECTION OF THE ENGINE REVEALED THE GEAR AT THE BACK OF THE CRANKSHAFT WAS DETACHED AND MOVING FREELY BETWEEN THE CORRESPONDING GEARS. THE CRANKSHAFT GEAR ATTACHING BOLT AND THREADS WERE UNDAMAGED AND THE BOLT APPEARED TO HAVE BACKED OUT OF THE CRANKSHAFT AND WAS RESTING IN THE CRANKSHAFT GEAR BORE. THE BOLT LOCKING PLATE REMAINED AT THE HEAD OF THE BOLT, AND EXHIBITED FRETTING SIGNATURES. FRETTING SIGNATURES WERE ALSO LOCATED AROUND THE MATING SURFACES OF THE GEAR AND CRANKSHAFT BORE. THE CRANKSHAFT GEAR DOWEL PIN HAD FAILED, WITH FATIGUE STRIATIONS VISIBLE TO THE NAKED EYE. AN ENGINE OVERHAUL WAS COMPLETED 1 MONTH AFTER AN AIRWORTHINESS DIRCTIVE (AD) WAS PUBLISHED REQUIRING INSPECTION OF THE CRANKSHAFT GEAR AND THE BOLT TO PREVENT THE BOLT FROM BACKING OUT AND LIBERATING THE CRANKSHAFT GEAR. NO EVIDENCE OF COMPLIANCE WITH THIS AD WAS FOUND IN THE ENGINE MAINTENANCE RECORDS.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N991PK · 1

Matched to the same aircraft by N-number and date.