CEN25LA171 · Piper PA28 180
Piper PA28 180 · Accident: abnormal runway contact during landing
Event
- NTSB case
- CEN25LA171
- 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 PA28 180
- Aircraft type
- Piper PA28
- 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
- N7951W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 61 years (built 1964)
- 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
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the instructional flight, the airplane was landing to the runway with the student pilot operating the flight controls. Upon touchdown, the airplane “swerved hard to the left.” The flight instructor immediately announced, “my controls” and he attempted to maintain directional control. He reported the loss of directional control happened “so fast” and that he was unable to recover the airplane. After the accident, the student pilot reported that he “may have had his feet on the brakes” upon touchdown. The airplane sustained substantial damage to the engine mount, with a bend in a truss tube. The flight instructor reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The flight instructor further reported that in the future, he will be having new student pilots announce, “heels on the floor” during the landing flare, to prevent inadvertent brake application.
Probable cause
The student pilot’s inadvertent brake application during the touchdown, that resulted in abnormal runway contact and a loss of directional control. Contributing to the accident was the flight instructor’s inadequate supervision of the student pilot during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA171
- Event ID
- 20250506200113
- Case number
- CEN25LA171
- 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, cause areas. 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: 270dc3e2d80f86ba556e9858b4981a64f7d7febcf21cfb90cd22843f18807231; retrieved 2026-09-16T19:52:03.593Z.