What happened
On September 9, 2021, a Cessna 402C, registration N88833, was operating a scheduled Part 135 flight from Boston-Logan International Airport to Provincetown Municipal Airport. The flight was conducted in instrument meteorological conditions (IMC) characterized by heavy rain and low ceilings.
As the aircraft approached runway 7, the pilot executed an ILS approach. While the pilot reported encountering a downdraft that prompted an immediate go-around, airport surveillance cameras captured a different sequence: the aircraft made a normal landing approximately 500 feet from the runway threshold. Due to heavy rain and an 11-knot tailwind, the aircraft failed to decelerate sufficiently. Late in the landing roll, the pilot initiated a go-around. The aircraft became airborne again near the end of the runway, entered a shallow climb, and collided with a cluster of trees approximately 660 feet beyond the runway perimeter. The impact caused the aircraft to catch fire.
There were 7 occupants on board, including the pilot and six passengers. All seven sustained 7 serious injuries, specifically extensive burns, soft tissue damage, and bone fractures, but there were 0 fatalities.
The investigation
An investigation into the wreckage and flight data revealed that the aircraft's approach became unstabilized when the sink rate exceeded 1,000 feet per minute at 400 feet MSL. While the pilot believed the approach was unstable due to a downdraft, the operator's manual required an immediate missed approach once the sink rate exceeded that threshold.
Performance studies using ADS-B data and video analysis showed the aircraft touched down at a calibrated airspeed approximately 18 knots faster than the speed assumed in the airplane's flight manual. The combination of this high touchdown speed and the reduced braking friction of the wet runway significantly increased the required stopping distance. Calculations indicated that if the pilot had continued to decelerate rather than attempting to accelerate for a go-around, the aircraft likely would have stopped within or just beyond the runway limits.
Findings
- The pilot made a delayed decision to abort the landing late in the landing roll with insufficient runway remaining.
- The approach became unstabilized due to a sink rate exceeding 1,000 feet per minute, and the pilot failed to execute a go-around per company procedures.
- The aircraft landed with a significant tailwind component that had increased during the approach.
- The wet runway surface reduced the effectiveness of braking and increased the required landing distance.