NYC94LA105 · Piper PA-32R-300
Piper PA-32R-300 · Accident: loss of control on ground/water during landing
From John Glenn Columbus International Airport (CMH) to Whalen Heliport (OH30)
Event
- NTSB case
- NYC94LA105
- 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-32R-300
- Aircraft type
- Piper PA-32
- 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
- N5716F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From John Glenn Columbus International Airport (CMH), Columbus, OHTo Whalen Heliport (OH30)
- 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
- 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 › Aircraft handling, inadequate
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WROTE IN HIS STATEMENT THAT AFTER TOUCHDOWN THE LEFT LANDING GEAR 'FELT FUNNY,' AND THE AIRPLANE PULLED TO THE LEFT. THE PILOT APPLIED FULL POWER, AND THE AIRPLANE 'PULLED...TO THE RIGHT.' THE PILOT BROUGHT THE AIRPLANE TO A STOP BY REDUCING THE POWER, APPLYING THE BRAKES, AND RIGHT RUDDER. ACCORDING TO A WITNESS THE AIRPLANE, 'CAME IN, HOT,' AND TOUCHED DOWN BEFORE THE RUNWAY NUMBERS. THE LEFT WING 'DIPPED LEFT, 20-30 DEGREES,' THE PILOT ATTEMPTED TO ABORT THE LANDING BY ADDING POWER TO THE ENGINE. THE LEFT WING DIPPED AND STRUCK A SIGN NEAR THE RUNWAY, WHICH RESULTED IN THE WING SEPARATING, AND CAUSING THE AIRPLANE TO VEER OFF TO THE LEFT. TIRE MARKS SHOWED THAT THE AIRPLANE LANDED ON THE LEFT EDGE OF THE RUNWAY.
Probable cause
THE PILOT'S INADEQUATE CONTROL AND FAILURE TO MAINTAIN DIRECTIONAL CONTROL WHICH RESULTED IN COLLISION WITH A SIGN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC94LA105
- Event ID
- 20001206X01826
- Case number
- NYC94LA105
- 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: 77e2c8840e9f8e884ac050d6fd2a99796f1d151d7e5f20730bdd5907d2f79ced; retrieved 2026-09-23T00:57:52.997Z.