CHI98LA364 · Piper PA-34-220T
Piper PA-34-220T · Accident: loss of control in flight during landing
From Battle Creek Executive Airport at Kellogg Field (BTL) to Mariposa Yosemite Airport (RMY)
Event
- NTSB case
- CHI98LA364
- 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
Piper PA-34-220T
- Aircraft type
- Piper PA-34
- 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
- N9267W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Battle Creek Executive Airport at Kellogg Field (BTL), Battle Creek, MITo Mariposa Yosemite Airport (RMY)
- 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
- Landing · aborted
- 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
- Loss of control in flight
- 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
- Dual student › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a simulated engine out landing, the student initiated an aborted landing. The airplane yawed and rolled right. The instructor pilot took control of the airplane; however, was unable to establish a climb and the airplane impacted the terrain. The instructor's written statement indicated no previous experience in giving dual instruction in multi-engine airplanes. An inspection of the airplane failed to reveal any pre-accident anomalies.
Probable cause
the pilot-in-command (CFI)'s inadequate supervision of the student, his not obtaining control of the airplane, and his lack of total experience in the type of operation. A factor was the dual student's not maintaining control of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA364
- Event ID
- 20001211X11032
- Case number
- CHI98LA364
- 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: 428d9f95883682220e816c8dbb6575a2be0a6a102c718a41f9c25f8af79d04ec; retrieved 2026-09-22T16:37:59.935Z.