CEN24LA380 · XAG P100 PRO
LCG Family Farms XAG P100 PRO · Accident: loss of control in flight during landing
From Francesville, IN to Francesville, IN
Event
- NTSB case
- CEN24LA380
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
XAG P100 PRO
- Aircraft type
- Xag P100
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N268MQ
- Operator
- LCG Family Farms
- Onboard fatalities
- Unknown
- Route
- From Francesville, INTo Francesville, IN
- Aircraft age
- Built the same year (2024)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 137: Agricultural
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft systems
- Environmental issues › Operating environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The remote pilot reported that the unmanned aircraft system (UAS) was landing and had reached the designated landing spot and descent height just before the accident. When the UAS was about 1 foot above the ground, the aircraft flew sideways about 30 ft and struck a person assisting with the operation. That individual sustained a broken shoulder. The unmanned aircraft sustained damage to one rotor blade and to the onboard radar assembly; both were replaced.
A review of the available flight logs for the UAS indicated that as the aircraft was landing, the number of available GPS satellites decreased. This was accompanied by frequent signal fluctuations. The UAS subsequently calculated a position deviation that it attempted to resolve by repositioning itself.
Probable cause
The remote pilot’s in-flight loss of control of the unmanned aircraft due to GPS signal fluctuations, which resulted in a collision with, and serious injury to, a person assisting the operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA380
- Event ID
- 20241010195293
- Case number
- CEN24LA380
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 72b99ae85444a2e800cbc9cf38b5e674589ccf68ffd7052daa22632140cf5740; retrieved 2026-09-16T19:22:07.379Z.