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 19, 2001 · Piper PA-20-135 · N8901C

Redmond, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 19, 2001
Injury Outcomes
No injuries (2 uninjured)
Location
Redmond, OR
Aircraft
Piper PA-20-135
Tail Number
N8901C
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA01LA137

Upon arrival at Redmond, the pilot was instructed to enter traffic for runway 28. On his first landing attempt, he bounced "moderately" and decided to go around. He reported that on his second approach, winds had increased and were variable. He stated that on this approach, the flare and initial rollout went well but that "the continuing rollout swerved to the left and did not respond well to correction." The pilot therefore decided to go around again, stating in his accident report: "Although I was unsure at the time whether I made contact or avoided a runway light, evidence on the aircraft indicates that a contact did occur." The pilot reported that at this point, he contacted the tower and told them that he was having trouble with crosswind on runway 28. The control tower then offered runway 4. The pilot stated that on the third approach, "I placed the aircraft with good speed control at the center of the runway while holding against a moderate crosswind from the left", but that "Within a few feet...a crosswind (seemingly quartering tailwind) from the right lifted the right wing", and that the aircraft then "arced immediately to the left" and subsequently ground looped at low speed. The aircraft's tailwheel collapsed during the ground loop. The pilot stated that at the approximate time of the accident, "two windsocks were visible indicating moderately strong winds in 180 degree opposite directions on the same runway." According to a special weather observation taken at Redmond at 1310, winds were variable between 280 and 010 degrees true at 8 knots.

NTSB Probable Cause

The pilot's inadequate compensation for wind conditions during landing. A factor was variable winds.

Full Narrative

On July 19, 2001, approximately 1308 Pacific daylight time, a Piper PA-20-135 airplane, N8901C, was substantially damaged in a ground loop during landing on runway 4 at Roberts Field, Redmond, Oregon. The private pilot, whose application to register the aircraft in his name was pending with the FAA, and one passenger were not injured in the accident. Visual meteorological conditions were reported at Redmond in a special observation taken at 1310. The aircraft was on a visual flight rules (VFR) flight plan from Pullman, Washington, to Ashland, Oregon, and according to the pilot, the aircraft departed its last departure point of Pendleton, Oregon, about 1030. The pilot stated that upon arrival at Redmond, he was instructed to enter traffic for runway 28 (7,006 feet by 100 feet grooved asphalt, according to the U.S. Government Airport/Facility Directory [A/FD].) The pilot stated that on his first landing attempt, he "bounced moderately and decided to go around and re-land to work on better landing technique." He reported that on his second approach, winds had increased and were variable. He stated that on this approach, the flare and initial rollout went well but that "the continuing rollout swerved to the left and did not respond well to correction." The pilot stated that he therefore decided to go around again, and stated: "Although I was unsure at the time whether I made contact or avoided a runway light, evidence on the aircraft indicates that a contact did occur." The pilot reported that at this point, he contacted the tower and told them that he was having some trouble with crosswind on runway 28. The control tower then offered runway 4 (7,040 feet by 150 feet grooved asphalt, per the A/FD.) The pilot stated that on the third approach, "I placed the aircraft with good speed control at the center of the runway while holding against a moderate crosswind from the left." He reported that "Within a few feet, however, a crosswind (seemingly quartering tailwind) from the right lifted the right wing", and that the aircraft then "arced immediately to the left." The pilot stated that he believed he was holding full right rudder at this point, but that the plane did not respond, with differential braking being "initially impossible or ineffective as the plane was on left main gear only." He reported that "The plane slowed and did its final swing at a low rate of speed (8-10 mph)." He stated that the tailwheel then began castering and then collapsed to the left, stating that "A bolt holder on the side of a shackle caging the spring had failed with side-load." The pilot stated that at the approximate time of the accident, "two windsocks were visible indicating moderately strong winds in 180 degree opposite directions on the same runway." According to a special weather observation taken at Redmond at 1310, winds were variable between 280 and 010 degrees true at 8 knots.

Flight

Event TypeAccident
Event Time13:08 PDT
Nearest AirportRoberts Field (0nm)
Runway04
Runway Length7040 ft
Runway Width150 ft
Flight Plan FiledVFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-20-135
Tail NumberN8901C
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-290-D2 · Reciprocating · 135
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind8 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point45 C
Altimeter29.94 inHg
Observation Time20:10
Weather SourceWFAC

Appendix: Source Data