“Ladies and gentlemen, this is the captain speaking. As you no doubt may be aware, we have a small problem with our engines.”
These words came from Captain Malcolm Waters on April 13, 2010, but they masked a dire reality. The "small problem" referred to a catastrophic failure: one engine had stopped entirely, while the other was stuck at full power. With 309 passengers and 13 crew aboard, the situation was horrifyingly precarious; they might soon find themselves plummeting into the South China Sea.
The journey began ordinarily enough. Cathay Pacific Flight 780 pushed back from Juanda International Airport in Surabaya, Indonesia, ready for its 5-hour trek to Hong Kong. The Airbus A330-300, an aircraft commonly used for medium to long-haul flights, was crewed by a well-trained team. Captain Waters, with 12 years in service and a wealth of flying hours under his belt, was accompanied by First Officer David Hayhoe, a veteran of the Australian Air Force.
As they took off in clear weather, the crew had no idea that what awaited them was beyond any training they had received. Quickly escalating warnings indicated something was critically wrong with their engines, leading to a terrifying revelation: they may not make it to their destination.
Shortly after their ascent, abnormal fluctuations in the EPR readings for engine two emerged, a troubling indicator of thrust output issues. The crew decided to continue flying to Hong Kong after consulting with the maintenance control, believing that the problem was manageable. However, as they got closer to their destination, the warnings escalated to critical levels. Alarmingly, both engines began to stall just as the aircraft was beginning its descent.
Each pilot's decision-making, collaboration, and training were put to the ultimate test as the gravity of their situation intensified. Captain Waters, facing a dual-engine failure, declared a Pan Pan to air traffic control, preparing for a landing under unusual and severe stress.
As the flight drew closer to Hong Kong, it increasingly resembled a desperate attempt to maintain control over a giant glider. Despite managing to get one engine responding, the situation remained dire; the second engine was unresponsive when the crew attempted to reduce power.
With only 100 miles left to their destination and descending through layers of cloud, the flight encountered additional hurdles. The pilots had to wrestle with the implications of their engines providing too much thrust, pushing the aircraft towards dangerously high approach speeds.
The First Officer relayed an urgent mayday to air traffic control, a chilling recognition of the precariousness of their predicament. As the crew regained sight of the ground, they realized they were fast approaching the airport—yet their aircraft was operating at an unsafe speed, bordering on uncontrollable.
A Dangerous Landing
At 2 PM, the Airbus A330 smashed down on the runway at shocking speeds—231 knots, nearly twice what was normal for a safe landing. It bounced upon arrival and skidded perilously close to the end of the runway, finally coming to rest just 309 meters from the sea's edge.
Miraculously, all aboard survived, though the aftermath was tense. Pilots received commendations for their performance as they orchestrated a safe landing under terrifying circumstances, even if the thrust reversers failed to deploy properly.
Analysis of the Incident
Despite the survival of all passengers and crew, investigators needed to unravel what had caused this catastrophic failure. The culprit was traced back to the fuel used to power the engines. The discovery of Super Absorbent Polymer (SAP) clogging critical components pointed towards a grave oversight during the fueling process at Surabaya airport.
Crucially, an overhaul of the fuel supply system had led to saltwater contamination, and subsequent fueling activities ignored telltale signs of improper function, resulting in the contamination of the aircraft's fuel by the very material designed to cleanse it.
Lessons Learned
The final investigation led to recommendations for improved fueling practices and monitoring of fuel quality to prevent similar catastrophes. Airbus took proactive measures by adding new guidelines to the A330's Quick Reference Handbook concerning potential fuel system contamination.
In summary, Cathay Pacific Flight 780's ordeal serves as a powerful reminder of the unpredictable nature of aviation and the remarkable capabilities of well-trained pilots amid crises. The fact that all 309 people on board returned safely showcases extraordinary teamwork and decision-making under extreme duress, affirming the resilience of both the crew and the aviation system at large.
Part 1/8:
The Harrowing Tale of Cathay Pacific Flight 780
“Ladies and gentlemen, this is the captain speaking. As you no doubt may be aware, we have a small problem with our engines.”
These words came from Captain Malcolm Waters on April 13, 2010, but they masked a dire reality. The "small problem" referred to a catastrophic failure: one engine had stopped entirely, while the other was stuck at full power. With 309 passengers and 13 crew aboard, the situation was horrifyingly precarious; they might soon find themselves plummeting into the South China Sea.
A Routine Flight Turns Chaotic
Part 2/8:
The journey began ordinarily enough. Cathay Pacific Flight 780 pushed back from Juanda International Airport in Surabaya, Indonesia, ready for its 5-hour trek to Hong Kong. The Airbus A330-300, an aircraft commonly used for medium to long-haul flights, was crewed by a well-trained team. Captain Waters, with 12 years in service and a wealth of flying hours under his belt, was accompanied by First Officer David Hayhoe, a veteran of the Australian Air Force.
As they took off in clear weather, the crew had no idea that what awaited them was beyond any training they had received. Quickly escalating warnings indicated something was critically wrong with their engines, leading to a terrifying revelation: they may not make it to their destination.
Engine Troubles Begin
Part 3/8:
Shortly after their ascent, abnormal fluctuations in the EPR readings for engine two emerged, a troubling indicator of thrust output issues. The crew decided to continue flying to Hong Kong after consulting with the maintenance control, believing that the problem was manageable. However, as they got closer to their destination, the warnings escalated to critical levels. Alarmingly, both engines began to stall just as the aircraft was beginning its descent.
Each pilot's decision-making, collaboration, and training were put to the ultimate test as the gravity of their situation intensified. Captain Waters, facing a dual-engine failure, declared a Pan Pan to air traffic control, preparing for a landing under unusual and severe stress.
An Unthinkable Emergency Scenario
Part 4/8:
As the flight drew closer to Hong Kong, it increasingly resembled a desperate attempt to maintain control over a giant glider. Despite managing to get one engine responding, the situation remained dire; the second engine was unresponsive when the crew attempted to reduce power.
With only 100 miles left to their destination and descending through layers of cloud, the flight encountered additional hurdles. The pilots had to wrestle with the implications of their engines providing too much thrust, pushing the aircraft towards dangerously high approach speeds.
Part 5/8:
The First Officer relayed an urgent mayday to air traffic control, a chilling recognition of the precariousness of their predicament. As the crew regained sight of the ground, they realized they were fast approaching the airport—yet their aircraft was operating at an unsafe speed, bordering on uncontrollable.
A Dangerous Landing
At 2 PM, the Airbus A330 smashed down on the runway at shocking speeds—231 knots, nearly twice what was normal for a safe landing. It bounced upon arrival and skidded perilously close to the end of the runway, finally coming to rest just 309 meters from the sea's edge.
Part 6/8:
Miraculously, all aboard survived, though the aftermath was tense. Pilots received commendations for their performance as they orchestrated a safe landing under terrifying circumstances, even if the thrust reversers failed to deploy properly.
Analysis of the Incident
Despite the survival of all passengers and crew, investigators needed to unravel what had caused this catastrophic failure. The culprit was traced back to the fuel used to power the engines. The discovery of Super Absorbent Polymer (SAP) clogging critical components pointed towards a grave oversight during the fueling process at Surabaya airport.
Part 7/8:
Crucially, an overhaul of the fuel supply system had led to saltwater contamination, and subsequent fueling activities ignored telltale signs of improper function, resulting in the contamination of the aircraft's fuel by the very material designed to cleanse it.
Lessons Learned
The final investigation led to recommendations for improved fueling practices and monitoring of fuel quality to prevent similar catastrophes. Airbus took proactive measures by adding new guidelines to the A330's Quick Reference Handbook concerning potential fuel system contamination.
Part 8/8:
In summary, Cathay Pacific Flight 780's ordeal serves as a powerful reminder of the unpredictable nature of aviation and the remarkable capabilities of well-trained pilots amid crises. The fact that all 309 people on board returned safely showcases extraordinary teamwork and decision-making under extreme duress, affirming the resilience of both the crew and the aviation system at large.