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

April 22, 2004 · Piper PA-18-150 · N82943

Minneapolis, MN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 22, 2004
Injury Outcomes
1 injury (1 minor injury)
Location
Minneapolis, MN
Aircraft
Piper PA-18-150
Tail Number
N82943
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI04CA108

The airplane impacted a power pole and trees during a forced landing after a loss of engine power during initial climb. According to the pilot, prior to the accident flight the airplane was completely fueled and fuel samples he took during the aircraft preflight were not contaminated with water. The pilot stated the airplane was taxied on the right main fuel tank, and he switched to the left fuel tank prior to takeoff as required by the pilot operating handbook. The pilot reported that he experienced an uneventful takeoff ground run, rotation, and initial climb until approximately 150 feet above ground level (agl) when the engine lost power suddenly. The pilot reported he switched fuel tank positions, verified the magneto switch was on both, and the throttle and mixture controls were fully advanced. The pilot reported, "Because of the suddenness and completeness of the loss of [engine] power, I suspected either fuel starvation or an ignition problem." The pilot stated, "I changed the tank selector at least two more times, and got ready to crash." The pilot stated that a landing on the departure runway was not an option and he maneuvered the airplane in between two houses prior to striking a power pole and several trees. A first responder reported the fuel selector was found in the "off" position upon his arrival at the accident site. The pilot reportedly said he did not reposition the fuel selector after the accident. The engine was subjected to an operational test-run. The engine started without hesitation and ran at idle power (~700 rpm) without any anomalies. The engine responded to brief throttle increases (~1,200 rpm) prior to being shutdown. The engine was not run above 1,200 rpm due to a damaged propeller.

NTSB Probable Cause

The pilot not verifying the position of the fuel selector prior to the takeoff, resulting in the loss of engine power during initial climb due to fuel starvation. Factors to the accident were the power pole and the trees.

Full Narrative

On April 22, 2004, at 0745 central daylight time, a Piper PA-18-150, N82943, piloted by a private pilot, sustained substantial damage during an in-flight collision with a power-pole and terrain during a forced landing near Minneapolis, Minnesota. The airplane was on initial climb from runway 24L (2,122 feet by 202 feet, dry turf) at the Crystal Airport (MIC) when the loss of engine power was encountered. Visual meteorological conditions prevailed at the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot sustained minor injuries. The flight was originating at the time of the accident and the intended destination was Maple Lake Municipal Airport (MGG), Maple Lake, Minnesota. According to the pilot, the airplane was completely fueled with 100 low-lead aviation fuel prior to the accident flight. The pilot reported the fuel samples he took during the aircraft preflight were not contaminated with water. The pilot stated the airplane was taxied on the right main fuel tank, and he switched to the left fuel tank prior to departing runway 24L as required by the pilot operating handbook. The pilot reported that he experienced an uneventful takeoff ground run, rotation, and initial climb until approximately 150 feet above ground level (agl) when the engine lost power suddenly. The pilot reported he switched fuel tank positions, verified the magneto switch was on both, and the throttle and mixture controls were fully advanced. The pilot reported, "Because of the suddenness and completeness of the loss of [engine] power, I suspected either fuel starvation or an ignition problem." The pilot stated, "I changed the tank selector at least two more times, and got ready to crash." The pilot stated that a landing on runway 24L was not an option and he maneuvered the airplane in between two houses prior to striking a power pole and several trees. The pilot stated the airplane came to rest inverted and that fuel was pouring from both sides of the cabin. Local fire and police departments responded to the accident. A fire department employee reported the fuel selector was found in the "off" position upon his arrival at the accident site. The pilot reportedly said he did not reposition the fuel selector after the accident. Federal Aviation Administration (FAA) inspectors performed the on-scene investigation. The wreckage was photo documented at the accident site prior to being repositioned to the departure airport. The engine was subjected to an operational test-run. The engine started without hesitation and ran at idle power (~700 rpm) without any anomalies. The engine responded to brief throttle increases (~1,200 rpm) prior to being shutdown. The engine was not run above 1,200 rpm due to a damaged propeller.

Flight

Event TypeAccident
Event Time07:45 CDT
Nearest AirportCrystal Airport (1nm WSW)
Runway24L
Runway Length2122 ft
Runway Width202 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-18-150
Tail NumberN82943
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 150
Seats2

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind10° @ 6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point37 C / 28 C
Altimeter30.12 inHg
Observation Time12:53
Weather SourceWFAC

Appendix: Source Data