Runway excursion Serious incident Airbus A321-112 I-BIXK,
ASN logo
ASN Wikibase Occurrence # 351835
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 9 April 2007
Time:22:40
Type:Silhouette image of generic A321 model; specific model in this crash may look slightly different    
Airbus A321-112
Owner/operator:Alitalia
Registration: I-BIXK
MSN: 1220
Year of manufacture:2000
Total airframe hrs:16790 hours
Cycles:10912 flights
Engine model:CFMI CFM56-5B2
Fatalities:Fatalities: 0 / Occupants:
Aircraft damage: Minor
Category:Serious incident
Location:Napoli Airport (NAP/LIRN) -   Italy
Phase: Landing
Nature:Passenger - Scheduled
Departure airport:Milano-Malpensa Airport (MXP/LIMC)
Destination airport:Napoli Airport (NAP/LIRN)
Investigating agency: ANSV
Confidence Rating: Accident investigation report completed and information captured
Narrative:
Alitalia flight AZ1295, an Airbus A321-112, suffered a runway excursion during landing at Napoli.
After landing on runway 24, a braking system failure occurred that prevented a rapid deceleration. After having covered the entire length of the runway, at a residual speed of about 40/50 knots, the pilot directed the aircraft to the left of the runway, exited onto the bordering grass, performed a wide left turn and finally re-entered the same runway, but in the opposite direction.
The aircraft finally came to a halt, when the parking brake was applied, without any further problems.

CAUSE
The event was triggered by a malfunction of the BSCU, related to the intermittent failure of one of its components. This failure, which occurred at different times in the two channels, created a complex operational scenario that resulted in a loss of braking action alternated with A/SKID engaged. In this context, the following factors should be highlighted:
- The use of the term "should" in the "BSCU RESET" procedure may have led the crew to not consider the application of the RESET procedure obligatory with the landing gear retracted;
- The indication of a fault in the autobrake system immediately after landing, even though the system was deactivated;
- The indication of pressure on the triple indicator confirming the transition from normal braking system operation to alternate braking system operation;
- The crew's failure to apply the memory maneuvers of the "LOSS OF BRAKING" procedure.
All these factors created a situation not foreseen by the procedures in the operational manual, leading the crew to make decisions using their own logical deductive process.

Accident investigation:
cover
  
Investigating agency: ANSV
Report number: 
Status: Investigation completed
Duration:
Download report: Final report

Sources:

ANSV

Revision history:

Date/timeContributorUpdates
21-Feb-2024 13:05 ASN Added
21-Feb-2024 13:06 ASN Updated [Departure airport]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org