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

November 26, 2000 · Aerostar PA-60-601P · N713HM

Preston, MN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 26, 2000
Injury Outcomes
No injuries (2 uninjured)
Location
Preston, MN
Aircraft
Aerostar PA-60-601P
Tail Number
N713HM
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CHI01LA042

During initial climb after takeoff, the pilot noticed that the airspeed indicator was not increasing past 112-115 mph. The pilot reported that he lowered the nose of the airplane to increase airspeed, but no response was noted on the airspeed indicator. The pilot stated that the airplane made contact with a tree line located at the end of the runway, causing substantial damage to the airplane. The pilot reported, "I pulled up sharply, but clipped the tops of the trees, the airspeed was still at 115 MPH IAS [Indicated Airspeed] with 12+ degrees nose up, and the airplane climbing rapidly. I then looked at the GPS [Global Positioning System] ground speed read out, and realized that it was at 140 KTS [Knots]. After assessing things, it became obvious that airspeed was not reading correctly." The pilot stated, "I had a problem six weeks ago with a mud dauber wasp building a nest in the pitot tube, but this had been cleared out, and the aircraft flown several times since."

NTSB Probable Cause

altitude/clearance from the trees not being obtained/maintained by the pilot. Factors to the accident were the trees and the contamination of the pitot/static system.

Full Narrative

On November 26, 2000, at 1000 central standard time, an Aerostar PA-60-601P, N713HM, owned and operated by a commercial pilot sustained substantial damage during an in-flight collision with trees during initial climb from runway 28 (4000 feet by 75 feet, ice-covered/asphalt) at the Fillmore County Airport, Preston, Minnesota. Instrument meteorological conditions prevailed at the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 and was on an instrument flight rules (IFR) flight plan. The pilot and his sole passenger reported no injuries. The flight was originating at the time of the accident and the pilot performed a precautionary landing at the Quad City International Airport, Moline, Illinois, subsequent to the in-flight collision with the trees. According to the pilot's written statement, "I initiated the takeoff, on runway 28 accelerated to 100 MPH, rotated & lifted off. The gear and flaps were raised, and the aircraft stopped accelerating at about 112-115 MPH. I lowered the nose to pick up some speed, but it still wouldn't accelerate. I could see the trees approaching west of the airport & knew I didn't have climb speed, but also knew there was no choice but to pull up & hope I didn't stall." The pilot reported, "I pulled up sharply, but clipped the tops of the trees, the airspeed was still at 115 MPH IAS [Indicated Airspeed] with 12+ degrees nose up, and the airplane climbing rapidly. I then looked at the GPS [Global Positioning System] ground speed read out, and realized that it was at 140 KTS [Knots]. After assessing things, it became obvious that airspeed was not reading correctly." The pilot reported that he requested to divert from his IFR flight plan and land at the Quad City International Airport, Moline, Illinois, to determine the extent of damage to the airplane. The pilot stated, "During the trip to Moline, the airspeed indicator stayed at 115 MPH for about 15 minutes then pegged out at the back side of the "0" indication, and stayed there for a few minutes and came back to 160 KTS. My GPS was showing about 170 KTS at 7000 ft during the trip." The pilot reported, "I had a problem six weeks ago with a mud dauber wasp building a nest in the pitot tube, but this had been cleared out, and the aircraft flown several times since."

Flight

Event TypeAccident
Event Time10:00 CST
Nearest AirportFilmore County Airport (0nm)
Runway28
Runway Length4000 ft
Runway Width75 ft
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAerostar PA-60-601P
Tail NumberN713HM
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · IO-540-S1A5 · Reciprocating · 290
Seats7

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 57 · Third Class

Conditions

ConditionsIMC
LightDaylight
Wind320° @ 6 kt
Visibility0.2 sm
Ceiling100 ft
Temperature / Dew Point70 F
Altimeter29.00 inHg
Observation Time15:54
Weather SourceWFAC

Appendix: Source Data