On July 14, 1982, a Singapore Airlines Boeing 747 flying from Singapore to Melbourne flew into ash from Mount Galunggung and lost power in three of its four engines. The crew restarted one engine and landed at Jakarta’s Halim International Airport.
It came roughly three weeks after the British Airways incident over the same volcano. The pairing of two near-identical events is what turned volcanic ash from an informal awareness problem into a formal international warning obligation — the system that produces today’s ash advisories and reroutes.
The British Airways 747 that lost all four engines over Indonesia in 1982 is the one everybody knows. It has a documentary, a famous mayday recording, and a permanent place in aviation-safety syllabuses. The Singapore Airlines 747 that flew into the same volcano’s ash roughly three weeks later has almost none of that.
That imbalance is the reason this article exists. The second case is the one that closed the argument — the evidence that made ash ingestion into a rule-making problem rather than a curiosity.
Before 1982, the industry pictured volcanic ash as an abrasion problem. Windscreens sandblasted. Pitot tubes clogged — damage that was cosmetic or confined to instruments.
The idea that ash could stall a jet engine in flight, at altitude, at night, was not the working assumption.
One incident could be written off as a freak. Two, on the same corridor, within three weeks, could not.
The night three engines quit over Java
It was already dark over Java on July 14, 1982. A Singapore Airlines Boeing 747, bound for Melbourne out of Singapore, pushed into the high-altitude plume of ash that Mount Galunggung had thrown up.
Three of the four engines quit, per the contemporaneous UPI account. The jet dropped roughly 8,000 feet. Captain Nicholas Evans managed to restart one of them and flew the aircraft into Jakarta’s Halim International Airport on the two that were left.
UPI described 230 passengers and crew aboard. No injuries were reported.
That same report pins down the route, the emergency sequence and the safe ending — and gives no flight number. Later retellings call it Flight 21A. Neither the flight number nor the exact headcount can be treated as settled, and the record is inconsistent enough that it is worth saying so plainly rather than picking a version.
There is a second conflict in the record, and it matters. UPI and the fact base say three of four engines stalled, while some ICAO- and WMO-hosted historical summaries describe two.
The three-of-four figure is the one used here because it traces to the contemporaneous report — but the discrepancy is real and should not be silently resolved.
Why the second case, not the first, forced the change
Investigators looking at both incidents concluded the same thing: volcanic ash particles had been ingested, and that ingestion caused the engine stalls. Flying through the ash left both aircraft with significant damage to engines and exterior surfaces.
That finding is the load-bearing one. It reclassified ash from a nuisance to a hazard capable of taking a widebody out of the sky.
The institutional result has a date attached. Well before it, ICAO’s Air Navigation Commission worked up interim guidance on how ash information should be passed around and how diversions should be arranged. The formal step came in March 1987, when the ICAO Council adopted amendments to its Annexes and Procedures for Air Navigation Services — the framework that grew into the International Airways Volcano Watch.
What the record does not carry is the Singapore Airlines aircraft’s own technical file. There is no detailed post-landing strip-down report, no per-engine assessment, no repair record in the sources reviewed.
A later airline-history note claims all four engines were swapped out; that is secondary and should not be weighed against BA009’s far fuller documentation.
That asymmetry is itself the point. The better-documented incident became the canonical one. The second case quietly did the systemic work.
One question the sources leave open is whether any satellite observation or ash-dispersion product reached the crew that night.
The reviewed material never shows a usable warning reaching the flight — but that silence is not evidence that no data existed, nor that the encounter could have been prevented. Why roughly three weeks passed without the second crew receiving any effective warning from the first incident is a fair question to pose, and one nobody has answered.
Superdeals cover departures from North America, Europe and Australia.
Flight deals most people never see
Air Traveler Club monitors thousands of routes for pricing anomalies that traditional search engines miss. With ATC Superdeals members save up to 80% on each flight vs. regular fares.
Too good to be true? Check it out yourself. It's free.
Delivered weekly. Unsubscribe anytime.
How an ash warning actually reaches a cockpit today
A volcano observatory or another observing source is usually the first to report an eruption or a sighting of ash, feeding it into the aviation and meteorological network. From there VAAC Darwin — the centre whose patch takes in Indonesia, Papua New Guinea and the southern Philippines — maps where the ash sits and where it is expected to drift, and issues a Volcanic Ash Advisory.
That advisory is what the responsible Meteorological Watch Office turns into volcanic-ash SIGMETs, while aeronautical information services may add NOTAM or ASHTAM notices.
Dispatchers, airlines and air-traffic services make the routing call from there. What a traveller actually sees is a reroute, a delay or a cancellation — not a pilot choosing to press on through an advisory.
What this means for travellers today
For anyone flying to, from or through Asia-Pacific, this is not history. It is the origin of the operational layer that protects the flight.
Ash advisories can force reroutes, delays and cancellations on Australia–Southeast Asia–Europe corridors. The systems that generate those decisions trace back to these two 1982 events.
Understanding that ash is an engine-stall hazard, not just an abrasion nuisance, explains why airlines reroute early rather than pressing on. An ash-related reroute is a genuine safety call, not an overreaction — and it is the reason a modern crew crossing Indonesian or Philippine airspace receives ash guidance at all.
Reporting by
Key terms
- VAAC
- A Volcanic Ash Advisory Centre (VAAC) is a meteorological office that issues Volcanic Ash Advisory messages, setting out where volcanic ash sits and where it is forecast to drift across its assigned region. The centre’s role is advisory only: it maps the ash, while the decision about whether a given flight proceeds belongs to the airline and the air-traffic system. It is the part of the warning chain that gives airlines their first picture of an ash cloud, and it exists because the 1982 Galunggung encounters showed the industry that it had none.
- SIGMET
- A SIGMET is a short, time-critical warning to aircraft about a hazard in a defined area, and the volcanic-ash version is prepared by the responsible Meteorological Watch Office. SIGMETs are built from the VAAC’s Volcanic Ash Advisory and passed into the aviation network for dispatchers and air-traffic services to act on. For a crew, the ash SIGMET is the layer that turns a distant eruption into a specific question about their own route.
- NOTAM / ASHTAM
- A NOTAM is a notice to airspace users about a temporary change or hazard affecting a flight, and an ASHTAM is the volcanic-ash-specific version of the same kind of notice. Both are issued through aeronautical information services and sit alongside the VAAC advisory and the ash SIGMETs rather than replacing them. They mark the point at which an ash event stops being a meteorological observation and starts generating concrete restrictions on real routes.
- International Airways Volcano Watch
- The International Airways Volcano Watch is the ICAO-coordinated framework for reporting volcanic ash, warning aircraft about it and routing traffic around it in international airspace. It grew out of the formal Annex and PANS amendments ICAO adopted in the years after the 1982 Galunggung encounters, and later absorbed the VAAC office network. Its significance for a traveller is that an eruption on a busy Asia-Pacific corridor now reaches airlines as a coordinated warning instead of a local anecdote.
Questions? Answers.
Is it true that a plane flew through volcanic ash?
Yes. On July 14, 1982, a Singapore Airlines Boeing 747 flew into ash from Mount Galunggung and lost engine power. The contemporaneous UPI report says three of four engines stalled, while some ICAO- and WMO-hosted summaries describe two — the accounts conflict and neither should be treated as settled.
Which Jakarta airport did the Singapore Airlines flight land at?
Jakarta’s Halim International Airport, according to the contemporaneous UPI report. The aircraft touched down there after the crew restarted one engine.
What warning systems exist today for volcanic ash?
Volcanic Ash Advisory Centres issue Volcanic Ash Advisory messages — VAAC Darwin covers Indonesia, Papua New Guinea and the southern Philippines. Meteorological Watch Offices turn that information into volcanic-ash SIGMETs, and aeronautical information services may add NOTAM or ASHTAM notices.
