ATL99LA133 · Grumman-Schweizer G-164B
Grumman-Schweizer G-164B · Accident: loss of engine power on approach
From Yedinka Airport (EDN) to an unrecorded destination
Event
- NTSB case
- ATL99LA133
- 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
Grumman-Schweizer G-164B
- 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
- N6736Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yedinka Airport (EDN)To 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
- Approach · VFR pattern final
- 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
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he departed Enterprise Airport with a full load of chemicals for aerial application to a nearby cotton field. Shortly after takeoff, the engine began to surge. He adjusted the propeller lever control to the 'high' position and turned the fuel boost pump 'on.' He elected to return to the airport and while on short final he observed another airplane pass beneath him. His airplane, although surging, had been producing sufficient power therefore, he executed a left 360 degree turn for spacing. When the turn was nearly complete, the engine lost all power and he maneuvered for an open field. The airplane collided with a tree and then the ground. Examination of the wreckage revealed that the wings, empennage, and fuselage were destroyed almost beyond recognition. The only recognizable portion of the engine was the power section and the entire turbine section was destroyed. A fuel sample of the Jet-A fuel used in the airplane showed no visible evidence of contamination. The airplane and engine were consumed by fire.
Probable cause
The loss of engine power for undetermined reasons. Contributing to the severity of the accident was the in-flight collision with a tree during the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA133
- Event ID
- 20001212X19697
- Case number
- ATL99LA133
- 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: 07b3905f67e1b9461b5ea16c26ea50cd19375489d547ef7edfcf12f3b36558cd; retrieved 2026-09-21T20:23:17.191Z.