# Incident 20260802010229I: Xag P100 PRO, Jacson, MN, August 2, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 2, 2026, 12:00 local time
- Place: Jacson, MN
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: Agricultural (Part 137)
- Operator: 5L5G
- Aircraft: N451WX, registered now (https://openairdocs.org/aircraft/N451WX) (OpenAirDocs)
- Registry model: Xag P100 PRO (registry code 06102FP, https://openairdocs.org/model/xag-p100-pro) (OpenAirDocs)
- Reported make and model: XAG P100 PRO
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260802010229I

## Narrative

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

WHILE CONDUCTING A NIGHTTIME AGRICULTURAL APPLICATION WITH TWO AIRCRAFT, WHILE THE PIC WAS OPERATING  THE TWO XAG P100 PRO UAS NEAR A TRANSMISSION LINE ONE OF THE AIRCRAFT UNEXPECTEDLY STOPPED ITS PLANNED MISSION, CLIMBED TO AN ALTITUDE OF MORE THAN 150 FEET AGL, AND THEN INITIATED A RETURN-TO-HOME (RTH) SEQUENCE FOR REASONS THAT ARE CURRENTLY UNKNOWN. THE SECOND XAG P100 PRO WAS COMPLETING ITS MISSION AND RETURNING A FOR LANDING. HIS ATTENTION WAS FOCUSED ON ENSURING THAT AIRCRAFT LANDED SAFELY. WHEN HE HEARD THE RETURN-TO-HOME NOTIFICATION FROM THE CONTROLLER ASSIGNED TO THE OTHER AIRCRAFT, HE IMMEDIATELY LOOKED TOWARD THE OPERATING DRONE AND OBSERVED THAT IT HAD CLIMBED WELL ABOVE ITS EXPECTED OPERATING ALTITUDE. HE PICKED UP THE CONTROLLER IN AN ATTEMPT TO INTERVENE; HOWEVER, THE SEQUENCE OCCURRED TOO QUICKLY FOR RECOVERY. FROM THE TIME THE RETURN-TO-HOME SEQUENCE INITIATED UNTIL THE AIRCRAFT BECAME ENTANGLED IN THE OVERHEAD STATIC WIRE WAS APPROXIMATELY 20 SECONDS.

PRIOR TO THIS EVENT, PIC STATED THAT BOTH AIRCRAFT HAD COMPLETED THE REMAINDER OF THE FIELD WITHOUT INCIDENT. BOTH DRONES WERE OPERATING WITH RTK ENABLED, AND THE FIELD HAD BEEN EVALUATED DURING DAYLIGHT BEFORE THE NIGHTTIME OPERATION

BEGAN.

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.