Saudia Flight 163: Difference between revisions
Elva Reichel (talk | contribs) m Undid revision 1243774843 by 203.166.237.152 (talk) |
Undid revision 1260468929 by 122.150.235.66 (talk) They were all in the cockpit the moment the warning sounded; no reason to remove the ‘Why,’ it just made the sentence wrong; and the last part is not necessary |
||
(21 intermediate revisions by 16 users not shown) | |||
Line 16: | Line 16: | ||
| crew = 14 |
| crew = 14 |
||
| fatalities = 301 |
| fatalities = 301 |
||
| injuries = |
|||
| missing = |
| missing = |
||
| survivors = 0 |
| survivors = 0 |
||
Line 24: | Line 23: | ||
| stopover0 = |
| stopover0 = |
||
| last_stopover = |
| last_stopover = |
||
| destination = [[ |
| destination = [[Kandara Airport]],<br />[[Jeddah]], Saudi Arabia |
||
| aircraft_name = |
| aircraft_name = |
||
| operator = [[Saudia]] |
| operator = [[Saudia]] |
||
Line 33: | Line 32: | ||
}} |
}} |
||
'''Saudia Flight 163''' was a scheduled [[Saudia]] passenger flight departing from [[Jinnah International Airport|Quaid-e-Azam Airport]] in [[Karachi, Pakistan]], bound for [[Kandara Airport]] in [[Jeddah, Saudi Arabia]], via [[Riyadh Air Base|Riyadh International Airport]] in [[Riyadh, Saudi Arabia]] |
'''Saudia Flight 163''' was a scheduled [[Saudia]] passenger flight departing from [[Jinnah International Airport|Quaid-e-Azam Airport]] in [[Karachi, Pakistan]], bound for [[Kandara Airport]] in [[Jeddah, Saudi Arabia]], via [[Riyadh Air Base|Riyadh International Airport]] in [[Riyadh, Saudi Arabia]], which caught fire after takeoff from Riyadh International Airport (now the [[King Salman Air Base|Riyadh Air Base]])<ref name="ASN">{{cite web |last=Ranter |first=Harro |title=ASN Aircraft accident Lockheed L-1011 Tristar 200 HZ-AHK Riyad International Airport (RUH) |url=http://aviation-safety.net/database/record.php?id=19800819-1 |website=Aviation Safety Network |publisher=[[Flight Safety Foundation]]}}</ref> on 19 August 1980. Although the [[Lockheed L-1011 TriStar|Lockheed L-1011-200 TriStar]] made a successful emergency landing at Riyadh, the flight crew failed to perform an [[Emergency aircraft evacuation|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>{{Cite web |last=Ranter |first=Harro |title=Lockheed L-1011 TriStar |url=http://aviation-safety.net/database/types/Lockheed-L-1011-TriStar/index |access-date=2019-01-23 |website=Aviation Safety Network |publisher=Flight Safety Foundation}}</ref> and the deadliest to occur in Saudi Arabia.<ref name="ASN" /><ref>{{Cite web |last=Ranter |first=Harro |title=Saudi Arabia air safety profile |url=https://aviation-safety.net/database/country/country.php?id=HZ |access-date=2019-01-23 |website=Aviation Safety Network |publisher=Flight Safety Foundation}}</ref> At the time, this was the second-deadliest aircraft accident [[List of aircraft accidents and incidents resulting in at least 50 fatalities|in the history of aviation]] involving a single airplane after [[Turkish Airlines Flight 981]] and the third-deadliest overall.<ref>{{Cite web |last=Ranter |first=Harro |date= |title=ASN Aircraft accident McDonnell Douglas DC-10-10 TC-JAV Bois d'Ermenonville |url=https://aviation-safety.net/database/record.php?id=19740303-1 |access-date=2020-11-24 |website=Aviation Safety Network |publisher=Flight Safety Foundation}}</ref> |
The accident is the deadliest aviation disaster involving a Lockheed L-1011 TriStar,<ref>{{Cite web |last=Ranter |first=Harro |title=Lockheed L-1011 TriStar |url=http://aviation-safety.net/database/types/Lockheed-L-1011-TriStar/index |access-date=2019-01-23 |website=Aviation Safety Network |publisher=Flight Safety Foundation}}</ref> and the deadliest to occur in Saudi Arabia.<ref name="ASN" /><ref>{{Cite web |last=Ranter |first=Harro |title=Saudi Arabia air safety profile |url=https://aviation-safety.net/database/country/country.php?id=HZ |access-date=2019-01-23 |website=Aviation Safety Network |publisher=Flight Safety Foundation}}</ref> At the time, this was the second-deadliest aircraft accident [[List of aircraft accidents and incidents resulting in at least 50 fatalities|in the history of aviation]] involving a single airplane after [[Turkish Airlines Flight 981]] and the third-deadliest overall.<ref>{{Cite web |last=Ranter |first=Harro |date= |title=ASN Aircraft accident McDonnell Douglas DC-10-10 TC-JAV Bois d'Ermenonville |url=https://aviation-safety.net/database/record.php?id=19740303-1 |access-date=2020-11-24 |website=Aviation Safety Network |publisher=Flight Safety Foundation}}</ref> |
||
== Aircraft and crew == |
== Aircraft and crew == |
||
The aircraft involved in the accident was a Lockheed L-1011-200 TriStar ([[Aircraft registration|registered]] in Saudi Arabia as HZ-AHK). It made its first flight on 13 July 1979, and was delivered to Saudia on 21 August 1979.<ref name="riyadh">{{cite web|last=|first=|date=16 January 1982|title=Aircraft Accident Report, Saudi Arabian Airlines Lockheed L-1011, HZ-AHK, Riyadh, Saudi Arabia August 19th, 1980|url= |
The aircraft involved in the accident was a Lockheed L-1011-200 TriStar ([[Aircraft registration|registered]] in Saudi Arabia as HZ-AHK). It made its first flight on 13 July 1979, and was delivered to Saudia on 21 August 1979.<ref name="riyadh">{{cite web |last= |first= |date=16 January 1982 |title=Aircraft Accident Report, Saudi Arabian Airlines Lockheed L-1011, HZ-AHK, Riyadh, Saudi Arabia August 19th, 1980 |url=https://www.faa.gov/sites/faa.gov/files/AircraftAccidentReportSAA.pdf |url-status=live |archive-url=https://web.archive.org/web/20140101170608/http://lessonslearned.faa.gov/Saudi163/AircraftAccidentReportSAA.pdf |archive-date=1 January 2014 |access-date=26 February 2017 |website= |publisher=Saudi Arabian Presidency of Civil Aviation |via=Federal Aviation Administration}}</ref>{{rp|89}}<ref>{{cite web|title=Saudia HZ-AHK (Lockheed L-1011 TriStar - MSN 1169)|url=http://www.airfleets.net/ficheapp/plane-l10-1169.htm|access-date=28 February 2018|publisher=Airfleets aviation}}</ref> |
||
The [[Pilot in command|captain]] of the flight was 38-year-old Mohammed al-Khowyter, a Saudi who was hired by Saudia in 1965. He had flown numerous aircraft such as the [[Douglas DC-3]] and [[Douglas DC-4|DC-4]], the [[McDonnell Douglas DC-9]], and the [[Boeing 707]] and [[Boeing 737|737]]. Al-Khowyter's records described him as a slow learner and needing more proper [[Flight training|training]]. Al-Khowyter had 7,674 flying hours, including 388 hours in the TriStar. The [[First officer (civil aviation)|first officer]] was 26-year-old Sami Hasanain, also a Saudi, who joined the airline in 1977 and had previously worked as a trainee. He received his type rating on the TriStar 11 days before the accident. At one point during his training, however, Hasanain was removed from flying school for poor performance. Hasanain had 1,615 flying hours, including 125 hours in the TriStar. The [[flight engineer]] was 42-year-old Bradley Curtis (born Zdzisław Szczęsny), a Polish-born American who was hired by the airline in 1974. He had been qualified as a captain of the Douglas DC-3, and was then assigned to train in either the Boeing 707 or 737, but failed to qualify either as a captain or as a first officer because he did not meet the requirements. He had needed to pay for his own training as an L-1011 flight engineer to keep his job. Curtis had 650 flying hours, including 157 hours in the TriStar.<ref name="riyadh" />{{rp|86–88}}<ref>{{cite web|author=Thomson, Jim|date=16 January 1982|title=Human behaviour in a crisis{{Snd}} Saudia 163|url=http://www.safetyinengineering.com/FileUploads/Human%20behaviour%20in%20a%20crisis%20-%20Saudia%20163_1369664909_2.pdf|access-date=2 March 2018|archive-date=24 September 2015|archive-url=https://web.archive.org/web/20150924093448/http://www.safetyinengineering.com/FileUploads/Human%20behaviour%20in%20a%20crisis%20-%20Saudia%20163_1369664909_2.pdf|url-status=dead}}</ref> |
The [[Pilot in command|captain]] of the flight was 38-year-old Mohammed al-Khowyter, a Saudi who was hired by Saudia in 1965. He had flown numerous aircraft such as the [[Douglas DC-3]] and [[Douglas DC-4|DC-4]], the [[McDonnell Douglas DC-9]], and the [[Boeing 707]] and [[Boeing 737|737]]. Al-Khowyter's records described him as a slow learner and needing more proper [[Flight training|training]]. Al-Khowyter had 7,674 flying hours, including 388 hours in the TriStar. The [[First officer (civil aviation)|first officer]] was 26-year-old Sami Hasanain, also a Saudi, who joined the airline in 1977 and had previously worked as a trainee. He received his type rating on the TriStar 11 days before the accident. At one point during his training, however, Hasanain was removed from flying school for poor performance. Hasanain had 1,615 flying hours, including 125 hours in the TriStar. The [[flight engineer]] was 42-year-old Bradley Curtis (born Zdzisław Szczęsny{{Citation needed|date=September 2024}}), a Polish-born American who was hired by the airline in 1974. He had been qualified as a captain of the Douglas DC-3, and was then assigned to train in either the Boeing 707 or 737, but failed to qualify either as a captain or as a first officer because he did not meet the requirements. He had needed to pay for his own training as an L-1011 flight engineer to keep his job. Curtis had 650 flying hours, including 157 hours in the TriStar.<ref name="riyadh" />{{rp|86–88}}<ref>{{cite web|author=Thomson, Jim|date=16 January 1982|title=Human behaviour in a crisis{{Snd}} Saudia 163|url=http://www.safetyinengineering.com/FileUploads/Human%20behaviour%20in%20a%20crisis%20-%20Saudia%20163_1369664909_2.pdf|access-date=2 March 2018|archive-date=24 September 2015|archive-url=https://web.archive.org/web/20150924093448/http://www.safetyinengineering.com/FileUploads/Human%20behaviour%20in%20a%20crisis%20-%20Saudia%20163_1369664909_2.pdf|url-status=dead}}</ref> |
||
Saudia was criticised for assigning to a single flight three pilots who had shown poor performance.{{Citation needed|date=June 2024}} |
Saudia was criticised for assigning to a single flight three pilots who had shown poor performance.{{Citation needed|date=June 2024}} |
||
Line 47: | Line 46: | ||
[[File:Saudia Flight 163 aftermath of fire onboard.jpg|thumb|The aftermath of the fire aboard Flight 163]] |
[[File:Saudia Flight 163 aftermath of fire onboard.jpg|thumb|The aftermath of the fire aboard Flight 163]] |
||
[[File:Saudia 163 overview.jpg|thumb|left|An overview of Saudia Flight 163 after the fire]] |
[[File:Saudia 163 overview.jpg|thumb|left|An overview of Saudia Flight 163 after the fire]] |
||
Flight 163 departed Qu'aid-e-Azam International Airport (now [[Jinnah International Airport]]) in Karachi, Pakistan, at 18:32 [[Time in Pakistan|Pakistan time]] (13:32 UTC) bound for [[ |
Flight 163 departed Qu'aid-e-Azam International Airport (now [[Jinnah International Airport]]) in Karachi, Pakistan, at 18:32 [[Time in Pakistan|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 [[Time in Saudi Arabia|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" />{{rp|66–67,98}} 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 al-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" />{{rp|6}} |
Almost seven minutes into the flight, the crew received warnings of smoke from the cargo compartment.<ref name="riyadh" />{{rp|66–67,98}} 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 al-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" />{{rp|6}} |
||
Line 54: | Line 53: | ||
At 21:35 (18:35 UTC), al-Khowyter declared an emergency and landed back at Riyadh.<ref>{{cite news|url=https://query.nytimes.com/gst/abstract.html?res=9F01E4DF1138E732A25753C2A96E9C94619FD6CF&legacy=true|title=265 Are Feared Dead As Saudi Plane Burns In Landing at Riyadh|date=August 20, 1980|work=The New York Times|access-date=26 February 2017|agency=UPI|issn=0362-4331}}</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 {{convert|13000|ft|m|adj=on|order=flip}} runway to slow and then exit onto the taxiway. The airplane stopped facing in the opposite direction from landing.<ref name="riyadh" />{{rp|7}} |
At 21:35 (18:35 UTC), al-Khowyter declared an emergency and landed back at Riyadh.<ref>{{cite news|url=https://query.nytimes.com/gst/abstract.html?res=9F01E4DF1138E732A25753C2A96E9C94619FD6CF&legacy=true|title=265 Are Feared Dead As Saudi Plane Burns In Landing at Riyadh|date=August 20, 1980|work=The New York Times|access-date=26 February 2017|agency=UPI|issn=0362-4331}}</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 {{convert|13000|ft|m|adj=on|order=flip}} runway to slow and then exit onto the taxiway. The airplane stopped facing in the opposite direction from landing.<ref name="riyadh" />{{rp|7}} |
||
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" />{{rp|8}} |
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 [[Flashover|flashed over]], and was destroyed by fire.<ref name="riyadh" />{{rp|8}} |
||
Why Captain al-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">{{cite news|title=Saudi Fire Negligence Suit Filed|date=27 October 1980|newspaper=[[Aviation Week & Space Technology]]|department=Air Transport|page=32}}</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>{{cite news|last1=Witkin|first1=Richard|url=https://query.nytimes.com/gst/abstract.html?res=940CE4D81639E731A25752C2A96E9C94619FD6CF&legacy=true|title=Fire on Saudi Plane Believed to Have Started in Cabin: Cockpit Escape Hatch Not Used|date=August 21, 1980|work=The New York Times|access-date=26 February 2017|issn=0362-4331}}</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" />{{rp|78}} |
Why Captain al-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">{{cite news|title=Saudi Fire Negligence Suit Filed|date=27 October 1980|newspaper=[[Aviation Week & Space Technology]]|department=Air Transport|page=32}}</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>{{cite news|last1=Witkin|first1=Richard|url=https://query.nytimes.com/gst/abstract.html?res=940CE4D81639E731A25752C2A96E9C94619FD6CF&legacy=true|title=Fire on Saudi Plane Believed to Have Started in Cabin: Cockpit Escape Hatch Not Used|date=August 21, 1980|work=The New York Times|access-date=26 February 2017|issn=0362-4331}}</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" />{{rp|78}} |
||
Line 84: | Line 83: | ||
|- |
|- |
||
|{{flagicon|Ireland}} Ireland |
|{{flagicon|Ireland}} Ireland |
||
| style="text-align:center;" |1 |
|||
|- |
|||
|{{flagicon|Sweden}} Sweden |
|||
| style="text-align:center;" |1 |
| style="text-align:center;" |1 |
||
|- |
|- |
||
Line 99: | Line 101: | ||
|- |
|- |
||
|{{flagicon|Pakistan}} Pakistan |
|{{flagicon|Pakistan}} Pakistan |
||
| style="text-align:center;" | |
| style="text-align:center;" |64 |
||
|- |
|- |
||
|{{flagicon|Philippines|1936}} Philippines |
|{{flagicon|Philippines|1936}} Philippines |
||
Line 153: | Line 155: | ||
* [[Air Canada Flight 797]] suffered an on-board fire in its aft lavatory, believed to be due to an electrical fault, which began damaging the aircraft's systems. The crew managed to successfully land the aircraft, but a flashover fire during the evacuation killed 23 of the 41 passengers on board. |
* [[Air Canada Flight 797]] suffered an on-board fire in its aft lavatory, believed to be due to an electrical fault, which began damaging the aircraft's systems. The crew managed to successfully land the aircraft, but a flashover fire during the evacuation killed 23 of the 41 passengers on board. |
||
*[[British Airtours Flight 28M]] had to abort takeoff at [[Manchester Airport]] due to an [[uncontained engine failure]] and engine fire. While an evacuation was ordered and conducted, issues with the evacuation led to 55 of the 182 occupants dying as a result of smoke inhalation. |
*[[British Airtours Flight 28M]] had to abort takeoff at [[Manchester Airport]] due to an [[uncontained engine failure]] and engine fire. While an evacuation was ordered and conducted, issues with the evacuation led to 55 of the 182 occupants dying as a result of smoke inhalation. |
||
*[[ValuJet Flight 592]] crashed into the [[Everglades|Florida Everglades]] shortly after takeoff from Miami International Airport on May 11, 1996, due to a fire caused by expired and improperly stored oxygen generators in the cargo hold. The crash resulted in the death of all 110 people on board, making it the deadliest aviation |
*[[ValuJet Flight 592]] crashed into the [[Everglades|Florida Everglades]] shortly after takeoff from Miami International Airport on May 11, 1996, due to a fire caused by expired and improperly stored oxygen generators in the cargo hold. The crash resulted in the death of all 110 people on board, making it the deadliest aviation disaster in Florida's history and leading to significant changes in airline safety regulations. |
||
==References== |
==References== |
Latest revision as of 15:54, 1 December 2024
Accident | |
---|---|
Date | 19 August 1980 |
Summary | Failure to evacuate following in-flight fire |
Site | Riyadh International Airport, Riyadh, Saudi Arabia 24°42′42″N 46°43′37″E / 24.71167°N 46.72694°E |
Aircraft | |
Aircraft type | Lockheed L-1011-200 TriStar |
Operator | Saudia |
IATA flight No. | SV163 |
ICAO flight No. | SVA163 |
Call sign | SAUDIA 163 |
Registration | HZ-AHK |
Flight origin | Quaid-e-Azam Int'l Airport, Karachi, Pakistan |
Stopover | Riyadh International Airport, Riyadh, Saudi Arabia |
Destination | Kandara Airport, Jeddah, Saudi Arabia |
Occupants | 301 |
Passengers | 287 |
Crew | 14 |
Fatalities | 301 |
Survivors | 0 |
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)[1] 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,[2] and the deadliest to occur in Saudi Arabia.[1][3] 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.[4]
Aircraft and crew
[edit]The aircraft involved in the accident was a Lockheed L-1011-200 TriStar (registered in Saudi Arabia as HZ-AHK). It made its first flight on 13 July 1979, and was delivered to Saudia on 21 August 1979.[5]: 89 [6]
The captain of the flight was 38-year-old Mohammed al-Khowyter, a Saudi who was hired by Saudia in 1965. He had flown numerous aircraft such as the Douglas DC-3 and DC-4, the McDonnell Douglas DC-9, and the Boeing 707 and 737. Al-Khowyter's records described him as a slow learner and needing more proper training. Al-Khowyter had 7,674 flying hours, including 388 hours in the TriStar. The first officer was 26-year-old Sami Hasanain, also a Saudi, who joined the airline in 1977 and had previously worked as a trainee. He received his type rating on the TriStar 11 days before the accident. At one point during his training, however, Hasanain was removed from flying school for poor performance. Hasanain had 1,615 flying hours, including 125 hours in the TriStar. The flight engineer was 42-year-old Bradley Curtis (born Zdzisław Szczęsny[citation needed]), a Polish-born American who was hired by the airline in 1974. He had been qualified as a captain of the Douglas DC-3, and was then assigned to train in either the Boeing 707 or 737, but failed to qualify either as a captain or as a first officer because he did not meet the requirements. He had needed to pay for his own training as an L-1011 flight engineer to keep his job. Curtis had 650 flying hours, including 157 hours in the TriStar.[5]: 86–88 [7]
Saudia was criticised for assigning to a single flight three pilots who had shown poor performance.[citation needed]
Accident
[edit]Flight 163 departed Qu'aid-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.[5]
Almost seven minutes into the flight, the crew received warnings of smoke from the cargo compartment.[5]: 66–67, 98 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 al-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.[5]: 6
At 21:35 (18:35 UTC), al-Khowyter declared an emergency and landed back at Riyadh.[8] 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 4,000-metre (13,000 ft) runway to slow and then exit onto the taxiway. The airplane stopped facing in the opposite direction from landing.[5]: 7
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.[5]: 8
Why Captain al-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.[9] 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.[10] 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.[5]: 78
Passengers
[edit]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.[5]: 89 [11][12]
Investigation
[edit]The investigation revealed the fire had started in the aft C3 cargo compartment.[5]: 77–78 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.[5]: 35 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.[13] The investigation found no evidence to support this theory.[5]: 78
Policy changes
[edit]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.[12]
Crew resource management
[edit]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.[14] "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.[15][14][16] 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 behaviour and actions during the flight were found to be contributing factors to the accident.[17]
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.[15]
In popular culture
[edit]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.[18]
This accident is covered in season 24, episode 8 of Mayday titled "Under Fire" (2024).[19]
See also
[edit]- List of accidents and incidents involving commercial aircraft
- Varig Flight 820 is a flight of the Brazilian airline Varig that departed from Galeão International Airport in Rio de Janeiro, Brazil, on July 11, 1973, for Orly Airport, in Paris, France. The plane, a Boeing 707, registration PP-VJZ, made an emergency landing on onion fields about 4 km from Orly Airport, because of smoke in the cabin from a fire in a lavatory. The fire caused 123 deaths, with only 11 survivors (10 crew members and a passenger).
- Air Canada Flight 797 suffered an on-board fire in its aft lavatory, believed to be due to an electrical fault, which began damaging the aircraft's systems. The crew managed to successfully land the aircraft, but a flashover fire during the evacuation killed 23 of the 41 passengers on board.
- British Airtours Flight 28M had to abort takeoff at Manchester Airport due to an uncontained engine failure and engine fire. While an evacuation was ordered and conducted, issues with the evacuation led to 55 of the 182 occupants dying as a result of smoke inhalation.
- ValuJet Flight 592 crashed into the Florida Everglades shortly after takeoff from Miami International Airport on May 11, 1996, due to a fire caused by expired and improperly stored oxygen generators in the cargo hold. The crash resulted in the death of all 110 people on board, making it the deadliest aviation disaster in Florida's history and leading to significant changes in airline safety regulations.
References
[edit]- ^ a b Ranter, Harro. "ASN Aircraft accident Lockheed L-1011 Tristar 200 HZ-AHK Riyad International Airport (RUH)". Aviation Safety Network. Flight Safety Foundation.
- ^ Ranter, Harro. "Lockheed L-1011 TriStar". Aviation Safety Network. Flight Safety Foundation. Retrieved 23 January 2019.
- ^ Ranter, Harro. "Saudi Arabia air safety profile". Aviation Safety Network. Flight Safety Foundation. Retrieved 23 January 2019.
- ^ Ranter, Harro. "ASN Aircraft accident McDonnell Douglas DC-10-10 TC-JAV Bois d'Ermenonville". Aviation Safety Network. Flight Safety Foundation. Retrieved 24 November 2020.
- ^ a b c d e f g h i j k l "Aircraft Accident Report, Saudi Arabian Airlines Lockheed L-1011, HZ-AHK, Riyadh, Saudi Arabia August 19th, 1980" (PDF). Saudi Arabian Presidency of Civil Aviation. 16 January 1982. Archived (PDF) from the original on 1 January 2014. Retrieved 26 February 2017 – via Federal Aviation Administration.
- ^ "Saudia HZ-AHK (Lockheed L-1011 TriStar - MSN 1169)". Airfleets aviation. Retrieved 28 February 2018.
- ^ Thomson, Jim (16 January 1982). "Human behaviour in a crisis – Saudia 163" (PDF). Archived from the original (PDF) on 24 September 2015. Retrieved 2 March 2018.
- ^ "265 Are Feared Dead As Saudi Plane Burns In Landing at Riyadh". The New York Times. UPI. 20 August 1980. ISSN 0362-4331. Retrieved 26 February 2017.
- ^ "Saudi Fire Negligence Suit Filed". Air Transport. Aviation Week & Space Technology. 27 October 1980. p. 32.
- ^ Witkin, Richard (21 August 1980). "Fire on Saudi Plane Believed to Have Started in Cabin: Cockpit Escape Hatch Not Used". The New York Times. ISSN 0362-4331. Retrieved 26 February 2017.
- ^ "Mecca pilgrims among victims Gas stoves found in burned plane". The Globe and Mail. 29 August 1980.
- ^ a b Haine, Edgar A. (2000). Disaster in the Air. Associated University Presses. pp. 67–69. ISBN 9780845347775.
- ^ "Jetliner fire first started by stove; death toll set at 301". The Morning Record and Journal. United Press International. 21 August 1980. p. 22.
- ^ a b Helmreich, Robert L.; Davies, Jan (2004). "Culture, Threat, and Error: Lessons from Aviation". Canadian Journal of Anesthesia. 51 (6): R2. doi:10.1007/bf03018331. S2CID 18098776.
- ^ a b Trkovsky, Josef (2017). Improved Flight Safety Through Effective Communication Among Multicultural Flight Crew (Ph.D. thesis). Scottsdale, Arizona: Northcentral University. pp. 4, 6–7, 104–114. Dissertation No.10278679 – via ProQuest Dissertations Publishing.
- ^ Helmreich, RL; Klinect, JR; Wilhelm, JA; Merritt, AC (2001). "Culture, Error, and Crew Resource Management". In Salas, Eduardo; Bowers, Clint A; Edens, Eleana (eds.). Improving Teamwork in Organizations: Applications of Resource Management Training. Lawrence Erlbaum Associates. ISBN 0805828443. OCLC 46790778.
- ^ Mayday Season 24, episode 8 "Under Fire" (2024), Cineflix Productions
- ^ Karlins, Marvin; Koh, Freddie; McCully, Len; Chan, C. T. "CRM for CRM: Cockpit Relevant Movies for Crew Resource Management". The CRM Advocate.
- ^ "Under Fire". IMBD. Retrieved 16 March 2024.
External links
[edit]External images | |
---|---|
Airliners.Net Picture of Saudia 163 | |
Airliners.Net Pre accident picture of HZ-AHK |
- Burian, Barbara K. (2006). "Aeronautical Emergency and Abnormal Checklists: Expectations and Realities" (PDF). NASA Ames Research Center. Retrieved 12 January 2017.
- Thomson, Jim (2013). "Human Behaviour in a Crisis – The Saudia 163 Accident, 1980" (PDF). Safetyinengineering.com. Archived from the original (PDF) on 24 September 2015. Retrieved 12 January 2017.
- Final Accident Report (Archive) – General Authority of Civil Aviation
- ICAO Circular 178-AN/111 No. 5 Lockheed L-1011 Tristar, HZ-AHK, accident at Riyadh, Saudi Arabia, on 19 August 1980. Report dated 16 January 1982, released by Presidency of Civil Aviation, Saudi Arabia.
- "Saudi Arabian Airlines Flight 163 Flight Path Animation". Federal Aviation Administration. 4 December 2020 – via YouTube.
- Cockpit voice recorder transcript
- Saudia accidents and incidents
- Airliner accidents and incidents caused by in-flight fires
- Aviation accidents and incidents in 1980
- Aviation accidents and incidents in Saudi Arabia
- August 1980 events in Asia
- 1980 in Saudi Arabia
- Accidents and incidents involving the Lockheed L-1011
- Fires in Saudi Arabia
- 1980 disasters in Saudi Arabia
- 20th century in Riyadh