# Accident 20100801039779A: Cessna 172P, Santa Fe, NM, August 1, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 1, 2010, 10:10 local time
- Place: Santa Fe, NM
- Airport: Santa Fe Municipal
- Damage: Destroyed
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 35.6695° N, 105.9501° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.6695&lon=-105.9501&mi=10
- Aircraft: N52708, a cancelled registration (https://openairdocs.org/deregistered/N52708-2010-11-22) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYCOMING 0-320
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 2
- Pilot certificates: Private pilot
- Pilot flight hours: 65 total, 65 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB CEN10LA449](https://openairdocs.org/ntsb/CEN10LA449) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100801039779A

## Narrative

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

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.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN10LA449](https://openairdocs.org/ntsb/CEN10LA449), Aug 1, 2010: Cessna 172P (N52708), Santa Fe, NM, substantial damage. Probable cause: A total loss of engine power following a loss of oil pressure for undetermined reasons.

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.