DFW05CA177 · Grumman-Schweizer G-164C
Grumman-Schweizer G-164C · Accident: loss of engine power while maneuvering
From Gillett, AR to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DFW05CA177
- 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-Schweizer G-164C
- Aircraft type
- Grumman Schweizer 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
- N6626K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gillett, ARTo 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
- Maneuvering · aerial application
- 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
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial Possible conflict
Cause areas
- Fuel system, line fitting › Disconnected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 18,738-hour pilot reported that while applying an aerial application of fertilizer to a field, the engine lost power. The pilot initiated a forced landing to a nearby field. During the forced landing, the airplane impacted trees and came to rest upright. A post-impact fire comsumed most of the airframe. Examination of the sooted engine revealed that the discharge pressure line (P3) at the fuel control unit was disconnected. The threads at the "B" nut were also covered with soot.
Probable cause
The loss of engine power resulting from a disconnected discharge pressure line at the fuel control unit. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA177
- Event ID
- 20050804X01155
- Case number
- DFW05CA177
- 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: 2ce8279657b875ad48c9314c11e406a677fdb32177e2cc163ee1e9f8f89e8ab3; retrieved 2026-09-22T05:42:21.289Z.