ASN Wikibase Occurrence # 45035
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Sunday 26 October 2003 |
| Time: | 22:10 |
| Type: |  Piper PA-30 Twin Comanche |
| Owner/operator: | Concept Displays LLC |
| Registration: | N7799Y |
| MSN: | 30-631 |
| Year of manufacture: | 1965 |
| Total airframe hrs: | 6948 hours |
| Engine model: | Lycoming IO-320-B1A |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Spartanburg Downtown Memorial Airport, SC -
 United States of America
|
| Phase: | Approach |
| Nature: | Executive |
| Departure airport: | Evansville-Dress Regional Airport, IN (EVV/KEVV) |
| Spartanburg Downtown Memorial Airport, SC (SPA/KSPA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20031031X01843&key=1
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=7799Y
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 09-Apr-2017 19:37 | Dr.John Smith | Updated [Time, Aircraft type, Operator, Location, Nature, Departure airport, Destination airport, Source, Narrative] |
| 09-Apr-2017 20:56 | Dr.John Smith | Updated [Departure airport] |
| 09-Apr-2017 20:58 | Dr.John Smith | Updated [Narrative] |
| 08-Dec-2017 19:58 | ASN Update Bot | Updated [Time, Nature, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation