ASN Wikibase Occurrence # 184004
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Thursday 28 January 2016 |
| Time: | 18:57 |
| Type: |  Piper PA-24-260 Comanche |
| Owner/operator: | Private |
| Registration: | N9362P |
| MSN: | 24-4862 |
| Year of manufacture: | 1969 |
| Total airframe hrs: | 5315 hours |
| Engine model: | Lycoming IO-540-N1A5 |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | near Charles M Schulz-Sonoma County Airport (KSTS), Santa Rosa, CA -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Palm Springs, CA (PSP) |
| Santa Rosa, CA (STS) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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 des
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.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N9362P/history/20160129/0102Z/KPSP/KSTS
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?nNumberTxt=9362P
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 29-Jan-2016 07:05 | Geno | Added |
| 08-Feb-2016 20:03 | Geno | Updated [Nature, Source, Narrative] |
| 21-Dec-2016 19:30 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 06-Jul-2017 13:28 | Aerossurance | Updated [Location, Narrative] |
| 19-Aug-2017 16:35 | ASN Update Bot | Updated [Time, Operator, Other fatalities, Departure airport, Destination airport, Source, Damage, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation