NYC01LA228 · Piper PA-22-150
Piper PA-22-150 · Accident: nose over during landing
From Huntington Municipal Airport (HHG) to Valley Point Airport (WV29)
Event
- NTSB case
- NYC01LA228
- 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-22-150
- Aircraft type
- Piper PA-22
- 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
- N7630D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Huntington Municipal Airport (HHG), Huntington, INTo Valley Point Airport (WV29), VALLEY POINT, WV
- 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
- Nose over
- 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, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had just purchased the airplane and was in the process of ferrying it home when he elected to divert because of en route weather. The pilot maneuvered the airplane for a 4,201-foot long by 75-foot wide runway. The airplane touched down on the first 1/3 of the runway with full flaps and an indicated airspeed of approximately 70 to 80 mph. The pilot retarded the throttle to idle, and applied the brakes, which caused the airplane to pull from side to side. Fearing that he would not be able to stop the airplane before reaching the end of the runway, he elected to drive it onto a grassy area to the right After departing the runway, the nose wheel struck a culvert, and the airplane nosed over. It was the pilot's first landing in the accident airplane. It was also his first landing in the accident airplane make and model. Winds in the area were approximately 5 knots, from 80 degrees to the left of the runway. After the accident, a mechanic applied the handbrake and then tried to push the airplane. The airplane did not move.
Probable cause
The pilot's failure to stop the airplane within the available runway. Factors included the uneven braking and the pilot's lack of experience in airplane make and model.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA228
- Event ID
- 20011010X02064
- Case number
- NYC01LA228
- 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: 46a5ca237d084f21acaf5fb0b10e70b0a9a72ad21175f7c26ab47c1d30ddd0a8; retrieved 2026-09-22T11:33:52.327Z.