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

October 2, 1998 · Cessna 152 · N957AF

San Jose, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 2, 1998
Injury Outcomes
1 injury (1 minor injury)
Location
San Jose, CA
Aircraft
Cessna 152
Tail Number
N957AF
Operator
Interwings
Injuries
Minor
Aircraft Damage
Destroyed
NTSB Number
LAX99LA002

The aircraft collided with mountainous terrain about 3,000 feet msl while descending from 4,500 feet toward the destination airport on a dark night. Weather reports showed consistent overcast cloud bases of 2,800 feet in the immediate area of the accident site. A review of the ATC tape revealed that the pilot did not clearly state his intentions when speaking with air traffic control. ATC had to ask him several times what he said and told him that they did not understand him. Interviews conducted with ATC controllers revealed that they were unsure exactly what the pilot intentions were other than to land at Reed Hillview airport. Weather in the area was deteriorating and ATC was in the process of sequencing traffic for IFR approaches into nearby airports. At one point ATC asked the pilot if he was going to find a hole and descend. The pilot stated affirmative. When radio and radar contact was lost, the controller asked a police helicopter flying near the last observed position to search for the airplane that had disappeared off the radar. The helicopter pilot told the controller that he was unable to proceed to the location due to clouds obscuring the ridges. The pilot stated he could hear a helicopter above him but could not see it because of poor visibility.

NTSB Probable Cause

Continued VFR flight by the pilot into instrument meteorological conditions (IMC) at night over mountainous terrain. The pilot's use of unclear language when stating his intentions to air traffic control was a factor.

Full Narrative

