Saudia Flight 163

Template:Short description Template:Not to be confused with Template:Use dmy dates Template:Infobox aircraft occurrence

Saudia Flight 163 was a scheduled Saudia passenger flight departing from Quaid-e-Azam Airport in Karachi, Pakistan, bound for Kandara Airport in Jeddah, Saudi Arabia, via Riyadh International Airport in Riyadh, Saudi Arabia, which caught fire after takeoff from Riyadh International Airport (now the Riyadh Air Base)<ref name="ASN">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> on 19 August 1980. Although the Lockheed L-1011-200 TriStar made a successful emergency landing at Riyadh, the flight crew failed to perform an emergency evacuation of the airplane, leading to the deaths of all 287 passengers and 14 crew on board the aircraft from smoke inhalation.

The accident is the deadliest aviation disaster involving a Lockheed L-1011 TriStar,<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> and the deadliest to occur in Saudi Arabia.<ref name="ASN" /><ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> At the time, this was the second-deadliest aircraft accident in the history of aviation involving a single airplane after Turkish Airlines Flight 981 and the third-deadliest overall.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

AircraftEdit

The aircraft involved in the accident was a Lockheed L-1011-200 TriStar, registered in Saudi Arabia as HZ-AHK with serial number 1169. The aircraft was certified on 23 July 1979 and was delivered to Saudia nearly a month later. It had accumulated a total of 3,023 flight hours and 1,759 cycles. HZ-AHK was equipped with three Rolls Royce RB211-524 engines with each having an average of 4,000 total engine hours.<ref name="riyadh">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>Template:Rp

Passengers and crewEdit

Nationalities of the victimsTemplate:Fact
Nationality	Number
Template:Flagicon Canada	1
Template:Flagicon China	1
Template:Flagicon Finland	1
Template:Flagicon France	1
Template:Flagicon West Germany	1
Template:Flagicon Iran	81
Template:Flagicon Ireland	1
Template:Flagicon Sweden	1
Template:Flagicon Italy	1
Template:Flagicon Japan	1
Template:Flagicon South Korea	4
Template:Flagicon Netherlands	1
Template:Flagicon Pakistan	64
Template:Flagicon Philippines	6
Template:Flagicon Saudi Arabia	125
Template:Flagicon Spain	1
Template:Flagicon Taiwan	1
Template:Flagicon Thailand	2
Template:Flagicon United Kingdom	4 passengers, 1 crew<ref name=Briton>Template:Cite news</ref>
Template:Flagicon United States	3
Total	301

Of the flight's passengers, 82 boarded in Karachi, while the remaining 205 boarded in Riyadh. The majority of the passengers were Saudis and Pakistani religious pilgrims on their way to Mecca. In addition to the Saudis and Pakistanis, 32 religious pilgrims were from Iran. Also, a small number of passengers were from various countries, who were heading to Jeddah for diplomatic missions.<ref name="riyadh" />Template:Rp<ref name="GlobeMailStove">Template:Cite news</ref><ref name="Haine2">Template:Cite book</ref> Four of the passengers were British.<ref name=Briton/>

There was a total of three crew members in the flight deck. All were inexperienced with the aircraft type:

