# Accident 20021124034979A: Beech B36TC, Unioncity, CA, November 24, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 24, 2002, 18:00 local time
- Place: Unioncity, CA
- Damage: Destroyed
- Operating rules: General operating rules (Part 91)
- Location: 37.6364° N, 121.9781° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.6364&lon=-121.9781&mi=10
- Aircraft: N3242Q, a cancelled registration (https://openairdocs.org/deregistered/N3242Q-2004-08-26) (OpenAirDocs)
- Registry model: Beech B36TC (registry code 1151609, https://openairdocs.org/model/beech-b36tc) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: BEECH B36TC
- People aboard: 1
- Fatal injuries: 1
- NTSB investigation: [NTSB LAX03FA037](https://openairdocs.org/ntsb/LAX03FA037) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20021124034979A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE AIRCRAFT WAS ON APPROACH TO THE PALO ALTO AIRPORT, ABOUT 12.4 NAUTICAL MILES AWAY, WHEN IT COLLIDED WITH RISING TERRAIN AT APPROXIMATELY 1,600 FEET ELEVATION, THREE MILES NORTH OF UNION CITY, CA. THE CRASH OCCURRED DURING THE NIGHT AND THE AIRCRAFT WAS DESTROYED BY IMPACT AND POST CRASH FIRE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX03FA037](https://openairdocs.org/ntsb/LAX03FA037), Nov 25, 2002: Beech B36TC (N3242Q), Union City, CA, destroyed, 1 fatal. 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…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.