FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04CA212 · Beech A60

15 May 2004 · Gualala, CA, United States

Beech A60 · Accident: overrun during landing

From Long Beach International Airport (LGB) to Q69 · Gualala, CA

Report a problem

Event

NTSB case
LAX04CA212
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 A60

Aircraft type
Beechcraft 60
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
N931RP
Operator
Richard L. Probert · private individual
Onboard fatalities
Unknown
Route
From Long Beach International Airport (LGB), Long Beach, CATo Q69 · Gualala, CA
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 · landing roll
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
Overrun
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, excessive
  • Pilot in command › Wrong runway, selected

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane overran the runway and collapsed the landing gear during the landing roll. The pilot reported landing a "bit too fast" with a tailwind. The airport manager reported observed tire skid marks from the displaced threshold down the entire length of the 2,500-foot runway. The airplane departed the end of the runway and came to rest down an embankment. The closest weather reporting facility (located 24 miles northeast of the accident site) depicted gusty winds out of the northwest. The pilot was landing to the southeast.

Probable cause

the pilot's inadequate in-flight planning which resulted in a downwind landing. The tailwind was a contributing factor and an overrun of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04CA212
Event ID
20040717X01003
Case number
LAX04CA212
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, coordinates. 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: 03cf79db8874e76e114994c2b0db7847ad4ec86bea81d7759ce0fdb2b91d4edb; retrieved 2026-09-22T07:33:31.380Z.