MIA07CA096 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of control on ground/water during landing
From Upshur County Regional Airport (W22) to Fairmont Municipal Airport Frankman Field (4G7)
Event
- NTSB case
- MIA07CA096
- 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-180
- 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
- N38730
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Upshur County Regional Airport (W22), Buckhannon, WVTo Fairmont Municipal Airport Frankman Field (4G7), Fairmont, 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
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he flew a stabilized approach and had a normal touchdown. After touchdown the airplane veered to the left, and he compensated with right rudder but got no response. As the airplane drifted to the left, he increased the right rudder inputs and also used right toe-brake but again got no response. Before exiting the runway he pulled the handbrake while applying hard right toe-brake. The aircraft did slow but didn't turn to the right. After exiting the runway the airplane overran the VASI light system and struck a row of runway lights. After which the airplane impacted an embankment and slid obliquely down the side of it. The airplane then impacted another embankment perpendicular to that one, shearing the nose-wheel, bending the prop and engine-cowl. The airplane then rolled to the left and the wing struck the ground, buckling the inboard side fuel tank bulkhead and partially shearing from the fuselage before it come to a stop. The pilot stated that the airplane's nosewheel steering and brakes performed normally prior to the accident flight. The responding FAA inspector stated that examination of the site indicated that the airplane touchdown point was 25 yards from the end of the runway and 8 yards left of the centerline, and angled directly towards the second VASI light installation. Following the tire tracks it appears that the underside of the left wing impacted the VASI light. The pilot stated to the FAA inspector that there were no mechanical difficulties with the aircraft.
Probable cause
The pilot's failure to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07CA096
- Event ID
- 20070828X01251
- Case number
- MIA07CA096
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-05-10.
- API snapshot SHA-256: 6edc74c36a8ee89511dde57f084ef897308bfc0ba0244149e083467016cc943a; retrieved 2026-09-22T03:50:17.294Z.