ASN logo
ASN Wikibase Occurrence # 17677
Last updated: 8 March 2021
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.

Type:Silhouette image of generic C172 model; specific model in this crash may look slightly different
Cessna 172N Skyhawk
Owner/operator:Felts Field Aviation
Registration: N75856
C/n / msn: 17268003
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Written off (damaged beyond repair)
Location:McCall Municipal Airport, McCall, ID -   United States of America
Phase: Landing
Departure airport:Spokane, WA (SFF)
Destination airport:McCall, ID (MYL)
Investigating agency: NTSB
The Cessna 172N and a Cessna 172 collided in flight over the approach end of the intended runway during day, visual meteorological conditions. The airplanes were destroyed during the collision and postcrash fire. The pilot of the 172N reported that he entered the airport traffic pattern from the northwest and positioned the airplane on the downwind leg of the traffic pattern for the landing runway. After transmitting position reports for each segment of the pattern on the common traffic radio frequency, the pilot turned the airplane onto final approach and proceeded to land. Approximately 30 feet above ground level, prior to touchdown, he maneuvered the airplane into a flare which was immediately followed by the collision. The pilot reported that he was not aware of the other airplane prior to and during the collision sequence. A witness on the ground reported that both airplanes appeared to be on final approach, one above the other. The witness lost sight of the airplanes and shortly thereafter observed a cloud of black smoke near the approach end of the runway. Recorded radar data revealed that the 172N's flight path descended towards the airport from the northwest and turned to adjoin the downwind leg for the landing runway. The airplane then turned onto a base leg for the landing runway, followed by a turn onto the final approach path for the runway. The flight path continued northbound and descended toward the runway. The radar data disclosed that the 172's flight path descended toward the runway from the south consistent with a straight-in approach. The data further indicated that when the 172N was turning onto final approach at 5,600 feet msl, the 172 was at 5,300 msl. The flight path continued northbound and descended toward the runway. Federal Aviation Regulations state that vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft. Postaccident examination disclosed no evidence of any preimpact mechanical anomalies with either airplane.
Probable Cause: The failure of the pilot to maintain adequate visual lookout and clearance from another airplane while attempting to land on the same runway. Contributing to the accident was the non-standard pattern entry by the pilot of the other airplane.



Revision history:

04-May-2008 23:31 Fusko Added
10-May-2008 08:37 Fusko Updated
21-Dec-2016 19:14 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
21-Dec-2016 19:16 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
21-Dec-2016 19:20 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
03-Dec-2017 10:51 ASN Update Bot Updated [Other fatalities, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description