FTW00LA160 · Cessna 195
Cessna 195 · Accident: partial loss of engine power (mechanical failure) en route
From Bud Dryden Airport (TX05) to Scholes International At Galveston Airport (GLS)
Event
- NTSB case
- FTW00LA160
- 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 195
- Aircraft type
- Cessna 195
- 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
- N9876A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bud Dryden Airport (TX05), McKinney, TXTo Scholes International At Galveston Airport (GLS)
- 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
- Partial 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
- Ignition system, magneto › Failure
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, 20 minutes after departure, while in cruise flight, the airplane's engine began to 'run rough' and vibrate. He reduced power in attempts to dampen the vibration and initiated a precautionary landing to a nearby airport. As the airplane touched down the pilot noticed a dirt embankment, which was approximately 2 feet high, running along the runway centerline. Subsequently, the airplane contacted the embankment, exited the runway surface, struck a fence and trees, and came to a stop upright. A test run of the engine revealed that the engine would not run with the ignition switch in the LEFT position, and would run rough in the BOTH position. Examination of the left magneto revealed that the resistance was less than 16,000 ohms, failing to meet the manufacturer's specifications. Additionally, the number 3, 4, and 5 rear spark plugs exhibited oil and lead deposits.
Probable cause
The failure of the left magneto, which resulted in a partial loss of engine power. Factors were the fouled number 3, 4, and 5 rear spark plugs and the lack of suitable terrain for the precautionary landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA160
- Event ID
- 20001212X21004
- Case number
- FTW00LA160
- 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: 1ea64ec78d0dccca455e2dd5e5f5d194ff6c032d51dfd5c26607d62cae2e82d2; retrieved 2026-09-21T20:13:13.735Z.