What happened
On 12 March 2022, an Alliance Air flight traveling from Delhi to Jabalpur experienced a serious incident during landing at Jabalpur Airport. The ATR-72-212A, registration VT-AIW, was performing a scheduled approach to Runway 24. As the aircraft crossed the runway threshold, it was approximately 60 feet above the ground and traveling at a speed significantly higher than the target approach speed.
The aircraft entered a prolonged float period lasting roughly 19 seconds. This resulted in a late touchdown more than halfway down the runway, followed by a bounce. The aircraft eventually made a second contact with the runway approximately 1600 meters from the start of the pavement, leaving only about 400 meters of runway available for braking. During the deceleration phase, the aircraft deviated from the centerline and exited the paved surface, entering the Runway End Safety Area (RESA). The aircraft eventually came to a halt 60 meters ahead of the runway end. There were no injuries among the 55 passengers or the crew, though the aircraft sustained damage to its landing gear and runway lights.
The investigation
AAIB India examined the flight data, cockpit voice recordings, and aircraft components to determine the sequence of events. The investigation focused on the approach stability, the crew's performance, and the airline's monitoring capabilities. Investigators analyzed the flight data recorder (DFDR) and cockpit voice recorder (CVR) to assess the pilot's inputs and the aircraft's flight parameters during the final approach and touchdown phases.
Findings
- The approach was unstabilized, as the indicated airspeed remained significantly above the target speed throughout the descent.
- The crew performed an inappropriate flare and delayed the retardation of power levers to flight idle, which contributed to the long float.
- The crew failed to initiate a go-around despite the landing no longer being safe.
- There was a lack of necessary call-outs from the pilot monitoring regarding deviations in flight parameters.
- The airline had failed to provide corrective training or feedback to the pilot in command, who had been involved in several high-severity long flare instances in the days preceding the incident.
- The airline's flight data monitoring software had limitations that prevented the timely identification of these flight parameter deviations.
Safety action
- The airline should implement comprehensive monitoring of all flight parameters defined in its safety manual to provide timely feedback and training.
- The airline should review its flight data monitoring parameters to include the tracking of inappropriate flares and delayed power lever retardation.
- Pilots should be reminded of the necessity of adhering to stabilized approach criteria and the importance of proper briefing and call-out procedures.