FTW96LA280 · Cessna 182N
Cessna 182N · Accident: total loss of engine power (mechanical failure) en route
From Tucson International Airport (TUS) to Rick Husband Amarillo International Airport (AMA)
Event
- NTSB case
- FTW96LA280
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 182N
- Aircraft type
- Cessna 182
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N9001G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tucson International Airport (TUS), TUSCON, AZTo Rick Husband Amarillo International Airport (AMA), Amarillo, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Engine assembly, piston › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that while cruising at 11,500 feet MSL over 10,000 foot terrain, he 'noticed the oil pressure gauge was reading 0.' Approximately 5 minutes later, the engine 'clanked and started to break apart internally.' Subsequently, a 'few minutes' after that, the engine seized. The pilot executed a forced landing between trees on a rocky ridge top. During the landing roll, the airplane hit a rock, nosed over and came to rest in an inverted position. Postcrash examination of the engine revealed extensive internal damage. Subsequently, the parts were sent to a metallurgical laboratory for analysis. It was determined that the number one piston had developed in-service fatigue cracks and subsequently disintegrated; which in turn caused the general failure of the engine.
Probable cause
The loss of engine power due to the fatigue failure of the number one piston. A factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA280
- Event ID
- 20001208X05996
- Case number
- FTW96LA280
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 39abe05aa40c89199b41a0e999c5aa6fe31dd4c0330273066980d0609849c8ff; retrieved 2026-09-22T22:04:16.594Z.