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

October 28, 2010 · Piper PA-28-151 · N44078

Julian, NC

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 28, 2010
Injury Outcomes
No injuries (1 uninjured)
Location
Julian, NC
Aircraft
Piper PA-28-151
Tail Number
N44078
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA11CA040

According to the pilot, he departed on the personal flight for the purpose of having an annual inspection performed on his airplane at the destination airport. While approaching the airport, he observed the windsock indicating the wind was from the south, and chose the appropriate runway. The pilot planned his approach to clear the fence at the end of the runway and still have enough distance for the roll out on the grass runway. Knowing that the terrain sloped upward from the fence to the runway threshold, he aimed to touchdown on the crest of the hill. As the airplane approached the runway, the pilot added power to compensate for a fast rate of descent, then reduced power when he felt he was aligned appropriately. The airplane touched down about half way up the slope and the nose gear collapsed; the airplane came to rest at the top of the slope. According to the Federal Aviation Administration inspector, the firewall was substantially damaged. The pilot reported that there were no mechanical malfunctions prior to the accident.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C

Full Narrative

According to the pilot, he departed on the personal flight for the purpose of having an annual inspection performed on his airplane at the destination airport. While approaching the airport, he observed the windsock indicating the wind was from the south, and he planned to land on runway 23. The pilot stated that he planned his approach to clear the fence at the end of the runway and still have enough room to stop on the 1,400-foot grass runway. He also stated that he knew that the terrain sloped upwards from the fence to the runway threshold, and that he "was aiming for the crest of the hill." As the airplane approached the runway, the pilot first added power to compensate for a "fast rate of decent," then reduced power when he felt he had the runway made. However, "the rise was greater than I thought, and the airspeed was lower than I thought." The airplane touched down about half way up the slope, the nose gear collapsed, and the airplane came to rest at the top of the slope. According to the Federal Aviation Administration inspector, the firewall was substantially damaged. The pilot reported that there were no mechanical malfunctions prior to the accident.

Flight

Event TypeAccident
Event Time13:15 EDT
Nearest AirportKecks Airport (0nm)
Runway23
Runway Length1400 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-151
Tail NumberN44078
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 53 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind240° @ 8 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point61 F
Altimeter29.96 inHg
Observation Time17:54
Weather SourceWFAC

Appendix: Source Data