Qantas 747 engine explodes (or some other small problem)
A Qantas 747 suffers a spectacular engine failure after takeoff, requiring a 30-minute fuel dump.
Summary
Shortly after departing San Francisco for Sydney, Qantas Flight 74 experienced a catastrophic failure of its number four engine. The crew spent approximately 30 minutes dumping fuel over the Pacific to reach a safe landing weight before returning to SFO. Despite the severity of the engine damage, the crew maintained a calm, professional demeanor throughout the return and landing.
Analysis
On August 31, 2010, Qantas Flight 74, a Boeing 747-400 bound for Sydney, experienced a major failure of its outboard right-hand engine (engine #4) shortly after takeoff from San Francisco International Airport. The failure was "contained" within the engine housing but was violent enough to cause significant vibration and visible sparking, which the pilots noted persisted even after the engine was shut down.
The recording highlights the deliberate nature of heavy aircraft emergencies. Because the 747 was fueled for a long-haul trans-Pacific flight, it was significantly above its Maximum Landing Weight (MLW). Landing immediately would have risked structural damage or a brake fire. Consequently, the crew coordinated with Oakland Center to dump fuel for 30 minutes near the "RAINS" waypoint. Notably, the pilot initially tells ATC they are a "negative emergency" while they are simply managing the situation, only upgrading to "Pan-Pan" (an urgency signal one level below "Mayday") once they were ready to commence the final approach.
A key technical moment occurs when the pilot informs ATC that due to their high weight, they cannot stay within the standard confines of the holding pattern. This is a critical piece of communication that ensures ATC provides enough airspace for the heavy jet's wider turning radius. The pilot’s refusal to provide detailed engine diagnostics to dispatch via ATC ("we're not in a position to pass that... at this stage") demonstrates "Aviate, Navigate, Communicate" priority—focusing on flying the plane rather than administrative reporting.
The incident concluded safely with a landing on Runway 28 Right. The crew requested an immediate inspection by fire services on the taxiway before taxiing to the terminal, concerned about the "severe damage" and previous sparking. This event is often cited in pilot training as a textbook example of CRM (Crew Resource Management) and calm professional communication during a high-stakes mechanical failure.