Casualties unknown

2011-12-26: Boeing 737-500 (PK-MDT) — Merpati Nusantara Airlines — Sultan Hasanuddin International Airport, Makassar, ID

Sultan Hasanuddin International Airport, Makassar, ID

On December 26, 2011, a Boeing 737-500 (registration PK-MDT) operated by Merpati Nusantara Airlines was involved in an aviation accident near Sultan Hasanuddin International Airport, Makassar, ID. Investigators recorded the probable cause as: The decision to continue the approach and land the aircraft was influenced by the pilot’s expectation that the aircraft condition would stabilise prior to landing. The pilot did not have sufficient directional control after touchdown. This summary draws on records from the Indonesian National Transportation Safety Committee (KNKT); 16 related events involving the same aircraft type or operator are linked below.

Sourcesthe Indonesian National Transportation Safety Committee (KNKT)Primary reportUpdated 1785107694Data APIEditorial standards
Boeing 737-500
Photo: San Diego Air & Space Museum Archives / Public domain, via Wikimedia Commons

On 26 December 2011, a Merpati Nusantara Boeing 737-500 veered right off runway 13 after landing at Sultan Hasanuddin International Airport, striking a taxi signboard and rolling on the shoulder before returning to the runway. No injuries occurred.

Summary

On 26 December 2011, a Boeing 737-500 aircraft, registered PK-MDT, operated by PT. Merpati Nusantara Airline as scheduled passenger flight MZ 755, experienced a runway excursion after landing at Sultan Hasanuddin International Airport, Makassar, Indonesia. The aircraft departed from Sam Ratulangi Airport, Manado at 0910 UTC with 64 persons on board: two pilots, four cabin crew, and 58 passengers. The flight proceeded without technical abnormalities.

Factual Information

History of the Flight

At 1009 UTC, the crew contacted Makassar Approach Control. The controller vectored the aircraft to fly direct to MKS VOR for an ILS approach to runway 03. At 1021 UTC, the crew requested and received approval to land on runway 13. At 1033 UTC, the crew was advised to contact Hasanuddin Tower, which issued a landing clearance and noted the runway was wet. At 1034 UTC, the aircraft established on the localizer of runway 13. At approximately 1036 UTC, at 550 feet radio altitude, the Pilot Flying (PF) felt uncomfortable with rain and suggested a go-around. The Pilot in Command (PIC) stated the runway was in sight and took over control. At 1038 UTC, the aircraft landed and veered to the right, hitting a taxi signboard and rolling on the shoulder for about 375 meters before returning to the runway. The tower controller instructed the crew to taxi to the apron. No injuries were reported.

Personal Information

The PIC, aged 42, held an Airline Transport Pilot License and had 1,339 hours total flying time, including 440 hours on type. The SIC, aged 23, held a Commercial Pilot License and was in line training to become a First Officer, with 188 hours total flying time.

Aircraft Information

The aircraft was a Boeing 737-500, registration PK-MDT. No technical or system abnormalities were reported or recorded during the flight.

Weather Information

During the approach, weather conditions included rain and a thunderstorm. The wind was from 140° at 6 to 10 knots. The runway was wet.

Damage to Aircraft

The right engine cowl was damaged. The aircraft also struck a taxi signboard.

Other Damage

Runway lights and the taxiway alpha signboard were broken.

Analysis

The investigation determined that the decision to continue the approach and land the aircraft was influenced by the pilot’s expectation that the aircraft condition would stabilise prior to landing. After touchdown, the pilot did not have sufficient directional control.

Conclusions

Findings

  • The aircraft was landed on a wet runway during rain and thunderstorm conditions.
  • At 550 feet radio altitude, the PF suggested a go-around due to discomfort with rain, but the PIC continued the approach.
  • After touchdown, the aircraft veered off the runway to the right.

Contributing Factors

1. The decision to continue the approach and land the aircraft was influenced by the pilot’s expectation that the aircraft condition would stabilise prior to landing. 2. The pilot did not have sufficient directional control after touchdown.

Safety Actions

The operator had ceased operations since January 2014. The KNKT recommended that the DGCA review the unstabilised approach procedure and include considerations for unstabilised approaches when crossing the runway threshold and for directional control after touchdown.

Probable cause

The decision to continue the approach and land the aircraft was influenced by the pilot’s expectation that the aircraft condition would stabilise prior to landing. The pilot did not have sufficient directional control after touchdown.