Air Crash Investigation 2022 | Titanic in the Sky | Qantas Flight 32 | Sunday, 6 February 2022

Air Crash Investigation 2022 | Titanic in the Sky | Qantas Flight 32 | Sunday, 6 February 2022.
Qantas Flight 32 was a regularly scheduled passenger flight from London to Sydney via Singapore. On 4 November 2010, the aircraft operating the route, an Airbus A380, suffered an uncontained failure in one of its four Rolls-Royce Trent 900 engines. The failure occurred over the Riau Islands, Indonesia, four minutes after takeoff from Singapore Changi Airport. After holding for almost two hours to assess the situation, the aircraft made a successful emergency landing at Changi. No injuries occurred to the passengers, crew, or people on the ground, despite debris from the aircraft falling onto houses in Batam.

On inspection, a turbine disc in the aircraft's number-two engine (on the port side nearer the fuselage) was found to have disintegrated, causing extensive damage to the nacelle, wing, fuel system, landing gear, flight controls, and engine controls, and a fire in a fuel tank that self-extinguished. The subsequent investigation concluded that the failure had been caused by the breaking of a stub oil pipe, which had been manufactured improperly.

The failure was the first of its kind for the A380, the world's largest passenger aircraft. At the time of the accident, 39 A380s were operating with five airlines: Qantas, Air France, Emirates, Lufthansa, and Singapore Airlines. The accident led to the temporary grounding of the rest of the six-plane Qantas A380 fleet. It also led to groundings, inspections, and engine replacements on some other Rolls-Royce-powered A380s in service with Lufthansa and Singapore Airlines, but not in the A380 fleets of Air France or Emirates, which were powered by Engine Alliance engines.

The accident, at 10:01 am Singapore Standard Time (02:01 UTC), was caused by an uncontained failure of the port inboard (number-two) engine, while en route over Batam Island, Indonesia.

Shrapnel from the engine punctured part of the wing and damaged the fuel system, causing leaks and a fuel-tank fire, disabled one hydraulic system and the antilock braking system, caused the number-one and number-four engines to go into a "degraded" mode, and damaged landing flaps and the controls for the outer left number-one engine.The crew, after finding the plane controllable, decided to fly a holding pattern close to Singapore Changi Airport, while assessing the status of the aircraft. Completing this initial assessment took 50 minutes. The first officer and supervising check captain (SCC) then put the plane's status into the landing distance performance application (LDPA) for a landing 50 tonnes over maximum landing weight at Changi. Based on these inputs, the LDPA could not calculate a landing distance. After discussion, the crew elected to remove inputs related to a wet runway, in the knowledge that the runway was dry. The LDPA then returned the information that the landing was feasible with 100 m of runway remaining.The flight then returned to Changi Airport, landing safely after the crew extended the landing gear by a gravity drop emergency extension system, at 11:45 am Singapore time. As a result of the aircraft landing 35 knots faster than normal, four tyres were blown.

Upon landing, the crew was unable to shut down the number-one engine, which had to be doused by emergency crews until flameout was achieved. The pilots considered whether to evacuate the plane immediately after landing, as fuel was leaking from the left wing near to the brakes, which were assumed to be extremely hot from maximum braking. The SCC pilot, David Evans, noted in an interview,
We’ve got a situation where there is fuel, hot brakes, and an engine that we can’t shut down. And really the safest place was on board the aircraft until such time as things changed. So, we had the cabin crew with an alert phase the whole time through ready to evacuate, open doors, inflate slides at any moment. As time went by, that danger abated, and thankfully, we were lucky enough to get everybody off very calmly and very methodically through one set of stairs.

The plane was on battery power and had to contend with only one VHF radio to coordinate emergency procedure with the local fire crew.

No injuries were reported among the 440 passengers and 29 crew on board the plane. On Batam Island, some debris fell on a school, some houses, and a car

[faronanderson]

According to history, previous similar incidents didn't end this well.Watching this, they we're teetering on the edge of catastrophy.This is truly a miracle 🙏 .

[krist]

This crew did a phenominal job!! It's truly incredible how they all worked together and saved everyone on board!!! These guys are not just professionals, they're heros!!!!

[shinyarticuno]

whats with those annoying piano notes playing over and over again lmaooo

[jonkingston]

that background drone music is extremely annoying and unnecessary. I can't watch this, as much as I want to. Also, what's up with the audio of the show? Sounds like it was recorded on a cassette tape!

[Spunkiewolf]

It was a great job on the assessment of the problems. They are Hero's as far as I am concerned. God bless you all. To the whole crew.

[sampsonbreh]

Professionalism displayed here by the crew members. God was on your side that day. Great job!

[inbarasanrajarathinam]

Great. But this video can be better without the non stop monotonous background music

[nizzyb]

These pilots did an incredible job! Whoever edited and uploaded this video, not so much.

[probablyjay]

5:31 is that the 737 ap disconnect sound

[V-tv]

The sound of this Youtube video is very bad. What did you do?

[Authoress]

I know the point of all the jump cuts and repeats sequences and background music that doesn’t go is likely a way to avoid a copyright strikes, but it makes it hard to watch.

[missliverpoolcatlady]

What the heck is wrong with the speeded up voiceover?!!!! 😂

[gagansingh]

No need music and tones at background Totley headache

[LoveAnimeAngel_]

what's with the background piano tune ruining this vid, if you're going to upload something then do it right

[Michelle_Schu-blacka]

5:49 - Why was King Charles' Mrs on that flight?

[txtworld]

The Qantas Captain did an admirable job to land the plane. But his judgment was debatable to keep the passengers holed up inside the plane for an hour after landing – with fuel gushing out of the left wing – and brake temps exceeding 950 degrees – which the Captain himself described as "beyond white hot".

An ABC Australia documentary on this emergency stated that if fire broke out, the passengers would've been evacuated in 90 seconds – but there's no way that all 469 passengers and crew would’ve survived if that had of happened – even if the evacuation went flawlessly, the fuselage interior would’ve been engulfed in flames within 30 seconds (not 90) had they only commenced the evacuation after a fire erupted.

Contrast this emergency to Cathay Pacific flight 780, earlier that same year in 2010 – also with an experienced Aussie flight crew, and also with brake temps exceeding 950 degrees upon landing. The Cathay Aussie Captain ordered an emergency evacuation down the slides. Sure, it made bad press for Cathay to have TV images of the plane with the slides deployed – and some passengers ended up with minor injuries, such as sprained ankles & broken bones – but it was the RIGHT CALL for the Captain to make. Better to be safe than sorry, when there's a real risk of the aircraft erupting in flames.

[Godfranci]

The worst recording or montage of air crush investigation ever! Voice just doesn’t-match most of the time...

[patriciaramsey]

This story had me glued to my seat. Tryue nail biter. I can ignore the so-called 'poor quality' of the video. Really, your videos are not that bad. The more I wat h, the better they get

[ljre]

This is unwatchable. Sorry I’m sure it was a lot of work but it misses the mark. Try try again.

[Kirovets]

The audio-track is a MESS!!
DO something about it! It's very annoying!!😡😡😡