ERA23FA131 · Cessna 150G
Cessna 150G · Accident: VFR encounter with IMC en route
From Burlington Alamance Regional Airport (BUY) to Twin County Airport (HLX)
Event
- NTSB case
- ERA23FA131
- 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
Cessna 150G
- Aircraft type
- Cessna 150
- 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
- N2991J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Burlington Alamance Regional Airport (BUY), Burlington, NCTo Twin County Airport (HLX), Hillsville, VA
- Aircraft age
- About 57 years (built 1966)
- 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
- En route
- 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
- VFR encounter with IMC
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The instrument-rated pilot was conducting a personal, cross-country, visual flight rules flight and did not receive a formal weather briefing before departing. Flight track data showed that, after departure, the airplane proceeded direct to the destination airport for about 40 minutes. Then, after entering mountainous terrain, the airplane completed a descending 540° left turn and reversed course while continuing to descend at a rate of 250 ft per minute. The airplane impacted trees and terrain and came to rest in a wooded area. The reported weather conditions in the area around the time of the accident included less than 2 miles visibility and clouds about 255 ft above ground level (agl). Examination of the airframe and engine revealed no evidence of any preaccident mechanical failures or malfunctions that would have precluded normal operation. Based on the cut branches located in the vicinity of the accident site, and the damage signatures observed on the propeller, the engine was likely producing power at the time of impact. While en route, the pilot likely encountered deteriorating weather conditions that obscured the mountainous terrain and as the pilot attempted to turn around and exit the deteriorating weather conditions the airplane gradually descended and struck trees and the terrain.
Probable cause
The pilot’s continued visual flight rules flight into instrument meteorological conditions, resulting in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA131
- Event ID
- 20230228106797
- Case number
- ERA23FA131
- 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, cause areas. 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: 525391f39e1d89877e75cac64ad637c80076fd92dd23cbd1e1529317b0b03a9d; retrieved 2026-09-15T07:56:59.674Z.