CEN15LA377 · Grumman G 164B
Grumman G 164B · Accident: loss of engine power (partial) while maneuvering
From Sac City Municipal Airport (KSKI) to Sac City Municipal Airport (KSKI)
Event
- NTSB case
- CEN15LA377
- 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
- N311AL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sac City Municipal Airport (KSKI), Sac City Mun, IATo Sac City Municipal Airport (KSKI), Sac City Mun, IA
- Aircraft age
- About 38 years (built 1977)
- 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
- 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 (partial)
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport pilot reported that he changed the engine oil the night before the accident flight. The next day, he performed a normal engine run-up and then departed on the agricultural application flight. The airplane's tail lifted when the airplane reached 60 mph, and the airplane then accelerated to 80 mph. Shortly after getting airborne, the pilot felt that the airplane was not performing as it should be and that the engine power was decreasing. He advanced the engine controls full forward and selected a cornfield for the forced landing.
The pilot reported that he thought that the engine's blower/supercharger had failed because the engine did not stop but did seem to lose power. An engine examination was not performed; therefore, the reason for the loss of engine power could not be determined.
Probable cause
The loss of engine power for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15LA377
- Event ID
- 20150824X65055
- Case number
- CEN15LA377
- 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, 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: 4a7a5f4f4322fc54b5841ae5bcbd2e740d7aff158833e1c043c51d5977497ac5; retrieved 2026-09-16T02:42:36.777Z.