ASN Wikibase Occurrence # 228567
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: | Tuesday 27 August 2019 |
| Time: | 18:35 LT |
| Type: |  Cessna 172 Skyhawk |
| Owner/operator: | Private |
| Registration: | N4108F |
| MSN: | 46008 |
| Year of manufacture: | 1958 |
| Total airframe hrs: | 4833 hours |
| Engine model: | Continental O-300-A |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near McKenzie Bridge State Airport (00S), OR -
 United States of America
|
| Phase: | Initial climb |
| Nature: | Private |
| Departure airport: | Lebanon, OR (S30) |
| Lebanon, OR (S30) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
After flying over mountainous terrain, the pilot attempted an approach into an airport with a 2,600-ft-long grass runway bordered by tall trees. Witnesses near the center of the runway described the airplane flying east over the runway about 5 ft above ground level when it came into their view. One witness stated that he could not hear any noise as the airplane came into view but that its wings rocked; he said he heard the engine power increasing and that the airplane may have started to climb when it reached his center of vision. A second witness stated that she heard the engine running and that the airplane began a slow climb and then disappeared from her view behind trees at a slightly higher altitude. About 15 minutes later, they saw smoke coming from the accident site. Impact signatures indicated that the airplane contacted treetops during the climbout; it then impacted the ground and came to rest inverted about 615 ft east of the departure end of the runway.
The witness statements support that the airplane was developing power when it began the climb. The propeller signatures were inconsistent with the engine producing power at the time of the impact; however, it is unknown if the pilot reduced power before impact. Rotational continuity of the engine and valve train could not be achieved because the engine crankcase and accessories were damaged by postcrash fire and the oil sump was destroyed. Although the crankshaft, camshaft, connecting rods, and piston were mostly damaged by postcrash fire, an examination of these components and the interior engine case revealed no indications of catastrophic engine failure.
Calculations based on takeoff and climb performance charts from the pilot's operating handbook showed that the airplane required a total takeoff distance of about 1,330 ft to clear a 50-ft obstacle at the end of the runway. However, the chart did not account for the 134 ft of rising terrain and 120-ft-tall trees at the end of the runway or the ambient temperature of about 98°F. The calculated density altitude on the day of the accident was 4,481 ft, which would have reduced the airplane's climb performance. Given these conditions, it is unlikely that the airplane was capable of clearing the rising terrain and tall trees at the end of the runway on the day of the accident.
Review of the pilot's logbook showed that he had not performed landings or takeoffs at mountain airports. Thus, he had insufficient experience to attempt a landing or takeoff at a short mountain airport runway bordered by trees on a day with a density altitude over 2,800 ft higher than the airport elevation. While it is unknown if the pilot had intended to perform a full-stop landing, a touch-and-go maneuver, or overfly the runway at a low altitude, he had selected a runway that was not recommended for takeoffs but was recommended for landing. The pilot likely misjudged the runway length needed and the airplane's performance when he chose to begin a climb about midfield in high density altitude conditions with rising terrain and 120-ft obstacles at the end of the runway.
Probable Cause: The pilot's delayed climb and misjudgment of the airplane's performance and the runway distance needed to clear obstacles at the end of the runway, which resulted in a collision with trees and subsequent impact with terrain. Contributing to the accident was the pilot's insufficient experience landing and taking off at mountain airports.
Accident investigation:
 |
|
Sources:
NTSB WPR19FA244
FAA register: https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=N4108F
https://flightaware.com/photos/view/8803265-e00f4ef95b08b91eef581f0d6f88b55a62699177/aircrafttype/PA31 (photo)
Location
Media:
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Aug-2019 06:27 | gerard57 | Added |
| 28-Aug-2019 07:13 | RobertMB | Updated [Location, Source, Narrative] |
| 28-Aug-2019 09:43 | Captain Adam | Updated [Operator, Phase, Departure airport, Narrative] |
| 28-Aug-2019 14:23 | Captain Adam | Updated [Aircraft type, Registration, Cn, Operator, Total fatalities, Total occupants, Phase, Source, Narrative] |
| 28-Aug-2019 14:26 | Geno | Updated [Time, Source] |
| 29-Aug-2019 11:58 | Iceman 29 | Updated [Source, Embed code] |
| 08-Jul-2022 12:22 | ASN Update Bot | Updated [Time, Other fatalities, Departure airport, Destination airport, Source, Narrative, Category, Accident report] |
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