Plane Crash List

Piper PA32R N323PA

22 December 2015 · Castro Valley, California, United States · Fatal

Summary

On 22 December 2015 at about 19:27 local time, a Piper PA32R registered N323PA was involved in an accident near Castro Valley, California, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 19:27
Classification
Accident
Location
Castro Valley, California, United States
Nearest airport
Metropolitan Oakland Intl (OAK)
Coordinates
37.6450, -121.9764
Aircraft
Piper PA32R
Registration
N323PA
Category
Airplane
Year built
2001
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Lincoln → Oakland
Aircraft damage
Destroyed
Weather
IMC
Light
Day
NTSB number
WPR16FA042

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The pilot's loss of control due to spatial disorientation while maneuvering during an instrument approach in instrument meteorological conditions.

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

Read the full NTSB narrative

The instrument-rated private pilot was operating the airplane on an instrument flight rules flight in instrument meteorological conditions (IMC). As the airplane neared the destination airport, the controller cleared the pilot for the instrument landing system (ILS) approach, instructed him to descend to 3,400 ft mean sea level (msl), and provided him with a heading to intercept the localizer course. The pilot acknowledged the clearance and began descending the airplane, but did not initiate the turn. About 30 seconds later, the controller again instructed the pilot to turn to intercept the localizer course. The pilot complied, turned west, and began tracking toward the airport south of the localizer course. The controller asked the pilot whether the airplane was established on the localizer, to which the pilot replied, "I'm re-establishing." Shortly thereafter, the controller asked the pilot if he was receiving the glideslope indication for the approach. The pilot confirmed that he was receiving the glideslope, but stated that he was "off glideslope" and "too high." However, at this time, the airplane was 800 ft below the minimum altitude for that segment of the approach (3,400 ft msl). The controller issued a low altitude alert, cancelled the approach clearance, and instructed the pilot to turn north and climb. The pilot acknowledged; however, the airplane turned south and did not climb. The controller again issued the pilot instructions to turn and climb, and the airplane began to turn north and climb before subsequently entering a descent. Shortly thereafter, the pilot stated, "I'm losing it." No further transmissions were received from the pilot, and radar contact was lost in the vicinity of the accident site. The airplane impacted heavily-wooded terrain about 12 nautical miles southeast of the destination airport, at an elevation about 1,400 ft. Postaccident examination of the airplane revealed heavy fragmentation consistent with a high-energy impact as well as evidence of a postimpact fire. Examination of the airframe, flight controls, and the engine revealed no evidence of any preimpact mechanical failures or anomalies. Although the extensive damage precluded examination of the primary vacuum pump and functional testing of the autopilot system, it is unlikely these components malfunctioned because before beginning the approach, the pilot experienced no difficulty complying with air traffic control-assigned altitudes and headings, and, throughout the flight, he gave no indication that he was experiencing problems with the flight controls, flight instruments, or autopilot. Based on weather data and the pilot's radio communication that he was "in the weather," the airplane was operating in IMC throughout the approach. When issued instructions to execute a missed approach, the pilot experienced a high workload that involved changes to the airplane's heading, altitude, and likely, configuration; this situation was conducive to the development of spatial disorientation. The pilot likely recognized the onset of spatial disorientation as evidenced by his statement to the controller, "I'm losing it;" however, the pilot was unable to make the appropriate corrective inputs before losing control of the airplane.

Quoted verbatim from the NTSB record.

Other Piper PA32R accidents

Date Aircraft Location Operator Outcome Died
2 Oct 2015 Piper PA32R
N782TM
Westminster, South Carolina, United States - Fatal 4
26 Mar 2015 Piper PA32R-301
C-GAUS
Townsend, Montana, United States David Charron Fatal 1
12 Apr 2016 Piper PA32R
G-MAIE
Hampshire, United Kingdom
no coordinates
- Minor injuries -
12 Nov 2016 Piper PA32R
N9084J
Bethel, Alaska, United States STATE OF ALASKA Department Of Public Safety Minor injuries -
15 Sep 2013 Piper PA32R-301T
F-GGBD
Lille Lesquin, France - No injuries -
26 Jan 2017 Piper PA32R
N6885F
Fort Mohave, Arizona, United States - No injuries -

All 55 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
26 Dec 2015 Boeing 737 76N
N7733B
San Diego, California, United States Southwest Airlines Co Serious injuries -
9 Jun 2015 Grumman Acft Eng Cor-Schweizer G 164A
N8372
Bakersfield, California, United States Nelson Kenneth D No injuries -
1 Feb 2015 Robinson R44 II
N510KJ
Calexico, California, United States John Reed Aviation No injuries -
14 Apr 2015 Robert C Hanson PITTS S2E
N75BH
Lebec, California, United States - Fatal 1
17 Apr 2015 Piper PA 18-150
N162SC
La Quinta, California, United States - Minor injuries -
18 Apr 2015 Cessna 206H
N3535M
Redding, California, United States McClelland Aviation Inc Fatal 1

All 170,864 records in United States