DFW05CA194 · Cessna 175A
Cessna 175A · Accident: airframe, component or system failure en route
From McKinney National Airport (TKI) to Yuma Municipal Airport (2V6)
Event
- NTSB case
- DFW05CA194
- 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 175A
- Aircraft type
- Cessna 175
- 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
- N6776E
- Operator
- Marvin D. Fletcher · private individual
- Onboard fatalities
- Unknown
- Route
- From McKinney National Airport (TKI), McKinney, TXTo Yuma Municipal Airport (2V6), Yuma, CO
- 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
- Airframe, component or system failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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
- Miscellaneous, seal/boot/gasket › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 306-hour pilot noticed that the oil pressure gauge indicated low and in the red operating range area while in cruise flight. The pilot elected to initiate a precautionary landing into a nearby open field. During the approach to the field, as the airplane descended closer to the ground, the pilot noted more obstructions. To avoid colliding with power lines, the pilot intentionally stalled the airplane at about 20 feet above the ground and landed hard, with power-on and full-flaps. Examination of the engine revealed that oil was leaking from a failed generator mounting gasket. No oil was observed on the dipstick for the engine crankcase.
Probable cause
The impending loss of engine power as result of the failure of the generator mounting gasket resulting in engine oil starvation. A contributing factor was the lack of suitable terrain for the precautionary landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA194
- Event ID
- 20050830X01327
- Case number
- DFW05CA194
- 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: 79e701d3479637929c0c64490f3e0158ca3740364f8988747ba0c8e9a2410dc0; retrieved 2026-09-22T05:35:24.479Z.