What happened
During a night approach under instrument meteorological conditions, the flight crew was performing an instrument landing system (ILS) approach. Although air traffic control notified the crew that weather conditions had dropped below minimums, the pilots chose to proceed because the aircraft type was stabilized and within the final approach fix. Both pilots reported seeing the runway approach lighting at the 200 ft decision altitude.
As the approach continued, the first officer transitioned back to instrument flying. The captain noted that the aircraft was drifting to the right of the runway centerline. The first officer subsequently expressed discomfort with the deteriorating visibility and attempted to initiate a go-around by pressing the takeoff and go-around switch, while the captain simultaneously called for the same maneuver.
While the crew believed the go-around began between 50 and 100 ft above ground level, flight data indicated the autopilot-coupled approach continued down to 50 ft agl, which violated procedure as coupled approaches were not permitted below 240 ft agl. As the aircraft descended between 30 and 20 ft agl, the captain issued multiple commands to flare and noted the continued rightward drift. A delay of three seconds occurred before the first officer attempted to transfer control to the captain. The captain did not take command and instead called for a go-around. The first officer applied full power and commanded flaps to 15 degrees, but the aircraft struck the ground approximately five seconds later, causing substantial damage to the fuselage. No mechanical or engine anomalies were identified.
Findings
- The approach likely became unstabilized following the disconnection of the autopilot and the loss of visual contact with the runway environment.
- The captain delayed the command for a go-around after the aircraft had already become unstabilized, leaving insufficient altitude for a successful recovery.