Plane Crash List

Beechcraft B36 N364AB

15 March 2012 · Panoche, California, United States · Fatal

Summary

On 15 March 2012 at about 02:55 local time, a Beechcraft B36 registered N364AB, operated by Jim Lafferty Aircraft Sales, was involved in an accident near Panoche, California, United States. One person was on board and one died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 02:55
Classification
Accident
Location
Panoche, California, United States
Nearest airport
Hollister Municipal (CVH)
Coordinates
36.5281, -120.8431
Aircraft
Beechcraft B36
Registration
N364AB
Category
Airplane
Engines
1
Operator
Jim Lafferty Aircraft Sales
Operating rule
Part 91: General Aviation
Purpose of flight
Positioning
Phase of flight
Not recorded
Route
St Johns → Hollister
Aircraft damage
Substantial
Weather
Unk
Light
Night/Dark
NTSB number
WPR12FA139

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The pilot’s lack of situational awareness regarding the surrounding terrain while descending during dark night conditions, which resulted in controlled flight into terrain.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The pilot was delivering the single engine airplane from England to the west coast of the United States. According to his resume, he had piloted 196 Atlantic crossings in general aviation airplanes. The trip began about 1 week before the accident. The flights from England to Maine, with a pilot-rated passenger on board, consisted of 6 legs, with a total flight time of about 27 hours over a period of about 96 hours. The passenger and pilot separated in Bangor, Maine, and the pilot continued to Kentucky that same day, with an additional 2 legs and 6 hours flight time. He spent a total of 13 hours on the ground in Kentucky before departing early in the morning on the day of the accident. The first leg was 5 hours followed by a fuel stop. The next leg was 3 hours 20 minutes, and another fuel stop was made. The pilot then departed on the accident leg to his destination in California. The pilot flew the over 4-hour accident leg under visual flight rules using air traffic control flight following services. He flew directly between waypoints instead of on established airways. The airplane was equipped with a panel-mounted GPS unit with altitude information capability, and the pilot's iPad was equipped with current flight planning and guidance software, and electronic navigation charts. The pilot had access to sufficient information in flight to remain clear of terrain, but the investigation was unable to determine whether the pilot accessed that information during any part of that flight leg. When the airplane was about 65 miles from its destination, the pilot began a steady descent from his cruise altitude of 12,500 feet, which he had flown without supplemental oxygen. The destination elevation was 230 feet. Due to coverage limitations, radar contact with the airplane was lost when it was descending through 5,100 feet. At this point, the airplane was 46 miles from its destination, and the controller cancelled the flight-following services. There were no further communications from the pilot; up to this point, he had acknowledged all transmissions from ATC. Twelve miles after flight-following services were cancelled, the airplane impacted a hillside at an elevation of about 1,960 feet. Ground scar and wreckage information indicated that the airplane impacted in a wings-level attitude on a near-horizontal flight path. The airplane was highly fragmented and damaged by postimpact fire. Evidence was consistent with the landing gear and flaps retracted. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Darkness prevailed at the time of the accident, and AIRMETs for mountain obscuration were current for the time and location of the accident. Satellite and weather radar data suggested the presence of instrument meteorological conditions along parts of the airplane's route, but the investigation was unable to determine whether the pilot encountered or entered instrument meteorological conditions during the descent. Extrapolation of radar-derived speed and descent rate data indicated that the airplane descended steadily on track from cruise to the impact point. The pilot's autopsy indicated that the cause of death was multiple blunt trauma injuries, with no adverse pre-existing conditions. The effects of possible fatigue or hypoxia on the pilot's performance could not be determined.

Quoted verbatim from the NTSB record.

Other Beechcraft B36 accidents

Date Aircraft Location Operator Outcome Died
6 Oct 2019 Beechcraft B36
N36LS
Ranger, Texas, United States - No injuries -
5 Jul 2019 Beechcraft B36
XB-HYS
Mexico, Mexico
no coordinates
- No injuries -
15 Mar 2021 Beechcraft B36
N236BC
Pembroke Pines, Florida, United States - Fatal 2
31 May 2025 Beechcraft B36
D-EHVM
Korschenbroich, Germany - Fatal 1
20 Mar 1984 Beechcraft B36
N6665X
Webb City, Missouri, United States Memphis Jet Center Fatal 2

All 6 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
4 Nov 2012 Remos Acft Gmbh Flugzeugbau REMOS GX
N110GX
Sacramento, California, United States Greg Thomas Group Inc No injuries -
21 Feb 2012 Haycraft SPORT HORNET
N72PD
Mariposa, California, United States - No injuries -
20 Apr 2012 Piper PA-18-150
N8451Y
Sierraville, California, United States - No injuries -
19 Feb 2012 Aeronca 7BCM
N6451C
Woodland, California, United States Red Sky Aviation, LLC No injuries -
27 May 2012 Beechcraft B36TC
N8234M
Santa Ynez, California, United States - No injuries -
20 Nov 2012 Cessna 210
N3919Y
San Rafael, California, United States Zachariah Kimsey No injuries -

All 170,864 records in United States