WPR16FA059 · Piper PA 24-260 260C
Piper PA 24-260 260C · Accident: loss of control in flight on approach
From Palm Springs International Airport (PSP) to Charles M. Schulz Sonoma County Airport (STS)
Event
- NTSB case
- WPR16FA059
- 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
- Instrument Meteorological Cond
Piper PA 24-260 260C
- Aircraft type
- Piper PA-24
- 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
- N9362P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Palm Springs International Airport (PSP), Palm Springs, CATo Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CA
- Aircraft age
- About 47 years (built 1969)
- 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
- Approach · IFR final approach
- Defining eventThe 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA059
- Event ID
- 20160128X25329
- Case number
- WPR16FA059
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-01-29.
- API snapshot SHA-256: ae2c38c1692a1813ba54f04febcb34d7846bae60b882a8bb8554341b47e67604; retrieved 2026-09-14T21:39:13.334Z.