FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI95LA201 · Beech V35B

24 Jun 1995 · Cameron, MO, United States

Beech V35B · Accident: hard landing

From FES · Festus, MO to EZZ

Report a problem

Event

NTSB case
CHI95LA201
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 V35B

Aircraft type
Beechcraft 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
N84FB
Operator
Unknown
Onboard fatalities
Unknown
Route
From FES · Festus, MOTo EZZ
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
Hard landing
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 › Flare, misjudged
  • Pilot in command › Recovery from bounced landing, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT STATED TO THE INVESTIGATING OFFICER OF THE CAMERON POLICE DEPARTMENT THAT, 'WHEN SHE STARTED HER APPROACH TO LAND THE PLANE BALLOONED ON HER WHEN SHE TOUCHED DOWN,' AND THAT, 'THE NOSE GEAR WENT DOWN AND THE FRONT LANDING GEAR GAVE OUT AND FOLDED UNDERNEATH HER, CAUSING THE AIRCRAFT TO GO INTO A NOSE SKID.' A PILOT WHO WITNESSED THE ACCIDENT REPORTED THAT THE AIRPLANE BOUNCED 15 FEET INTO THE AIR AFTER THE FIRST TOUCHDOWN. THE AIRPLANE THEN LANDED ON THE NOSE GEAR FIRST AND THEN THE MAIN GEAR ON THE SECOND TOUCHDOWN BEFORE BOUNCING ABOUT 20 FEET INTO THE AIR AGAIN. THE NOSE THEN PITCHED EXTREMELY NOSE LOW BEFORE HITTING THE PROPELLER AND THEN LANDING ON THE NOSE GEAR BEFORE IT COLLAPSED.

Probable cause

The pilot misjudged the flare and improper recovery from a bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI95LA201
Event ID
20001207X03680
Case number
CHI95LA201
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: e6495398056fd6ac70e337643dd795cbdd2bb3ea815b352ad1e1fa5f817d2181; retrieved 2026-09-21T22:14:06.320Z.