Fatal accident · Indonesia
Garuda Indonesia Airbus A300 crash near Medan, North Sumatra, kills 234
Garuda Indonesia Flight 152, an Airbus A300-B4 registered PK-GAI, crashed in a wooded, mountainous area near Buah Nabar, North Sumatra, on 26 September 1997 while approaching Medan. All 234 people on board died, 222 passengers and 12 crew. Indonesia's National Transportation Safety Committee investigated and classed it as controlled flight into terrain.
This is one of 19 Garuda Indonesia Airlines fatal accidents on record. See also all plane crashes in 1997.
What happened to Flight 152 on approach to Medan
Garuda Indonesia Flight 152 was a scheduled passenger service from Soekarno-Hatta International Airport in Jakarta to Polonia Airport in Medan. On 26 September 1997 the Airbus A300-B4 crashed in a mountainous, wooded area near Buah Nabar, about 20 miles from Medan. The site is also described as near Pancur Batu, Deli Serdang.
The aircraft was on approach to Polonia and was being radar vectored for an instrument landing system approach. It never reached the runway. All 222 passengers and 12 crew died, and there were no survivors. The exact local time of the crash has not been confirmed in the sources available.
Smoke and haze reduced visibility around Medan
On the day of the Garuda Indonesia crash near Medan, smoke and haze from regional forest fires reduced visibility and obscured the mountainous terrain around the approach path, according to reports on the investigation. The aircraft was flying in those conditions as it was vectored toward the airport.
Exact figures for visibility, cloud base and wind have not been confirmed. Haze did not cause the aircraft to lose control, since the investigation found it was under control until impact. For background on how conditions figure in accidents, see weather-related crashes.
A wrong-way turn and a descent below 2,000 feet
The summary of the final report on the Airbus A300 PK-GAI crash says the crew became confused about the direction of a turn during radar vectoring. They turned left when a right turn was expected. Their attention was on the lateral changes in heading, and that reduced their awareness of height.
The aircraft kept descending below its assigned altitude of 2,000 feet. It struck treetops at about 1,550 feet above mean sea level, in terrain well short of the airport. Nothing in the available material describes a mechanical emergency before impact.
What the National Transportation Safety Committee concluded
Indonesia's National Transportation Safety Committee, known as KNKT and in older English references as the NTSC, investigated the crash near Buah Nabar. Its final report is titled Garuda Indonesia Flight GA 152, Airbus A300-B4, PK-GAI, Buahnabar, Sumatera Utara, Indonesia, 26 September 1997. The investigation is closed.
The report classes the accident as controlled flight into terrain, meaning the aircraft was under control until it hit the ground. Contributing factors listed in the summary were:
- Inadequate vectoring charts or procedures used by air traffic control.
- Difficulties linked to the crew's familiarity with different A300 cockpit configurations.
- A ground proximity warning system failure, the cause of which was not determined.
The NTSB appears in the record only for comments on an NTSC draft, not as lead investigator. See how investigators determine the cause and what probable cause means.
Why the ground proximity warning failure matters
In the Garuda Indonesia Flight 152 crash, the ground proximity warning system is the one safeguard the report singles out as having failed. Such a system is meant to warn a crew when the aircraft is too close to terrain. The NTSC summary says the cause of the failure was not determined, so it is not known whether a working warning would have changed the outcome.
The other listed factors concern the human and procedural side. Vectoring charts or procedures used by controllers were judged inadequate, and the crew's familiarity with different A300 cockpit configurations was a difficulty. The summary does not rank these factors against each other. For a general explanation of this kind of accident, see why planes crash.
The aircraft, its engines and the two pilots
Garuda Indonesia Flight 152 was flown by an Airbus A300-B4-220, PK-GAI, powered by two Pratt & Whitney JT9D-59A engines. The aircraft was delivered in 1982, which made it about 15 years old at the time of the crash near Buah Nabar. The NTSC figures put its airframe at roughly 27,095 flight hours and 16,593 cycles. A secondary account gives rounder numbers, more than 27,000 hours and more than 16,500 cycles.
The report copy lists total engine cycles of 11,711 and 10,829, with the engines installed on aircraft that had about 25,567 and 26,533 hours. Damage history and earlier repairs are not covered in the material available, so none is given.
The captain was Hance Rachmo Wiyogo, 41, with about 11,978 total flight hours and 782 hours on type. The first officer, Tata Zuwaldi, was also 41 and had 709 hours on type. Secondary summaries say he had been a flight engineer and had recently moved up to pilot. The report table records no flying in the 24 hours before the accident for either pilot. In the preceding seven days the captain had flown 16.5 hours and the first officer 4.35 hours.
What the Medan ATIS and cockpit recording show about visibility
Before Garuda Indonesia Flight 152 reached Medan, the airport's weather broadcast already described very poor conditions. A published cockpit voice recorder transcript has the ATIS reporting calm surface wind, visibility 400 metres and smoke. At about 13:04:14 local time the broadcast said, "Visibility four hundred meter. Present weather: smoke." Around 13:06 a radio exchange again discussed the poor visual weather, with the sky not visible because of smoke.
Another summary describes visibility across the wider region as about 600 to 800 metres. That differs from the 400 metre figure at Medan itself, and the Medan figure is the one given in the transcript. The dominant problem was smoke on an instrument approach, not ordinary low cloud.
The transcript also covers the approach communications, the crew's response to the turn instruction and the alarmed exclamations at the end. It is a secondary publication, not the full NTSC appendix, so individual words, timestamps and speaker identifications have not been checked against the official recording record. The sources do not give a verified minute-by-minute timeline, an impact time or a rescue timeline. Nationality figures for the 234 people on board have also not been published in the material available.
Ten recommendations from a report issued in 2004
The NTSC final report on the Flight 152 crash near Buah Nabar was issued in 2004, several years after the accident. It went beyond the crew's turn error. It also named shortcomings in Garuda's training for a mixed fleet, since pilots flew both A300-600 aircraft with digital displays and A300-B4 aircraft with older analogue instruments. The report linked the captain's unfamiliarity with the analogue presentation to the workload problem.
Its recommendations included:
- Reinforcing compliance with flight-crew standard operating procedures.
- Ensuring dispatch and flight release met CASR Part 121, Subpart U.
- Reviewing radar-vectoring approaches to Polonia from the south.
- Setting radar rotational speed in line with ICAO Annex 10.
- Installing a Minimum Safe Altitude Warning System at Medan.
- Considering a full parallel taxiway at Polonia.
- Reinforcing controller phraseology training and recurrent training, including simulator practice for emergencies.
- Carrying out ground proximity warning checks according to maintenance instructions, and making the functional check mandatory where Airbus service bulletin 34-0121 had not been incorporated.
The material available does not show which of these were implemented, or when. It also does not show a redesign or a worldwide airworthiness directive caused by this accident. See preliminary vs final accident report for how such reports differ.
Responsibility, a dismissed lawsuit and no later inquiry
After the Garuda Indonesia Flight 152 crash, the NTSC spread its findings across the flight crew, Garuda's training system, Medan air traffic services and aircraft system maintenance. It did not treat the event as one person's error. No formal dissenting report from Airbus, Garuda or any government has been documented. Early press coverage, including the New York Times on 27 September 1997, described haze and pilot error as possibilities pending investigation, not as findings.
A U.S. lawsuit, Coyle v. P.T. Garuda Indonesia, was dismissed. The court held that it lacked jurisdiction over a domestic Indonesian flight operated by a foreign government-owned airline. No final judgment on the merits against Garuda in the United States has been found. Court awards, settlement amounts, insurer payments and any claims involving Airbus, Pratt & Whitney or air traffic authorities have not been made public in the material available.
No official memorial at Buah Nabar has been verified. The 2004 report is the main later development. No reopened investigation, new recorder evidence or superseding report is documented.
Aircraft record and earlier accidents
The Airbus A300-B4 registered PK-GAI is described in sources as an A300-B4-200 or A300B4-220. A photograph captioned as showing it at Denpasar in 1988 exists, but it does not point to an earlier accident. The airframe age has not been confirmed.
No verified list of earlier Garuda Indonesia or A300 accidents is available in the sources used, so none is given here. For wider context, see airline safety records.
Questions people ask about this accident
What happened to Garuda Indonesia Flight 152?
Garuda Indonesia Flight 152, an Airbus A300-B4, flew into terrain near Buah Nabar, North Sumatra, on 26 September 1997 while approaching Medan. All 234 on board died.
How many people died in the Garuda Flight 152 crash?
All 234 people on board the Airbus A300 died, 222 passengers and 12 crew. No survivors were reported and no ground fatalities have been identified.
Where did Garuda Indonesia Flight 152 crash?
It crashed in a mountainous, wooded area near Buah Nabar, North Sumatra, about 20 miles from Medan's Polonia Airport.
What caused the Garuda Indonesia Flight 152 crash?
Indonesia's NTSC classed it as controlled flight into terrain. The crew was confused about a turn direction during radar vectoring and the aircraft descended below its assigned 2,000 feet.
Did weather play a role in the Garuda Flight 152 crash?
Smoke and haze from forest fires reduced visibility near Medan, according to reports on the investigation. Exact weather values have not been confirmed.
Who investigated the Garuda Flight 152 crash?
Indonesia's National Transportation Safety Committee, known as KNKT or NTSC, investigated and published a final report on the Airbus A300 PK-GAI accident.
What route was Garuda Flight 152 flying?
The Airbus A300-B4 was flying from Soekarno-Hatta International Airport in Jakarta to Polonia Airport in Medan.
What is controlled flight into terrain?
It means a serviceable aircraft under crew control flies into the ground or obstacles, usually without the crew realizing the danger. The NTSC used this classification for Garuda Flight 152.
Related accidents
10 killed- 189 killed
- 122 killed, 19 on the ground
- 112 killed, 2 on the ground
- 102 killed
Correct this page or send a photo
Spotted a wrong date, registration or number? Have a photo of the aircraft or the site that you took yourself? Send it here. Nothing is published until an editor has checked it.