DFW06LA188 · Cessna P210N
Cessna P210N · Accident: loss of engine power en route
From AMR · Amarillo, TX to Lubbock Preston Smith International Airport (LBB)
Event
- NTSB case
- DFW06LA188
- 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
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- 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 P210N
- Aircraft type
- Cessna 210
- 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
- N732TZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From AMR · Amarillo, TXTo Lubbock Preston Smith International Airport (LBB), Lubbock, 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, oil › Starvation
- Lubricating system, oil pressure pump › Failure, total
- Unknown › Maintenance, installation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Shortly after departure, the pilot of a single-engine airplane reported that he had experienced a loss of engine power and needed to proceed to the nearest airport. An air traffic controller provided a heading to the closest airport and provided landmarks to help assist the pilot locate the runway. The 1,440-hour private pilot was not able to find the airport and elected to land in a short field with a prevailing tailwind. During the landing roll, the airplane collided with several obstacles before the airplane caught on fire. Examination of the engine revealed that the crankcase was breached above the number 2 cylinder. The components of the crankshaft and the number 1, number 2, and number 3 connecting rod assemblies exhibited signatures of thermal distress consistent with a lack of lubrication. The engine driven oil pump was disassembled and examined. The examination revealed that the two bushings that support the oil driven-gear were not installed, and the driven gear had fractured at the spline-drive. Further examination found that the oil pump driven-gear support shaft in the oil pump housing exhibited full gear length wear, indicating that it had been operating without bushings. In addition, the interior wall of the oil pump that housed the driven-gear exhibited heavy scoring and displaced material, indicating binding of the gear. The oil filter element was removed and the pleats were individually examined. The pleats contained a minimal amount of metallic debris. A review of the aircraft maintenance logs revealed that the engine was last overhauled on July 20,1998; however, pertinent details of the repair were not included in the logs and were only referenced in work orders. The maintenance records revealed that the engine was sent back to the overhauling facility on March 11, 2000, approximately 459.4 hours after the overhaul, due to a reported propeller strike. The Safety Board contacted the overhauling facility and requested a copy of the work orders for both repairs; however, a company official reported that they only retain records for two years as required by Federal Aviation Regulation 145.219 (c). Further review of the engine logbook revealed there were no entries that indicated that the oil pump had ever been removed or replaced after the overhaul was completed. As a result, it could not be determined when/who had last disassembled/re-assembled the pump. The engine had accrued approximately 1,059.7 hours since it was overhauled at the time of the accident. At the time of the accident the winds were reported from 210 degrees at 12 knots.
Probable cause
The loss of engine power as result of the failure by maintenance personnel to install oil pump support bushings, which resulted in the fracture of the driven-gear and subsequent loss of oil pressure. Contributing factors were the lack of suitable terrain for the forced landing and the prevailing tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06LA188
- Event ID
- 20060724X00990
- Case number
- DFW06LA188
- 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, coordinates. 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: 78a1dfcac16ac243045db65cd7fa0edbe70e26af623af91a05a551a86bc21ced; retrieved 2026-09-20T17:09:07.435Z.