FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03FA122 · Piper PA-32R-301

12 Jun 2003 · Carthage, MS, United States

Piper PA-32R-301 · Accident: in flight encounter with weather en route

From Anderson Municipal Darlington Field (KAID) to Lakefront Airport (KNEW)

Report a problem

Event

NTSB case
MIA03FA122
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
2 · 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-32R-301

Aircraft type
Piper PA-32
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
N232HC
Operator
Dominick C. Riso · private individual
Onboard fatalities
Unknown
Route
From Anderson Municipal Darlington Field (KAID), Anderson, INTo Lakefront Airport (KNEW), New Orleans, LA
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
En route · cruise
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
In flight encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Flight into known adverse weather, attempted
  • Pilot in command › In flight weather avoidance assistance, disregarded

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The non-instrument rated pilot twice phoned an FAA Automated Flight Service Station, the first and second phone calls were made 47 minutes and 29 minutes respectively, before the flight departed. During the first phone call the pilot advised that the flight would be proceeding under instrument flight rules, and the briefing specialist provided convective sigmet and airmet information. During the second phone call the pilot requested an abbreviated weather briefing and the briefing specialist provided winds aloft. The pilot filed an instrument flight rules flight plan during the second phone call. After takeoff, air traffic control communications were transferred to several facilities. The flight proceeded towards the destination and while in contact with Memphis Air Route Traffic Control Center, the pilot contacted briefly the Greenwood Automated Flight Service Station and advised the briefing specialist that the flight was located in the Meridian MOA but he did not provide an exact location, and questioned whether he would "...beat that line of storms uhh that was headed eastbound." The pilot was advised of a severe thunderstorm watch. The briefing specialist also advised the pilot that his, "...best bet is to probably to turn and land at meridian at this point and time I don't think [your] going to be able to beat that." The pilot responded, "do that we are going to change our course and we're going to land at meridian thank you for your help." The pilot re-established contact with Memphis ARTCC, and requested to land at Meridian. At 1112, the controller advised the pilot that there was a large cell of heavy weather between his position and Meridian, and that better weather conditions existed near Greenwood, Mississippi. The pilot advised the controller that he would proceed to the destination airport heading 187 degrees. At 1121, the pilot requested to descend to 6,000 feet, but air traffic communications were transferred to Jackson Air Traffic Control Tower. At 1120, the pilot established contact with that facility, and he was provided the altimeter setting. Radar and radio contact were lost with that facility at 1124; the communications with the facility were not recorded. Review of NTSB plotted radar data revealed that from 1030 until the time of the accident, the airplane was proceeding in a southwesterly direction until flying near Starkville, Mississippi, at which time the airplane turned to a westerly course. The airplane continued on the westerly direction until flying near Kilmichael, Mississippi, at which time the airplane turned left and proceeded until 1121:51, on a heading of 180 degrees flying at 8,000 feet, at an average ground speed of approximately 125 knots. At that time, the airplane began a right turn to heading 220 degrees, and descended at 440 feet-per-minute. At 1123:03, the airplane began a right descending turn in excess of 6,000 feet-per-minute descent, with the last recorded radar target at 1124:03, at 1,500 feet. The last recorded radar target was located at 32 degrees 41 minutes 21 seconds North latitude, and 089 degrees 40 minutes 57 seconds West longitude. A search for the airplane was initiated, it was located the following day. A NTSB weather report indicates that better weather conditions existed in Greenwood, Mississippi, at the time the controller advised the pilot that better weather conditions existed there. Additionally, the airplane entered an area of high reflectivity (about 45 dBZ), which equates to a very strong cell. Additionally, clouds existed throughout the region. The main wreckage consisting of the fuselage was located approximately 243 degrees and .24 nautical mile from the last radar target. The airplane crashed into a heavily wooded area. Examination of the airplane revealed the left wing and both sides of the horizontal stabilator were separated from the airplane; no evidence of preexisting cracks were noted on the fracture surfaces. Examination of the flight controls and engine revealed no evidence of preimpact failure or malfunction. A review of the pilot's logbooks revealed he logged 24 hours of simulated instrument instruction after receiving his private pilot certificate. He logged 1.0 hour of actual instrument conditions; the entry did not have a signature by a certified flight instructor. He did log 4.2 hours of actual instrument flight with a flight instructor. Toxicological analysis of specimens of the pilot performed by the FAA Toxicology and Accident Research Laboratory indicated tetrahydrocannabinol (.0034 ug/ml, ug/g) was detected in blood. Tetrahydrocannabinol Carboxylic Acid (.0167 ug/g, and .2324 ug/g) was detected in blood and bile respectively. Doxylamine was detected but not quantified in blood and liver. Located in the wreckage was drug paraphernalia and a green colored leaf type substance that was consistent with marijuana. No in-flight or post crash fire was noted on any wreckage component.

Probable cause

The failure of the non-instrument rated pilot to following the in-flight weather avoidance assistance instructions offered by the controller and his continued flight into known adverse weather condition (thunderstorm), resulting in overload failure of the left wing and both sides of the horizontal stabilator. A contributing factor in the accident was the pilot's impairment by marijuana.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03FA122
Event ID
20030619X00908
Case number
MIA03FA122
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, coordinates. 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: 4fd8c1b792434ca4167834e1f6571621f75a9301a73455911b24533e7a442de7; retrieved 2026-09-20T19:10:32.909Z.