WPR10CA361 · Beech V35
Beech V35 · Accident: abnormal runway contact during landing
From Livermore Municipal Airport (KLVK) to Bend Municipal Airport (KBDN)
Event
- NTSB case
- WPR10CA361
- 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
- Unknown
- 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 V35
- 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
- N24WG
- Operator
- Richard Degryse
- Onboard fatalities
- Unknown
- Route
- From Livermore Municipal Airport (KLVK), Livermore, CATo Bend Municipal Airport (KBDN), Bend, OR
- 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
- Defining eventThe 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
- Abnormal runway contact
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was on final approach to runway 34 at the destination airport. During the landing flare, the airplane encountered a gust of wind about 40 degrees off its nose. The airplane ballooned up off the runway surface and the pilot pushed the control yoke in an effort to counteract the wind. The airplane touched down hard, collapsing the nose landing gear. The airplane again became airborne and the pilot maneuvered to the ground and landed. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane. As a result of the accident, the airplane incurred damage to the right wing. A routine aviation weather report (METAR) for the airport, issued around the time of the accident, reported winds from 360 degrees at 07 knots; 20 minutes later it reported the wind from 360 degrees at 11 knots, gusting to 17 knots.
Probable cause
The pilot's inadequate compensation for a wind gust during the landing flare, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA361
- Event ID
- 20100722X42016
- Case number
- WPR10CA361
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-07-22.
- API snapshot SHA-256: fb395c98259ae9bbc0a717381ba7e8571acd500cfbc9753658390c82b0e7de2f; retrieved 2026-09-15T14:44:18.644Z.