ASN Wikibase Occurrence # 155978
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: | Saturday 18 May 2013 |
| Time: | 18:38 |
| Type: |  Cessna 170B |
| Owner/operator: | Private |
| Registration: | N2865C |
| MSN: | 26408 |
| Year of manufacture: | 1954 |
| Total airframe hrs: | 3688 hours |
| Engine model: | Continental O-300-A |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Near Auburn Municipal Airport - KAUN, Auburn, CA -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Middletown, CA |
| Auburn, CA (AUN) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot's friend reported that he observed the accident airplane enter the airport traffic pattern but that he then diverted his attention to putting his airplane inside a hangar. Shortly after, when the accident airplane had not arrived, he immediately notified local authorities. The airplane wreckage was located the following morning in a heavily wooded area almost directly in line with the runway. Postaccident examination of the airframe, flight control system, and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
GPS data revealed that the accident airplane entered the downwind leg of the airport traffic pattern and proceeded to turn left onto the base leg and final approach to the runway. The last three GPS data points showed the airplane at a groundspeed of about 64 knots, which was well above the stall speed. The GPS data showed that the airplane was well above the 3-degree glidepath to both the runway threshold and the precision approach path indicator location. Wreckage and impact signatures were consistent with a stall and subsequent spin and a near-vertical impact with terrain. However, the reason for the stall could not be determined.
Probable Cause: The pilot's failure to maintain airplane control during approach to landing, which resulted in an inadvertent stall and subsequent spin.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 19-May-2013 12:19 | dfix1 | Updated [Date, Time, Aircraft type, Phase, Source, Damage, Narrative] |
| 19-May-2013 16:48 | Geno | Added [[Date, Time, Aircraft type, Phase, Source, Damage, Narrative]] |
| 20-May-2013 00:13 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Destination airport, Source] |
| 20-May-2013 01:36 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Departure airport, Destination airport, Source, Narrative] |
| 20-May-2013 17:59 | Geno | Updated [Registration, Cn, Source, Damage, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Nov-2017 14:40 | ASN Update Bot | Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, 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