Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 17, 2026 · Pyka Pelican Cargo · N136ZP

Summit Point, WV

Overview

Report Status
Probable Cause
Event Type
Accident
Date
March 17, 2026
Injury Outcomes
No injuries (3 uninjured)
Location
Summit Point, WV
Aircraft
Pyka Pelican Cargo (2024)
Tail Number
N136ZP
Operator
Pyka
Injuries
None
Aircraft Damage
Substantial
NTSB Number
DCA26LA159

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.

NTSB 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.

Full Narrative

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.

Flight

Event TypeAccident
Event Time08:45 EDT
Nearest Airport0nm
Runway Length1150 ft
Runway Width33 ft
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPyka Pelican Cargo
Tail NumberN136ZP
Aircraft CategoryAir
DamageSubstantial
OperatorPyka
Operating RulePart 91
Engines4
Engine TypeElectric
Engine DetailsSunray · DT13855-42P-6 · Electric · 25 | Sunray · DT13855-42P-6 · Electric · 25 | Sunray · DT13855-42P-6 · Electric · 25
Seats0

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 21 · First Class · None
Crew 2Age 26 · Third Class · None
Crew 3Unknown · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point41 C / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data