FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09CA030 · Piper PA-38-112

31 Oct 2008 · Friant, CA, United States

Golden Eagle Enterprises Piper PA-38-112 · Accident: collision with terrain/object (non-CFIT) while maneuvering

From Fresno Yosemite International Airport (FAT) to Fresno Yosemite International Airport (FAT)

Report a problem

Event

NTSB case
WPR09CA030
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

Piper PA-38-112

Aircraft type
Piper PA-38
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
N2346G
Onboard fatalities
Unknown
Route
From Fresno Yosemite International Airport (FAT), Fresno, CATo Fresno Yosemite International Airport (FAT), Fresno, CA
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 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
Maneuvering · low-altitude flying
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
Collision with terrain/object (non-CFIT)
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

  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The purpose of the dual instructional flight was for the student pilot to practice simulated engine failures under the direction of his certified flight instructor (CFI). After completing three simulated engine failures without mishap, and the student setup for a fourth attempt. The airplane descended to about 100 feet above ground level (agl) and the student configured the airplane for a go-around by adding power and pitching the nose upward. Several seconds later the airplane collided with terrain. The CFI stated that accident could have been prevented if the go-around was initiated at a higher altitude. The CFI further added that there were no preimpact mechanical malfunctions or failures with the airframe or engine.

Probable cause

The student pilot's failure to execute a go-around in timely manner, which resulted in a collision with terrain. Also causal was the instructor's inadequate supervision of the flight and delayed remedial actions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09CA030
Event ID
20081103X25921
Case number
WPR09CA030
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: c35c2439b1d438fe9855facec1b3f83e8a99e15bd73591180fd96c7b79f987d4; retrieved 2026-09-15T10:31:13.072Z.