# Accident 20260317002569A: Pyka PELICAN CARGO, Summit Point, WV, March 17, 2026

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 17, 2026, 08:45 local time
- Place: Summit Point, WV
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: Agricultural (Part 137)
- Operator: 7YOG
- Location: 39.2366° N, 77.9769° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.2366&lon=-77.9769&mi=10
- Aircraft: N136ZP, registered now (https://openairdocs.org/aircraft/N136ZP) (OpenAirDocs)
- Registry model: Pyka PELICAN CARGO (registry code 06102C3, https://openairdocs.org/model/pyka-pelican-cargo) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: PYKA PELICAN CARGO
- Reported engine: SUNRAY DT13855-42P-60KV
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- Pilot flight hours: 140 total, 140 in this make and model, 4 in the last 90 days
- NTSB investigation: [NTSB DCA26LA159](https://openairdocs.org/ntsb/DCA26LA159) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260317002569A

## Narrative

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

PRIOR TO TAKEOFF, WEATHER, AIRSPACE, AND OTHER OPERATIONAL FACTORS WERE REVIEWED BY THE UAS TEAM. A CREW BRIEFING WAS CONDUCTED TO ESTABLISH ROLES, OBSERVER POSITIONS, AND CONTINGENCY PLANS, INCLUDING IDENTIFICATION OF AN ALTERNATE LANDING SITE. VISUAL OBSERVERS WERE POSITIONED ALONG THE FINAL APPROACH PATH, WHILE THE GROUND CONTROL OPERATOR MAINTAINED VISUAL LINE OF SIGHT NEAR THE RUNWAY. THE OPERATING SURFACE WAS A NON-STANDARD, MAKESHIFT RUNWAY ESTABLISHED ALONG A RACETRACK STRAIGHTAWAY.

DURING THE INITIAL FLIGHT, THE UAS DEPARTED FROM THE INTENDED RUNWAY WITHOUT ISSUE AND DEMONSTRATED SOLID PERFORMANCE DURING CLIMB-OUT.

IN PREPARATION FOR LANDING, MULTIPLE INSPECTION PASSES WERE FLOWN ALONG THE APPROACH PATH TO EVALUATE TERRAIN, SLOPE, AND OBSTACLE CLEARANCE. THESE PASSES INDICATED ADEQUATE SEPARATION FROM OBSTACLES. BASED ON THESE OBSERVATIONS AND THE AIRCRAFT’S PERFORMANCE, THE PILOT PROCEEDED WITH THE AUTONOMOUS LANDING.

DURING THE FINAL APPROACH, APPROXIMATELY 60 FEET ABOVE GROUND LEVEL, THE AIRCRAFT’S LEFT WING CONTACTED THE TALLEST TREE ALONG THE APPROACH PATH. THIS CONTACT LED TO A DESCENT THAT COULD NOT BE CORRECTED, AND THE AIRCRAFT SUBSEQUENTLY STRUCK A POWER LINE BEFORE CONTACTING THE HARD SURFACE COMING TO REST ON THE RACETRACK SAFETY BARRIER. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED. THERE WERE NO REPORTED INJURIES. THE FIRE DEPARTMENT AND HAZMAT TEAM RESPONDED TO THE SCENE; HOWEVER, NO FIRE OR CONTAMINATION WAS DETECTED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DCA26LA159](https://openairdocs.org/ntsb/DCA26LA159), Mar 17, 2026: Pyka Pelican Cargo (N136ZP), Summit Point, WV, substantial damage. Probable cause: The inaccurate obstacle height entered into mission planning that resulted in the aircraft wing’s impact with a tree during descent, resulting resulted in a loss of control.

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.