FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05FA099 · Beech 95

15 Feb 2005 · Calistoga, CA, United States

Beech 95 · Accident: in flight encounter with weather en route

From Oroville Municipal Airport (OVE) to Charles M. Schulz Sonoma County Airport (STS)

Report a problem

Event

NTSB case
LAX05FA099
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
2 · 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 95

Aircraft type
Beechcraft 95
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
N8269D
Operator
Rodney Kirby
Onboard fatalities
Unknown
Route
From Oroville Municipal Airport (OVE), Oroville, CATo Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, 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
En route · cruise
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
In flight encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › In-flight planning/decision, inadequate
  • Pilot in command › Preflight planning/preparation, inadequate
  • Pilot in command › VFR flight into imc, continued

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 impacted the southeast side of a mountain while the pilot was in a cruise descent and entering the vicinity of the destination airport. The instrument rated pilot departed on the 81 nautical mile (nm) flight and shortly thereafter began receiving visual flight rules (VFR) flight following services. There was no indication that he had ever flown that route prior to the accident flight. The cross-country flight path consisted of flying over level terrain for the first half, with the remainder of the flight crossing over several mountains (the last of which was the mountain the airplane impacted). The pilot regularly flew over level terrain for his commute to work. A regular passenger on those commuter flights (a coworker) reported that there were numerous times when the pilot would fly through a layer of clouds in an effort to descend down to the destination airport. The radar returns and voice tapes of the pilot's communications revealed that the airplane began a gradual descent about 18 nm prior to impact. The majority of the radar returns were all spaced uniformly and followed an anticipated route for the cross-country flight. The area in which the radar returns were lost is a typical region for air traffic controllers to lose radar contact with aircraft due to the surrounding terrain. The airplane's radar-derived ground speed was close to that expected for cruise flight according to the airplane manufacturer's owner's manual. The last radar target observed was about 1.45 nm from the accident site at the same altitude where the wreckage was located. Instrument meteorological conditions were forecasted over the mountainous areas near the destination airport. A pilot who was flying in the vicinity of the accident site stated that he was on an instrument flight rules (IFR) flight plan around the time of the accident. He recalled that the cloud tops were about 5,000 feet mean sea level (msl) and the bases were about 3,000 feet msl. He noted that the mountains in the area were obscured, but did not observe any unusual or hazardous meteorological conditions. The weather observation stations 14 nm southwest, 50 nm east, and 38 nm northwest, were reporting overcast conditions around the time of the accident at 9,000, 4,800, and 4,000 feet, respectively. An AIRMET for the accident area was issued by the National Weather Service indicating cloud layers at the same altitude as the accident site. It additionally stated that mountains in the area were occasionally obscured in clouds, precipitation, fog and mist. There was no evidence that the pilot ever obtained a weather briefing for the accident flight from any official FAA or NWS aviation source. The wreckage came to rest about 1,100 feet below the eastern summit of a mountain, at the 3,300-foot level. The debris was distributed over 90 feet of rugged terrain, on a slope of about 70 to 80 degrees that was comprised of rock outcroppings and wet dirt. Trees were located about 150 to 200 feet from the main wreckage that appeared to have been severed at the tops. After performing victim recovery, search and rescue personnel declined to return to the accident site stating that the terrain was too dangerous for even the most experienced mountaineers. The airplane was not recovered.

Probable cause

The pilot's inadequate preflight and in-flight planning/decision, which resulted in continued VFR flight into instrument meteorological conditions at an altitude insufficient to ensure adequate terrain clearance and impact with rising terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA099
Event ID
20050224X00222
Case number
LAX05FA099
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: d8244fae0aa6dd8e55941d8822ad3482c587839a4114b98507fdbeff8a367438; retrieved 2026-09-20T18:07:02.335Z.