ASN Wikibase Occurrence # 45353
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Sunday 24 November 2002 |
| Time: | 18:00 |
| Type: |  Beechcraft B36TC Bonanza |
| Owner/operator: | Private |
| Registration: | N3242Q |
| MSN: | EA-405 |
| Year of manufacture: | 1984 |
| Total airframe hrs: | 2253 hours |
| Engine model: | Continental TSIO-520-UB |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Union City, CA -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Ontario, OR (ONO) |
| Palo Alto, CA (PAO) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20021213X05606&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 09-Dec-2017 18:00 | ASN Update Bot | Updated [Operator, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation