FTW83LA425 · Beech A36
Beech A36 · Accident: in flight encounter with weather en route
From Baton Rouge Metropolitan Airport (BTR) to AAP · Houston, TX
Event
- NTSB case
- FTW83LA425
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
- N18BR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo AAP · Houston, TX
- 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
- En route · cruise
- First occurrenceThe 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
- In flight encounter with weather
- 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
- Pilot in command › Flight into known adverse weather, performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
BEFORE TAKEOFF, THE PLT WAS BRIEFED ON THE WX, INCLUDING SIGMET 20C, WHICH CALLED FOR IMBEDDED THUNDERSTORMS. WHILE EN ROUTE, HE DEVIATED AROUND AN AREA OF WX & WAS PROVIDED VECTORS TO AVOID STORM CELLS. IN THE VICINITY OF DAISETTA, TX, THE CONTROLLER SUGGESTED A FURTHER DEVIATION TO THE NORTH DUE TO WX. THE PLT RESPONDED THAT A NORTH TURN WOULD TAKE HIM INTO A CB TYPE CLOUD. HE DECLINED THE TURN & CONTINUED ON HIS HEADING. ABOUT 10 MI LATER, WHILE CRUISING AT 8000 FT, HE ENCOUNTERED HEAVY RAIN & A VIOLENT DOWNDRAFT & LOST MORE THAN 3500 FT IN A SHORT TIME. DURING THE ENCOUNTER, THE ENG COWLING SEPARATED & KNOCKED OUT THE WINDSHIELD. THE PRIMARY FLT INSTRUMENTS BECAME INOP & EXTENSIVE DEFORMATION OF THE AIRFRAME WAS SUSTAINED. THE PLT SUBSEQUENTLY RECOVERED IN VFR CONDITIONS BELOW THE CLOUDS &MADE AN EMERGENCY LANDING AT CLEVELAND, TX.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83LA425
- Event ID
- 20001214X44538
- Case number
- FTW83LA425
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 06300ee464480a46bfe4f7fd44b73cb73785d2976883638f30df08825596ea88; retrieved 2026-09-23T21:23:44.803Z.