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 5, 1994 · Cessna 175 · N7597M

Oakdale, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 5, 1994
Injury Outcomes
No injuries (3 uninjured)
Location
Oakdale, CA
Aircraft
Cessna 175
Tail Number
N7597M
Operator
Jerry Hansen
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX94LA113

Both aircraft were landing on runway 10 when they collided on the approach end of the runway. The pilot of the Cessna (N7597M) said he called on the CTAF on downwind, base, and final. He said the Piper called 3,000 feet over the airport for a practice engine out landing, but then he heard no further transmissions. The CFI on the Piper (N6171J) said they were going to do a simulated engine out emergency landing from 3,000 feet. He said he called his position and intentions on the CTAF, heard a Cessna in the traffic pattern, and looked for that aircraft. He saw a Cessna on final and planned to follow it. The CFI said the Cessna was turning off the runway as they were flaring when the collision occurred. The FBO UNICOM operator heard both aircraft. The Cessna pilot called on downwind, base, and final. The Piper pilot called once, when the aircraft was 3,000 feet over the airport. The Piper struck the Cessna from above and behind.

NTSB Probable Cause

the pilot of the other aircraft's failure to maintain an adequate visual lookout, and his failure to adequately communicate his postion and intentions on the Common Traffic Advisory Frequency. A factor in the accident was the pilot of the other aircraft's misidentification of the Cessna aircraft he was to follow in the pattern.

Full Narrative

On February 5, 1994, at 1130 hours Pacific standard time, a Cessna 175, N7597M, and a Piper PA28-235, N6171J, collided on the runway while landing at the Oakdale, California, airport. Both aircraft were in the traffic pattern and landing on runway 10 when they collided near the approach end of the runway. Visual meteorological conditions prevailed at the time of the accident and included a visibility of 5 miles in haze. Both aircraft incurred substantial damage. The Cessna 175 was on a local area personal flight which had originated from the Oakdale airport about 1100 hours. The certificated private pilot, the sole occupant, was not injured. The Piper PA28-235 was on a local area dual instructional flight which had originated from the Oakdale airport about 1030 hours. The certificated commercial pilot flight instructor and the dual primary student were not injured. The pilot of the Cessna 175 stated that he departed the airport on a local proficiency flight, and then returned to the traffic pattern to practice takeoffs and landings. According to the pilot, he announced on the CTAF frequency of 122.8 his intentions and made broadcasts on downwind, base, and final approach. He stated that he heard the Piper call from over the airport at 3,000 feet AGL for a practice engine out approach and landing. The pilot noted that he did not hear any further transmissions from the Piper. The pilot reported that he was just touching down on the approach end of the runway when he felt a jolt to his aircraft, then saw the Piper come down directly in front of his aircraft. Both aircraft then skidded to a stop on the runway. The instructor on the Piper PA28-235 stated in a telephone interview that his student was being prepared for his private pilot check ride. After takeoff, they departed the traffic pattern, performed some airwork, then arrived over the airport at about 3,000 feet AGL. The instructor said that he wanted the student to demonstrate a simulated engine out emergency approach and landing. He reported that he announced his position and intentions on the CTAF frequency of 122.8, then began the procedure. He stated that he recalled hearing a Cessna report in the traffic pattern and began looking for the aircraft. The instructor said that by the time the student had arrived at the key position, he spotted a Cessna on final approach and they planned to follow that aircraft. The instructor noted that the Cessna he was following was just starting to turn off the runway as they began to flare for landing. According to the instructor, he felt a "normal landing touchdown" on the runway, then the aircraft was skidding sideways through a ball of fire and came to a stop entangled with a Cessna aircraft. The UNICOM radio operator at the airport's fixed base operator stated that he heard both aircraft. The Cessna pilot transmitted his position and intentions while on downwind, base, and final approach. The Piper pilot transmitted his position and intentions only once when the aircraft was 3,000 feet over the airport. Airport personnel reported that they examined both aircraft. The damage to the Cessna 175 consisted of black rubber and blue paint transfers to the vertical stabilizer, rudder, top of the fuselage, and the upper surface of the wings. The left wing sustained slashes in the area of the fuel cell. The damage to the Piper was confined to the nose gear, lower engine cowling, and the bottom of the wings. The Piper paint scheme included blue paint trim on the wheel fairings.

Flight

Event TypeAccident
Event Time11:30 PST
Nearest AirportOAKDALE (0nm)
Runway10
Runway Length3020 ft
Runway Width66 ft
Flight Plan FiledNone
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftCessna 175
Tail NumberN7597M
Aircraft CategoryAir
DamageSubstantial
OperatorJerry Hansen
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · GO-300A · Reciprocating · 175 | Lycoming · O-540-B4B5 · Reciprocating · 235
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 64 · Third Class
Crew 2Age 47 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind10° @ 5 kt
Visibility5 sm
CeilingNone
Temperature / Dew Point55 / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data