Piper PA-34-200T accident near Huntington, West Virginia, January 30, 2009
On January 30, 2009 at about 6:31 pm local time, a Piper PA-34-200T, registered N8047C, was destroyed in an accident during maneuvering (low-alt flying) near Huntington, West Virginia (Huntington Tri-State Airport). It was a personal flight under general aviation rules (Part 91). 6 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
(1) The pilot’s failure to perform adequate preflight planning and to use available in flight resources in a timely manner and (2) his decision to continue visual-flight-rules flight in instrument meteorological conditions despite his lack of an instrument rating and proficiency in instrument flying, which resulted in spatial disorientation and impact with terrain.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 30, 2009 · about 6:31 pm local time · cases in 2009
- Place
- Huntington, West Virginia · Huntington Tri-State Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 6 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA-34-200T · all PA-34-200Ts on the register
- Registration
- N8047C · no longer on the register · serial 34-7670112
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The non-instrument-rated pilot departed Lake in the Hills Airport (3CK), Lake in the Hills, Illinois, on a cross-country trip to Raleigh-Durham International Airport (RDU), Raleigh Durham, North Carolina, in the accident airplane without filing a flight plan; therefore, the planned and most of the actual flight routes could not be determined. Further, no record was found that the pilot obtained a weather briefing before the flight. In addition, postaccident weight and balance calculations indicated that, when the airplane took off, it exceeded the allowable weight and center of gravity limits. Another pilot at the airport advised the accident pilot to file a flight plan, recalculate the weight and balance, and obtain a weather briefing; however, no evidence indicates that the pilot did so. Although visual meteorological conditions were recorded at RDU for the expected time of arrival, snow was forecast and instrument meteorological conditions (IMC) were observed for en route areas between 3CK and RDU for the time before, during, and after the flight. The noninstrument rated pilot exercised poor judgment by attempting a visual flight rules cross country flight, over mountainous terrain, without getting adequate weather information for the flight route, especially in January when snowy conditions are likely. The accident occurred near Huntington Tri-State Airport (HTS), Huntington, West Virginia, which was about 350 nautical miles (nm) from 3CK and 10 nm southwest of the direct flight route between 3CK and RDU. Federal Aviation Administration (FAA) radar data first recorded the airplane about 1244 central standard time at an altitude of about 9,700 feet about 50 nm southwest of HTS and then showed the airplane turning northeast toward HTS. According to FAA air traffic control (ATC) transcripts, about 1305, the pilot transmitted a “mayday” call to the HTS ATC tower and then advised, “I’m flying VFR [visual flight rules], low on fuel, and need to land.” Subsequently, the local controller asked the pilot if he was capable of instrument flight, and the pilot responded, “yes,” even though he was not instrument rated. (The airplane was equipped for instrument flight, and no evidence indicated that an instrument malfunction occurred.) About 8 minutes later, the controller asked the pilot how much fuel was on board, and he answered, “not much.” For about 10 minutes, the controller attempted to vector the airplane to HTS. Although the pilot stated several times that he had visual ground contact, he was not able to maintain it, and he never acknowledged that he had the airport in sight. After about 12 minutes of providing detailed course headings and corrections to the pilot, the final approach controller was able to vector the airplane onto an extended final course for an airport surveillance radar approach to runway 30 at HTS. However, when the airplane was about 3 nm from the runway, it turned about 80 degrees off course to the left. The controller vectored the airplane back to the right, and the airplane turned so far to the right that it proceeded directly opposite the original inbound course. Additionally, the airplane descended below the minimum descent altitude, which the controller issued to the pilot, and which the pilot acknowledged, multiple times. Weather conditions recorded at HTS, which was about 4 nm northwest of the accident site, included an overcast ceiling at 1,000 feet and a visibility of 3/4 statute mile in snow. Witnesses at the airport and in the vicinity of the crash site described the snowfall at the time of the accident as “heavy” and estimated the visibility to be between 1/4 and 3/4 mile. The pilot did not request any in-flight weather assistance nor did he seek any ATC assistance before the situation had deteriorated. After the pilot contacted ATC, his communications became fragmented and intermittent, consistent with increased workload resulting from efforts to control the airplane in IMC. Although ATC attempted to guide the pilot to a landing at HTS using an airport radar surveillance approach, these efforts were not effective as evidenced by radar data showing that the pilot could not maintain assigned altitudes or headings, indicating that he was most likely experiencing spatial disorientation during the attempt to maneuver the airplane for landing. The spatial disorientation was likely caused by his operating in reduced visual conditions (clouds and falling snow), which obscured outside references, and his inability to consistently use the airplane’s instruments to positively maneuver the airplane when this occurred.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- VFR encounter with IMC during maneuvering (low-alt flying) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Planning/preparation › Weather planning › Pilot
- cause Personnel issues › Task performance › (general) › (general) › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Snow › Not specified
- Personnel issues › Psychological › Perception/orientation/illusio › Spatial disorientation › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: private
- Ratings: multi-engine land; rotorcraft: glider
- Flight time: 2,200 hours in all
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 4,570 lb
- Seats: 6
- Landing gear: retractable
- Engine 1: Cont Motor TSIO-360 SER (piston); 0 hours total
- Engine 2: Cont Motor LTSIO-360 SER (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: 3CK Lake In Hills IL at 3:00 pm
- Destination: RDU Raliegh-Durham NC
- Flight plan: none
- Runway 30, 6,517 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 290° at 3 knots
- Visibility: 1 statute miles
- Sky: overcast at 1,000 ft
- Temperature: 27°F (-3°C), dew point 25°F (-4°C)
- Altimeter: 30.05 inHg
- Observation at 6:48 pm from HTS, 4 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 5 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
24 documents, released by the NTSB on January 4, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N8047C: not on the register today · the record of its deregistration
- Piper PA-34 Seneca 997 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Cont Motor TSIO-360 SER 1,907 aircraft carry this series today · as the NTSB recorded it
- Engine: Cont Motor LTSIO-360 SER 4 aircraft carry this series today · as the NTSB recorded it
- Tri-State/Milton J Ferguson Field · nearest airport
- Lake IN The Hills Airport · departed from
- Raleigh-Durham International · bound for
- Accidents and incidents in West Virginia 424 since 1982 · 54 in the last ten years
- West Virginia 885 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA09FA145.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
