ERA14FA073 · Raytheon Aircraft Company 390
Raytheon Aircraft Company 390 · Accident: controlled flight into terrain/object (CFIT) on approach
From Fulton County Airport Brown Field (FTY) to Lakefront Airport (NEW)
Event
- NTSB case
- ERA14FA073
- 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
- Visual Meteorological Cond
Raytheon Aircraft Company 390
- Aircraft type
- Raytheon 390
- 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
- N50PM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fulton County Airport Brown Field (FTY), Atlanta, GATo Lakefront Airport (NEW), New Orleans, LA
- Aircraft age
- About 10 years (built 2003)
- 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 · VFR pattern base
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and passenger departed on a night personal flight. A review of the cockpit voice recorder (CVR) transcript revealed that, immediately after departure, the passenger asked the pilot if he had turned on the heat. The pilot subsequently informed the tower air traffic controller that he needed to return to the airport. The controller then cleared the airplane to land and asked the pilot if he needed assistance. The pilot replied "negative" and did not declare an emergency. The pilot acknowledged to the passenger that it was hot in the cabin. The CVR recorded the enhanced ground proximity warning system (EGPWS) issue 11 warnings, including obstacle, terrain, and stall warnings; these warnings occurred while the airplane was on the downwind leg for the airport. The airplane subsequently impacted trees and terrain and was consumed by postimpact fire. Postaccident examination of the airplane revealed no malfunctions or anomalies that would have precluded normal operation. During the attempted return to the airport, possibly to resolve a cabin heat problem, the pilot was operating in a high workload environment due to, in part, his maneuvering visually at low altitude in the traffic pattern at night, acquiring inbound traffic, and being distracted by the reported high cabin temperature and multiple EGPWS alerts. The passenger was seated in the right front seat and in the immediate vicinity of the flight controls, but no evidence was found indicating that she was operating the flight controls during the flight.
Although the pilot had a history of coronary artery disease, the autopsy found no evidence of a recent cardiac event, and an analysis of the CVR data revealed that the pilot was awake, speaking, and not complaining of chest pain or shortness of breath; therefore, it is unlikely that the pilot's cardiac condition contributed to the accident. Toxicological testing detected several prescription medications in the pilot's blood, lung, and liver, including one to treat his heart disease; however, it is unlikely that any of these medications resulted in impairment. Although the testing revealed that the pilot had used marijuana at some time before the accident, insufficient evidence existed to determine whether the pilot was impaired by its use at the time of the accident.
Toxicology testing also detected methylone in the pilot's blood. Methylone is a stimulant similar to cocaine and Ecstasy, and its effects can include relaxation, euphoria, and excited calm, and it can cause acute changes in cognitive performance and impair information processing. Given the level of methylone (0.34 ug/ml) detected in the pilot's blood, it is likely that the pilot was impaired at the time of the accident. The pilot's drug impairment likely contributed to his failure to maintain control of the airplane.
Probable cause
The pilot's failure to maintain airplane control while maneuvering the airplane in the traffic pattern at night. Contributing to the accident was the pilot's impairment from the use of illicit drugs.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14FA073
- Event ID
- 20131217X20444
- Case number
- ERA14FA073
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2013-12-18.
- API snapshot SHA-256: fc0d623fa2bcd70a7c2b4ad8299569ccc8f2d345ef78b9a36bd144742b7c6a93; retrieved 2026-09-14T16:08:51.681Z.