DFW05LA147 · Grumman G-164B
O'Brien Flying Service Grumman G-164B · Accident: airframe, component or system failure during initial climb
From O'Brien Flying Service Airport (LA71) to an unrecorded destination
Event
- NTSB case
- DFW05LA147
- 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
Grumman G-164B
- Aircraft type
- Grumman G-164
- 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
- N6832K
- Operator
- O'Brien Flying Service
- Onboard fatalities
- Unknown
- Route
- From O'Brien Flying Service Airport (LA71), Iowa, LATo not recorded
- 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 137: Agricultural
- 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
- Initial climb
- 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
- Wire, transmission
- 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
- Propeller system/accessories, governor › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Following takeoff and after initiating a left turn to return to the field being sprayed, the 19,000 hour pilot reduced propeller RPM and the 2-bladed propeller "went to the full coarse setting and lost drive." During the forced landing the airplane struck a power line and subsequently impacted terrain. Examination of the propeller governor by a repair facility revealed that the "propeller governor pilot valve had failed, causing an internal oil leak, which resulted in the failure of the propeller governor. "
Probable cause
The failure of the propeller governor which resulted in a forced landing. A contributing factor was the transmission wire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05LA147
- Event ID
- 20050615X00772
- Case number
- DFW05LA147
- 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: 01202361e66952eee54d3b97fc5e69164e5cf52c42a449a1d682b7abd4bc76da; retrieved 2026-09-22T05:50:03.420Z.