The U.S. aircraft register, updated daily
Accidents · NTSB CEN25LA206 · Preliminary: the investigation is not finished

XAG P100 PRO accident near Pontiac, Illinois, June 5, 2025

On June 5, 2025 at about 4:55 pm local time, a XAG P100 PRO (helicopter), registered N231CU, was substantially damaged in an accident during maneuvering (hover) near Pontiac, Illinois. It was flown under agricultural flying rules (Part 137). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 5, 2025 · about 4:55 pm local time · cases in 2025
Place
Pontiac, Illinois · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
XAG P100 PRO · all P100 PROs on the register
Registration
N231CU · registry record · serial 1863FPEG8219314A8X26
Damage
Substantial damage
Flight
Flight · agricultural flying rules (Part 137)

The NTSB's narrative preliminary · quoted from the NTSB record

On June 5, 2025, at 1155 central daylight time, a XAG P100 Pro, N231CU, was substantially damaged when it was involved in an accident near Pontiac, Illinois. The unmanned aerial system (UAS) was operated under Title 14 Code of Federal Regulations as a Part 137 aerial application flight. The UAS was in a hover about 10 ft above ground level spraying an agricultural field with fertilizer when a propeller blade separated from the UAS. The UAS then descended and impacted the field. The UAS sustained substantial damage to the propeller. The portion of the propeller that remained attached to the UAS was retained for further examination.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Part(s) separation from AC during maneuvering (hover) defining event

The aircraft

  • Seats: 0
  • Landing gear: fixed
  • Operator: Nutrien AG Solutions INC

The flight

  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 040° at 12 knots, gusting 17
  • Visibility: 7 statute miles
  • Sky: scat at 2,500 ft
  • Temperature: 72°F (22°C), dew point 61°F (16°C)
  • Altimeter: 30.06 inHg
  • Observation at 11:55 am from PNT

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
  • N231CU on the register today · the tail number may have moved to another aircraft since
  • XAG P100 548 registered today · the model family and its accident history
  • XAG 1,041 aircraft on the register
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN25LA206.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.