CHI92LA241 · Beech A36TC
Beech A36TC · Accident: loss of control in flight on approach
From Western Neb. Rgnl/William B. Heilig Airport (BFF) to an unrecorded destination
Event
- NTSB case
- CHI92LA241
- 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 A36TC
- 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
- N1812E
- Operator
- Judson C. Martin · private individual
- Onboard fatalities
- Unknown
- Route
- From Western Neb. Rgnl/William B. Heilig Airport (BFF), Scottsbluff, NETo 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
- Approach · VFR pattern final
- 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
- Loss of control in flight
- 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
- 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 › Airspeed(vs), not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS CLEARED FOR AN NDB RWY 31 APPROACH AND RADAR SERVICE WAS TERMINATED. UPON SEEING A HOLE IN THE CLOUDS, HE ELECTED TO CIRCLE THE AIRPORT AT 1,000' AND ENTER A TRAFFIC PATTERN FOR RUNWAY 13. DURING THE TURN FROM BASE TO FINAL, THE PILOT LOST SIGHT OF THE RUNWAY DUE TO OBSCURED VISIBILITY AND OVERSHOT FINAL APPROACH. HE REPORTED HE THEN REDUCED THE THROTTLE AND MADE A LEFT TURN TO REALIGN HIMSELF WITH THE RUNWAY. WHEN TURNING TO THE RIGHT TO STOP THE TURN, THE AIRPLANE STALLED. THE RIGHT WING CONTACTED THE RUNWAY FOLLOWED BY THE NOSE. THE AIRPLANE CAME TO REST INVERTED.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN ADEQUATE AIRSPEED. FACTORS RELATED TO THE ACCIDENT WERE THE WEATHER OBSCURATION AND FAILURE TO ATTAIN PROPER RUNWAY ALIGNMENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92LA241
- Event ID
- 20001211X15363
- Case number
- CHI92LA241
- 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: 65038da8bbcc08eb7630abfdaf62d19bafcfc84ee634cfaf239fcc14d72bead0; retrieved 2026-09-21T14:48:39.300Z.