Accident Briefs: May 2018

Reports from the NTSB

Are you an aviation enthusiast or pilot?Sign up for our newsletter, full of tips, reviews and more!

These are official summaries from the NTSB. They are printed in their entirety and verbatim.

Stinson SR 5E

No injuries

Burlington, Washington

The pilot of the amphibious, float-equipped airplane reported that, 2 days before a repositioning flight, he inspected the destination airport. He had planned to land on an alternate grass landing area, adjacent to an asphalt runway, and stop before reaching a gravel driveway. He further reported that he noticed in the airport facility directory (AFD) that the intended landing area was closed due to soft, wet conditions.

The pilot reported that, during landing, he was "high and fast." He further reported that he landed "too far along to stop before the gravel drive." The airplane reached the gravel driveway, bounced, and then landed hard, and nosed over.

The airplane sustained substantial damage to the left wing.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

The AFD for the accident airport, in part, stated: "[Alternate Grass Landing Area (AGLA)]: AGLA clsd 1 Nov-1 June. Gnd soft when wet. [Daylight] hrs only. Use of AGLA prohibited when Rwy 04-22 in use!.Pilots use at own risk."

Probable Cause: The pilot's unstabilized approach, which resulted in a hard, bounced landing and nose-over. Also causal to the accident was the pilot's improper decision to land on a closed alternate grass landing area.


Aeronca 65 CA

1 Fatal

Mount Vernon, Ohio

The private pilot prepared to hand-prop the airplane, which was not equipped with an electrical starter, by tying the tail down with a nylon rope. The pilot then hand-propped the engine, which started at a high power setting. The airplane moved forward, breaking the rope, and continued to taxi in circles. The pilot and another individual tried to stop the airplane; however, the propeller struck the pilot, resulting in fatal injuries. The airplane eventually came to stop farther down the runway. Although the pilot attempted to secure the airplane by tying down the tail, the throttle was set at a high engine power setting, allowing the airplane's movement.

Probable Cause: The pilot's improper starting procedure before hand propping the engine, and his subsequent attempt to stop the moving airplane, which resulted in him being struck by the propeller.


Cessna 340

2 Fatal

Tampa, Florida

The airline transport pilot and pilot-rated passenger were departing on an instrument flight rules (IFR) cross country flight from runway 4 in a Cessna 340A about the same time that a private pilot and pilot-rated passenger were departing on a visual flight rules repositioning flight from runway 36 in a Cessna 172M. Visual meteorological conditions prevailed at the airport. The runways at the nontowered airport converged and intersected near their departure ends. According to a witness, both airplanes had announced their takeoff intentions on the airport's common traffic advisory frequency (CTAF), which was not recorded; the Cessna 340A pilot's transmission occurred about 10 to 15 seconds before the Cessna 172M pilot's transmission. However, the witness stated that the Cessna 172M pilot's transmission was not clear, but he was distracted at the time. Both occupants of the Cessna 172M later reported that they were constantly monitoring the CTAF but did not hear the transmission from the Cessna 340A pilot nor did they see any inbound or outbound aircraft. Airport video that captured the takeoffs revealed that the Cessna 172M had just lifted off and was over runway 36 approaching the intersection with runway 4, when the Cessna 340A was just above runway 4 in a wings level attitude with the landing gear extended and approaching the intersection with runway 36. Almost immediately, the Cessna 340A then began a climbing left turn with an increasing bank angle while the Cessna 172M continued straight ahead. The Cessna 340A then rolled inverted and impacted the ground in a nose-low and left-wing-low attitude. The Cessna 172M, which was not damaged, continued to its destination and landed uneventfully. The Cessna 340A was likely being flown at the published takeoff and climb speed of 93 knots indicated airspeed (KIAS). The published stall speed for the airplane in a 40° bank was 93 KIAS, and, when the airplane reached that bank angle, it likely exceeded the critical angle of attack and entered an aerodynamic stall. Examination of the Cessna 340A wreckage did not reveal any preimpact mechanical malfunctions that would have precluded normal operation. Because of a postcrash fire, no determination could be made as to how the radios and audio panel were configured for transmitting and receiving or what frequencies were selected. There were no reported discrepancies with the radios of the Cessna 172M, and there were no reported difficulties with the communication between the Cessna 340A and the Federal Aviation Administration facility that issued the airplane's IFR clearance. Additionally, there were no known issues related to the CTAF at the airport. Toxicological testing detected unquantified amounts of atorvastatin, diphenhydramine, and naproxen in the Cessna 340A pilot's liver. The Cessna 340A pilot's use of atorvastatin or naproxen would not have impaired his ability to hear the radio announcements, see the other airplane taking off on the Page 2 of 4 ERA16FA133 converging runway, or affected his performance once the threat had been detected. Without an available blood level of diphenhydramine, it could not be determined whether the drug was impairing or contributed to the circumstances of the accident.

Probable Cause: The intentional low altitude maneuvering during takeoff in response to a near-miss with an airplane departing from a converging runway, which resulted in an exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.

Subscribe to Our Newsletter

Get the latest Plane & Pilot Magazine stories delivered directly to your inbox

Subscribe to our newsletter