IAD01LA029 · Piper PA 46-350P
Piper PA 46-350P · Accident: forced landing during takeoff
From Ross County Airport (RZT) to KGX · FLEMING MASON, OH
Event
- NTSB case
- IAD01LA029
- 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
- Instrument Meteorological Cond
Piper PA 46-350P
- Aircraft type
- Piper PA-46
- 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
- N747RC
- Operator
- Jerry Richard Anderson
- Onboard fatalities
- Unknown
- Route
- From Ross County Airport (RZT), Chillicothe, OHTo KGX · FLEMING MASON, 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
- Takeoff · rejected takeoff
- 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
- Forced landing
- 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 › Ice/frost removal from aircraft, not performed
- Pilot in command › Preflight planning/preparation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
When the private pilot, co-pilot and passenger arrived at the airport it began to snow heavily. The airplane was pre-flighted, then towed out of the heated hangar and fueled. The private pilot taxied to the end of the 5,400 foot long runway, parked, and performed an engine run-up. After the run-up, the co-pilot reached the Elkins, West Virginia, AFSS on his cell phone, received a weather briefing, filed an IFR flight plan, and requested an IFR clearance. Since Elkins was not the primary AFSS for the area, the briefer placed him on hold to service his request. The call got disconnected, so he called the FSS back. Due to the long hold time, the co-pilot then called Indianapolis Center and received an IFR clearance. Once the clearance was obtained, the private pilot performed another engine run-up and noticed that about 3 to 4 inches of slush had accumulated on the runway, and about 1/2 to 3/4 inches of slush had accumulated along the surface of both wings. The pilots discussed if they should return to the hangar and wipe off the wings, but agreed that the slush would "blow-off" during the take-off roll. The private pilot estimated that he used about 4,500 feet of the runway before he obtained 80 knots (Vr). He rotated the airplane, but it did not lift normally. To avoid obstructions, the private pilot simultaneously turned the aircraft to the right, and retarded the throttle. The airplane touched down, slid, turned, and came to rest upright facing the runway. Examination of the airplane revealed that both wings were covered with snow, and localized areas of ice were found along the top surfaces of both wings near the trailing edge. The air intake and pitot tube were absent of debris. According to the airplane's pre-flight checklist, the wings and empennage surfaces should be clear of ice, snow, and frost prior to take-off. The pilot estimated that from the time the airplane was pulled from the hangar to the time of the accident was about 1-hour. The pilot also reported that there were no mechanical deficiencies.
Probable cause
pilot's improper pre-flight planning and failure to follow the published checklist procedures, which resulted in ice and snow not being removed from the wings prior to take-off.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD01LA029
- Event ID
- 20010201X00382
- Case number
- IAD01LA029
- 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: 175b811fb7935630699cffbc7b1785dfdafb463e20c230cc85084301f50cd54f; retrieved 2026-09-22T12:13:26.961Z.