# NTSB WPR16LA146: Cessna 172, N8184B, Emmett, ID, July 17, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 17, 2016, 09:30 local (15:30 UTC) - Place: Emmett, ID - Coordinates: 43.840278, -116.501388 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.8403&lon=-116.5014&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining events: [Enroute-cruise: Midair collision](https://openairdocs.org/ntsb-events/250); [Enroute-cruise: Midair collision](https://openairdocs.org/ntsb-events/250) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 12, 2016 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 93623 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR16LA146 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93623/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93623 - Page: https://openairdocs.org/ntsb/WPR16LA146 ## Probable cause (aircraft 1) The failure of both pilots to see and avoid each other during cruise flight, which resulted in a midair collision. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 1; cases with it: [Cessna 172, 3 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072402), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 1; cases with it: [Cessna 172, 3 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072402), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 2; cases with it: [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Midair collision](https://openairdocs.org/ntsb-events/250) (defining event), aircraft 1; cases with it: [Cessna 172, 3 cases](https://openairdocs.org/ntsb-events/250/sequence.md?model=2072402), [All aircraft, 196 cases](https://openairdocs.org/ntsb-events/250/sequence.md) - [Enroute-cruise: Midair collision](https://openairdocs.org/ntsb-events/250) (defining event), aircraft 2; cases with it: [All aircraft, 196 cases](https://openairdocs.org/ntsb-events/250/sequence.md) ## Analysis (aircraft 1) 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. ## Factual narrative (aircraft 1) 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) orvisual 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." ## Aircraft 1 - Registration: [N8184B](https://openairdocs.org/aircraft/N8184B), registered now, S/N 29984, built 1957 (OpenAirDocs) - Reported make and model: CESSNA 172 (UNDESIGNAT) - Registry model: [Cessna 172](https://openairdocs.org/model/cessna-172) (registry code 2072402) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 29984 - Year built: 1957 - Airframe hours: 7190 - Engines: Continental O-300A 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 15, 2015, 42 hours before - Departed: S78, Emmett, ID - Destination: S78, Emmett, ID - Equipment: Handheld GPS ## Aircraft 2 - Registration: unknown (not matched to a registry record) - Reported make and model: UNKNOWN UNKNOWN - Category: Unknown - Serial number: unknown - Fire: Unknown - Operator: Unknown - Registered owner: Unknown - Airworthiness certificate: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N8184B; age 62; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review April 1, 2016; seat: left; restraint: lap only; flight hours: 497 total, 246 in this make and model, 428 as pilot in command, 12 in the last 90 days, 6 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 50 °F - Altimeter: 29.90 inHg - Observed at: MAN, 20 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20160717011201A](https://openairdocs.org/incident/20160717011201A), Jul 17, 2016: Cessna 172, Emmitt, ID, Substantial damage. Pilot reported another aircraft made a radio call that said that was close. Pilot said he did not hear or feel anything at the time. After landing pilot… ## Other investigations on N8184B (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB MKC69D0261](https://openairdocs.org/ntsb/MKC69D0261), Nov 1, 1968: Cessna 172 (N8184B), Fredericksburg, IA, substantial damage ## Docket (4 files) The files NTSB released with the investigation on August 31, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93623. 3.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40444060&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation (item 2, .PDF, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40444063&FileExtension=.PDF&FileName=Record%20of%20Conversation-Master.PDF - Weather Report and Record (item 3, .PDF, 90 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40444064&FileExtension=.PDF&FileName=Weather%20Report%20and%20Record-Master.PDF - Accident Photographs (item 4, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40444066&FileExtension=.PDF&FileName=Accident%20Photographs-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.