FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08FA116 · Cessna 172N

2 May 2008 · McCall, ID, United States

Felts Field Aviation Cessna 172N and Cessna 172 · Accident: midair collision on approach

Report a problem

Event

NTSB case
SEA08FA116
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
3 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Cessna 172N

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N75856
Onboard fatalities
Unknown
Route
From Felts Field (SFF), Spokane, WATo McCall Municipal Airport (MYL), McCall, ID
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Aircraft 2 · Cessna 172

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N4008F
Operator
William D. Keating · private individual
Onboard fatalities
Unknown
Route
From Caldwell Executive Airport (EUL), Caldwell, IDTo McCall Municipal Airport (MYL), McCall, ID
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08FA116
Event ID
20080508X00635
Case number
SEA08FA116
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2008-05-03.
  • API snapshot SHA-256: 64f4068f1e771374913810363dc8dd4c6e4240f034039a1669543647e34fbaee; retrieved 2026-09-13T18:03:32.069Z.