DFW06CA050 · Cessna T210
Cessna T210 · Accident: total loss of engine power (mechanical failure) en route
From San Antonio International Airport (SAT) to Midland, TX
Event
- NTSB case
- DFW06CA050
- 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
- 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 T210
- 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
- N5279A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Antonio International Airport (SAT), San Antonio, TXTo Midland, 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, connecting rod › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While in cruise flight at an altitude of 6,500 feet, the 1,150-hour commercial pilot noticed a rise in engine oil temperature. The pilot opened the cowl flaps and increased the mixture control, which reduced the EGT and the CHT. Approximately 5 minutes later, the engine started "running rough and sparks appeared from the cowling with loud bangs." The pilot shut-down the engine and extended the landing gear for a forced landing on a road. The airplane was unable to make the road and during the night forced landing in a mesquite covered field, the airplane sustained structural damage. An examination of the engine revealed that several of the engine's connecting rods had failed and the number one piston was found to be eroded.
Probable cause
The loss of engine power due to a connecting rod failure. Contributing factors were the dark night conditions and the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA050
- Event ID
- 20060301X00258
- Case number
- DFW06CA050
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-01-05.
- API snapshot SHA-256: f498141e70fb7e42e0955670155e8a60d9d8e2f9dba74afb3226a0667b329ccb; retrieved 2026-09-22T05:10:21.267Z.