The U.S. aircraft register, updated daily
Accidents · NTSB WPR16LA146 · Final report

Cessna 172 and Unknown UNKNOWN mid-air collision near Emmett, Idaho, July 17, 2016

On July 17, 2016 at about 3:30 pm local time, 2 aircraft, Cessna 172 (N8184B) and Unknown UNKNOWN (UNKNOWN), were involved in a mid-air collision near Emmett, Idaho. No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 17, 2016 · about 3:30 pm local time
Place
Emmett, Idaho · map
Type
Accident · mid-air collision
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Cessna 172 UNDESIGNAT, built 1957 · all 172s on the register
Registration
N8184B · registry record · serial 29984
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)
Aircraft 2
Unknown UNKNOWN
Registration
UNKNOWN · no longer on the register · serial unknown
Damage
Not recorded
Flight
Flight · rules the NTSB did not record

The NTSB's narrative for the Cessna 172 final · quoted from the NTSB record

The private pilot of a red and white Cessna was conducting a personal local flight. The pilot reported that, about 10 minutes into the flight, the pilot of an unknown aircraft contacted him over the airport's common traffic advisory frequency (CTAF) and stated "we almost got you." However, the pilot later reported that he had not heard any previous communications from other aircraft in the local area on the CTAF, that he did not observe any aircraft nearby at the time of the radio call, and that he did not feel any sudden movement of the airplane, so he chose to continue the flight. He landed about 40 minutes later at his originating airport. Postaccident examination of the airplane revealed substantial damage to the rudder, which displayed a lateral tear and a blue paint mark at the trailing edge of the control surface. Although the pilot did not feel any sudden movement of the airplane, the blue paint mark and rudder damage indicates that his airplane's rudder was contacted by another object during the flight. The unknown pilot's statement, "we almost got you," suggests that the unknown pilot also might not have been aware that the two aircraft actually collided; however, this could not be confirmed because the pilot and other aircraft were never identified.

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 Unknown UNKNOWN final · quoted from the NTSB record

The private pilot of a red and white Cessna was conducting a personal local flight. The pilot reported that, about 10 minutes into the flight, the pilot of an unknown aircraft contacted him over the airport's common traffic advisory frequency (CTAF) and stated "we almost got you." However, the pilot later reported that he had not heard any previous communications from other aircraft in the local area on the CTAF, that he did not observe any aircraft nearby at the time of the radio call, and that he did not feel any sudden movement of the airplane, so he chose to continue the flight. He landed about 40 minutes later at his originating airport. Postaccident examination of the airplane revealed substantial damage to the rudder, which displayed a lateral tear and a blue paint mark at the trailing edge of the control surface. Although the pilot did not feel any sudden movement of the airplane, the blue paint mark and rudder damage indicates that his airplane's rudder was contacted by another object during the flight. The unknown pilot's statement, "we almost got you," suggests that the unknown pilot also might not have been aware that the two aircraft actually collided; however, this could not be confirmed because the pilot and other aircraft were never identified.

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 172 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during enroute (cruise) defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot of other aircraft

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 497 hours in all; 246 in this make and model; 12 in the last 90 days; 6 in the last 30 days; 428 as pilot in command
  • Last flight review: April 1, 2016
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 7,190 hours
  • Last inspection: annual inspection, July 15, 2015; 42 hours since
  • Maximum gross weight: 2,200 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental O-300A (piston); 5,302 hours total

The flight

  • Departed from: S78 Emmett ID at 3:20 pm
  • Destination: S78 Emmett ID
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 50°F (10°C)
  • Altimeter: 29.90 inHg
  • Observation at 3:30 pm from MAN, 20 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

The factual record for the Unknown UNKNOWN from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during enroute (cruise) defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot of other aircraft

The aircraft

  • Landing gear: fixed
  • Not recorded

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.