FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA283 · Beech A36

7 Jul 2023 · Rayville, LA, United States

Beech A36 · Accident: VFR encounter with IMC on approach

From Addison Airport (ADS) to an unrecorded destination

Report a problem

Event

NTSB case
CEN23FA283
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
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
N15RP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Addison Airport (ADS), Dallas, TXTo not recorded
Aircraft age
About 49 years (built 1974)
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
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was enroute to the destination airport under visual flight rules and without air traffic control services; radar data showed that it made several turns before approaching the airport from the south. The turns were not consistent with a standard visual airport traffic pattern. The airplane wreckage was located about 1 mile south of the airport. Ground scarring and airplane damage was consistent with a nose-down, high-speed terrain impact with the landing gear extended. Postaccident examination of the airplane and engine revealed no mechanical anomalies that would have precluded normal operation. The accident site was located ahead of a cold front; it had rained earlier in the evening, leading to abundant surface moisture after sunset. High-Resolution Rapid Refresh (HRRR) model sounding for the approximate accident site location and time indicated a conditionally unstable environment from the surface through 200 ft above ground level (agl) then a stable environment from 200 ft agl through 4,000 ft. With a subsidence inversion of approximately 1,600 ft, it is likely fog and low clouds were beginning to form above the accident site at the accident time. Recorded weather observations indicated ceilings down to 200 ft agl and decreasing visibilities below a mile after the accident time. It is likely the accident flight likely encountered instrument meteorological conditions between 200 ft agl and 1,600 ft mean sea level east of Monroe Regional Airport, which was about 13 miles west of the accident site. Based on the variation in measured ethanol levels, the extent of the pilot’s injuries, and the presence of other alcohols, at least some of the detected ethanol likely was from sources other than alcohol consumption. The levels of ethanol in the tested tissue specimens could not be used to reliably determine the pilot’s blood ethanol level at the time of the crash, or to exclude the possibility of alcohol consumption and associated impairment. The postmortem concentrations of delta-9-THC and its metabolite indicate that the pilot had used a cannabis product. However, the precise timing of last cannabis use, and whether associated impairing effects were present at the time of the crash, could not be determined from the toxicological evidence. The toxicology results also indicate that the pilot had used phentermine, but the levels measured in tissues could not be used to establish the presence of associated impairing effects at the time of the crash. Overall, several substances were detected that may cause performance impairment alone or in combination, but no reliable conclusion could be drawn from toxicological evidence about specific effects on the pilot at the time of the crash.

Probable cause

The pilot’s visual flight rules flight into instrument meteorological conditions, which resulted in a loss of control during the approach to the destination airport and subsequent impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA283
Event ID
20230707192556
Case number
CEN23FA283
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, coordinates, 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: 8ba6b1013bafa7ff6c846a250446c50c4b41b890ffc14ff32ca471ca9e2c0480; retrieved 2026-09-15T08:02:34.217Z.