FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA082 · Piper PA-32RT-300

29 Nov 2009 · Memphis, TN, United States

Piper PA-32RT-300 · Accident: loss of control in flight on approach

From Greenbrier Valley Airport (LWB) to Frederick W. Smith International Airport (MEM)

Report a problem

Event

NTSB case
ERA10LA082
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
1 · 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-32RT-300

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
N9243C
Operator
Emmett Oryan
Onboard fatalities
Unknown
Route
From Greenbrier Valley Airport (LWB), Lewisburg, WVTo Frederick W. Smith International Airport (MEM), Memphis, TN
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
Approach · IFR final approach
Defining eventThe 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 in flight
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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 was conducting an instrument landing system (ILS) approach, in instrument weather conditions, to his home airport after a 4 hour, 20 minute flight. According to air traffic control radar and voice data, the airplane maintained a parallel course, left of the runway centerline, for the entire approach, and when it was about 3 miles from the end of the runway, it descended below the glideslope. The air traffic controller issued two low altitude alerts over the next few minutes, after which the pilot acknowledged and initiated a climb. During the second climb, the ground speed decreased, and the pilot banked to the right and then sharply to the left. The groundspeed continued to decrease until the airplane stalled and impacted a grass area about 1 mile from the end of the runway. Witnesses reported the airplane appeared to be aligned with a parallel (center) runway, instead of the (left) runway the pilot was cleared for, when it descended from below the cloud layer.

The pilot, who was also a co-owner of the airplane, had a significant amount of total and instrument flight experience. He flew the accident airplane exclusively for the previous 11 years, and had conducted numerous instrument approaches at his home airport.

Weight and balance calculations revealed, at the time of the accident the airplane center of gravity was at about 99.26 inches aft of the airplane datum or approximately 3.26 inches aft of the rear center of gravity (CG) limit.

The pilot had a long history of significant liver disease (cirrhosis) as a result of chronic hepatitis C, and was apparently experiencing symptoms of insomnia and lethargy possibly related to his liver disease. He was regularly prescribed (for sleep) an evening dose of a potentially impairing medication (clonazepam) typically contraindicated in significant liver disease and a daily dose of a wakefulness-promoting medication (modafanil). The pilot and his physician had omitted information regarding the pilot's known cirrhosis, symptoms, and use of medications in information submitted to the FAA. Evidence of actively worsening liver disease was noted on autopsy. It is possible that the pilot's judgment and/or performance were somewhat impaired by chronic effects of hepatitis C or by the effect of a sudden deterioration in his condition. It is also possible the pilot may have been impaired as a result of his use of a prescription medication for sleep, particularly given that the metabolism of that medication may have been adversely affected by his liver disease. An inactive marijuana metabolite was detected in the pilot's urine on post-mortem toxicological testing, suggesting only that the pilot had used marijuana sometime in the previous days or weeks.

Probable cause

The pilot's failure to execute a timely missed approach and subsequent failure to maintain aircraft control, after he was unable to establish the airplane on the instrument approach. Contributing to the accident was the pilot's possible impairment due to his medical condition and/or medication use.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA082
Event ID
20091130X93025
Case number
ERA10LA082
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 6c1788104406ce8063aafdb77f8035579f0ff16fd02b527f9ac137b8b15980d5; retrieved 2026-09-13T20:34:57.187Z.