CHI94LA281 · Beech B-35
Beech B-35 · Accident: loss of control in flight during landing
From Strum, WI (no airport) to an unrecorded destination
Event
- NTSB case
- CHI94LA281
- 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 B-35
- Aircraft type
- Beechcraft B-35
- 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
- N5095C
- Operator
- Joel D. Parker · private individual
- Onboard fatalities
- Unknown
- Route
- From Strum, WI (no airport)To 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
- Landing · flare/touchdown
- 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
- 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 › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT WHILE ON FINAL APPROACH, AT APPROXIMATELY 15 TO 20 FEET ABOVE THE RUNWAY SURFACE, THE AIRPLANE EXPERIENCED AN EXTREME DOWNDRAFT. HE STATED HE FLARED THE AIRPLANE, BUT WAS UNABLE TO KEEP THE AIRPLANE FROM BEING SLAMMED ONTO THE RUNWAY. AFTER THE INITIAL IMPACT, THE AIRPLANE BOUNCED INTO THE AIR IN A NOSE HIGH ATTIUTDE. THE PILOT IMMEDIATELY PUSHED THE NOSE DOWN AND APPLIED ENGINE POWER. THE AIRPLANE IMPACTED THE GRASS ADJACENT TO THE RUNWAY, THE NOSE WHEEL COLLAPSED, AND THE RIGHT WING STRUCK THE GROUND BEFORE THE AIRPLANE CAME TO REST. NO PREIMPACT MECHANICAL ANOMALIES WERE REPORTED BY THE PILOT. THE PILOT REPORTED THE WINDS TO BE FROM 270 DEGREES AT 14 KNOTS, GUSTING TO 20 KNOTS.
Probable cause
The pilot-in-command's inadequate compensation for the existing wind conditions during the landing flare/touchdown. A factor was the gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94LA281
- Event ID
- 20001206X02006
- Case number
- CHI94LA281
- 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: cf4b9ff9358c036fb4f8eb26e900576081ce1d65cf33062c2833eb1108afc0ca; retrieved 2026-09-23T00:48:55.017Z.