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

December 13, 1999 · Piper PA-28-180 · N41910

Mankato, MN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
December 13, 1999
Injury Outcomes
2 injuries (2 minor injuries)
Location
Mankato, MN
Aircraft
Piper PA-28-180
Tail Number
N41910
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI00LA041

The airplane collided with trees while landing at night. An on scene examination of the aircraft found no anomalies that could be associated with a preexisting condition. In his written statement, the pilot listed no mechanical malfunction. The pilot stated that he '... was experiencing the classic optical illusion of thinking I was closer to the approach end of the runway, than I actually was.' The pilot stated that the accident could have been prevented by receiving additional night dual instruction and a visual approach slope indicator (VASI) on runway 22. According to the Airport/Facility Directory (A/FD), runway 22 has a VASI system that is activated using the aircraft radio tuned to the airport common traffic advisory frequency (CTAF). According to a statement from the airport manager, three flight instructors that operated aircraft during the late afternoon and early evening on the day of the accident were contacted. All three flight instructors indicated that the VASI lights were operational at the time of their flights. On the day following the accident, the airport maintenance manager conducted a daily inspection and determined that the VASI system was operational and in working order.

NTSB Probable Cause

the pilots failure to maintain a proper glidepath. Factors were the dark night and the pilots lack of recent night flying experience.

Full Narrative

On December 12, 1999, at 1800 central standard time, a Piper PA-28-180, N41910, piloted by a private pilot, sustained substantial damage after colliding with trees while landing on runway 22 (3,999 feet by 75 feet, dry/asphalt) at the Mankato Municipal Airport (MKT), Mankato, Minnesota. The 14 CFR Part 91 personal flight was not operating on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The pilot and his one passenger received minor injuries. The flight departed from the L J Bose Airstrip, Orleans, Nebraska, at 1455, and was en route to MKT. The Federal Aviation Administration conducted an on scene examination of the aircraft and found no anomalies that could be associated with a preexisting condition. In his written statement, the pilot listed no mechanical malfunction. In a written statement, the pilot stated that he "...remained at 150 feet above ground level until I felt we needed to expedite our descent to make the runway. Position calls were made at downwind entry, and upon turning final. My only explanation is that I was experiencing the classic optical illusion of thinking I was closer to the approach end of the runway, than I actually was. As the landing light had been turned on during the downwind leg, we saw the tree top just before we hit it." The pilot stated, in his written statement, that the accident could have been prevented by receiving additional night dual instruction and a visual approach slope indicator (VASI) on runway 22. According to the Airport/Facility Directory (A/FD), runway 22 has a VASI system that is activated using the aircraft radio tuned to the airport common traffic advisory frequency (CTAF). According to a statement from the airport manager, three flight instructors that operated aircraft during the late afternoon and early evening on the day of the accident were contacted. All three flight instructors indicated that the VASI lights were operational at the time of their flights. On the day following the accident, the airport maintenance manager conducted a daily inspection and determined that the VASI system was operational and in working order.

Flight

Event TypeAccident
Event Time18:00 CST
Nearest Airport0nm
Runway22
Runway Length3999 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-180
Tail NumberN41910
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4A · Reciprocating · 180
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 44 · Third Class

Conditions

ConditionsVMC
LightDark Night
Wind220° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point39 C / 0 C
Altimeter29.00 inHg
Weather SourcePILO

Appendix: Source Data