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

July 23, 2008 · Piper PA-28-235 · N8942W

Lowell, MI

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 23, 2008
Injury Outcomes
1 injury (1 minor injury), 1 uninjured
Location
Lowell, MI
Aircraft
Piper PA-28-235
Tail Number
N8942W
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI08CA206

The pilot had performed 56 flights in the accident airplane from the airport in "similar" atmospheric conditions at airplane weights that equaled or exceeded the accident flight takeoff. The pilot stated that the "numerous" trees surrounding the airport and the departure end of each runway are "extremely dangerous" and provide "few, if any, options" for an uneventful aborted takeoff. During the accident takeoff on runway 30 (2,394 feet by 48 feet, dry asphalt), the airplane performed within the pilot’s expectations, but after rotation, the airplane was not climbing "normally" nor was it accelerating to best angle climb speed at the rate he previously experienced. The pilot then aborted the takeoff while the airplane was within a "few" feet above the runway because he did not want to risk hitting the trees at the departure end of the runway. The pilot was uninjured and the passenger received minor injuries. The airplane overran the runway with the application of "full" braking and impacted the trees. A post crash fire then ensued consuming the airplane. The pilot stated that he can only "speculate" that something changed after takeoff rotation that affected airplane performance. The airplane flight manual states that the takeoff distance over a 50-foot obstacle is about halfway down the runway and the calculated landing ground roll is within the remaining runway distance. The pilot stated that he used 10 degrees of flaps for the takeoff rather than 25 degrees of flaps cited in the airplane flight manual for a short field takeoff. There is no takeoff performance data based upon a 10-degree flap setting cited in the airplane flight manual.

NTSB Probable Cause

The inadequate preflight planning/preparation and the short field takeoff procedure not followed by the pilot. An additional cause was the delayed aborted takeoff by the pilot. A contributing factor was the trees.

Full Narrative

The pilot had performed 56 flights in the accident airplane from the airport in "similar" atmospheric conditions at airplane weights that equaled or exceeded the accident flight takeoff. The pilot stated that the "numerous" trees surrounding the airport and the departure end of each runway are "extremely dangerous" and provide "few, if any, options" for an uneventful aborted takeoff. During the accident takeoff on runway 30 (2,394 feet by 48 feet, dry asphalt), the airplane performed within the pilot’s expectations, but after rotation, the airplane was not climbing "normally" nor was it accelerating to best angle climb speed at the rate he previously experienced. The pilot then aborted the takeoff while the airplane was within a "few" feet above the runway because he did not want to risk hitting the trees at the departure end of the runway. The pilot was uninjured and the passenger received minor injuries. The airplane overran the runway with the application of "full" braking and impacted the trees. A post crash fire then ensued consuming the airplane. The pilot stated that he can only "speculate" that something changed after takeoff rotation that affected airplane performance. The airplane flight manual states that the takeoff distance over a 50-foot obstacle is about halfway down the runway and the calculated landing ground roll is within the remaining runway distance. The pilot stated that he used 10 degrees of flaps for the takeoff rather than 25 degrees of flaps cited in the airplane flight manual for a short field takeoff. There is no takeoff performance data based upon a 10-degree flap setting cited in the airplane flight manual.

Flight

Event TypeAccident
Event Time18:10 EDT
Nearest Airport0nm
Flight Plan FiledIFR
Aircraft FireGrd

Aircraft

AircraftPiper PA-28-235
Tail NumberN8942W
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-540-B4B5 · Reciprocating

People & Injuries

Injury Summary1 injury (1 minor injury), 1 uninjured
Fatal0
Serious0
Minor1
Uninjured1
Total2
Crew 1Age 33 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind360° @ 8 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point48
Altimeter30.04 inHg
Observation Time21:53

Appendix: Source Data