ERA09FA514 · Beech A36
Beech A36 · Accident: controlled flight into terrain/object (CFIT) on approach
From Asheville Regional Airport (AVL) to Asheville Regional Airport (AVL)
Event
- NTSB case
- ERA09FA514
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N888WD
- Operator
- Youngblood Larry J
- Onboard fatalities
- Unknown
- Route
- From Asheville Regional Airport (AVL), Asheville, NCTo Asheville Regional Airport (AVL), Asheville, NC
- 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 · VFR pattern final
- 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
- Substantial
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Although the pilot was instrument rated, the investigation found no record that his rating was current. The pilot advised the air traffic controller before departure that he did not want to execute any instrument landing system (ILS) approaches even though they were in use at the time, and neither transceiver was configured to the localizer frequency. Due to the mountainous terrain surrounding the airport, local air traffic control (ATC) had designated certain mode 3 transponder codes that inhibit minimum safe altitude warning (MSAW) processing for a controller. This was accomplished to prevent repeated nuisance alarms for aircraft operating under visual flight rules (VFR) and not requesting MSAW processing. The pilot did not request MSAW monitoring before departure or at any time during the flight; therefore, the assigned VFR transponder code (0210) inhibited the MSAW. The pilot departed the flight with a reported ceiling of 1,500 feet and 10 miles visibility before proceeding south of the departure airport and electing to return, remaining in constant contact with ATC. While operating only several hundred feet above mountainous terrain, in instrument flight rules conditions due to fog, the pilot did not advise the controller of the weather encountered. While being vectored towards the airport, the airplane impacted trees then terrain at an elevation of approximately 2,809 feet mean sea level. The pilot made no distress call and the controller did not provide a MSAW warning to the pilot. Postaccident examination of the airplane, engine, and engine systems revealed no evidence of preimpact failure or malfunction. While testing of avionics revealed that the “Trim” light bulbs of the autopilot remote mode annunciator and the autopilot and flight director computer were illuminated at the moment of impact, the left pitch trim actuator was found in the neutral position and the circumstances of the accident do not support a pitch trim malfunction. Additionally, the autopilot was not activated at the moment of impact.
Probable cause
The pilot’s attempt to maintain visual flight during instrument meteorological conditions, resulting in controlled flight into mountainous terrain. Contributing to the accident was the pilot’s failure to advise the controller of the weather conditions encountered, and his failure to request minimum safe altitude warning (MSAW) monitoring before departure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09FA514
- Event ID
- 20090910X61833
- Case number
- ERA09FA514
- 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. 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: cd0b2f30555ebe3c0cce0e1832360d139ee5fb8120d53a1b529dd15b99b0374c; retrieved 2026-09-13T20:27:58.458Z.