FTW94LA145 · Grumman G-164A
Grumman G-164A · Accident: partial loss of engine power (mechanical failure) during initial climb
Event
- NTSB case
- FTW94LA145
- 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 G-164A
- 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
- N9682
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Partial loss of engine power (mechanical 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
- Destroyed
Cause areas
- Ignition system, magneto › Arcing
- Ignition system, magneto › Deteriorated
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A LOSS OF ENGINE POWER WAS EXPERIENCED DURING INITIAL TAKEOFF CLIMB. DURING THE EMERGENCY DESCENT THE AIRPLANE STRUCK POWER LINES, AND DESCENDED OUT OF CONTROL. THE AIRPLANE CAME TO REST INVERTED, AND WAS DESTROYED BY A POST IMPACT FIRE. AN EXAMINATION OF THE ENGINE REVEALED NO MECHANICAL FAILURES THAT COULD HAVE CAUSED THE LOSS OF POWER; HOWEVER, TESTING OF THE MAGNETOS REVEALED THAT ONE WAS WEAK AND THE OTHER WAS ARCING INSIDE ITS CASE.
Probable cause
THE PARTIAL LOSS OF ENGINE POWER DUE TO ONE MAGNETO BEING WEAK AND THE OTHER MAGNETO ARCING INSIDE ITS CASE. A FACTOR WAS THE LACK OF SUITABLE TERRAIN FOR THE FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW94LA145
- Event ID
- 20001206X01279
- Case number
- FTW94LA145
- 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: 636a3e55507ca6ae554814c9d12b245d778d915d0b709fd6184a84ef9fcd9fc1; retrieved 2026-09-21T13:57:58.647Z.