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

March 14, 1996 · Cessna 172L · N7668G

Napa, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 14, 1996
Injury Outcomes
No injuries (2 uninjured)
Location
Napa, CA
Aircraft
Cessna 172L
Tail Number
N7668G
Operator
Vintage Flyers
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX96LA134

The pilot of the Cessna 172L, N7668G, was cleared to enter right traffic. He had been instructed to report entering downwind and to watch for other aircraft in the pattern. When he did not report entering downwind as requested, the tower operator saw the collision course and told him to turn downwind, advising him of the traffic. At the same time he was preparing to turn downwind he saw another aircraft already in the pattern. He immediately initiated a turn to avoid a collision; however, a few seconds later he felt a bang on the tail of the aircraft. The pilot of the Cessna 172M, N20858, had been on downwind when he saw the other aircraft approaching from his left. He turned and dove his aircraft to avoid a collision, but within a few seconds felt a bump. After the collision both aircraft landed without incident. Neither pilot reported seeing the other until they were within a few hundred feet of each other.

NTSB Probable Cause

the failure of both pilots to see and avoid the other aircraft, and the failure of the pilot of the Cessna 172L, N7668G, to follow VFR procedures by not yielding the right of way to the Cessna 172M, N20858, which was already established in the traffic pattern.

Full Narrative

On March 14, 1996, at 1328 hours Pacific standard time, a Cessna 172L, N7668G, collided in flight with a Cessna 172M, N20858, while entering the traffic pattern at the Napa County airport, Napa, California. After colliding, each aircraft continued on its approach and landed without further incident. Each aircraft sustained substantial damage; however, neither pilot was injured. Each aircraft was being operated as a personnel flight, N7668G, by the pilot/owner, and N20858, by Vintage Flyers, Inc. Visual meteorological conditions prevailed. No flight plan was filed for N7668G; however, a VFR flight plan was filed for N20858. The flight of N7668G originated from Petaluma, California, earlier that day, while the flight of N20858 originated from Napa about 1321. According to the pilot of N7668G, he reported over Schelleville and was cleared to enter right traffic for runway 18R. He was told to report entering downwind for runway 18R and to watch for other aircraft in the pattern. He was on a 45-degree entry preparing to turn downwind when he saw another aircraft 200 to 300 feet to his right. He turned left and asked the tower ". . .how this airplane got there. . . ." The tower operator directed him to turn left. He replied that he ". . .already had. . ." and was continuing to do so when a few seconds later he felt a bang on the tail of his aircraft. He notified the tower of the collision and was asked to confirm the accident in reply. He replied "Affirmative, I got hit." The pilot was able to maintain control of the aircraft after the collision and was cleared to land without further incident. The pilot of N20858 stated that he was established in the pattern, turning downwind for runway 18R, when he saw the other aircraft about 100 feet away approaching directly from his left. He made a hard right turn and dove the aircraft attempting to avoid a collision, but felt a bump a few seconds later. After the collision the pilot called the tower operator and reported the accident. The pilot was asked to verify that there had been a collision and was then cleared to land without further incident. A transcript of the air-to-ground communications tapes at the Napa air traffic control tower (ATCT) was reviewed. The tower operator cleared N7668G for right traffic on runway 18R and to report entering downwind. He advised the pilot that there were two Cessnas in the pattern, which the pilot acknowledged. The aircraft did not report entering downwind as requested. Just before the collision occurred the local controller instructed the pilot of N7668G to "turn downwind now." He also advised him that his traffic was a Cessna to his right. The pilot's reply was ". . .right next to me. . . ." The tower operator called to verify that the pilot had been involved in a collision and then cleared him to land without further incident. (A transcript from the Napa ATCT tape is appended to this report.) A postaccident inspection of the aircraft revealed damage to the leading and lower side of the left wing tip of N20858. There was also damage to the outboard trailing edge portion of the right elevator and horizontal stabilizer of N7668G.

Flight

Event TypeAccident
Event Time13:28 PST
Nearest AirportNapa County (0nm W)
Runway18R
Runway Length5931 ft
Runway Width150 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172L
Tail NumberN7668G
Aircraft CategoryAir
DamageSubstantial
OperatorVintage Flyers
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E2D · Reciprocating · 150 | Lycoming · O-320-E2D · Reciprocating · 150
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind190° @ 8 kt
Visibility50 sm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter30.00 inHg
Observation Time21:30
Weather SourceWFAC

Appendix: Source Data