# Incident 20260721009979I: Greensboro, NC, July 21, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 21, 2026, 13:30 local time
- Place: Greensboro, NC
- Damage: No damage
- Phase of flight: Hover/Holding
- Location: 36.0726° N, 79.7920° W: Placed by OpenAirDocs: center of Greensboro, NC, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.0726&lon=-79.7920&mi=10
- Aircraft: NONE (not matched to a registry record)
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260721009979I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON JULY 21, 2026 AT APPROXIMATELY 1330 EDT A SMALL UNMANNED AIRCRAFT SYSTEM (SUAS) COLLIDED WITH A VEHICLE NEAR THE LOCATION OF ^PRIVACY DATA OMITTED^.  OPERATION TOOK PLACE IN A LARGE OPEN PARKING LOT.  BOTH THE OWNER OF THE VEHICLE AND REMOTE PILOT IN COMMAND STATED THAT THERE WERE ONLY TWO VEHICLES IN THE AREA THAT WERE BOTH STATIONARY AND UNOCCUPIED; OPERATIONS WERE NOT INTENDED TO BE CONDUCTED NEAR THE VEHICLES.  THE SUAS IS REGISTERED AS ^PRIVACY DATA OMITTED^ AND HOLDS NO AIRWORTHINESS CERTIFICATE.  FLIGHT OPERATIONS WERE TO CONSIST OF A ROUTINE BATTERY DRAIN FLIGHT OPERATED UNDER 14 CFR 107.  TECHNICAL SUPPORT FROM THE MANUFACTURER OF THE AIRCRAFT, LUCID BOTS, PROVIDED AN ANALYSIS OF THE SEQUENCE OF EVENTS.  DURING THE FLIGHT A GPS RECEIVER DEGRADED LEADING TO NAVIGATION-AIDING FAILURE.  THE AIRCRAFT'S FLIGHT CONTROL MODE THEN AUTOMATICALLY SWITCHED FROM POSITION MODE TO MANUAL MODE AS A FALLBACK.  THIS HANDED CONTROL OF THE AIRCRAFT DIRECTLY TO THE REMOTE PIC UNEXPECTEDLY WHILE THE AIRCRAFT WAS APPROXIMATELY 15 FEET IN THE AIR.  THE REMOTE PIC'S WAS ALREADY APPLYING LARGE CONTROL INPUTS BEFORE THE AIRCRAFT'S FLIGHT CONTROL MODE AUTOMATICALLY SWITCHED FROM POSITION MODE TO MANUAL MODE.  IN POSITION MODE, LARGE CONTROL INPUTS ONLY PRODUCE MODEST MOVEMENT OF THE AIRCRAFT.  HOWEVER, THESE LARGE INPUTS TRANSLATED INTO FULL AUTHORITY COMMANDS THE INSTANT THE CONTROL MODE CHANGED WHICH CAUSED AGGRESSIVE NEGATIVE ATTITUDE RESPONSE AND RAPID LATERAL ACCELERATION LEADING TO THE COLLISION WITH THE VEHICLE.  THE ANALYSIS ALSO SUGGESTS NO MOTOR OR ACTUATOR FAILURE, NO SPONTANEOUS CONTROL COMMANDS BY THE REMOTE PIC, AND NO LOSS OF THE RADIO LINK BETWEEN THE AIRCRAFT AND CONTROLLER.  THE INCIDENT WAS REPORTED BY THE REMOTE PIC IN ACCORDANCE WITH 14 CFR 107.9.  AIRCRAFT IS BEING SENT BACK BY THE REMOTE PIC TO THE MANUFACTURER FOR FURTHER ANALYSIS AND DETERMINING CAUSE OF GPS DEGRADATION.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.