FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18LA055 · Cessna 182 Q

16 Dec 2017 · Burlington, NC, United States

Cessna 182 Q and Piper J3C 65 · Accident: midair collision en route

Report a problem

Event

NTSB case
ERA18LA055
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
0 · 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 182 Q

Aircraft type
Cessna 182
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
N199RN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Burlington Alamance Regional Airport (BUY), Burlington, NCTo Burlington Alamance Regional Airport (BUY), Burlington, NC
Aircraft age
About 40 years (built 1977)
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
En route · cruise
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
Substantial

Aircraft 2 · Piper J3C 65

Aircraft type
Piper J3
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
N25786
Operator
Unknown
Onboard fatalities
Unknown
Route
From Burlington Alamance Regional Airport (BUY), Burlington, NCTo Burlington Alamance Regional Airport (BUY), Burlington, NC
Aircraft age
About 78 years (built 1939)
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
Maneuvering
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
Substantial

Cause areas

  • Environmental issues › Physical environment
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18LA055
Event ID
20171216X54947
Case number
ERA18LA055
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: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 016939f8ac918105aa0f654e20f359b50ad4ddc2e1f5aed21419d0892eb8b84d; retrieved 2026-09-13T18:28:25.298Z.