Overview
• Operator: SriLankan Airlines
• Aircraft Model: Airbus A330-200
• Registration: 4R-ALS
• Flight Number: UL-226
• Route: Dubai (United Arab Emirates) → Colombo (Sri Lanka)
• Date: 8 July 2024
• Occupants: Not specified
• Incident Type: Temporary Runway Excursion on Landing
Incident Summary
SriLankan Airlines flight UL-226, operated by an Airbus A330-200 (4R-ALS), was on approach to Colombo Bandaranaike International Airport (VCBI) when it experienced a runway excursion during landing on runway 22. The aircraft veered left off the runway before the crew regained control and brought it back onto the centreline. The aircraft slowed safely and taxied to the apron without further issues.
A post-landing inspection revealed significant damage to four left main landing gear (MLG) tyres, and four runway edge lights were found damaged. The incident was not reported by the flight crew, and it was only detected during routine maintenance checks.
Sri Lanka’s Civil Aviation Authority (CAA) launched an investigation, classifying the occurrence as a serious incident. On 13 February 2025, the CAA released its final report, identifying pilot error, poor situational awareness, and failure to initiate a go-around as the primary causes of the incident.
Sequence of Events
Final Approach & Touchdown
• The aircraft was stabilised on approach with the autopilot engaged until 390 feet RA.
• The First Officer (FO) manually took control but began applying left roll inputs, causing a deviation from the runway centreline.
• At 20 feet RA, the FO attempted to correct the leftward drift using rudder input instead of roll input, which was not the appropriate technique for lateral deviation correction.
• The aircraft touched down 250m after the threshold with the left main landing gear outside the runway surface and the right main landing gear still on the runway.
Runway Excursion & Recovery
• The aircraft continued drifting left, crossing the runway edge.
• It returned fully to the runway at 700m after touchdown and realigned with the centreline at 900m after touchdown.
• The flight crew did not report the incident, believing it was a normal landing.
Investigation Findings
Primary Cause
• The flight crew’s decision to land despite significant lateral deviation and failure to initiate a go-around.
Contributing Factors
1. Pilot Handling Errors
• Incorrect control inputs: The FO applied rudder instead of roll to correct drift, worsening the deviation.
• Poor crosswind technique: The crew mismanaged the crosswind reversal, leading to unstable alignment.
2. Poor Situational Awareness & Decision Making
• Lack of leadership from the Captain (PM): The PIC failed to intervene despite clear signs of deviation.
• Cognitive biases: The crew’s continuation bias led them to persist with landing instead of executing a go-around.
3. Failure to Execute a Go-Around
• Airbus procedures recommend that if an aircraft is unstabilised or misaligned, a go-around should be initiated.
• Simulator tests confirmed that a go-around could have been executed safely and effectively at any point before touchdown.
4. Crew Resource Management (CRM) Failures
• Poor communication: The Captain did not call out the deviation or advise corrective action.
• Lack of assertiveness: Neither pilot considered aborting the landing despite clear visual cues of misalignment.
5. Failure to Report the Incident
• The flight crew did not report the excursion, delaying corrective safety actions.
• Similar issues were noted in a previous SriLankan Airlines incident in 2019, indicating a systemic issue with safety reporting.
Safety Recommendations & Preventative Measures
1. Improve Flight Crew Training on Crosswind Landings
• Reinforce correct control techniques: Pilots should use roll inputs, not rudder, for lateral deviation correction.
• Emphasise decision-making under pressure, ensuring pilots prioritise a go-around when necessary.
2. Enhance Situational Awareness & CRM Training
• PICs must assert leadership and intervene early in unstabilised approaches.
• Promote a “go-around mindset”, where pilots are encouraged to abandon landings if alignment is poor.
3. Mandatory Reporting of Unusual Landings
• Implement strict reporting procedures for all runway excursions, regardless of severity.
• Ensure pilots understand their responsibility to report any deviations for safety analysis.
4. Strengthen Air Traffic Control (ATC) Weather Communication
• ATC should provide real-time updates on significant changes in wind conditions.
• Improve coordination between ATC and flight crew during challenging landing conditions.
5. Improve Post-Incident Runway Inspection Procedures
• Conduct thorough inspections for foreign object debris (FOD) after any suspected runway excursion.
• Ensure accurate information transmission between maintenance, ATC, and ground operations to facilitate timely responses.
Disclaimer
This report is based on available information as of 13 February 2025. While every effort has been made to ensure accuracy, the completeness of the details cannot be guaranteed. If you are the rightful owner of any referenced materials and wish them removed, please email takedown@cockpitking.com.
