ASN Wikibase Occurrence # 385380
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: | Wednesday 4 October 2000 |
| Time: | 09:31 LT |
| Type: |  Cessna 182S |
| Owner/operator: | Dragonfly Aviation, Inc. |
| Registration: | N2373D |
| MSN: | 18280621 |
| Year of manufacture: | 1999 |
| Total airframe hrs: | 228 hours |
| Engine model: | Lycoming IO-540-AB1A5 |
| Fatalities: | Fatalities: / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Santa Rosa, CA -
 United States of America
|
| Phase: | En route |
| Nature: | Executive |
| Departure airport: | Santa Rosa, CA (KSTS) |
| Concord, CA (KCCR) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
During initial climb in instrument meteorological conditions, the pilot failed to maintain directional control and altitude. The airplane entered a right descending spiral until impacting terrain 2 miles west of the airport. In accordance with the instrument departure procedure, the pilot had taken off from runway 19, elevation 125 feet msl, under a 600-foot overcast sky condition. Thereafter, the pilot commenced a right climbing turn. The pilot reported climbing through 1,100 feet and 1,600 feet msl, and the radar controller informed the pilot that he was not receiving the airplane's mode C transponder signal. The radar controller then observed one radar hit and then lost contact with the airplane. All recorded radar data from the area around the airport at the time of the accident was reviewed. The FAA indicated that this location had only one long-range radar site that covered the area below 5,000 feet. When the recorded radar data was filtered to search for targets within a 10 nm radius around the airport and up to 5,000 feet, the subject airplane was only observed one time on a transponder code of 3311. The target had an invalid Mode C code at that time, with no radar reinforcement. The approximate distance and bearing from the end of runway 19 to this first radar hit, was 2.3 nm and 261 degrees, magnetic. The approximate distance and bearing from the radar hit to the crash site was 0.6 nm and 042 degrees, magnetic. Based upon a subsequent examination of the radar data showing all targets, three additional non Mode C transponder (primary) targets were located. The positions of these targets were noted southwest of the airport, at the following times: 0929:22, 0929:58, and 0930:22. The calculated ground speed between these hits and the previously identified Mode C target was, respectively, 75, 131, and 163 knots. During the subsequent airframe and engine examination, no evidence of any mechanical failure or malfunction was found. However, neither the artificial horizon nor the directional gyroscope were recovered from the 50-foot deep pond. During the wreckage examination, the airframe was found accordioned in an aft direction, and the wings were fragmented. Evidence was found that could document the pilot's instrument flying currency and familiarity with the make and model airplane.
Probable Cause: the pilot's loss of airplane control due to spatial disorientation. A related factor was the low ceiling.
Accident investigation:
 |
|
Sources:
NTSB LAX01FA003
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 04-Apr-2024 17:59 | ASN Update Bot | Added |
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