Aviation Crash Map

Piper PA 24-260 N9362P

29 January 2016 · Santa Rosa, California, United States · Fatal

Summary

On 29 January 2016 at about 02:57 local time, a Piper PA 24-260 registered N9362P was involved in an accident near Santa Rosa, California, United States. 2 people were on board and 2 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:57
Classification
Accident
Location
Santa Rosa, California, United States
Nearest airport
Charles M Schulz - Sonoma Coun (STS)
Coordinates
38.4789, -122.7864
Aircraft
Piper PA 24-260
Registration
N9362P
Category
Airplane
Year built
1969
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Palm Springs → Santa Rosa
Aircraft damage
Substantial
Weather
IMC
Light
Night
NTSB number
WPR16FA059

People

2 people died.

On board Died Serious Minor Uninjured
2 2 0 0 0

Probable cause

The pilot’s failure to maintain airplane control during an instrument approach in night instrument meteorological conditions, which resulted in a collision with terrain. Contributing to the accident was the pilot’s lack of recent experience in night instrument meteorological conditions.

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

Read the full NTSB narrative

The commercial pilot and his wife departed on a visual flight rules cross-country flight to their home airport. About 46 nautical miles from the destination airport, the pilot requested an instrument flight rules clearance and was subsequently cleared for an instrument landing system (ILS) approach at the destination airport. GPS data indicated that the airplane followed a straight course with minimal variation during its cruise flight in a manner consistent with use of the autopilot. The airplane's course movements became more erratic when the airplane neared the destination airport, which suggests that the pilot began to hand-fly the airplane. A combination of radar data, GPS data, and air traffic control audio showed that the pilot complied with the controller's instructions. After the pilot intercepted the glideslope, he maintained a shallow descent rate until the final approach fix. The pilot subsequently crossed the final approach fix 1,000 ft above the intercept altitude on a heading track to the right of the localizer. The tower controller reported multiple deviations over the radio to the pilot, but the pilot did not make appropriate corrections. Radar data showed the airplane enter progressively steeper descent rates after passing the final approach fix, and the airplane began to deviate to the left of the localizer. In the final moments of the flight, the airplane turned to the right about 50°, crossed the localizer, and then immediately began a 60° steep left turn at an approximate 1,200-fpm descent rate. Debris path signatures indicated the airplane was in a high-speed, steep left turn with a nose-down attitude when it impacted a field about 1.5 nautical miles south of the runway approach end. The proximity of the accident site to the final GPS data point and the similarity between the impact signatures and the track shown by the last few GPS data points indicates that the last data points closely represent the airplane's final movements before impact. Examination of the wreckage and of engine analyzer data did not reveal any evidence of preimpact anomalies with the airframe or engine. Circumferential scoring from the gyros was found on the case of the heading indicator and both attitude indicators, which indicates that these instruments were likely functioning normally at the time of impact. The pilot obtained weather information from an online service about 24 hours before the flight; however, the forecasts he received were not valid at the time of his departure. In his communication to an Air Route Traffic Control Center (ARTCC) controller, the pilot asked, "what are they doing for approaches?" which indicated that he was aware of possible instrument meteorological conditions (IMC) at the destination airport. The pilot's audio transmissions to ARTCC did not indicate that he had received current Airport Terminal Information System weather. Further, the ARTCC controller did not provide the pilot with the current weather as required by Federal Aviation Administration (FAA) procedure, and the airport tower controller had not been disseminating pilot reports, also required by FAA procedure. The pilot's flight instructors commended his aeronautical decision-making skills; however, the investigation was unable to confirm if the pilot obtained current weather and if knowledge of the low-visibility weather conditions would have altered his decision to continue the flight despite his desire to return home that night. Two months before the accident, the pilot completed an instrument proficiency check and made a night flight to fulfill the night currency requirement. Other than these two events, the pilot had no recent instrument or night flight experience. Further, the pilot's flight records did not show any evidence that he had completed a flight in night IMC in nearly 3 years. Given the pilot's lack of recent experience in night IMC, he was most likely overwhelmed by the complexity of hand-flying the airplane on an ILS approach in night IMC. Once the pilot crossed the final approach fix, he doubled his descent rate to correct for his high crossing altitude and then deviated from the localizer course line. The airplane's final movements suggest that the pilot likely lost control of the airplane during the large heading adjustment he made to correct his course and was not able to regain control.

Quoted verbatim from the NTSB record.

Other Piper PA-24 accidents

Date Aircraft Location Operator Outcome Died
4 Jun 2016 Piper PA 24
N5376P
Loda, Illinois, United States - Minor injuries -
20 Jun 2016 Piper PA 24
N5661R
Houston, Texas, United States - Serious injuries -
8 Nov 2016 Piper PA 24-250
N7682P
Houlton, Maine, United States - No injuries -
24 Jun 2016 Piper PA 24
N5138P
Springfield, Missouri, United States - No injuries -
7 Sep 2015 Piper PA-24
N7708P
Stratford, Connecticut, United States Kumar Sanjay No injuries -
18 Jan 2015 Piper PA-24-260
D-EERZ
Rechberghausen, Germany
no coordinates
Not Provided by Authority Fatal 2

All 2,700 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
6 Oct 2016 Joe Salomone SUPER CUB SQ2
N786AB
Boca Reservoir, California, United States - No injuries -
12 Dec 2016 Cessna T210M
N761SZ
Mecca, California, United States - Serious injuries -
25 Aug 2016 Siai-Marchetti SF260
N16FD
Fullerton, California, United States Air Combat, USA Minor injuries -
15 Dec 2016 Bombardier CL 600 2B19
N986SW
San Francisco, California, United States Skywest Airlines Inc Unknown -
24 Aug 2016 Cessna 182
N4810N
Fallbrook, California, United States Civil Air Patrol Inc. Minor injuries -
8 Jul 2016 Cessna 172
N9488G
San Diego, California, United States - No injuries -

All 170,864 records in United States