CHI96LA027 · Beech 33
Beech 33 · Accident: loss of engine power during initial climb
From Tri-County Regional Airport (LNR) to Richland Airport (93C)
Event
- NTSB case
- CHI96LA027
- 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
- Visual Meteorological Cond
Beech 33
- Aircraft type
- Beechcraft 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
- N9559Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tri-County Regional Airport (LNR)To Richland Airport (93C), Richland Center, WI
- 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
- Initial climb
- 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 engine power
- 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
- Substantial
Cause areas
- Pilot in command › Airspeed, not maintained
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE HAD DEPARTED RUNWAY 27, AND AT 400 FEET ABOVE GROUND LEVEL, JUST AFTER HE HAD RETRACTED THE LANDING GEAR, THE ENGINE HAD A LOSS OF POWER. HE REPORTED THAT HE MADE A 180 DEGREE LEFT TURN TO DOWNWIND TO RETURN TO THE RUNWAY. WHEN HE REALIZED THAT HE WAS NOT GOING TO REGAIN POWER, HE MADE ANOTHER LEFT TURN TO TRY TO LAND ON THE RUNWAY. THE AIRCRAFT IMPACTED A FIELD LEFT WING FIRST AND CAME TO REST ABOUT 20 FEET BEYOND THE INITIAL ENGINE IMPACT. THE PILOT STATED THAT THE STALL WARNING WAS SOUNDING DURING MUCH OF HIS ATTEMPT TO RETURN TO THE RUNWAY. THE RUNWAY WAS SURROUNDED BY FLAT PLOWED FARM FIELDS. AN INSPECTION OF THE AIRCRAFT AND ENGINE SYSTEMS, EXCEPT FOR THE FUEL INJECTION UNIT WHICH WAS DESTROYED, REVEALED NO DEFECTS.
Probable cause
a partial loss of engine power for an undetermined reason, and the pilot's failure to maintain airspeed during his attempt to land the airplane back on the runway. A factor in the accident was the pilot's decision not to land in the suitable fields surrounding the airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA027
- Event ID
- 20001207X04824
- Case number
- CHI96LA027
- 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: 17952028c276df236a7495a5055e4bd0da6dca5b5820dbd372ece46c33989ef0; retrieved 2026-09-21T22:01:00.326Z.