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

August 2, 2003 · Piper J3C-65 · N70522

Chadron, NE

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 2, 2003
Injury Outcomes
1 injury (1 minor injury)
Location
Chadron, NE
Aircraft
Piper J3C-65
Tail Number
N70522
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI03LA244

The airplane was substantially damaged when it impacted a hangar immediately after takeoff from an alfalfa field. The pilot reported that he taxied for takeoff, leaving what he thought was sufficient distance for the takeoff roll and initial climb. He noted that during the takeoff, at a point three-quarters of the distance to the hangar, he realized he was not going to be able to clear the obstacles. The pilot stated: "I was in a nose up attitude to try to clear the hangar but could not gain enough altitude. I hit the hangar just left of center and the plane fell back to the ground." The field was approximately one mile square and was surrounded by a barbed-wire fence. The available distance from the point where the takeoff was initiated to the hangar was approximately 730 feet. The takeoff path reportedly sloped upward about 10 feet. The pilot reported that there were no malfunctions with the aircraft or engine prior to the accident. Winds in the vicinity were reported from the south at eight knots. Temperature and dew point were 22 degrees Celsius and 29.98 inches of mercury. Density altitude was calculated as 4,847 feet. Federal regulations require the pilot-in-command to review takeoff distance data prior to flight to ensure sufficient runway distance is available.

NTSB Probable Cause

Inadequate preflight planning by the pilot to ensure the required takeoff distance was utilized, as well as a failure to abort the takeoff. Contributing factors were the uphill gradient and the hangar.

Full Narrative

On August 2, 2003, at 0815 mountain daylight time, a Piper J3C-65, N70522, piloted by a private pilot, was substantially damaged following an in-flight collision with a hangar immediately after takeoff from a field in Chadron, Nebraska. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under 14 CFR Part 91 and was not on a flight plan. The pilot reported minor injuries. The local flight was originating at the time of the accident. The pilot's written statement reported that he taxied for takeoff, leaving what he thought was sufficient distance for the takeoff roll and initial climb. The operating area was reportedly an alfalfa field with a hangar located on the north end. The pilot noted that during the takeoff, at a point three-quarters of the distance to the hangar, he realized he was not going to be able to clear the obstacles. He reported he stayed to the left of his intended takeoff path in order to minimize the hazard to people on the ground. The pilot stated: "I was in a nose up attitude to try to clear the hangar but could not gain enough altitude. I hit the hangar just left of center and the plane fell back to the ground." The owner of the aircraft reported that prior to the accident he had flown two passes over the field in the accident airplane, landed and shutdown approximately 50 yards south of the hangar. He stated that the pilot, who was going to take the aircraft for a flight, situated himself in the rear seat. He assisted the pilot start the engine and observed him taxi to the south. He noted: "I had began to walk back to the [hangar] when my attention was returned to the aircraft ... and noted he had shorten[ed] the takeoff area to less [than] I expected. ... As the aircraft passed by me I noted he had enough altitude to clear the fence, but the aircraft seemed to stall as it hit the [hangar]." According to the Federal Aviation Administration (FAA) investigator on-scene, the field was approximately one mile square and was surrounded by a barbed-wire fence. The investigator estimated the available distance from the point where the takeoff was initiated to the hangar was approximately 730 feet. In addition, the takeoff path reportedly sloped upward about 10 feet. Owners of the same make and model aircraft were asked about the expected takeoff performance by the FAA investigator. They reportedly estimated a required takeoff distance of 900 feet based on the weather and loading conditions. The post-accident examination of the aircraft did not reveal any pre-impact anomalies. In addition, the pilot reported that there were no malfunctions with the aircraft or engine prior to the accident. The pilot reported weather conditions at the scene as clear, 10 miles visibility, and northeast winds at less than 10 knots. Conditions reported by the Chadron Municipal Airport (CDR) Automated Surface Observing System at 0753, located 6 miles south-southwest of the accident site, were clear skies, 10 miles visibility, and winds from 160 degrees at 8 knots. The temperature and altimeter setting were reported as 22 degrees Celsius and 29.98 inches of mercury. The density altitude calculated based on these conditions was 4,847 feet. Federal regulations require the pilot-in-command to review takeoff distance data prior to flight. Specifically, 14 CFR 91.103, Preflight Action, states in part: "For civil aircraft for which an approved Airplane or Rotorcraft Flight Manual containing takeoff and landing distance data is required, the takeoff and landing distance data contained therein," or for other civil aircraft "other reliable information appropriate to the aircraft, relating to aircraft performance under expected values of airport elevation and runway slope, aircraft gross weight, and wind and temperature."

Flight

Event TypeAccident
Event Time08:15 MDT
Nearest AirportPVT (0nm)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper J3C-65
Tail NumberN70522
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · C65 · Reciprocating · 65
Seats2

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 54 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind160° @ 8 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point59
Altimeter29.97 inHg
Observation Time13:53
Weather SourceWFAC

Appendix: Source Data