Cessna 172N and Cessna 172 mid-air collision near Mccall, Idaho, May 3, 2008
On May 3, 2008 at about 1:50 am local time, 2 aircraft, Cessna 172N (N75856) and Cessna 172 (N4008F), were involved in a mid-air collision near Mccall, Idaho (Mccall Municipal Airport). 3 people were killed, 1 person was seriously injured and 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
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 of the pilot.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 3, 2008 · about 1:50 am local time
- Place
- Mccall, Idaho · Mccall Municipal Airport · map
- Type
- Accident · mid-air collision
- Injuries
- 3 people were killed, 1 person was seriously injured and 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cessna 172N · all 172Ns on the register
- Registration
- N75856 · no longer on the register · serial 17268003
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Cessna 172 · all 172s on the register
- Registration
- N4008F · registry record · serial 36908
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Cessna 172N final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Cessna 172 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Cessna 172N from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during approach (VFR pattern final) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
- factor Environmental issues › Operating environment › Air traffic/operating proc › Traffic pattern procedure › Decision related to condition
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
- Flight time: 478 hours in all; 413 in this make and model; 49 in the last 90 days; 25 in the last 30 days; 351 as pilot in command; 61 on instruments
- Last flight review: July 10, 2007
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 4,402 hours
- Last inspection: annual inspection, April 18, 2008
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360 SERIES (piston); 0 hours total
- Fire on the ground
- Operator: Felts Field Aviation
The flight
- Departed from: SFF Spokane WA at 11:20 pm
- Destination: MYL Mccall ID
- Flight plan: VFR
- Runway 34, 6,108 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 180° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 41°F (5°C), dew point 21°F (-6°C)
- Altimeter: 30.07 inHg
- Observation at 1:50 am from KMYL
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
The factual record for the Cessna 172 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during approach (VFR pattern final) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- factor Environmental issues › Operating environment › Air traffic/operating proc › Traffic pattern procedure › Decision related to condition
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 808 hours in all; 386 in this make and model
- Last flight review: February 18, 2008
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 3,472 hours
- Last inspection: annual inspection, October 18, 2007
- Maximum gross weight: 2,200 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor O-300 SER (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: EUL Caldwell ID at 1:05 am
- Destination: MYL Mccall ID
- Flight plan: none
- Runway 34, 6,108 ft by 75 ft
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.