What led to Worlds 6th Deadliest Air Crash : Saudi Arabian Airlines Fight 163 - Avgeek | Engineer | Aspiring Pilot

Breaking

Sunday, November 29, 2020

What led to Worlds 6th Deadliest Air Crash : Saudi Arabian Airlines Fight 163




Among the world's top deadliest air crashes, Saudi Arabian Airlines Flight 163 is ranked 6th after the bombing of Air India Flight 182 that killed all 329 passengers on board.

What happened on 19 August 1980, which resulted in all 287 fatalities even after the aircraft had made a safe emergency landing in Riyadh?

Brief History of Saudia


Formerly known as Saudi Arabian Airlines, is the flag carrier of Saudi Arabia, based in Jeddah.

The airline currently operates to over 85 destinations in the Middle East, Asia, Africa, North America, and Europe from its various main operational bases such as King Khalid International Airport in Riyadh and the World Largest Airport by area, King Fahd International Airport in Dammam.

The airline was established in September 1945, when U.S President Roosevelt presented a Douglas DC-3 gift to King Abdul Aziz Ibn Saud, the first monarch and founder of Saudi Arabia.

Besides being the 3rd largest airline in the middle east with a fleet of 159 State-of-the-art aircraft, it is awarded by Skytrax in 2017 for the "World's Most Improved Airline".


Aircraft and Crew of Flight 163


According to Airfleets, Lockheed L-1011 TriStar, registration HZ-AHK, was delivered to Saudia on 21st of August 1979 and was written off after the incident in Riyadh in 1980.

On the night of 19th August 1980, the jet was commanded by the captain Mohammed Ali Khowyter, a Saudi National, who had over 7000 flying hours, of which 388 hours in the Lockheed L-1011 TriStar.

Although having had flown diverse aircraft in his career, his previous records revealed him incompetent during high-stress environments and being a slow learner.

The 26-year-old first officer, on the other hand, Sami Abdullah M. Hasanain, had around 1600 flight hours and obtained his type rating on Lockheed L-1011 TriStar 11 days before the incident. 

His past accomplishments explained he wasn't too sharp either, Hasnain was removed from his flying school due to poor performance but managed to fly for Saudi Arabian Airlines as a first officer either way.

The 42-year-old flight engineer Bradley Curtis, an American was hired by the airline 6 years before the incident. 
Even after failing to qualify as a captain and a flight officer for the Boeing 707 and 737, he was hired by Saudia as a flight engineer.

Moreover, with his dyslexia, he wasn't positioned to be a crew in the first place.


What happened


( 18.16:06 UTC)

Flight Engineer: Both "A" and "B" aft cargo smoke detection
Captain: So we have smoke there
( 18.16:07 UTC)
Flight Engineer: I would say so, yeah
Captain: What's the procedure for it in the checklist?
( 18.16:20 UTC)
Captain: Yeah I am looking for it now
Captain: ((Singing in Arabic))




After departing Karachi, Pakistan bound for Jeddah, Saudi Arabia, Flight 163 had a layover at Riyadh for 2 hours, whereby refueling and disembarking passengers took place.

About 7 minutes after taking off (18:08 UTC), the crew underwent several warnings of smoke from the cargo compartment.

At (18:25), the number two (Tail-mounted) engine shut down, as the fire raged through the working cable, leaving the crew with 2 operational engines.


Aftermath of Saudia Flight 163 burned out fuselage 


( 18.28:54 UTC )

First Officer: Please advise fire trucks to be a tail of the airplane aftertouch, please.
Riyadh Tower: Yes, will do
Captain: Where is the airport, I don't see it?
Flight Attendant: Captain there is too much smoke in the back
First Officer: There is the airport road, the yellow lamps are the airport road.
Captain: Huh
First Officer: The yellow lamps are the airport road



By (18:35 UTC) the captain declared an emergency and landed at Riyadh Airport.

Besides the smoke blazing through the cabin, Flight 163 continued to a taxiway and stopped 2 minutes after the touchdown.



( 18.31:30 UTC )

Flight attendant: Shall we evacuate?
Captain: What?
Flight Attendant: Did you say we should evacuate ---
Captain: Okay
Flight Attendant: The passengers
Flight Engineer: Say again
Flight Attendant: Can we evacuate all the passengers?
Captain: Flaps ten, please
Flight engineer: When we're on the ground yes
Flight Attendant: Okay after we are on the ground yes
First Officer: Flaps ten




Furthermore, due to the 2 wing-mounted engines running, the emergency rescue personal on arriving at the aircraft prevented them from accessing the doors.

By (18:42 UTC) 3 minutes after arrival, the communication with the crew was lost and the aircraft was consumed by fire.

All 301 passengers, the majority of them being from Pakistan and Saudi Arabia, perished due to smoke inhalation.


On Investigation  



Saudia flight 163 seen on taxiway few days after the incident


With victims found in the forward section of the fuselage, it is apparent that the fire originated from the aft C3 cargo compartment.

Besides Saudi officials finding 2 Butane stoves during the search, it was a likelihood that the passengers could have used it for their cooking needs causing fire to erupt, however the theory was dismissed due to no substantial evidence.

It is also evident from the actions of the crew operating flight 163, that prevented the evacuations of the passengers successfully.

Unlike SwissAir Flight 111, the crew of Saudia flight 163, had the advantage of Riyadh Airport being nearby, But due to the Captain's incapability to make fast decisions and the dyslexic flight engineer made the condition worse.

After this tragic event, Saudia updated its training and emergency procedures. Lockheed thereby discarded insulation from the cargo area and introduced glass laminate structural reinforcement.

Flight 163, also made Crew Resource Management advent during the training and day to day operations for pilots and crew.


Reference 


FlightSafetyAustralia 2019, Situation deadly, but not serious , Viewed on 29th November 2020


CVR Transcript : Saudia 163 CVR Transcript 






No comments:

Post a Comment