ERA17LA125 · Grob Aircraft AG G120TP-A
Cae USA Grob Aircraft AG G120TP-A · Accident: loss of engine power (total) on approach
From Dothan Regional Airport (DHN) to Abbeville Municipal Airport (0J0)
Event
- NTSB case
- ERA17LA125
- 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
Grob Aircraft AG G120TP-A
- Aircraft type
- Grob G120
- 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
- N196TP
- Operator
- Cae USA
- Onboard fatalities
- Unknown
- Route
- From Dothan Regional Airport (DHN), Dothan, ALTo Abbeville Municipal Airport (0J0), Abbeville, AL
- Aircraft age
- About 1 year (built 2016)
- 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
- Approach · VFR pattern base
- Defining eventThe 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 (total)
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff on a local instructional flight, the turboprop engine’s continuous ignition switch was turned off, where it likely remained for the remainder of the flight. The pilot, who was receiving instruction, performed flight maneuvers, after which the instructor took control of the airplane to demonstrate a simulated loss of engine power procedure. The procedure was initiated with the crew alerting system (CAS) circuit breaker pulled, per the operator’s checklist, and the continuous ignition switch remained off, which was contrary to the recently amended procedure specified in the airplane’s flight manual. As part of the procedure, while flying with the power lever at flight idle at 3,350 ft pressure altitude and about 1.8 nautical miles from the intended runway, the flight instructor slowly moved the condition/propeller rpm lever aft to the “low” gate detent. One second later, the engine indications began to decrease, consistent with an engine flameout. Although visual annunciations of an engine flameout would have been available to differing degrees on the flight displays, no aural annunciations occurred because CAS circuit breaker had been pulled. The instructor continued the maneuver, unaware of the loss of power, and extended the landing gear on the downwind leg of the airport traffic pattern. While on the base leg of the traffic pattern, about 2.5 minutes after the engine flamed out, the instructor recognized the situation, turned toward the runway, and immediately called for an engine restart; at this time, the airplane was less than 100 ft above the ground. The pilot attempted to restart the engine, and the engine began to restart, but about 3 seconds later, the airplane impacted trees and the ground. The engine was placed in the manufacturer’s test cell and found to operate with minor discrepancies noted. The fuel control unit (FCU) was operationally tested at the manufacturer’s facility and was found to provide a flow of 20.4 pounds-per-hour (PPH); the specification was 28.0 to 30.0 PPH. The low setting occurred at manufacturing and was attributed to a flow bench indication error. The manufacturer had experienced engine flame-out issues during production acceptance flight testing. These instances were initially attributed to either rapid movement of the condition lever or the placement of the continuous ignition switch in the off position. To address the issue, the flight manual procedures for simulated forced landing events were updated to address these scenarios. Eight subsequent engine flame-out events were eventually attributed to be from a mis-set minimum flow test point of the FCU at manufacturing, the same condition as the accident FCU. The FCU manufacturer identified 124 units that were possibly mis-set, and service bulletins were published by the FCU and engine manufacturers to address the low fuel flow of the suspect units.
Probable cause
The flame-out of the engine due to a mis-set fuel control unit at the time of manufacture. Contributing to the accident was the pilots’ delayed recognition that the engine had flamed out, partially due to the operator’s requirement to disable the crew awareness system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA125
- Event ID
- 20170308X94158
- Case number
- ERA17LA125
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: f9896137f11dd676ec6e315a327b18f75cd80b47deef1c3c21a0db0e475f02ac; retrieved 2026-09-16T05:05:04.409Z.