Aviation Accident Summaries

Aviation Accident Summary ERA18LA136

Barre Plains, MA, USA

Aircraft #1

N87266

CESSNA 402

Analysis

The private pilot was conducting a local, personal flight. The pilot reported that he checked the weather conditions at three local airports before the flight but stated that he did not trust the wind reports. He added that he did not get a preflight weather briefing. Once at the destination airport, he conducted two go-arounds due to gusting wind conditions. During the third attempted landing, he made a steep approach at a normal approach speed and flared the airplane about midway down the 3,000-ft-long runway. The airplane floated down the runway for much longer than the pilot expected before touching down. Despite applying maximum braking, there was insufficient remaining runway to stop, and the airplane skidded off the runway, impacted trees, and subsequently caught fire, which resulted in substantial damage to the airframe. The wind conditions reported at an airport located about 13 miles away included a tailwind of 16 knots, gusting to 27 knots. Given the tailwind conditions reported at this airport and the pilot's description of the approach and landing, it is likely that the pilot conducted the approach to the runway in a tailwind that significantly increased the airplane's groundspeed, which resulted in a touchdown with insufficient runway remaining to stop the airplane, even with maximum braking.

Factual Information

On April 26, 2018, about 1715 eastern daylight time, a Cessna 402B, N87266, was substantially damaged during landing at Tanner-Hiller Airport (8B5), Barre Plains, Massachusetts. The private pilot and two passengers were not injured. No flight plan was filed for the local personal flight that was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed at the time of the accident. The flight departed Dillant-Hopkins Airport (EEN), Keene, New Hampshire, about 1630.According to the pilot, he was trying to land at 8B5 in gusty wind conditions and performed two go-arounds prior to landing on runway 06. He said the wind was "bumpy" below the trees, and he made a steep approach to the runway "consistent with a short field landing." He flared about midfield, and the airplane continued to float down the runway. He stated the airplane "floated and floated much further down the runway than normal" even though he approached the runway at a "normal" airspeed of 95 knots and with full flaps. The airplane touched down and despite maximum braking, overran the departure end of runway 06, and impacted trees. The pilot and passengers egressed the airplane before a post-impact fire ensued. The pilot stated that he believed he encountered a wind rotor over the trees, which changed the direction of the wind to a quartering tailwind. He checked the weather at three surrounding airports, but he did not trust the wind reports. He did not get a weather briefing before the flight. A FAA inspector examined the airplane where it came to rest, about 300 ft past the end of the 3,027 ft-long runway. The left wing outboard of the left engine impacted trees. The left wingtip was separated, and the left horizontal stabilizer was damaged. All major components were accounted for at the scene and all flight controls were functional. According to FAA records, the pilot held a private pilot certificate with ratings for airplane single-engine and multi-engine land airplane. His most recent FAA third-class airman medical certificate was issued December 7, 2009. A review of the pilots logbooks revealed he had about 330 hours of total flight time flight time and 220 hours of multi-engine flight time. At 1654, the weather conditions reported at Worcester Regional Airport (ORH), about 13 miles southeast of 8B5, included wind from 270° at 16 knots gusting to 27 knots, visibility 10 statute miles, scattered clouds at 4,500 ft, temperature 14°C, dew point 4°C, and an altimeter setting of 29.70 inches of mercury.

Probable Cause and Findings

The pilot's improper decision to land with a tailwind, which resulted in a touchdown with insufficient runway remaining to stop the airplane.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports