Aviex Jet Beech BE-200 accident
Beech BE-200 · Accident: in flight encounter with weather on approach
From William P. Hobby Airport (HOU) to an unrecorded destination
Event
- NTSB case
- CHI84LA065
- 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
- Charter & commuter
- 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 BE-200
- Aircraft type
- Beechcraft BE-200
- 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
- N90DF
- Operator
- Aviex Jet
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU), Houston, TXTo not recorded
- 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 135: Air Taxi & Commuter
- 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
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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
- Horizontal stabilizer surface › Ice
- Weather condition › Icing conditions
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE RECEIVING VECTORS FOR AN ILS APCH, THE ACFT ENCOUNTERED RIME ICING CONDITIONS. THE LEFT WINDSHIELD BEGAN ICING OVER & WOULD NOT CLEAR WHEN THE PLT ADJUSTED THE WINDSHIELD HEAT FROM NORMAL TO HIGH. SINCE THE AUTOPILOT WAS ENGAGED, HE MOVED TO THE RIGHT (COPILOT'S) SEAT. AFTER TURNING INBOUND ON THE LOCALIZER, HE DISENGAGED THE AUTOPILOT. PRIOR TO REACHING THE OUTER MARKER, HE CYCLED THE DEICE BOOTS & NOTICED THAT THE WING BOOTS CYCLED PROPERLY. WHILE ON SHORT FINAL WITH 60% FLAPS & 130 KTS, A SINK RATE DEVELOPED. THE PLT APPLIED POWER & THE SINK RATE DECREASED MOMENTARILY, THEN BEGAN INCREASING AGAIN. SUBSEQUENTLY, THE ACFT LANDED HARD ABOUT 125 FT SHORT OF THE RWY. IT THEN ROLLED ONTO THE RWY & SKIDDED OFF THE RIGHT SIDE INTO A SNOW COVERED AREA. THE ACFT RECEIVED WING & ENG DAMAGE DURING THE OCCURRENCE. A POST-ACCIDENT EXAM REVEALED THE RIGHT SIDE OF THE WINDSHIELD WAS COVERED WITH ICE & APPX 1/2 INCH OF ICE REMAINED UNBROKEN ON THE HORIZONTAL STABILIZER. THE STABILIZER DEICE BOOTS WERE CYCLED & FUNCTIONED PROPERLY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI84LA065
- Event ID
- 20001214X45251
- Case number
- CHI84LA065
- 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: 534c7b6d5520ed1aef0f34042f529660af1de9802dae0e1d232daf96efe1d6c6; retrieved 2026-09-18T20:46:52.330Z.