DEN93LA055 · Piper PA-30
Piper PA-30 · Accident: loss of control on ground/water during landing
From 01V · Aurora, CO to FTG
Event
- NTSB case
- DEN93LA055
- 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-30
- Aircraft type
- Piper PA-30
- 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
- N7198Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 01V · Aurora, COTo FTG
- 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 · landing roll
- 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 on ground/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Dual student › Proper alignment, not maintained
- Dual student › Remedial action, inadequate
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE INSTRUCTOR PILOT SAID THE AIRPLANE TOUCHED DOWN 3 TO 5 DEGREES NOSE RIGHT OF THE RUNWAY CENTERLINE, AND HE TOLD THE INSTRUCTOR TRAINEE TO APPLY LEFT RUDDER. THE RUDDER PEDAL DID NOT MOVE. THE INSTRUCTOR PILOT ALSO APPLIED LEFT RUDDER AND GOT THE SAME RESULT. AS THE AIRPLANE STARTED TO GO OFF THE SIDE OF THE RUNWAY, THE INSTRUCTOR PILOT APPLIED FULL POWER. THE AIRPLANE BECAME AIRBORNE FOR APPROXIMATELY 1,000 FT, THEN BEGAN TO STALL AND ROLL. TO AVOID STRIKING THE GROUND IN A BANKED ATTITUDE, THE INSTRUCTOR PILOT RETARDED THE THROTTLES AND LEVELLED THE WINGS. THE RIGHT WING STRUCK THE AIRPORT'S SEGMENTED CIRCLE, SPUN TO THE RIGHT, AND SKIDDED TO A HALT. POST ACCIDENT EXAMINATION OF THE RUDDER CONTROL SYSTEM DID NOT DISCLOSE ANY MALFUNCTION OR FAILURE.
Probable cause
THE STUDENT'S FAILURE TO MAINTAIN PROPER TOUCHDOWN ALIGNMENT, AND THE INSTRUCTOR PILOT'S INADEQUATE SUPERVISION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN93LA055
- Event ID
- 20001211X12373
- Case number
- DEN93LA055
- 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: 52531732efd2684f61c89b7963e606f33b1ad4f24889352afaadaf768cb148e2; retrieved 2026-09-23T02:07:00.506Z.