ASN Wikibase Occurrence # 295072
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 19 October 2003 |
| Time: | 09:30 LT |
| Type: | Kolb Mark III |
| Owner/operator: | Private |
| Registration: | NONE |
| MSN: | 065 |
| Total airframe hrs: | 11 hours |
| Engine model: | Hirth F30 |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Prineville, Oregon -
 United States of America
|
| Phase: | Unknown |
| Nature: | Private |
| Departure airport: | Prineville, OR (S39) |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
This was only the second time that the pilot, who was conducting a series of evaluation flights on a recently built unregistered aircraft, had flown a pusher-type aircraft. During the first flight, he could not keep the aircraft from constantly porpoising, and that flight ended in an "exceedingly hard landing." During the accident flight, the pilot pulled onto the runway, applied power, and lifted off to a height of about five feet. He then immediately cut the power and landed straight ahead. Then, because he still had a lot of runway left, he attempted another liftoff. This time he allowed the aircraft's nose to pitch up significantly steeper than he wanted it to, and therefore the aircraft quickly climbed to a height of 10 to 20 feet above the runway. The pilot then "immediately cut the power" and the aircraft pitched to a steep nose down attitude, and made a "very hard landing." As the aircraft impacted the runway surface, the pilot accidentally "hit the throttle" and the aircraft lifted off a second time. The pilot therefore "...chopped the throttle" leading to the aircraft hitting "fairly hard" a second time. At that point, because he had been severely injured by the two impacts, the pilot was no longer able to make control inputs, so he "...let the aircraft run off the runway and stop on its own." There was no evidence of any problems with the flight controls, and there was no indication that there had been any other aircraft anomalies that would have contributed to the accident sequence.
Probable Cause: The pilot in command's failure to maintain aircraft control during an aborted takeoff. Factors include the pilot's lack of experience in this type of aircraft (pusher).
Accident investigation:
 |
|
Sources:
NTSB SEA04LA014
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 12-Oct-2022 17:38 | 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