ASN Wikibase Occurrence # 357149
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 30 June 1996 |
Time: | 11:30 LT |
Type: | Cessna 172 |
Owner/operator: | Private |
Registration: | N6819H |
MSN: | 172-65595 |
Total airframe hrs: | 3465 hours |
Engine model: | Lycoming O-320-E2D |
Fatalities: | Fatalities: 0 / Occupants: 2 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | Frazier Park, CA -
United States of America
|
Phase: | Unknown |
Nature: | Private |
Departure airport: | Tehachapi, CA (KTSP) |
Destination airport: | |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The pilot entered a left traffic pattern to land on the dirt strip. He touched down long and elected to go-around. The terrain off the departure end of the dirt runway rose gradually. The pilot used full power and retracted the flaps from full down to an intermediate setting. He then began a left turn airplane to fly downslope and increase the airplane's height above the ground. While in the turn, the airplane struck wires and crashed. The density altitude was about 8,000 feet msl.
Probable Cause: the failure of the pilot to maintain terrain clearance after a misjudged approach and landing that necessitated a go-around and subsequent collision with some wires. Factors were high density altitude and an inadequate evaluation by the pilot-in-command of the weather conditions.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | LAX96LA255 |
Status: | Investigation completed |
Duration: | 5 months |
Download report: | Final report |
|
Sources:
NTSB LAX96LA255
Location
Revision history:
Date/time | Contributor | Updates |
13-Mar-2024 14:49 |
ASN Update Bot |
Added |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation