NYC02LA016 · Piper PA-28-160
Piper PA-28-160 · Accident: loss of control on ground/water during landing
From Upshur County Regional Airport (W22) to John Glenn Columbus International Airport (CMH)
Event
- NTSB case
- NYC02LA016
- 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-28-160
- Aircraft type
- Piper PA-28
- 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
- N5725W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Upshur County Regional Airport (W22), Buckhannon, WVTo John Glenn Columbus International Airport (CMH), Columbus, OH
- 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
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After two unsuccessful attempts to land on runway 29, due to crosswind conditions, the student pilot attempted a third landing. The airplane touched down about 400-600 feet beyond the runway threshold, and departed the right side of the runway onto the grass. The student pilot applied full power and attempted to abort the landing; however, when he raised the nose of the airplane, the stall warning horn sounded. The student pilot realized that he would not be able to climb over an embankment and aborted the takeoff. The airplane continued into the embankment, sheared off the nose gear, and came to rest upright. The pilot estimated the wind from 270 degrees at 20 knots, gusts to 25 knots.
Probable cause
The student pilot's failure to maintain directional control while landing. A factor related to the accident were the gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA016
- Event ID
- 20011025X02144
- Case number
- NYC02LA016
- 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: 36416e8d62375d3b544a24914a1ad16c3ea4cc4c9fe3ace917d6b9c472900f73; retrieved 2026-09-22T11:30:38.568Z.