FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA037 · Beech B36TC

24 Nov 2002 · Union City, CA, United States

Beech B36TC · Accident: in flight collision with terrain/water on approach

From Ontario Municipal Airport (ONO) to Palo Alto Airport (PAO)

Report a problem

Event

NTSB case
LAX03FA037
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech B36TC

Aircraft type
Beechcraft 36
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3242Q
Operator
Robert A. Dowlett · private individual
Onboard fatalities
Unknown
Route
From Ontario Municipal Airport (ONO), Ontario, ORTo Palo Alto Airport (PAO), Palo Alto, CA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight collision with terrain/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane collided with rising mountainous terrain while descending toward the destination during a dark, nighttime VFR approach to the airport about 12 miles south of the accident site. The pilot had requested and was receiving radar flight following service, but he had not requested minimum safe altitude warnings, and that service was not provided. At 1752:55, the pilot contacted the TRACON radar facility and told the controller he was descending out of 5,800 feet inbound to the airport. The controller told the pilot to fly his own navigation to the airport and to maintain VFR. The controller terminated radar flight following service about 1 minute prior to the accident. The airplane was last recorded on radar at 1759:30. At this time, its ground speed had decreased to about 130 knots, its altitude had decreased to 1,700 feet, and the airplane's ground track was about 167 degrees, magnetic. Two ground witnesses were about 1/3 mile from the crash site and reported observing the accident airplane fly by their position; however, their view of the airplane was restricted due to the presence of localized fog, and they had only observed the illumination of the airplane's flashing white strobe light as it flew past their location. Minutes later, they observed the glow of a ground fire in the direction the airplane had been flying. The three closest airports to the accident site that reported their weather conditions were, respectively, 7 miles west-southwest, 8 miles northeast, and 12 miles south-southwest from the accident site. Within 15 minutes of the accident, these three airports reported a clear sky, 5- to 10-mile visibility, and surface wind between 6 and 7 knots. At 1755, the closest airport, which was northeast of the accident site, reported 5 miles visibility, mist, and a temperature/dew point of 9 and 8 degrees, respectively. The on-scene accident investigation revealed that the airplane cruised into 28-degree upsloping terrain, and it was destroyed by impact forces and a post impact fire. The initial impact point was at 1,660 feet mean sea level (msl), about 60 feet below the hilltop south of the site. The bearing between the initial impact point and the main wreckage was 163 degrees. No evidence of a preimpact mechanical malfunction was found during the wreckage examination. The Safety Board investigator noted that when located on the hilltop south of the impact site, the pilot's destination was visible. No higher elevation exists between the accident site hilltop and the airport.

Probable cause

the pilot's failure to maintain an adequate terrain clearance altitude, which resulted in controlled flight into rising mountainous terrain. Contributing factors were the pilot's loss of situational awareness to his terrain proximity, the dark night, and the localized low clouds that obscured the terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA037
Event ID
20021213X05606
Case number
LAX03FA037
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-11-25.
  • API snapshot SHA-256: 13cf10f56a80a005aa7e151d93623d863ec653b7fdacf3dc24ee3b60762391aa; retrieved 2026-09-20T19:37:52.260Z.