WPR15LA106 · Grumman Acft ENG COR-Schweizer G 164A
Grumman Acft ENG COR-Schweizer G 164A · Accident: loss of engine power (total) during an emergency descent
From Goering Ranches / Chocheta Estates Airport (50OR) to Goering Ranches / Chocheta Estates Airport (50OR)
Event
- NTSB case
- WPR15LA106
- 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 Acft ENG COR-Schweizer 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
- N4863
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Goering Ranches / Chocheta Estates Airport (50OR), Alfalfa, ORTo Goering Ranches / Chocheta Estates Airport (50OR), Alfalfa, OR
- Aircraft age
- About 43 years (built 1972)
- 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
- Emergency descent
- 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
- 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 commercial pilot/owner, an airframe and powerplant mechanic with inspection authorization privileges, performed an annual inspection on the airplane in order to return it to service after it had been in storage for about 2 years. Ground engine run-up checks revealed no discrepancies, and he decided to perform a test flight. After takeoff, the engine sputtered and lost power, and the pilot returned to the airport for a precautionary landing. The airplane overran the runway, struck a tire, and came to rest inverted.
A postaccident engine run revealed no mechanical discrepancies that would have precluded normal operation. The reason for the loss of engine power was not determined.
Probable cause
A total loss of engine power after takeoff for reasons that could not be determined, because examination of the engine did not reveal any mechanical anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15LA106
- Event ID
- 20150219X43846
- Case number
- WPR15LA106
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-02-18.
- API snapshot SHA-256: a6372c812e69ad6869637de98cf419af7f26e2dd490c80cab201465ec98d675a; retrieved 2026-09-16T02:05:48.582Z.