The U.S. aircraft register, updated daily
Accidents · NTSB ERA12FA433 · Final report

Piper PA-32R-300 accident near New Site, Mississippi, July 8, 2012

On July 8, 2012 at about 6:58 pm local time, a Piper PA-32R-300, registered N4386F, was substantially damaged in an accident during enroute (cruise) near New Site, Mississippi. It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's decision to operate into a known area of adverse weather, which resulted in the inadvertent penetration of a severe thunderstorm, a subsequent loss of control, and in-flight breakup of the airplane.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 8, 2012 · about 6:58 pm local time
Place
New Site, Mississippi · map
Type
Accident
Injuries
3 people were killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32R-300 · all PA-32R-300s on the register
Registration
N4386F · no longer on the register · serial 32R-7680446
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

Before departing on the accident flight, the pilot filed three instrument flight rules flight plans but had not requested nor received a weather briefing. A witness near the accident site reported a thunderstorm in the vicinity and observed the airplane enter a cloud followed shortly by a "loud pop." The witness then observed pieces of the airplane coming out of the cloud. The left wing and vertical stabilizer were located about 1,500 feet away from the main wreckage. Examination of the fracture surfaces revealed signatures consistent with tensile overload failure. No preimpact mechanical malfunctions were noted that would have precluded normal operation of the airplane. Review of radar and weather data indicated the presence of thunderstorms along the route of flight, as well as in the vicinity of the accident site, with the potential for some of them to be severe. The satellite datalink weather product in the airplane cockpit uploaded weather data every 5 minutes and likely would have shown a thunderstorm cell increasing in severity to the highest intensity level near the time of the in-flight breakup. According to Federal Aviation Administration publication “General Aviation Pilot’s Guide to Preflight Weather Planning, Weather Self-Briefings, and Weather Decision Making,” datalink weather products are not as accurate or current as onboard weather radar, which provide real-time weather radar images in the cockpit. It is likely that the pilot attempted to maneuver around the weather hazard and inadvertently encountered a thunderstorm cell, which resulted in an in-flight breakup of the airplane due to overstress of the structure.

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

  1. Windshear or thunderstorm during enroute (cruise) defining event
  2. Inflight upset during enroute (cruise)
  3. Loss of control in flight during enroute (cruise)
  4. Aircraft structural failure during enroute (cruise)
  5. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Decision related to condition
  • cause Aircraft › Aircraft structures › (general) › (general) › Capability exceeded
  • cause Personnel issues › Psychological › Personality/attitude › Confidence/reliance on equip › Pilot
  • Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Accuracy of related info
  • Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 452 hours in all; 98 in this make and model; 17 in the last 90 days; 9 in the last 30 days; 401 as pilot in command
  • Last flight review: February 25, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,763 hours
  • Last inspection: annual inspection, February 14, 2012; 38 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540-K1G5D (piston); 0 hours total

The flight

  • Departed from: RHP Andrews NC at 5:18 pm
  • Destination: UOX Oxford MS
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 260° at 9 knots
  • Visibility: 8 statute miles
  • Sky: clear
  • Temperature: 90°F (32°C), dew point 72°F (22°C)
  • Altimeter: 30.03 inHg
  • Observation at 6:53 pm from TUP, 20 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.