Pyka INC PELICAN CARGO accident near Summit Point, West Virginia, March 17, 2026
On March 17, 2026 at about 12:45 pm local time, a 2024 Pyka INC PELICAN CARGO, registered N136ZP, was substantially damaged in an accident during approach near Summit Point, West Virginia. It was a flight test under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 17, 2026 · about 12:45 pm local time
- Place
- Summit Point, West Virginia · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Pyka INC PELICAN CARGO, built 2024
- Registration
- N136ZP · registry record · serial 16056PC0007
- Damage
- Substantial damage
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
A Pyka Pelican Cargo unmanned aircraft system (UAS), N136ZP, was substantially damaged after it impacted a tree and subsequently the ground during its descent to land at Summit Point Training Facility in Summit Point, West Virginia. The flight was operated by Pyka Inc. as a developmental flight test and was conducted under the provisions of Title 14 Code of Federal Regulations Part 91 and a Federal Aviation Administration (FAA) Certificate of Authorization (COA). There were no injuries. The Pelican Cargo is a fixed-wing UAS with four electrically-driven, wing-mounted motors (figure 1). Each motor has two propellers and are powered by a battery system. The airframe has a fixed tricycle landing gear. The accident aircraft held an experimental airworthiness certificate. Figure 1. Pyka Pelican Cargo. (source: Pyka Inc.) According to the operator, the aircraft departed from the same runway as the intended landing with no issues. The flight was conducted autonomously with the option for manual control. There was a pilot in command, a remote pilot, two visual observers (one positioned at the beginning of the final approach path, and one positioned abeam the tallest obstacle along the approach course), and a ground control station operator as part of the operation. During the flight, multiple passes were conducted to both ensure a stable approach and terrain clearance for landing. The pilot elected to proceed with landing, which the aircraft accomplished autonomously. During descent, at about 60 ft above ground level, the aircraft wing contacted a tree and subsequently struck a powerline before impacting the ground and fragmenting. No postcrash fire was reported and there were no injuries. During preflight planning, the operator stated that personnel measured nearby trees as being about 46 ft (14 meters) tall. However, these measurements were taken relative to the elevation of the runway, but the elevation of the trees was lower than that of the runway. The measured height of the trees was input as obstacles into the aircraft’s mission planning software. As a result, the aircraft interpreted these obstacles as extending 46 ft above the ground from where the trees were located. Furthermore, the operator reported finding, after the accident occurred, that one tree that was about 15 ft taller than the surrounding trees. This taller tree was missed during preflight planning and was not input into the mission planning software. The Pelican Cargo was not equipped with light detection and ranging (LIDAR) equipment or analogous remote sensing technology for obstacle detection and collision avoidance. Such equipment could have detected the impending conflict with the tree and aborted the landing autonomously.
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
- Controlled flight into terrain or object (CFIT) during approach defining event
The NTSB's findings
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Effect on equipment
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Accuracy of related info
Pilot
- Certificate: commercial pilot, remote
- Ratings: single-engine land; instrument: airplane; rotorcraft: glider; rotorcraft: unmanned (suas)
- Flight time: 664 hours in all; 140 in this make and model; 3 in the last 90 days; 608 as pilot in command
- Last flight review: June 29, 2025
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: none
- Injury: no injuries
Other crew
- Certificate: flight instructor, commercial pilot, private
- Ratings: single-engine land; instructor: glider; rotorcraft: glider
- Flight time: 610 hours in all; 139 in this make and model; 48 in the last 90 days; 15 in the last 30 days; 463 as pilot in command
- Last flight review: October 22, 2025
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: none
- Injury: no injuries
Other crew
- Certificate: private
- Flight time: 50 in this make and model
- Medical certificate: Unknown
- Seat: none
- Injury: no injuries
The aircraft
- Airframe total time: 12 hours
- Last inspection: inspection type not recorded, December 16, 2024
- Seats: 0
- Landing gear: fixed
- Engine 1: Sunray DT13855-42P-6 (electric); 12 hours total
- Engine 2: Sunray DT13855-42P-6 (electric); 12 hours total
- Engine 3: Sunray DT13855-42P-6 (electric); 12 hours total
- Engine 4: Sunray DT13855-42P-6 (electric); 12 hours total
- Operator: Pyka INC
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: scat at 6,000 ft
- Temperature: 41°F (5°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on July 16, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report NTSB Form 6120.1 | PDF, 10 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
