# NTSB ERA18LA055: Cessna 182, N199RN, Burlington, NC, December 16, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: December 16, 2017, 12:30 local (17:30 UTC) - Place: Burlington, NC - Coordinates: 36.04972, -79.473052 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.0497&lon=-79.4731&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); [Maneuvering: Midair collision](https://openairdocs.org/ntsb-events/250) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report July 23, 2019 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 96526 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA18LA055 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96526/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96526 - Page: https://openairdocs.org/ntsb/ERA18LA055 ## Probable cause (aircraft 2) The pilot's failure to maintain adequate clearance from another airplane before beginning an inverted flight maneuver, which resulted in a collision with the airplane when he rolled his airplane upright. ## Probable cause (aircraft 1) The other pilot's failure to maintain adequate clearance from the airplane before beginning an inverted flight maneuver, which resulted in a collision with the airplane when he rolled his airplane upright. ## 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 of other aircraft (probable cause), aircraft 1; cases with it: [Cessna 182Q, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072732), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Effect on operation (probable cause), aircraft 1; cases with it: [Cessna 182Q, 1 case](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=2072732), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 2; cases with it: [Piper J3C-65, 4 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=7100510), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Effect on operation (probable cause), aircraft 2; cases with it: [Piper J3C-65, 3 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=7100510), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/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 182Q, 1 case](https://openairdocs.org/ntsb-events/250/sequence.md?model=2072732), [All aircraft, 196 cases](https://openairdocs.org/ntsb-events/250/sequence.md) - [Maneuvering: Midair collision](https://openairdocs.org/ntsb-events/250) (defining event), aircraft 2; cases with it: [Piper J3C-65, 3 cases](https://openairdocs.org/ntsb-events/250/sequence.md?model=7100510), [All aircraft, 196 cases](https://openairdocs.org/ntsb-events/250/sequence.md) ## Analysis (aircraft 2) The commercial pilot of the Piper airplane reported that he had recently performed maintenance on the smoke generator. Before the flight, the Piper pilot coordinated with the pilot of a Cessna to fly adjacent to his airplane to verify whether the Piper's smoke system was operating. After departure, the Piper pilot flew on the right side of and parallel to the Cessna, and both pilots acknowledged each other visually. The Cessna pilot subsequently verified that the Piper's smoke system was operating normally with a "thumbs up" signal, and the Piper pilot then broke off to the right, and the Cessna pilot continued straight ahead. After clearing for traffic, the Piper pilot then performed a check of the oil system and mixture control, which required inverted flight. He rolled the airplane inverted, verified the system operation, and then rolled the airplane upright, at which point its right wing collided with the Cessna's left wing. The Cessna pilot saw the Piper strike his airplane while in a descent. The Piper pilot stated that he never saw the Cessna and thought he was experiencing a flight control problem after the collision. Both airplanes returned to the departure airport and landed without further incident. The Piper's right wing and aileron and the Cessna's left wing were structurally damaged. The Cessna pilot was flying straight ahead, and the Piper pilot was maneuvering; therefore, the Piper pilot was responsible for ensuring that the area was clear before initiating the inverted maneuver. Given the described geometry of the collision, the Piper pilot likely did not adequately clear for traffic before beginning the inverted flight maneuver, which he should have done, and failed to see the Cessna before impacting its left wing. ## Analysis (aircraft 1) The commercial pilot of the Piper airplane reported that he had recently performed maintenance on the smoke generator. Before the flight, the Piper pilot coordinated with the pilot of a Cessna to fly adjacent to his airplane to verify whether the Piper's smoke system was operating. After departure, the Piper pilot flew on the right side of and parallel to the Cessna, and both pilots acknowledged each other visually. The Cessna pilot subsequently verified that the Piper's smoke system was operating normally with a "thumbs up" signal, and the Piper pilot then broke off to the right, and the Cessna pilot continued straight ahead. After clearing for traffic, the Piper pilot then performed a check of the oil system and mixture control, which required inverted flight. He rolled the airplane inverted, verified the system operation, and then rolled the airplane upright, at which point its right wing collided with the Cessna's left wing. The Cessna pilot saw the Piper strike his airplane while in a descent. The Piper pilot stated that he never saw the Cessna and thought he was experiencing a flight control problem after the collision. Both airplanes returned to the departure airport and landed without further incident. The Piper's right wing and aileron and the Cessna's left wing were structurally damaged. The Cessna pilot was flying straight ahead, and the Piper pilot was maneuvering; therefore, the Piper pilot was responsible for ensuring that the area was clear before initiating the inverted maneuver. Given the described geometry of the collision, the Piper pilot likely did not adequately clear for traffic before beginning the inverted flight maneuver, which he should have done, and failed to see the Cessna before impacting its left wing. ## Factual narrative (aircraft 2) On December 16, 2017, about 1230 eastern standard time, a Cessna 182Q, N199RN, and a Piper J3C-65, N25786, collided in midair near Burlington-Alamance Regional Airport (BUY), Burlington, North Carolina. The private pilot of the Cessna and the commercial pilot of the Piper were not injured. The Cessna and the Piper both sustained substantial damage. Both flights were conducted under the provisions of Title 14 Code of Federal Regulations part 91 as personal flights. Day, visual meteorological conditions prevailed, and no flight plans were filed for either flight. The flights originated at BUY about 1220.The Piper pilot reported that he had recently performed maintenance on the smoke generator system and installed a new fuel pump. Prior to the flight, he asked the Cessna pilot to fly adjacent to him to verify the smoke system operation. After departure, the Piper pilot flew on the right side of the Cessna and both pilots acknowledged each other visually. The Piper pilot turned on the smoke system and the Cessna pilot verified that it operated normally with a "thumbs up" signal. The Piper pilot then broke off to the right to leave the formation. The Piper pilot subsequently elected to fly inverted to check the oil system and mixture control. After clearing for traffic and tightening his harness, he rolled inverted. The systems operated normally, so he rolled again to level the airplane upright. During the return to level flight, he heard a loud noise and the airplane rolled to the right. He believed that he had experienced aileron flutter. He was able to control the airplane and returned to BUY and landed without further incident. It was after landing that he realized that he had collided with the Cessna. The Cessna pilot reported that, after checking the smoke system on the Piper and giving a thumbs up signal, the Cessna pilot climbed and disappeared from view due to the high wing on the Cessna. Subsequently, while still in straight and level flight, he observed a flash of yellow at his 9 o'clock position, which was the Piper in a descent. He reported that the Piper struck his left wing. He was able to maintain airplane control and returned to BUY for landing. An inspector with the Federal Aviation Administration examined both airplanes. The right wing and aileron of the Piper were structurally damaged, as was the outboard portion of the Cessna's left wing. Numerous paint transfer marks were noted on both airplanes. No other damage was noted. ## Factual narrative (aircraft 1) On December 16, 2017, about 1230 eastern standard time, a Cessna 182Q, N199RN, and a Piper J3C-65, N25786, collided in midair near Burlington-Alamance Regional Airport (BUY), Burlington, North Carolina. The private pilot of the Cessna and the commercial pilot of the Piper were not injured. The Cessna and the Piper both sustained substantial damage. Both flights were conducted under the provisions of Title 14 Code of Federal Regulations part 91 as personal flights. Day, visual meteorological conditions prevailed, and no flight plans were filed for either flight. The flights originated at BUY about 1220.The Piper pilot reported that he had recently performed maintenance on the smoke generator system and installed a new fuel pump. Prior to the flight, he asked the Cessna pilot to fly adjacent to him to verify the smoke system operation. After departure, the Piper pilot flew on the right side of the Cessna and both pilots acknowledged each other visually. The Piper pilot turned on the smoke system and the Cessna pilot verified that it operated normally with a "thumbs up" signal. The Piper pilot then broke off to the right to leave the formation. The Piper pilot subsequently elected to fly inverted to check the oil system and mixture control. After clearing for traffic and tightening his harness, he rolled inverted. The systems operated normally, so he rolled again to level the airplane upright. During the return to level flight, he heard a loud noise and the airplane rolled to the right. He believed that he had experienced aileron flutter. He was able to control the airplane and returned to BUY and landed without further incident. It was after landing that he realized that he had collided with the Cessna. The Cessna pilot reported that, after checking the smoke system on the Piper and giving a thumbs up signal, the Cessna pilot climbed and disappeared from view due to the high wing on the Cessna. Subsequently, while still in straight and level flight, he observed a flash of yellow at his 9 o'clock position, which was the Piper in a descent. He reported that the Piper struck his left wing. He was able to maintain airplane control and returned to BUY for landing. An inspector with the Federal Aviation Administration examined both airplanes. The right wing and aileron of the Piper were structurally damaged, as was the outboard portion of the Cessna's left wing. Numerous paint transfer marks were noted on both airplanes. No other damage was noted. ## Aircraft 1 - Registration: [N199RN](https://openairdocs.org/aircraft/N199RN), registered now, S/N 18266079, built 1977 (OpenAirDocs) - Reported make and model: CESSNA 182 (Q) - Registry model: [Cessna 182Q](https://openairdocs.org/model/cessna-182q) (registry code 2072732) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18266079 - Year built: 1977 - Engines: CONT MOTOR O-470 SERIES 230 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: BUY, Burlington, NC - Destination: BUY, Burlington, NC - Airport: BUY, Burlington Alamance Regional - Equipment: Stall warning system, ADS-B, Auto-pilot, Electronic multifunction display, Electronic primary flight display ## Aircraft 2 - Registration: [N25786](https://openairdocs.org/aircraft/N25786), registered now, S/N 3740, built 1939 (OpenAirDocs) - Reported make and model: PIPER J3C (65) - Registry model: [Piper J3C-65](https://openairdocs.org/model/piper-j3c-65) (registry code 7100510) (OpenAirDocs) - Registry engine: [Continental O-200 series](https://openairdocs.org/engine/continental-o-200-series) (registry code 17402, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 3740 - Year built: 1939 - Airframe hours: 2096 - Engines: CONT MOTOR O-200 Exp 100 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, July 20, 2017, 45 hours before - Departed: BUY, Burlington, NC - Destination: BUY, Burlington, NC - Airport: BUY, Burlington Alamance Regional - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N199RN; age 31; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review June 26, 2016; seat: left; restraint: 3-point; flight hours: 353 total, 11 in this make and model, 353 as pilot in command, 20 in the last 90 days, 5 in the last 30 days - Pilot, aircraft N25786; age 45; injuries: none; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: rear; restraint: 5-point; flight hours: 2,500 total, 500 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 48 °F, dew point 23 °F - Altimeter: 30.20 inHg - Observed at: BUY, 10 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 20171216023182A](https://openairdocs.org/incident/20171216023182A), Dec 16, 2017: Piper J3C-65, Burlington, NC, Substantial damage. Piper cub departed buy and remained overhead until 182 also departed buy. The aircraft came in close proximity of each other while airborne. Piper and 182… ## Docket (8 files) The files NTSB released with the investigation on February 7, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96526. 4.8 MB in all. - Pilot's Written Statement - N25786 (item 1, .PDF, 187 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470103&FileExtension=.PDF&FileName=Pilot%27s%20Written%20Statement%20-%20N25786-Master.PDF - NTSB Correspondence with Pilot - N25786 (item 2, .PDF, 461 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470104&FileExtension=.PDF&FileName=NTSB%20Correspondence%20with%20Pilot%20-%20N25786-Master.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (N199RN) (item 3, .PDF, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470105&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20(N199RN)-Master.PDF - Pilot's Written Statement - N199RN (item 4, .PDF, 234 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470106&FileExtension=.PDF&FileName=Pilot%27s%20Written%20Statement%20-%20N199RN-Master.PDF - FAA Inspector's Statement - N25786 (item 5, .PDF, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470107&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement%20-%20N25786-Master.PDF - FAA Inspector's Statement - N199RN (item 6, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470108&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement%20-%20N199RN-Master.PDF - Photo Array (item 7, .PDF, 10 photos, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470109&FileExtension=.PDF&FileName=Photo%20Array-Master.PDF - Excerpts - Maintenance Records for N25786 (item 8, .PDF, 379 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470110&FileExtension=.PDF&FileName=Excerpts%20-%20Maintenance%20Records%20for%20N25786-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.