# Incident 20260625006959I: Xag P150, Guthrie, TN, June 25, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 25, 2026, 12:00 local time
- Place: Guthrie, TN
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: Agricultural (Part 137)
- Operator: 77MG
- Aircraft: N929NU, registered now (https://openairdocs.org/aircraft/N929NU) (OpenAirDocs)
- Registry model: Xag P150 (registry code 06102JS, https://openairdocs.org/model/xag-p150) (OpenAirDocs)
- Reported make and model: XAG P150
- 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/20260625006959I

## Narrative

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

THE RPIC FILED A NOTAM THE DAY BEFORE OPERATIONS. ANOTHER NUTRIEN AG SOLUTIONS REMOTE PILOT FLEW A REMOTE SENSING FLIGHT TO COLLECT PHOTOGRAMMETRY DATA TO GENERATE FIELD BOUNDARIES AND PASSED IT OFF TO THE RPIC. THE RPIC ARRIVED ON SIGHT AT THE FIRST OPERATING LOCATION AT APPROXIMATELY 7AM CENTRAL TIME AND CONDUCTED A SITE SURVEY, SAFETY BRIEF, AND AIRCRAFT PHYSICAL INSPECTION YIELDING THAT THE AIRCRAFT IS AIRWORTHY. THE RPIC CONDUCTED OPERATIONS FROM THE FIRST LOCATION FOR APPROXIMATELY 2-3 HOURS. THE RPIC RELOCATED TO A NEW OPERATING LOCATION ROUGHLY 0.5NM TO THE NORTH. THE RPIC PERFORMED AN ABBREVIATED SITE SURVEY. THE RPIC CONDUCTED APPROXIMATELY 10 FLIGHTS FROM THE SECOND LOCATION BEFORE THE INCIDENT. THE RPIC COMMANDED THE AIRCRAFT TO ASCEND TO 86 FEET AGL, TRANSITION EAST WARD OVER A TREE LINE AND POWERLINE, THEN DESCEND DOWN TO 15 FEET AGL INTO THE OPERATIONS AREA ON THE OPPOSITE SIDE OF THE TREE LINE. THE PRIC REPORTS NOT MAINTAINING VLOS AND MONITORING AIRCRAFT PERFORMANCE VIA C2 DISPLAYED ON THE GCS. THE RPIC REPORTS THAT THE AIRCRAFT CONDUCTED 7 PASSES, HALF WAY THROUGH THE 8TH PATH THE RPIC REPORTS LOSS OF FPV. THE RPIC STATED THE C2 TELEMETRY DATA INDICATED THAT THE AIRCRAFT PAUSED UNEXPECTEDLY ON THE NORTH SIDE OF THE OPERATIONS AREA, AND THEN AIRCRAFT TELEMETRY DATA WENT TO 0 (FOR GROUND SPEED, ALTITUDE, SPRAY RATE ETC). THE RPIC WENT TO THE AIRCRAFT’S LOCATION WHERE IT WAS STUCK IN THE POWER LINES WITH ONE POWER LINE SEVERED AND OUTAGES REPORTED. THE UTILITY COMPANY WAS NOTIFIED AND ONSITE TO REPAIR THE LINES, AND REMOVE THE AIRCRAFT, WITHIN THE HOUR. THE RPIC THEN INITIATED INCIDENT RESPONSE PROCEDURES.

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.