CHI98LA310 · Piper PA-25-235
Piper PA-25-235 · Accident: hard landing
Event
- NTSB case
- CHI98LA310
- 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-25-235
- Aircraft type
- Piper PA-25
- 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
- N75HM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 · flare/touchdown
- 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
- Hard landing
- 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 › Elevator, inadvertent use
- Dual student › Flare, inadequate
- Dual student › Proper descent rate, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student reported that he was told to release the control stick when it was yanked upon by the instructor. During the student's fourth landing, the aircraft bounced and the instructor yanked the stick. The student reported that he released the stick and the instructor took control of the airplane. It was also stated by the student that when the instructor took the stick, the instructor said, give me the stick. The instructor applied full power after the bounce and continued 2/3 down the runway a little nose high. The student also observed the airspeed to be 50 KIAS. The nose pitched upwards and the airplane stalled. The right wing dropped and the nose impacted the ground. The instructor reported that the student bounced the landing and applied full aft control. The instructor called out, 'my controls', but the stick remained in the full aft position. The instructor attempted to fly the aircraft with throttle and rudder. Inspection of the elevator control system found no anomalies.
Probable cause
Control interference between the pilot-in-command and the student. An excessive descent rate and inadequate flare by the student during landing are contributing factors. The inadequate supervision by the pilot-in-command is an additional factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA310
- Event ID
- 20001211X10538
- Case number
- CHI98LA310
- 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: 6ddfe55dd17743a59574087e0e74114ea4a98b3808582b1fbbebf037f70b5f92; retrieved 2026-09-22T17:27:04.979Z.