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

February 22, 2011 · Piper PA-31P-350 · N9237Y

North Bend, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 22, 2011
Injury Outcomes
No injuries (1 uninjured)
Location
North Bend, OR
Aircraft
Piper PA-31P-350
Tail Number
N9237Y
Operator
Eal Leasing
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR11CA142

According to the pilot, while in the process of executing a terminal instrument approach to his home airport, he transitioned from instrument meteorological conditions to visual meteorological conditions. He canceled his instrument flight rules clearance, and transitioned from the terminal instrument approach to a visual flight rules approach pattern. During this sequence of events he did not follow a written checklist, and inadvertently forgot to lower the landing gear. During the landing flare, he heard the noise caused by the wing flaps and both propellers contacting the surface of the runway, and he added power and immediately executed a go-around. He then entered a closed pattern, lowered the landing gear and repositioned the flaps, before making an uneventful landing. He said during the approach he heard the gear warning horn sounding, but he thought it was the altitude alerting system. An inspection of both the runway surface scarring and each propeller blade revealed that the tips of all six blades had been grounded down by repeated contact with the asphalt surface. He also said that the airplane did not have any system malfunctions.

NTSB Probable Cause

The pilot's failure to lower the landing gear while on approach to landing. Contributing to the accident was the pilot's failure to follow a written checklist during the approach portion of the flight.

Full Narrative

According to the pilot, while in the process of executing a terminal instrument approach to his home airport, he transitioned from instrument meteorological conditions (IMC) to visual meteorological conditions (VMC). He therefore canceled his instrument flight rules (IFR) clearance, and transitioned from the terminal instrument approach to a visual flight rules (VFR) approach pattern. During this sequence of events, the pilot, who was not following a written checklist, inadvertently forgot to lower the landing gear. During the landing flare, the pilot heard the noise caused by the wing flaps and both propellers contacting the surface of the runway, and therefore he added power and immediately executed a go-around. The pilot then entered a closed pattern, lowered the landing gear and repositioned the flaps, before making an uneventful landing. According to the pilot, during his approach he heard the gear warning horn sounding, but he thought it was the altitude alerting system. An inspection of both the runway surface scarring and each propeller blade revealed that the tips of all six blades had been ground down by repeated contact with the asphalt surface. The pilot also said that the airplane did not have any system malfunctions.

Flight

Event TypeAccident
Event Time13:00 PST
Nearest AirportSouthwest Oregon Regional (0nm)
Runway31
Runway Length4470 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-31P-350
Tail NumberN9237Y
Aircraft CategoryAir
DamageSubstantial
OperatorEal Leasing
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540-V2AD · Reciprocating · 350
Seats7

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 49 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind300° @ 10 kt, gusting 18 kt
Visibility10 sm
CeilingOvercast 3500 ft
Temperature / Dew Point45 C / 34 C
Altimeter30.21 inHg
Weather SourcePILO

Appendix: Source Data