20100801039779A

Accident · Destroyed

FAA accident report · Cessna 172P · Santa Fe, NM · August 1, 2010

Date
August 1, 2010 · 10:10 local
Place
Santa Fe, NM
Airport
Santa Fe Municipal
Phase of flight
Takeoff: Climb Out
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N52708
NTSB investigation
NTSBCEN10LA449
Reported as
Cessna 172P
Reported engine
Lycoming 0-320
People aboard
2
Fatal injuries
0
Other injuries
2
Pilot’s certificate
Private pilot
Pilot’s flight hours
65 total65 in this make and model5 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 8/01/2010 aircraft departed saf enroute to aeg. Shortly after take off, the pilot reported the engine oil pressure guage dropped to zero, then noticed the engine was running very rough. He attempted to return to the airport but noticed smoke coming from the engine compartment and a second later the engine siezed. The pilot attempted an emergency landing four miles sw of the airport on a mesa in rocky terrain. The aircraft touched down and hit the rocks and then caught fire & burned. The investigation revealed the engine oil cooler and oil filter had been replaced the day before but the impact and fire damage to the aircraft was too severe to reveal if either of these components were improperly installed. On 08/03/10, the saf airport manager called to report that on the day of the accident, he noticed a pool of oil on the runway the aircraft departed from but could not confirm the oil had come from the accident aircraft. Due to the extent of damage the fire caused to the engine it could not be determined where or if there was a loose line or missing oil fitting or other component that may have failed. The investigator in charge from the NTSB is doing further review to determine if an engine teardown is necessary. If the investigation continues and a teardown is performed, an FAA inspector will be involved and if another probable cause is determined, an amemded report will be filed.

As the FAA filed it

ON 8/01/2010 AIRCRAFT DEPARTED SAF ENROUTE TO AEG. SHORTLY AFTER TAKE OFF, THE PILOT REPORTED THE ENGINE OIL PRESSURE GUAGE DROPPED TO ZERO, THEN NOTICED THE ENGINE WAS RUNNING VERY ROUGH. HE ATTEMPTED TO RETURN TO THE AIRPORT BUT NOTICED SMOKE COMING FROM THE ENGINE COMPARTMENT AND A SECOND LATER THE ENGINE SIEZED. THE PILOT ATTEMPTED AN EMERGENCY LANDING FOUR MILES SW OF THE AIRPORT ON A MESA IN ROCKY TERRAIN. THE AIRCRAFT TOUCHED DOWN AND HIT THE ROCKS AND THEN CAUGHT FIRE & BURNED. THE INVESTIGATION REVEALED THE ENGINE OIL COOLER AND OIL FILTER HAD BEEN REPLACED THE DAY BEFORE BUT THE IMPACT AND FIRE DAMAGE TO THE AIRCRAFT WAS TOO SEVERE TO REVEAL IF EITHER OF THESE COMPONENTS WERE IMPROPERLY INSTALLED. ON 08/03/10, THE SAF AIRPORT MANAGER CALLED TO REPORT THAT ON THE DAY OF THE ACCIDENT, HE NOTICED A POOL OF OIL ON THE RUNWAY THE AIRCRAFT DEPARTED FROM BUT COULD NOT CONFIRM THE OIL HAD COME FROM THE ACCIDENT AIRCRAFT. DUE TO THE EXTENT OF DAMAGE THE FIRE CAUSED TO THE ENGINE IT COULD NOT BE DETERMINED WHERE OR IF THERE WAS A LOOSE LINE OR MISSING OIL FITTING OR OTHER COMPONENT THAT MAY HAVE FAILED. THE INVESTIGATOR IN CHARGE FROM THE NTSB IS DOING FURTHER REVIEW TO DETERMINE IF AN ENGINE TEARDOWN IS NECESSARY. IF THE INVESTIGATION CONTINUES AND A TEARDOWN IS PERFORMED, AN FAA INSPECTOR WILL BE INVOLVED AND IF ANOTHER PROBABLE CAUSE IS DETERMINED, AN AMEMDED REPORT WILL BE FILED.

NTSB investigation

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