On October 1, 1998, at 2013 hours Pacific daylight time, a Cessna 152, N957AF, collided with mountainous terrain approximately 4.8 miles north of Reed Hillview Airport, San Jose, California. The airplane was destroyed and the private pilot, the sole occupant, sustained minor injuries. The pilot reported the accident at 0800 the following morning. Instrument meteorological conditions existed at the at the accident site at the time of the accident. The aircraft was operated by Wings International of San Jose and rented by the pilot for the cross-country personal flight under the provisions of 14 CFR Part 91 of the Federal Aviation Regulations. The 1950 official aviation surface observations at the San Jose International Airport (8 miles west of the accident site) and the Reid-Hillview airport included overcast sky conditions at 2,800 feet. The Santa Clara Sheriff's Office reported that there was a heavy overcast with a 1,500-foot base the next morning when they located the wreckage. The accident site was on the side of a hill at the 3,000-foot elevation. The pilot was initially interviewed over the telephone by Safety Board investigators shortly after he had reached a nearby farm house located near the crash site. The pilot told investigators that he hit a downdraft, which forced him into the ground. He stated that he had power and full fuel tanks. He said that there was no problem with the engine. He stated that he had departed San Jose airport about 1900, performed a touch-and-go at Oakdale Airport, and was returning to Reed HillView Airport when the accident occurred. The Federal Aviation Administration (FAA) interviewed the pilot 4 days after the accident. According to the FAA Aviation Safety Inspector who conducted the interview, the pilot said he was in the vicinity of the Sunol Pass, heading 190 degrees at 4,500 feet, when Bay Tracon "told" him he should turn left to 180 degrees and that he could begin his descent from 4,500 feet. The pilot said he could see the lights on the ground in front of him, and that there were a "few" clouds between him and the ground. He stated he never went into the clouds, and would have maneuvered around the clouds in his descent, had he deemed it necessary to maintain visual flight rules (VFR). He said he was not completely comfortable with Bay Tracon's 180-degree heading, in that he thought the heading would take him toward the mountains rather than away, but he complied with the their instruction. The pilot said he began his descent and shortly thereafter entered the "downdraft." He said he felt the downdraft and saw on the vertical speed indicator first a 400-feet-per-minute descent, and then later a 700-feet-per-minute descent. He said that he then saw the ground approaching, applied full power, and pitched the nose up in an attempt to avoid the terrain. He said the airplane impacted the terrain, rolled left on the ground, and slid backwards and down the mountain for a distance. He said that the airplane came to rest inverted, the wings supported by the sides of the narrow ravine. He was able to force the door open and climb out. He then began walking for help. At one point, he said he could hear a helicopter above him, but that he could not see it "because of the poor visibility." The pilot eventually came to a house and called "911" for help. Safety Board investigators reviewed personnel statements received from the FAA Bay Terminal Radar Approach controllers who were working the accident aircraft. The controller who was talking with the pilot asked him what his intentions were and he responded that he "intended to land at Reid Hillview Airport (RHV)." The controller, in his written statement, replied "I then asked him if he was going to find a hole for his descent," and he responded with "affirmative." Safety Board investigators listened to a working copy of the ATC tapes with the air traffic controller working the AR-2 position from 0242 to 0250 hours UTC, and the air traffic controller working the DR-3 position from 0249 to 0300 hours UTC. The following is a synopsis of the air traffic control tape. During discussions with the accident aircraft, other traffic including 14 CFR Part 121 scheduled airlines were being sequenced into the Bay area for IFR approaches. A complete copy of the ATC tape is appended to this report. ATC controller working position AR-2: 957AAF, altimeter 30.03, Quebec current at Reed Hillview Airport. ATC: 7AF radar service terminated. Pilot of 7AF: unintelligible ATC: Didn't understand, say that again. Pilot of 7AF: unintelligible ATC: Still didn't understand, say that again. ATC: 7AF, you're below MVA (minimum vectoring altitude,) suggest a heading of about 200 degrees. ATC: Below MVA, Sir, suggest heading of 200 degrees for Reed Hill View. Radar service terminated, squawk 1200. Frequency change approved, good day. 7AF: Can get Bay Approach on 121.21? ATC: 7AF stand by, remain this frequency. ATC: 7AF, contact approach 121.3. 7AF: 7AF, 121.3? ATC interphone: 7AF, I don't know what he wants...he wanted radar vectors, he was down at 4,300 feet. Response, Ok, I'll take care of him 7AF: Cessna 7AF with you at 4,500. ATC position DR-3: Cessna 957AF, roger. What are your intentions now? 7AF: going to land at Reed Hill View Airport. ATC: Ok, are you going to find a hole and descend? 7AF: Roger. ATC: 7AF, radar contact lost. What is your altitude now? ATC: Cessna 957AF, radar contact lost. Say your altitude. ATC interphone: Reed Hill View (RHV), Saratoga. RHV: Reed Hill View ATC interphone: Are you talking to 957AF? RHV: Negative, I'm not talking to anybody. ATC: Let me know when you do, ok? RHV: 957AF? ATC: Yeah, he's about 5 north of you. I lost him on radar and he's trying to descend down through a hole or something... RHV: Oh God! I don't see any holes! Ok, I'll keep my eye out for him and call you as soon as I hear anything. ATC: Ok then. ATC: 957AF, Bay ATC: 957AF, Bay Approach According to the written statements provided by the controllers who were working the accident airplane, one controller said the controller who was talking with the pilot of the accident airplane notified him that radar and radio contact had been lost. This controller asked a police helicopter flying near the last observed position to search for the airplane that had disappeared off the radar. The helicopter pilot told the controller that he was unable to proceed to the location because of weather. The FAA inspector informed Safety Board investigators that the pilot had been preparing for his commercial pilot certificate at the time of the accident. The pilot "insisted" on taking his checkride in the days immediately following the accident. The pilot passed the oral portion of the checkride, but "dismally" failed the flying portion of the examination. The FAA also stated that the pilot was scheduled to depart from the United States en route to his home country within days of the crash.

Flight

Event TypeAccident
Event Time20:13 PDT
Nearest Airport0nm
Runway0
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 152
Tail NumberN957AF
Aircraft CategoryAir
DamageDestroyed
OperatorInterwings
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-235-L2C · Reciprocating · 118
Seats2

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 22 · Second Class

Conditions

ConditionsIMC
LightDark Night
Wind340° @ 10 kt
Visibility10 sm
CeilingOvercast 2800 ft
Temperature / Dew Point59 / 54
Altimeter30.00 inHg
Observation Time02:53
Weather SourceWFAC

Appendix: Source Data