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

January 25, 1995 · Piper PA-32R-300 · N1999H

Burnsville, NC

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 25, 1995
Injury Outcomes
2 injuries (2 serious injuries)
Location
Burnsville, NC
Aircraft
Piper PA-32R-300
Tail Number
N1999H
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ATL95LA045

ACCORDING TO THE AIRPORT MANAGER, THE PILOT HAD JUST COMPLETED A FLYBY OF THE RUNWAY AND WAS IN THE PATTERN TO LAND. THE WITNESS NOTICED THAT ON FINAL APPROACH, THE PILOT HAD NOT LOWERED THE LANDING GEAR. THE PILOT STATED THAT HE HAD NOT PERFORMED A COMPLETE, BEFORE-LANDING CHECKLIST AND HAD FORGOTTEN TO LOWER THE GEAR. AFTER THE PROPELLER BLADE TIPS STRUCK THE RUNWAY, THE PILOT ADDED POWER TO GO AROUND BUT THEN DECIDED TO MAKE A GEAR-UP LANDING. THE AIRCRAFT OVERRAN THE RUNWAY AND COLLIDED WITH TERRAIN.

NTSB Probable Cause

THE PILOT'S FAILURE TO COMPLETE THE BEFORE-LANDING CHECKLIST TO ENSURE THAT THE LANDING GEAR WAS EXTENDED.

Full Narrative

On January 25, 1994, about 1710 eastern standard time, a Piper PA-32R-300, overran the departure end of the runway at the Mountain Air Country Club Airport, Burnsville, North Carolina. The airplane was operated by Peach State Aviation under the provisions of 14 CFR Part 91, and visual flight rules. The business flight was conducted in visual meteorological conditions. There were serious injuries to the private pilot and his passenger. The airplane was substantially damaged. There was no flight plan filed for this flight, nor was the aircraft in radar or radio contact with any Air Traffic Control facility. Origination of the flight was Chamblee, Georgia, at 1608 on the same day. The airport manager witnessed the accident. He reported that the pilot had made prior landing arrangements at the private, 4,432 foot elevation, 2,900 foot long airstrip. Salt had been applied to morning ice patches and the runway was dry at the time of the attempted landing. According to the airport manager, there were very strong winds from the northwest with gusts in excess of 25 knots. When the pilot reported that he was approaching to land runway 32, Mountain Country Club Airport Unicom advised the pilot to execute a flyby so that he may judge the gusty winds before he attempted to land. The pilot conducted a flyby with the gear down. During the go-around, the pilot retracted the gear and then continued in the airport pattern to attempt a full stop landing on runway 32. While the airplane was on final approach to runway 32, the airport manager noted that the airplane's landing gear was not extended. According to the pilot, he realized that he had not lowered the landing gear just as the propellers struck the runway. The radio call to warn the pilot was made about the time the airplane touched down. At this time, the pilot added power in attempt to execute a go-around. The pilot stated that he then noted a strong engine vibration and elected to reduce the power and attempt a gear up landing. Skid marks were observed on the runway about 500 feet from the departure end. The airport manager stated that the airplane continued off the end of the runway, and down a steep embankment. As aircraft descended approximately 75 feet below the end of the runway, the pilot attempted to add right rudder to align the aircraft with an access road. The nose of the aircraft then struck a tree on the right side of the road. This dislodged the engine from the engine mounts. The fuselage then spun approximately 270 degrees to the right and came to rest on the right side of the road. The pilot stated that he had forgotten to put the gear down prior to landing.

Flight

Event TypeAccident
Event Time17:10 EST
Nearest AirportMountain Air Country Club (0nm)
Runway32
Runway Length2900 ft
Runway Width50 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32R-300
Tail NumberN1999H
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540 SER · Reciprocating · 310
Seats7

People & Injuries

Injury Summary2 injuries (2 serious injuries)
Fatal0
Serious2
Minor0
Uninjured0
Total2
Crew 1Age 47 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind320°, gusting 25 kt
Visibility20 sm
CeilingNone
Temperature / Dew Point50 / 21 C
Altimeter30.00 inHg
Weather SourceWIT

Appendix: Source Data