Raytheon Aircraft Company 390 N351CW accident near Naples, Florida

Probable cause

The pilot was unable to stop the airplane during the landing for reasons which could not be determined, resulting in a runway excursion.

NTSB analysis

The pilot stated that the flight was uneventful. During landing, he applied normal braking and the airplane started to slow down. Suddenly the brakes “faded away,” and he was unable to stop the airplane. He further described that he applied full braking pressure and the pedals were operating as they should, but the airplane was not stopping. He added that every few feet the brakes would grab, lock-up for a few feet, and then release. The brakes grabbed several times during the landing roll but were not slowing the airplane down. The airplane overran the end of the runway, and the pilot steered the airplane into the grass and away from a jet blast fence.

The anti-skid box, brake valve, anti-skid valve, and both wheel speed transducers were removed and sent to the manufacturer for bench testing. All the components passed the bench tests, and no anomalies were noted.

The airplane was not equipped with a flight data recorder. According to automatic dependent surveillance broadcast (ADS-B) data, the airplane landed about 8 knots higher than the Vref speed of 110 knots, with about 4,500 ft of runway remaining. According to the airplane flight manual, the airplane required about 3,000 ft for landing.

Based on the available evidence, the reason that the pilot was unable to stop the airplane on the runway could not be determined.

Text from the NTSB. Open the NTSB docket for ERA21LA350 for the full record.