The captain of the flight was 38-year-old Mohammed Khowyter ({{#invoke:Lang|lang}}), a Saudi national hired by Saudia in 1965 who had flown the Douglas DC-3, DC-4, McDonnell Douglas DC-9, Boeing 707 and 737. Despite being certified to fly such a wide range of aircraft, Khowyter's records described him as a slow learner and in need of more appropriate training. Khowyter had 7,674 flying hours but only 388 hours on the TriStar - a significantly more sophisticated aircraft.<ref name="riyadh" />Template:Rp

The first officer was 26-year-old Sami Hasanain ({{#invoke:Lang|lang}}), also a Saudi national, who joined the airline as a pilot in 1977. During training Hasanain had at one point been removed from flying school for poor performance. He had 1,615 flying hours in total but only 125 hours in the TriStar: he received his type rating just 11 days before the accident. .<ref name="riyadh" />Template:Rp

The flight engineer was 42-year-old Bradley Curtis. Previously certified as a captain of the antiquated and comparatively unsophisticated Douglas DC-3, he was hired by Saudia during a major recruitment drive in 1974 and assigned to pilot training for their expanding Boeing 707 and 737 international fleet. He failed to qualify but was offered the opportunity to continue employment with Saudia by funding his own training as an flight engineer on the new TriStar. Curtis had 650 flying hours as an FE, and 157 hours on type.<ref name="riyadh" />Template:Rp<ref>{{#invoke:citation/CS1|citation

|CitationClass=web }}</ref>

Six flight attendants were from the Philippines, three flight attendants were from Pakistan, and one flight attendant was from the United Kingdom.<ref>Template:Cite news</ref>

AccidentEdit

File:Saudia 163 overview.jpg

An overview of Saudia Flight 163 after the fire

Flight 163 departed Quaid-e-Azam International Airport (now Jinnah International Airport) in Karachi, Pakistan, at 18:32 Pakistan time (13:32 UTC) bound for Kandara Airport in Jeddah, Saudi Arabia, with a scheduled intermediate stop at Riyadh Airport. The flight arrived in Riyadh at 19:06 Saudi time (16:06 UTC) and had a two-hour layover for refueling. During the layover, several of the passengers disembarked. After refueling, the flight took off at 21:08 (18:08 UTC) bound for Jeddah.<ref name="riyadh" />

Almost seven minutes into the flight, the crew received warnings of smoke from the cargo compartment.<ref name="riyadh" />Template:Rp The crew spent the next four minutes trying to confirm the warnings, after which Flight Engineer Curtis went back into the cabin to confirm the presence of smoke. Captain Khowyter decided to return to the airport, and First Officer Hasanain radioed their intentions at 21:20 (18:20 UTC). At 21:25 (18:25 UTC), the thrust lever for the number two engine (the center engine) became jammed as the fire burned through the operating cable. Then, at 21:29 (18:29 UTC), the engine was shut down during final approach.<ref name="riyadh" />Template:Rp

File:Saudia 163 close-up.jpg

The remains of HZ-AHK, after the fire

At 21:35 (18:35 UTC), Khowyter declared an emergency and landed back at Riyadh.<ref>Template:Cite news</ref> After touchdown at 21:36 (18:36 UTC), the airplane continued to a taxiway at the end of the runway where it exited the runway, stopping at 21:39 (18:39 UTC), 2 minutes and 40 seconds after touchdown. The airport fire rescue equipment was stationed back on the landing section of the runway, with emergency personnel expecting an emergency stop and evacuation. This meant they had to rush after the aircraft, which had used the entire length of a Template:Convert runway to slow and then exit onto the taxiway. The airplane stopped facing in the opposite direction from landing.<ref name="riyadh" />Template:Rp

Once the aircraft had stopped, the crew reported that they were shutting down the engines and about to evacuate. On arrival at the aircraft soon after, however, the rescue personnel found that the two wing-mounted engines were still running, preventing them from opening the doors. These were finally shut down at 21:42 (18:42 UTC), 3 minutes and 15 seconds after the aircraft came to a stop, when communication with the crew was lost. No external fire was visible at this time, but flames were observed through the windows at the rear of the aircraft. Twenty-three minutes after engine shutdown, at 22:05 (19:05 UTC), the R2 door (second door on the right side) was opened by ground personnel. Three minutes later, the interior of the aircraft flashed over, and was destroyed by fire.<ref name="riyadh" />Template:Rp

Why Captain Khowyter failed to evacuate the aircraft promptly is not known. Saudi reports stated that the crew could not get the plug-type doors to open in time.<ref name="AviationWeekSuitFiled2">Template:Cite news</ref> It is assumed that most passengers and flight attendants were incapacitated during the landing roll, or they did not attempt to open a door on a moving aircraft.<ref>Template:Cite news</ref> The aircraft is known to have remained pressurized during the landing roll as the cabin pressurization system was on standby, and the aircraft was found with both pressurization hatches almost completely closed. The pressurization hatches should have opened completely on touchdown to depressurize the aircraft. The crew were found still in their seats, and all the victims were found in the forward half of the fuselage. Autopsies were conducted on some of the non-Saudi nationals, including the American flight engineer. All of them perished from smoke inhalation and not burns, which indicated that they had died long before the R2 door was opened. The source of the fire in compartment C3 could not be determined.<ref name="riyadh" />Template:Rp

InvestigationEdit

File:Saudia 163 hold C3.jpg

Cargo compartment C3 after the fire

The investigation revealed the fire had started in the aft C3 cargo compartment.<ref name=riyadh/>Template:Rp The fire was intense enough to burn through the cabin floor, causing passengers seated in that area of the cabin to move forward prior to the landing. Saudi officials found two butane stoves in the burned-out remains of the airliner, and a used fire extinguisher near one of them.<ref name=riyadh/>Template:Rp One early theory was that the fire began in the passenger cabin when a passenger used his own butane stove to heat water for tea.<ref>Template:Cite news</ref> The investigation found no evidence to support this theory.<ref name="riyadh"/>Template:Rp

Policy changesEdit

After the event, the airline revised its training and emergency procedures. Lockheed also removed the insulation from above the rear cargo area and added glass laminate structural reinforcement. The US National Transportation Safety Board recommended that aircraft use halomethane extinguishers instead of traditional hand-held fire extinguishers.<ref name="Haine2"/>

Crew resource managementEdit

Flight 163 encapsulated the further need for the advent of crew resource management. This is evident from the primary lapses in effective communication that prevented the crew from carrying out a final successful evacuation from the aircraft. These lapses are enabled in part by so-called power distances between juniors and superiors in workplace settings, relationships found in all societies, but emphasized more in some than in others.<ref name=hel1>Template:Cite journal</ref> "In high power-distance cultures, juniors do not question superiors and leaders may be autocratic", leading to situations where a first officer finds it difficult to question decisions made by the captain, conditions that may have been present on Saudia Flight 163.<ref name=trk/><ref name=hel1/><ref>Template:Cite book</ref> Analysis of the CVR found that a power distance may have taken place, as the captain repeatedly ignored requests from the flight's chief purser to order an evacuation. As the aircraft's CVR stopped recording before the emergency landing due to fire damage, the exact reason for the captain refusing to order an evacuation is unknown, though his behavior and actions during the flight were found to be contributing factors to the accident.<ref>Mayday Season 24, episode 8 "Under Fire" (2024), Cineflix Productions</ref>

The power distance phenomenon has the capability of affecting flight safety globally, but as the work performed in the cockpit is markedly dependent upon the ability of one worker to crosscheck the work of another and vice versa, the danger is most apparent in individuals brought up in cultures that traditionally revere high power distances between those in positions of power and their subordinates.<ref name=trk>Template:Cite thesis</ref>

In popular cultureEdit

In 1982, the British current-affairs program World in Action aired an episode entitled "The Mystery of Flight 163". This documented the accident and was subsequently used to train pilots in the value of crew resource management.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

This accident is covered in season 24, episode 8 of Mayday titled "Under Fire" (2024).<ref name="Mayday">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

ReferencesEdit

Template:Reflist

External linksEdit

Template:External media

{{#invoke:citation/CS1|citation

|CitationClass=web }}

{{#invoke:citation/CS1|citation