FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26FA223 · Comp Air CA6-WB

20 Jun 2026 · Nicholasville, KY, United States

Comp Air CA6-WB · Accident: loss of control in flight en route

From Blue Grass Airport (LEX) to Gwinnett County Briscoe Field (LZU)

Report a problem

Event

NTSB case
WPR26FA223
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
Ongoing
API-reported fatalities
2 · 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

Comp Air CA6-WB

Aircraft type
Comp Air CA6
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
N82BT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Blue Grass Airport (LEX), Lexington, KYTo Gwinnett County Briscoe Field (LZU), Lawrenceville, GA
Aircraft age
About 22 years (built 2004)
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
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On June 20, 2026, about 0846 eastern daylight time, an experimental amateur-built Comp Air CA6-WB, N82BT, was destroyed when it was involved in an accident near Nicholasville, Kentucky. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Recorded ADS-B data provided by the Federal Aviation Administration (FAA) showed that the airplane departed from Lexington, Kentucky (LEX), runway 27 at about 0840:00, made a climbing left turn toward the southeast and ascended to an altitude of about 4,500 ft mean sea level (msl). At 0844:57, the data showed that the airplane began a descent, and its groundspeed steadily increased, until ADS-B contact was lost, about 1 nautical mile north of the accident location at 0845:23. Review of radio communications between the pilot, Lexington Tower and Terminal Radar Approach Control revealed that about 1 minute after departure, the pilot established radio communications with Terminal Radar Approach Control and requested flight-following services. At 0845:23, the controller stated radar contact was lost, and despite multiple attempts, no response from the pilot was received.

Figure 1: ADS-B Flight Path A flight log recovered from the accident site identified Gwinnett County Airport–Briscoe Field (LZU), Lawrenceville, Georgia, as the intended destination for the flight segment, with subsequent waypoints continuing to Fernandina Beach Municipal Airport (FHB), Fernandina Beach, Florida. According to witness video and audio captured by a doorbell camera near the accident site, the airplane was observed flying at a low altitude while emitting a grinding noise, followed by a popping sound. Witnesses reported that the fuselage then descended inverted after separating from both wings. The airplane continued in an inverted, near-vertical descent until the airplane went out of visual range. Several witnesses described the airplane as “spinning” about its lateral axis in the vertical descent. Examination of the accident site revealed that the airplane impacted level pasture terrain at a horse farm approximately 8 nautical miles south of LEX at an elevation of about 890 ft mean sea level. The first identified point of contact (FIPC) was the engine, which was found inverted, partially embedded within terrain, and partially separated from the fuselage. The fuselage came to rest on its left side approximately 2 ft east of the engine. The debris path extended approximately 1,700 ft, on a heading of about 090° magnetic from the main wreckage. Throughout the wreckage debris path, various components of the airplane, including portions of the flight control surfaces and propeller fragments were observed. The wreckage was recovered to a secure location for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR26FA223
Event ID
20260620203202
Case number
WPR26FA223
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, coordinates. 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: cf12c60151c2b27f34b1da4af2ec25311e4fd0f065a17f3446f6ffe81634c97f; retrieved 2026-09-15T09:17:08.536Z.