ASN Aircraft accident Airbus A320-214 RP-C3222 Bacolod Airport (BCD)
ASN logo

Status:Accident investigation report completed and information captured
Date:Sunday 22 March 1998
Type:Silhouette image of generic A320 model; specific model in this crash may look slightly different
Airbus A320-214
Operator:Philippine Air Lines
Registration: RP-C3222
MSN: 708
First flight: 1997
Total airframe hrs:1224
Engines: 2 CFMI CFM56-5B4
Crew:Fatalities: 0 / Occupants: 6
Passengers:Fatalities: 0 / Occupants: 124
Total:Fatalities: 0 / Occupants: 130
Ground casualties:Fatalities: 3
Aircraft damage: Damaged beyond repair
Location:Bacolod Airport (BCD) (   Philippines)
Phase: Landing (LDG)
Nature:Domestic Scheduled Passenger
Departure airport:Manila International Airport (MNL/RPLL), Philippines
Destination airport:Bacolod Airport (BCD/RPVB), Philippines
Flight PR 137 was a regular scheduled passenger flight and departed Manila for Bacolod at 18:40. The airplane departed with the thrust reverser of engine no. 1 inoperative.
At 19:20, PR137 called Bacolod Approach Control and reported passing FL260 and 55 DME to Bacolod . The crew then requested landing instructions and was instructed to descend to FL90 after passing Iloilo and descend to 3,000 ft for a VOR runway 04 approach. Wind was 030° at 08 kts, altimeter 1014 mbs, transition level at FL60 and temperature at 28°C. At 19:28, the flight requested to intercept the final approach to runway 04 and Approach Control replied "PR 137 visual approach on final". At 19:37, Bacolod Tower cleared the flight to land at runway 04 and the clearance was acknowledged by the pilot.
The approach was flown with the Autothrust system was engaged in SPEED mode. The thrust lever of engine no.1 was left in Climb detent. Upon touchdown the first officer called out "no spoilers, no reverse, no decel". Engine no.2 was set to full reverse thrust after touchdown, but the engine no .1 thrust lever was not retarded to idle and remained in the climb power position. Consequently, the spoilers did not deploy.
Because one engine was set to reverse, the autothrust system automatically disengaged. With the autothrust disengaged, no. 1 engine thrust increased to climb thrust. Due to the asymmetrical thrust condition, the A320 ran off the right side of the runway. At this speed, rudder and nosewheel steering are ineffective. Engine no.2 was moved out of reverse up to more than 70 percent N1 and the airplane swerved back onto the runway. The A320 continued past the runway end. The aircraft hit the airport perimeter fence and then jumped over a small river. It continued to slice through a hallow block fence where it went through several clusters of shanties and trees. No fire ensued after the crash.

Probable Cause:

PROBABLE CAUSE: "The probable cause of this accident was the inability of the pilot flying to assess properly the situational condition of the aircraft immediately upon touch down with No. 1 engine reverse inoperative, thereby causing an adverse flight condition of extreme differential power application during the landing roll resulting in runway excursion and finally an overshoot.
Contributory to this accident is the apparent lack of technical systems knowledge and lack of appreciation of the disastrous effects of misinterpreting provisions and requirements of a Minimum Equipment List (MEL).

Runway excursion

» Aircraft Accident Report / Air Transportation Office (ATO)


photo of Airbus-A320-214-RP-C3222
accident date: 22-03-1998
type: Airbus A320-214
registration: RP-C3222
photo of Airbus-A320-214-RP-C3222
accident date: 22-03-1998
type: Airbus A320-214
registration: RP-C3222
photo of Airbus-A320-214-RP-C3222
accident date: 22-03-1998
type: Airbus A320-214
registration: RP-C3222
photo of Airbus-A320-214-RP-C3222
accident date: 22-03-1998
type: Airbus A320-214
registration: RP-C3222

This map shows the airport of departure and the intended destination of the flight. The line between the airports does not display the exact flight path.
Distance from Manila International Airport to Bacolod Airport as the crow flies is 475 km (297 miles).
Accident location: Exact; as reported in the official accident report.

This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages: languages


Airbus A320

  • 4751+ built
  • 6th loss
» safety profile

  • 71st worst accident (at the time)
  • 82nd worst accident (currently)
» safety profile

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