# Accident 20050120001039A: Cessna 172F, Sallisaw, OK, January 20, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 20, 2005, 13:40 local time
- Place: Sallisaw, OK
- Airport: Sallisaw Municipal Airport
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 35.4381° N, 94.8028° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.4381&lon=-94.8028&mi=10
- Aircraft: N8203U, a cancelled registration (https://openairdocs.org/deregistered/N8203U-2018-01-29) (OpenAirDocs)
- Registry model: Cessna 172F (registry code 2072414, https://openairdocs.org/model/cessna-172f) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172F
- Reported engine: CONT O300D
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 7,100 total, 1,750 in this make and model, 15 in the last 90 days
- NTSB investigation: [NTSB DFW05LA067](https://openairdocs.org/ntsb/DFW05LA067) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050120001039A

## Narrative

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

(-23) PILOT REPORTED AT APPROXIMATELY 10 MILES NORTHEAST OF SALLISAW, OK AT 3500 FT. ON A EASTERLY HEADING ENROUTE TO TAHLEQUAH, OK HE STARTED EXPERIENCING ENGINE TROUBLE. THE ENGINE STARTED RUNNING ROUGH, LIKE IT WAS DEVELOPING CARB ICE. PULLED ON CARB HEAT AND CHECKED FUEL SELECTOR, MIXTURE AND MAGS. THE AIRCRAFT CONTINUED TO RUN ROUGH AND THE AIRCRAFT WAS LOSING ALITUDE. AT APPROXIMATELY 3 MILES NORTHEAST OF SALLISAW, HE DECIDED TO TRY AND LAND IN A PASTURE. AFTER THE AIRCRAFT TOUCHED DOWN THE WINGS HIT SMALL TREES, PLUS THE PROP AND HORIZONTAL AND VERTICAL STABILIZER. AIRCRAFT DAMAGE: WINGS PUSHED BACK INTO FUSELAGE, BUCKLING SPAR, HORIZONTAL STABILIZER DAMAGED. FUSELAGE DAMAGED DUE TO WINGS BEING PUSHED BACK INTO FUSELAGE.

## 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 DFW05LA067](https://openairdocs.org/ntsb/DFW05LA067), Jan 20, 2005: Cessna 172F (N8203U), Sallisaw, OK, substantial damage. Probable cause: A loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.

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.