The U.S. aircraft register, updated daily
Accidents · NTSB LAX05FA099 · Final report

Beech 95 accident near Calistoga, California, February 15, 2005

On February 15, 2005 at about 5:25 pm local time, a Beech 95, registered N8269D, was destroyed in an accident near Calistoga, California (Charles M. Schulz- Sonoma Coun airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 15, 2005 · about 5:25 pm local time
Place
Calistoga, California · Charles M. Schulz- Sonoma Coun · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Beech 95 · all 95s on the register
Registration
N8269D · no longer on the register · serial TD-59
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 581 hours in all; 88 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 4,000 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming O-360-A1A (piston); 0 hours total

The flight

  • Departed from: OVE Oroville CA
  • Destination: STS Santa Rosa CA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 070° at 7 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 7,000 ft; clear
  • Temperature: 54°F (12°C), dew point 48°F (9°C)
  • Altimeter: 29.96 inHg
  • Observation at 5:53 pm from STS, 14 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.