# Accident 20250721009409A: Xag P100 PRO 2023, Macon, IL, July 21, 2025

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 21, 2025, 09:35 local time
- Place: Macon, IL
- Damage: Substantial damage
- Phase of flight: Other, Specify
- Operating rules: Agricultural (Part 137)
- Operator: 77MG
- Location: 39.7087° N, 88.9967° W: Placed by OpenAirDocs: center of Macon, IL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.7087&lon=-88.9967&mi=10
- Aircraft: N918NU, registered now (https://openairdocs.org/aircraft/N918NU) (OpenAirDocs)
- Registry model: Xag P100 PRO 2023 (registry code 06102HJ, https://openairdocs.org/model/xag-p100-pro-2023) (OpenAirDocs)
- Reported make and model: XAG P100 PRO 2023
- 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/20250721009409A

## Narrative

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

PILOT STATEMENT

7:30 – 7:45 AM

ARRIVED AT THE FIELD LOCATED AT 394204N 0885935W. DROVE AROUND THE FIELD VIA W RIDLEN RD AND

CARDINAL DR TO IDENTIFY A SAFE LOCATION TO PARK THE TRUCK AND TRAILER, AS WELL AS TO ESTABLISH A SAFE

TAKEOFF AND LANDING AREA.

7:46 – 7:55 AM

WALKED THE SOUTH AND WEST EDGES OF THE FIELD TO ASSESS OBSTACLES PRESENT IN THE AREA.

7:55 – 8:05 AM

UNLOADED THE DRONE AND PREPARED THE TRAILER FOR OPERATIONS.

8:05 – 8:35 AM

COMPLETED THE XAG AERIAL APPLICATIONS START-OF-DAY CHECKLIST (SEE ATTACHED).

? LOADED BATTERIES INTO THE DRONE AND FILLED IT WITH THE APPROPRIATE PRODUCT.

? VERIFIED THE FIELD BOUNDARY IN THE XAG APP.

? SET BOUNDARY SAFETY BARRIER ON FIELD EDGES TO 18.5 FT.

? IDENTIFIED THREE POWER POLES SET SAFETY BARRIER AT 50 FT.

? CHECKED REMOTE CONNECTION: “GOOD”.

? VERIFIED SATELLITE LOCK: 21+ SATELLITES CONNECTED.

? MANUALLY TURNED ON THE DRONE’S LIQUID PUMPS: “GOOD”.

? MANUALLY TESTED PROPELLERS: “GOOD”.

8:35 – 8:38 AM

CONDUCTED FINAL CHECK OF CONTROL SETTINGS AND FIELD ENTRY POINT FOR SAFETY PRIOR TO DRONE TAKEOFF.

8:39 – 8:45 AM

DRONE TAKEOFF: I INITIATED AUTONOMOUS TAKEOFF. ONCE INSIDE THE FIELD BOUNDARY, I BRIEFLY SWITCHED

TO MANUAL CONTROL TO VALIDATE OPERATION, THEN RESUMED AUTONOMOUS FLIGHT.

? THE DRONE COMPLETED ITS FIRST APPLICATION FLIGHT WITHOUT ISSUE.

? I MONITORED ALTITUDE, SPRAY PATTERN, AND OBSTACLE AVOIDANCE — ESPECIALLY NEAR THE WEST

POWER POLE — WITH NO PROBLEMS OBSERVED.

? NOTED MINOR "BUCKING" BEHAVIOR, BUT NOTHING UNUSUAL OR OUTSIDE NORMAL OPERATION.

8:45 – 8:51 AM (ESTIMATED)

COMPLETED SECOND FLIGHT.

8:51 – 9:00 AM (ESTIMATED)

COMPLETED THIRD FLIGHT.

9:00 – 9:12 AM (ESTIMATED)

COMPLETED FOURTH FLIGHT.

9:12 – 9:22 AM (ESTIMATED)

COMPLETED FIFTH FLIGHT.

9:22 – 9:35 AM (ESTIMATED)

DURING THE SIXTH FLIGHT, THE DRONE ENTERED AUTONOMOUS HOVER MODE NEAR A POWER POLE IN THE

MIDDLE OF THE FIELD. THE DRONE WAS APPROXIMATELY 900 FT AWAY FROM MY LOCATION, BUT I STILL HAD

LINE OF SIGHT.

THE CONTROLLER DISPLAYED TWO FLIGHT PATH OPTIONS. I WAS NOT COMFORTABLE SELECTING EITHER OPTION, SO

I DECIDED TO MANUALLY MOVE THE DRONE AWAY FROM THE POWER POLE, ASCEND, AND RETURN TO HOME.

I TOOK MANUAL CONTROL BY ROTATING THE DRONE AWAY FROM THE OBSTACLE, THEN FLEW NORTHWEST UNTIL I

BELIEVED THE DRONE WAS IN A SAFE POSITION TO ASCEND.

WHEN I COMMANDED THE DRONE TO ASCEND, IT MADE CONTACT WITH A POWER LINE.

? THE DRONE’S PROPELLERS STRUCK THE LINE, AND IT IMMEDIATELY FELL TO THE GROUND.

? AFTER IMPACT TO THE GROUND, I HELD THE THROTTLE STICK DOWN TO SHUT OFF THE DRONE.

9:35 – 10:40 AM (ESTIMATED)

ENTERED THE FIELD TO INSPECT THE DRONE.

? UPON APPROACH, THERE WAS NO SMOKE, SOUND, OR INDICATION OF FIRE.

? BATTERIES REMAINED INSTALLED.

? PERFORMED A 2-MINUTE RISK ASSESSMENT. THE DRONE HAD BROKEN ARMS AND PROPELLERS AND

WAS RESTING IN A TILTED UPRIGHT POSITION.

? NO POWER OR ACTIVITY WAS OBSERVED FROM THE DRONE.

? I ATTEMPTED TO CONTACT THE CHIEF DRONE PILOT, BUT MY PHONE HAD BEEN LOCKED (DUE TO

INCORRECT PASSCODE ATTEMPTS IN MY POCKET) AND WAS INACCESSIBLE FOR 1 HOUR.

? I DECIDED TO REMOVE THE DRONE FROM THE FIELD. REMOVED BOTH BATTERIES AND RETURNED THEM

TO THE TRAILER.

? RETURNED TO THE DRONE, SEPARATED THE PAYLOAD TANK FROM THE DRONE TO MAKE IT EASIER TO

CARRY. TRANSPORTED BOTH BACK TO THE TRAILER.

10:40 – 11:30 AM (ESTIMATED)

PHONE REMAINED LOCKED, SO I LOADED THE DRONE INTO THE TRAILER AND RETURNED TO THE NUTRIEN

PRECISION BUILDING IN CERRO GORDO, IL.

SECURED THE TRUCK, TRAILER, AND DRONE, THEN WENT HOME TO CHANGE CLOTHING AND SHOWER.

11:30 AM – 12:30 PM

AFTER THE PHONE UNLOCKED, I CONTACTED THE NUTRIEN AG CHIEF DRONE PILOT AND MY GENERAL

MANAGER TO REPORT THE INCIDENT.

3:45 PM – 5:00PM

HELD A FACT-FINDING MEETING WITH VIA MICROSOFT TEAM:

? ^PRIVACY DATA OMITTED^

? J^PRIVACY DATA OMITTED^ – ADVISOR, SH&E RETAIL, CORNBELT REGION

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

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.
