ASN Wikibase Occurrence # 288237
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: | Thursday 5 August 2010 |
| Time: | 16:14 LT |
| Type: |  Cessna 172 |
| Owner/operator: | |
| Registration: | N9730H |
| MSN: | 17266338 |
| Year of manufacture: | 1975 |
| Total airframe hrs: | 12444 hours |
| Engine model: | Lycoming O-320 |
| Fatalities: | Fatalities: 0 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Roche Harbor, Washington -
 United States of America
|
| Phase: | Initial climb |
| Nature: | Private |
| Departure airport: | Roche Harbor, WA (WA09) |
| Oak Harbor-Whidbey Island Naval Air Station, WA (KNUW) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot departed from an uphill runway, with 10 to 15 degrees of flaps extended for takeoff, which was contrary to the manufacturer's guidance in the Pilot Operating Handbook (POH). The pilot stated that after liftoff, while trying to achieve and maintain an appropriate airspeed, the airplane encountered a downdraft, and he then heard a 'pop†that he believed to be an engine problem. The airplane struck trees and terrain about 1,500 feet from the departure end of the runway, and incurred substantial damage to the wings and fuselage. Two separate post accident examinations, including a brief engine run, did not reveal any anomalies that would have precluded normal engine operation, and propeller cuts to tree limbs at the accident site indicated that the engine was developing power. According to the pilot, he selected the departure direction based on his observation of a windsock nearest the runway threshold. He had flown into the airport about 10 times previously, and was aware the runway sloped uphill and that there were trees about 1,000 feet beyond the departure end.
The lack of an airport wind information recording system precluded determination of the wind conditions at the time of the accident, but calculations based on wind direction and speed information from the three weather observation stations nearest the accident site yielded values that ranged from a 4-knot headwind to an 8-knot tailwind. The POH stated that normal and obstacle clearance takeoffs were to be performed with wing flaps retracted, and specified the use of takeoff flaps only for soft or rough fields. The operator developed checklist used by the pilot did not include any specific guidance on the use of flaps for takeoff. The performance data in the POH did not enable a takeoff distance calculation that accounted for the runway slope or the use of flaps; calculations that used the available POH data indicated that with a tailwind of 8 knots, about 2,000 feet were required to clear a 50-foot obstacle. The accident site terrain elevation was approximately 100 feet higher than the departure threshold, and the trees at the site were approximately 50 feet tall.
Probable Cause: The pilot's failure to attain an adequate climb airspeed due to his use of flaps for takeoff, and his selection of a runway, which resulted in an uphill, and possibly downwind, takeoff and subsequent collision with a known obstacle. Contributing to the accident was the operator's cockpit checklist that did not accurately reflect the manufacturer's takeoff procedures.
Accident investigation:
 |
|
Sources:
NTSB WPR10FA384
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 04-Oct-2022 19:53 | 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