ATL04FA027 · Piper PA-30
Piper PA-30 · Accident: in flight collision with object on approach
From Evansville Regional Airport (KEVV) to Spartanburg Downtown Memorial Airport (KSPA)
Event
- NTSB case
- ATL04FA027
- 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-30
- Aircraft type
- Piper PA-30
- 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
- N7799Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Evansville Regional Airport (KEVV), Evansville, INTo Spartanburg Downtown Memorial Airport (KSPA), Spartanburg, SC
- 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
- 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 collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › IFR procedure, not followed
- Pilot in command › Proper glidepath, continued below
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight was cleared for the ILS runway 5 approach. The last recorded radar position showed the airplane at an altitude of approximately 1800 feet mean sea level, aligned with the runway 5 localizer 2.8 nautical miles from the runway threshold. A witness near the accident site heard the airplane's engines rev up, then heard popping and crashing noises and saw the airplane on the ground in flames. The wreckage was located in a wooded area 0.7 nautical miles from the runway 5 threshold about 950 feet to the right of the center of the runway 5 localizer course. Examination revealed no evidence of mechanical malfunction with the airframe or engines. A co-worker of the pilot reported the flight initially departed Spartanburg, South Carolina, as a business flight that morning. The pilot flew the airplane to Lawrenceville, Georgia, then to Lexington, Kentucky, and then to Evansville, Indiana. The pilot dropped off his last passenger in Evansville, Indiana, and elected to return to Spartanburg, South Carolina. A family member stated the pilot had a cold and "had the sniffles." A co-worker of the pilot stated he noticed the pilot seemed to have a cold two days prior to the accident, and he stated the pilot "seemed fine" the day of the accident. Forensic toxicology revealed 0.008 ug/ml, ug/g brompheniramine was detected in the blood, and brompheniramine, pseudoephedrine, and phenylpropanolamine were detected in the urine. Title 14 CFR Part 91.17, Alcohol or Drugs, states, "(a) No person may act ... as a crewmember of a civil aircraft ... (3) While using any drug that affects the person's faculties in a way contrary to safety ...."
Probable cause
The pilot's failure to follow IFR procedures and descent below the glide path, which resulted in an inflight collision with trees during an instrument approach. A factor was the pilot's impairment due to the sedating effects of medication.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04FA027
- Event ID
- 20031031X01843
- Case number
- ATL04FA027
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-10-27.
- API snapshot SHA-256: 299ff3157ba7e629db8123cdd698d6b3f91880233043c6e10713e83cf30c912d; retrieved 2026-09-20T18:50:24.411Z.