Midair Collision · NTSB SEA08FA116

CESSNA 172N — McCall, ID

3 fatal Base-to-final turn
DateMay 3, 2008
LocationMcCall, ID
AircraftCESSNA 172N
Purpose of flightPersonal
ConditionsDay · Visual Meteorological Cond
Phase / occurrenceApproach-VFR pattern final Midair collision
Pilot age30
Pilot total time478 hrs · Building experience
Time in type413 hrs
Fatalities3, 1 serious

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.

NTSB findings

  • Personnel issues-Action/decision-Action-Lack of action-Pilot - C
  • Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
  • Environmental issues-Operating environment-Air traffic/operating proc-Traffic pattern procedure-Decision related to condition - F

What happened

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.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →