17 Jul 2016: CESSNA 172 UNDESIGNAT

17 Jul 2016: CESSNA 172 UNDESIGNAT (N8184B) — Unknown operator

No fatalities • Emmett, ID, United States

Probable cause

The failure of both pilots to see and avoid each other during cruise flight, which resulted in a midair collision.

— NTSB Determination

Accident narrative

On July 17, 2016, about 0930 mountain daylight time, a red and white colored Cessna 172 airplane, N8184B, was substantially damaged during a mid-air collision near Emmett, Idaho. The private pilot was not injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the local flight that departed Emmett Municipal Airport (S78), Emmett, Idaho, at approximately 0920.

According to the pilot, he departed runway 28, and flew the left hand traffic pattern during his ascent to 3,500 feet mean sea level. After he exited the traffic pattern on the downwind leg, the pilot flew east for approximately 2 miles and then turned northeast. About 10 minutes into the uneventful flight, he received a radio call from another airplane on the airport's Common Traffic Advisory Frequency (CTAF) that stated "aircraft east of Emmett…we almost got you." The pilot had not observed any aircraft in his range of view and elected to continue the flight. He landed about 40 minutes later and parked the airplane, but as he tied it down on the airport ramp, he observed a tear in the airplane's rudder, which was accompanied by a stretch of blue paint. The pilot reported that he monitored the airport CTAF, and had not heard any reports from anyone near the town of Emmett or transitioning through the town during the flight. He further stated that he did not observe any damage to the rudder before he departed. The pilot did not feel any sudden movement of the airplane between his departure and the time he received the radio call.

Postaccident examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed substantial damage to the airplane rudder, which displayed a lateral tear and a blue mark at the trailing edge of the control surface.

The other aircraft was not identified at any point during the investigation. A review of FAA radar data from 0820 and 0840 showed a total of three radar targets that passed through the town of Emmett. Two of the targets appeared as VFR primary radar targets, and did not display aircraft registration numbers. According to the pilot of the third target, identified as N471AM, he was on a cross country flight from Cascade, Idaho, to Nampa, Idaho, and was following a friend who was flying a brown and orange airplane. The pilot stated that he did not encounter a near mid-air collision at any point during the flight, and photographs of N471AM revealed that the airplane paint scheme did not contain any traces of blue consistent with the mark on the rudder of N8184B.

The FAA Airplane Flying Handbook states,

"Collision Avoidance

All pilots must be alert to the potential for midair collision and near midair collisions… This concept requires that vigilance shall be maintained at all times, by each person operating an aircraft regardless of whether the operation is conducted under instrument flight rules (IFR) or visual flight rules (VFR)…Most midair collision accidents and reported near midair collision incidents occur in good VFR weather conditions and during the hours of daylight. Most of these accident/incidents occur within 5 miles of an airport and/or near navigation aids."

Contributing factors

  • cause Pilot
  • cause Pilot of other aircraft
  • cause Pilot
  • cause Pilot of other aircraft

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.