WPR22LA183 · Pyka Inc PELICAN 7
Pyka Inc PELICAN 7 · Accident: system/component malfunction/failure (non-power) while maneuvering
Event
- NTSB case
- WPR22LA183
- 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
Pyka Inc PELICAN 7
- Aircraft type
- Pyka PELICAN
- Category
- Airplane
- 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
- N605PK
- Operator
- Pyka
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Built the same year (2022)
- 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 91: General Aviation
- 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
- Maneuvering · low-altitude flying
- 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft structures
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The operator of the uncrewed aircraft system (UAS) reported that, during a demonstration flight at a company event, the UAS made a left turn and the right wing skin, along with the flaps and ailerons, separated from the UAS. He further reported that, after separating the wing skins opened and floated behind the UAS as it rolled right, spun, and impacted terrain. Substantial damage was identified to the entire UAS, to include the fuselage, both wings, and empennage
Postaccident examination by a Federal Aviation Administration inspector revealed that the right-wing skin had delaminated/separated from the wing spar consistent with a failed bond between the wing skin and wing spar.
Probable cause
Delamination of the uncrewed aircraft systems’ right wing skin surfaces from the wing spar that resulted in a spin and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA183
- Event ID
- 20220520105109
- Case number
- WPR22LA183
- 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: cfbbad818da74d2686e36df44c9466e7b05fd72df7e3f75d24a2cebac57079be; retrieved 2026-09-16T15:14:38.843Z.