CHI91FA126 · Beech F.33A
Beech F.33A · Accident: in flight encounter with weather en route
Event
- NTSB case
- CHI91FA126
- 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
- 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 F.33A
- Aircraft type
- Beechcraft F-33
- 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
- N8012T
- Operator
- Truckaline Suspension Centers
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 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 · climb to 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
- 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
- Tree(s)
- 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
- Pilot in command › Flight into known adverse weather, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
TWO INSTRUMENT RATED PILOTS INTENDED A CHECKOUT IN MODEL FOR THE FIRST PILOT. TEMPERATURES NEAR FREEZING, LOW CEILINGS AND LOW VISIBILITY IN PRECIPITATION EXISTED OVER THE AREA. THE FIRST PILOT FILED AN IFR FLIGHT PLAN FOR A 30 MINUTE, LOCAL FLIGHT. AIRBORNE, FLIGHT TWICE AMENDED ITS CRUISE ALTITUDE, ITS DESTINATION TWICE AND ARRIVED BACK AT ORIGIN FOR APPROACH. THE PILOT REPORTED HAVING 'QUITE A BIT OF ICE' BEFORE CLEARANCE FOR HIS APPROACH. THE AIRCRAFT, CONFIGURED TO LAND, FLEW INTO TREES UPRIGHT, IN A SHALLOW DESCENT WHILE CIRCLING FROM THE APPROACH COURSE TO THE OPPOSITE RUNWAY. ENGINE CONTROLS WERE FULL FORWARD AND POWER WAS EVIDENT.
Probable cause
THE FIRST PILOT'S CONTINUED FLIGHT IN KNOWN ADVERSE WEATHER. FACTORS IN THE ACCIDENT WERE THE FIRST PILOT'S POOR WEATHER EVALUATION, THE SECOND PILOT'S COMPLACENCY AND THE FIRST PILOT'S SELF INDUCED PRESSURE TO COMPLETE A CHECKOUT IN MODEL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI91FA126
- Event ID
- 20001212X16748
- Case number
- CHI91FA126
- 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: 49ae7cbd7b73276ed14872c9ff786413c53048ffee705af8cdb03d7e29b6baf2; retrieved 2026-09-21T01:52:01.701Z.