South African Airways Flight 295

1987 plane crash in the Indian Ocean

South African Airways Flight 295

ZS-SAS, the aircraft involved in the accident

Accident
Date| 28 November 1987 (1987-11-28)
Summary| In-flight fire of undetermined origin in cargo hold leading to loss of control and in-flight breakup[1]
Site| Indian Ocean
19°10′30″S 59°38′0″E﻿ / ﻿19.17500°S 59.63333°E﻿ / -19.17500; 59.63333﻿ (SA Helderberg Debris Site1)
Aircraft
Aircraft type| Boeing 747-244BM Combi
Aircraft name| Helderberg
Operator| South African Airways
IATA flight No.| SA295
ICAO flight No.| SAA295
Call sign| SPRINGBOK 295
Registration| ZS-SAS
Flight origin| Chiang Kai-shek International Airport,
Taipei, Taiwan
Stopover| Plaisance Airport,
Plaine Magnien, Mauritius
Destination| Jan Smuts International Airport, Johannesburg, South Africa
Occupants| 159
Passengers| 140
Crew| 19
Fatalities| 159[2]
Survivors| 0

South African Airways Flight 295 (SA295/SAA295) was a scheduled international passenger flight from Chiang Kai-shek International Airport, Taipei, Taiwan, to Jan Smuts International Airport, Johannesburg, South Africa, with a stopover in Plaisance Airport, Plaine Magnien, Mauritius. On 28 November 1987, the aircraft serving the flight, a Boeing 747-200 Combi named Helderberg, experienced a catastrophic in-flight fire in the cargo area, broke up in mid-air, and crashed into the Indian Ocean east of Mauritius, killing all 159 people on board.[3][4] An extensive salvage operation was mounted to try to recover the aircraft's flight recorders, one of which was recovered from a depth of 4,900 metres (16,100 ft).

The official inquiry, headed by Judge Cecil Margo, was unable to determine the cause of the fire. This lack of a conclusion led to conspiracy theories, debates and speculation about the nature of Flight 295's cargo, as well as a subsequent post-apartheid investigation and calls from relatives of those on the flight to re-open the investigation in the years following the accident.[5]

## Aircraft and crew[edit]

The aircraft involved was a Boeing 747-244BM Combi registered ZS-SAS and named Helderberg. This was the 488th built 747, made its first flight on 12 November 1980 and was delivered to South African Airways (SAA) on 24 November 1980.[6]

The Boeing 747-200B Combi model permits the mixing of passengers and cargo on the main deck according to load factors on any given route and Class B cargo compartment regulations.[6] Flight 295 had 140 passengers and six pallets of cargo on the main deck.[6] The master waybills stated that 47,000 kilograms (104,000 lb) of baggage and cargo were loaded on the aircraft.[7] A Taiwanese customs official performed a surprise inspection of some of the cargo; he did not find anything that could be characterised as suspicious.[7] According to Tinus Jacobs who was SAA's manager in Taiwan at the time of Flight 295, the flight crew appeared relaxed and "happy to fly" before takeoff and did not display any concerns about the cargo.[8]

The captain of Flight 295 was 49-year-old Dawid Jacobus Uys, a former South African Air Force pilot with 13,843 hours' experience of which 3,884 hours was on the Boeing 747 series airplanes.[9] Uys was described by colleagues as professional and skilled and at the time of the accident was considering retiring to take up a role with the South African Pilots' Association.[10] The flight crew also consisted of 36-year-old first officer David Attwell and 37-year-old relief first officer Geoffrey Birchall, with 7,362 and 8,749 hours' experience (including 4,096 and 4,555 hours on the Boeing 747) respectively; and 45-year-old flight engineer, Giuseppe "Joe" Bellagarda and 34-year-old relief flight engineer, Alan Daniel, with 7,804 hours and 1,595 hours (4,254 and 227 of them on the Boeing 747) of experience respectively.[11]

## Accident[edit]

Flight 295 took off at 14:23 UTC (22:23 local time) on 27 November 1987 from Taipei Chiang Kai Shek International Airport on a flight to Johannesburg via Mauritius.[6][12]

Thirty-four minutes after departure, the crew contacted Hong Kong air traffic control to obtain clearance from waypoint ELATO (22°19′N 117°30′E﻿ / ﻿22.317°N 117.500°E﻿ / 22.317; 117.500) to ISBAN. A position report was made over ELATO at 15:03:25, followed by waypoints SUNEK at 15:53:52, ADMARK at 16:09:54 and SUKAR (12°22′N 110°54′E﻿ / ﻿12.367°N 110.900°E﻿ / 12.367; 110.900) at 16:34:47.[13] The aircraft made a routine report to the SAA base at Johannesburg at 15:55:18.[13]

At some point during the flight, believed to be during the beginning of its landing approach to Mauritius, a fire developed in the cargo section on the main deck which was probably not extinguished before impact. The 'smoke evacuation' checklist calls for the aircraft to be depressurised, and for two of the cabin doors to be opened. No evidence exists that the checklist was followed or that the doors were opened. A crew member might have gone into the cargo hold to try to fight the fire. A charred fire extinguisher was later recovered from the wreckage on which investigators found molten metal.[7]

The following communication was recorded with Mauritius air traffic control, located at Plaisance Airport near Port Louis:[13][14]

Transcript of communication with Mauritius air traffic control

Time  | Speaker  | Dialog  | Comment from official inquiry
23:48:51  | 295  | Eh, Mauritius, Mauritius, Springbok Two Niner Five.  |
23:49:00  | ATC | Springbok Two Nine Five, eh, Mauritius, eh, good morning, eh, go ahead.  |
23:49:07  | 295  | Eh, good morning, we have, eh, a smoke, eh, eh, problemsss and we're doing emergency descent to level one five (in error), eh, one four zero. (flight level 140 is at 14,000 feet)  |
23:49:18  | ATC  | Confirm you wish to descend to flight level one four zero.  |
23:49:20  | 295  | Ja, we have already commenced, an, due to [a] smoke problem in the aeroplane.  |
23:49:25  | ATC  | Eh, roger, you are clear to descend immediately to flight level one four zero.  |
23:49:30  | 295  | Roger, we will appreciate if you can alert the fire, ehp, ehp eh (inhale) eh  |
23:49:40  | ATC  | Do you wish to eh, do you request a full emergency?  |
23:49:48  | 295  | Okay Joe, kan jy...vir ons | [in Afrikaans] Okay Joe can you...for us
23:49:51  | ATC  | Springbok Two Nine Five, Plaisance.  |
23:49:54  | 295  | Sorry, go ahead?  |
23:49:56  | ATC  | Do you, eh, request a full emergency please, a full emergency?  |
23:50:00  | 295  | Affirmative, that's Charlie Charlie.  |
23:50:02  | ATC  | Roger, you declare a full emergency, roger.  |
23:50:04  | 295  | Thank you.  |
23:50:40  | ATC  | Springbok Two Nine Five, Plaisance.  |
23:50:44  | 295  | Eh, go ahead.  |
23:50:46  | ATC  | Request your actual position please and your DME distance?  |
23:50:51  | 295  | Eh, we haven't got the DME yet.  |
23:50:55  | ATC  | Eh, roger and your actual position please.  |
23:51:00  | 295  | Eh, say again.  |
23:51:02  | ATC  | Your actual position.  |
23:51:08  | 295  | Now we've lost a lot of electrics, we haven't got anything on the, on the aircraft now.  |
23:51:12  | ATC  | Eh, roger, I declare a full emergency immediately.  |
23:51:15  | 295  | Affirmative.  |
23:51:18  | ATC  | Roger.  |
23:52:19  | ATC  | Eh, Springbok Two Nine Five, do you have an Echo Tango Alfa Plaisance please?  |
23:52:30  | ATC  | Springbok Two Nine Five, Plaisance.  |
23:52:32  | 295  | Ja, Plaisance?  |
23:52:33  | ATC  | Do you have an Echo Tango Alfa Plaisance please?  |
23:52:36  | 295  | Ja, eh, zero zero, eh eh eh three zero.  |
23:52:40  | ATC  | Roger, zero zero three zero, thank you.  |
23:52:50  | 295  | Hey Joe, shut down the oxygen left.  | Inadvertent transmission from the aircraft
23:52:52  | ATC  | Sorry, say again please?  |
00:01:34  | 295  | Eh, Plaisance, Springbok 295, we've opened the door[s] to see if we (can?)...we should be OK  |
00:01:36  | 295  | Look there (?)  | Exclamation by someone else, and is said over the last part of the previous sentence
00:01:45  | 295  | Donnerse deur t... | [in Afrikaans] Close the bloody door (More directly translated: Damned door c...)
00:01:57  | 295  | Joe, switch up quickly, then close the hole on your side.  |
00:02:10  | 295  | Pressure(?) twelve thousand  |
00:02:14  | 295  | ...Genoeg is...Anders kan ons vlug verongeluk | [in Afrikaans] ...Is enough...otherwise our flight could come to grief (More directly translated: ...enough is... otherwise our flight might crash)
00:02:25  | 295  | (Carrier wave only)  |
00:02:38  | 295  | Eh Plaisance, Springbok Two Nine Five, do [did] you copy?  |
00:02:41  | ATC  | Eh negative, Two Nine Five, say again please, say again.  |
00:02:43  | 295  | We're now sixty five miles.  |
00:02:45  | ATC  | Confirm sixty five miles.  | Incorrectly understood by air traffic control to mean that the aircraft was 65 miles from the airport; in fact it was 65 miles from waypoint Xagal, and 145 miles from the airport.
00:02:47  | 295  | Ja, affirmative Charlie Charlie.  |
00:02:50  | ATC  | Eh, Roger, Springbok eh Two Nine Five, eh re you're recleared flight level five zero. Recleared flight level five zero.  |
00:02:58  | 295  | Roger, five zero.  |
00:03:00  | ATC  | And, Springbok Two Nine Five copy actual weather Plaisance Copy actual weather Plaisance. The wind one one zero degrees zero five knots. The visibility above one zero kilometres. And we have a precipitation in sight to the north. Clouds, five oktas one six zero zero, one okta five thousand feet. Temperature is twenty two, two two. And the QNH one zero one eight hectopascals, one zero one eight over.  |
00:03:28  | 295  | Roger, one zero one eight.  |
00:03:31  | ATC  | Affirmative, eh and both runways available if you wish.  |
00:03:43  | ATC  | And two nine five, I request pilot's intention.  |
00:03:46  | 295  | Eh, we'd like to track in eh, on eh one three.  |
00:03:51  | ATC  | Confirm runway one four.  |
00:03:54  | 295  | Charlie Charlie  |
00:03:56  | ATC  | Affirmative and you're cleared, eh direct to Foxtrot Foxtrot. You report approaching five zero  | Clearance granted to the Flic-en-Flac non-directional navigation beacon.
00:04:02  | 295  | Kay  | Last transmission from the aircraft
00:08:00  | ATC  | Two Nine Five, Plaisance  |
00:08:11  | ATC  | Springbok Two Nine Five, Plaisance  |
00:08:35  | ATC  | Springbok Two Nine Five Plaisance  | No answer

The fire began to destroy the aircraft's important electrical systems, resulting in loss of communication and control of the aircraft. At exactly 00:07 UTC (4:07 local time), the aircraft broke apart in mid-air, the tail section breaking off first, due to the fire beginning to burn the structure of the aircraft, and crashed into the Indian Ocean, about 134 nautical miles (154 mi; 248 km) from the airport.[2] Other theories given for the ultimate demise of the aircraft were that the flight crew eventually became incapacitated by the smoke and fire or extensive damage to the 747's control systems rendered the plane uncontrollable before it hit the ocean.[15]

After communication with Flight 295 was lost for thirty-six minutes, at 00:44 (04:44 local time), air traffic control at Plaisance Airport formally declared an emergency.[7]

## Search and salvage[edit]

Taiwan

Johannesburg

Crash site

Mauritius

class=notpageimage|

Map of the Indian Ocean, showing the origin of the flight in Taiwan, stopover in Mauritius, destination of Johannesburg and accident site near Mauritius

When Flight 295 last informed Plaisance air traffic control of its position, its report was incorrectly understood to be relative to the airport rather than its next waypoint, which caused the subsequent search to be concentrated too close to Mauritius.[13] The United States Navy sent aircraft from Diego Garcia, which were used to conduct immediate search and rescue operations in conjunction with the French Navy.[16] By the time the first surface debris was located twelve hours after impact, it had drifted considerably from the impact location. Oil slicks and eight bodies showing signs of extreme trauma appeared in the water.[7] There were no survivors.

After recovery of the wreckage from 4,000 m (13,000 ft) below the surface of the ocean, the aircraft's fuselage and cabin interior were partly reassembled in one of SAA's hangars at Jan Smuts Airport, where it was examined and finally opened for viewing to the airline's staff and selected members of the public.[citation needed]

## Investigation[edit]

Rennie Van Zyl, South Africa's head crash investigator, examined three wristwatches from baggage recovered from the surface; two of the watches were still running according to Taiwan time. Van Zyl deduced the approximate time of impact at 00:07:00, around three minutes after the last communication with air traffic control.[7]

Immediately after the crash, the press and public opinion suspected that terrorism brought down Flight 295. South Africa, then under the control of the apartheid government, was the target of terrorism both domestically and internationally, and offices for SAA, the country's flag carrier, had previously been attacked.[17] Experts searched for indicators of an explosion on the initial pieces of wreckage discovered, such as surface pitting, impact cavities and spatter cavities caused by white-hot fragments from explosive devices that strike and melt metal alloys found in aircraft structures. Experts found none of this evidence.[7] The investigators drew blood samples from two of the recovered bodies and found that the bodies had soot in their tracheae, indicating that at least two had died from smoke inhalation before the aircraft had crashed, and concluded that some of the passengers would have already lost their lives even if the pilots had successfully reached the airport.[7][18][19]

South Africa mounted an underwater search, named 'Operation Resolve', to try to locate the wreckage. The underwater locator beacons (ULBs) attached to the flight recorders were not designed for deep ocean use; nevertheless, a two-month-long sonar search for them was carried out before the effort was abandoned on 8 January 1988 when the ULBs were known to have stopped transmitting (at the time a ULB had to generate sonic pulses for thirty days).[20] Steadfast Oceaneering, a specialist deep-ocean recovery company in the US, was contracted at great expense to find the site and recover the flight recorders.[21] The search area is described as being comparable in size to that of the wreck of the Titanic, with the water at 5,000 metres (16,000 ft) being considerably deeper than any previously successful salvage operation.[22] The wreckage was found within two days of Steadfast Oceaneering commencing its search.[22]

Map this section's coordinates using OpenStreetMap

Download coordinates as:

* KML
* GPX (all coordinates)
* GPX (primary coordinates)
* GPX (secondary coordinates)

Three debris fields were found: 19°10′30″S 59°38′0″E﻿ / ﻿19.17500°S 59.63333°E﻿ / -19.17500; 59.63333﻿ (SA Helderberg Debris Site1), 19°9′53″S 59°38′32″E﻿ / ﻿19.16472°S 59.64222°E﻿ / -19.16472; 59.64222﻿ (SA Helderberg Debris Site2) and 19°9′15″S 59°37′25″E﻿ / ﻿19.15417°S 59.62361°E﻿ / -19.15417; 59.62361﻿ (SA Helderberg Debris Site3). These locations were spread 1.5 km (0.93 mi), 2.3 km (1.4 mi) and 2.5 km (1.6 mi) apart, indicating that the aircraft broke up in mid-air (it was suggested that the tail separated first).[15] On 6 January 1989, the cockpit voice recorder (CVR) was salvaged successfully from a record depth of 4,900 metres (16,100 ft) by the remotely operated vehicle (ROV) Gemini,[23] but the flight data recorder was never found.[18]

Van Zyl took the voice recorder to the US National Transportation Safety Board (NTSB) in Washington, DC, both to show his goodwill and to ensure neutral observers.[7] Van Zyl believes that if he kept the CVR in South Africa he could have been accused of covering up the truth.[7] At the NTSB, Van Zyl felt frustration that the degraded (but still functional) CVR, which had been in the deep ocean for fourteen months,[23] did not initially yield any useful information. Around twenty-eight minutes into the recording the CVR indicated that the fire alarm sounded. Fourteen seconds after the fire alarm, the circuit breakers began to pop. Investigators believe that around eighty circuit breakers failed. The CVR cable failed eighty-one seconds after the alarm. The recording revealed the extent of the fire.[7]

Van Zyl discovered that the front-right pallet located in the main deck's cargo hold was the seat of the fire. The flight manifest said that pallet mostly comprised computers in polystyrene packaging. The investigators said that the localised fire likely came in contact with the packaging and produced gases that accumulated near the ceiling. They also said that gases ignited into a flash fire that affected the entire cargo hold. The fire did not burn lower than one metre above the cargo floor. The walls and ceiling of the cargo hold received severe fire damage. Van Zyl ended his investigation without discovering why the fire started.[7]

The official report noted the presence of the computer equipment, and suggested that a possible cause could have been the batteries contained in the computers exploding or spontaneously combusting, although this was not given as a conclusive cause of the fire.[24]

### Margo commission[edit]

An official commission of inquiry was chaired by South African Judge Cecil Margo,[18][25] with co-operation from the NTSB and the aircraft's manufacturer, Boeing. The board of the "Margo Commission" consisted of Judge Cecil S. Margo, Judge Hurrylall Goburdhun (Mauritius), George N. Tompkins Jr (USA), G.C. Wilkinson (UK), Dr Y. Funatsu (Japan), J.J.S. Germisuys (South Africa), Dr J. Gilliland (South Africa) and Colonel Liang Lung (Taiwan).[26]

The official report determined that while Flight 295 was over the Indian Ocean, a fire had occurred in the cargo hold of the main deck, originating in the front right-hand cargo pallet.[18] Aircraft parts recovered from the ocean floor showed fire damage sustained in temperatures over 300 °C (570 °F); tests showed that temperatures of 600 °C (1,100 °F) would have been required to melt a carbon-fibre tennis racket recovered from the crash site. The fire also damaged and destroyed the aircraft's electrical systems resulting in the loss of many of the instruments on the flight deck and rendering the crew unable to determine their position.[19] The reason for the aircraft's loss was not identified beyond doubt, but there were two possibilities detailed in the official report: firstly, that the crew became incapacitated due to smoke penetrating into the cockpit;[18] and secondly, that the fire weakened the structure so that the tail separated, leading to impact with the ocean. The commission concluded that it was not possible to apportion blame to any one individual for the fire, removing any terrorism concerns.[27] Boeing is quoted in the report as having "contested" any scenario that involved a break-up of the aircraft, hence the commission went no further than simply mentioning the two possible scenarios in its final report, as incidental to the primary cause of the accident.[15]

The commission determined that inadequate fire detection and suppression facilities in the class B cargo bays (the type used aboard the 747-200 Combi) were the primary cause of the aircraft's loss.[5] The accident alerted aviation authorities worldwide that the regulations regarding class B cargo bays had lagged far behind the growth in their capacity. The exact source of ignition was never determined, but the report concluded that there was sufficient evidence to confirm that the fire had burned for some considerable time and that it might have caused structural damage.[28]

### Combi design[edit]

The crash was the first fire incident on the 747 Combi and one of few fires on widebody aircraft. Fred Bereswill, the investigator from Boeing, characterised the Flight 295 fire as significant for this reason.[29] Barry Strauch of the NTSB visited Boeing's headquarters to inquire about the Combi's design. Boeing's fire test in the Combi models did not accurately match the conditions of Flight 295's cargo hold; in accordance with federal US rules, the Boeing test involved setting a bale of tobacco leaves ablaze. The fire stayed within the cargo hold. The air in the passenger cabin was designed to have a marginally higher pressure than cargo area hold, so if a crew member opened the door to the cargo hold, the air from the passenger cabin would flow into the cargo hold, stopping any smoke or gases from exiting through the door.[7]

Investigators devised a new test involving a cargo hold with conditions similar to the conditions of Flight 295; the plastic covers and extra pallets provided fuel for the fire, which would spread quickly before generating enough smoke to activate smoke alarms. The hotter flame achieved in the new test heated the air in the cargo hold. This heated air had a higher pressure than normal, and overcame the pressure differential between the cargo hold and the passenger cabin. When the door between the passenger and cargo holds was open, smoke and gases therefore flowed into the passenger cabin.[7]

The test, as well as evidence from the accident site, proved to the investigators that the 747 Combi's use of a class B cargo hold did not provide enough fire protection to the passengers.[30][31] The US Federal Aviation Administration (FAA) confirmed this finding in 1993 with its own series of tests.[32]

After the accident, SAA discontinued use of the Combi and the FAA introduced new regulations in 1993 specifying that manual firefighting must not be the primary means of fire suppression in the cargo compartment of the main deck.[33][34] The new regulations banned larger cargo hold variants of the 747 Combi, the smaller variants also need to comply with these new standards, which required weight increases, made the 747 Combi less efficient. Nevertheless, the Combi variants remained in the 747 product line up until 2002, when the last 747-400 Combi was delivered to KLM.[35]

The cenotaph of the South African Airways 295 accident, located near Taiwan Taoyuan International Airport. The cenotaph reads South African Airways Air Disaster Cenotaph (南非航空公司空難紀念碑, Hanyu Pinyin: Nánfēi Hángkōng Gōngsī Kōngnàn Jìnìanbēi, literally South African Airways Air Disaster Memorial Stone)

## Theories regarding the cause of the fire[edit]

In January 1992, the journal of the Royal Aeronautical Society (RAeS) reported that the inquiry into the in-flight fire that destroyed Flight 295 might be reopened because SAA had allegedly confirmed that its passenger jets had carried cargo for Armscor, a South African arms manufacturer. The RAeS journal, Aerospace, asserted: "It is known that the crew and passengers were overcome by a main deck cargo fire, and the ignition of missile rocket fuel is one cause now under suspicion."[36] A complaint against the newspaper that first published the allegations, Weekend Star, was lodged by Armscor.[37]

The inquiry was not reopened, which likely led to the proliferation of a number of conspiracy theories concerning the nature of the cargo that caused the fire, which subsequently increased public doubts about the outcome of the initial inquiry.[38] Examples of such theories include:

* The South African Defence Force was smuggling the hoax substance red mercury on Flight 295 for its atomic bomb project.

* Reports from the Project Coast investigation suggested there was a waybill showing that 300 grams of activated carbon had been placed on board Flight 295, leading to speculation that this substance had caused the fire.[39]

In 2000, the South African television program Carte Blanche dedicated an investigation to a number of these allegations.[40]

A South African government chemist examined a microscopic particle on the nylon netting next to the front-right pallet on Flight 295. The chemist found that the airflow patterns on the iron suggested that it travelled at a high velocity while in a molten state; therefore the fire on Flight 295 may have not been a flash fire triggered by packaging.[7] Fred Bereswill, the investigator from Boeing, said that this would suggest that the source of the fire would have had properties like a sparkler, with the source including its own oxidising agent. A British fire and explosion analyst examined the exterior skin of the aircraft which had been located above the pallet; the analyst found that the skin became as hot as 300 degrees Celsius. Bereswill said that it would be difficult for a fire to burn through the skin of an aircraft in-flight because of the cool airflow outside the aircraft.[7]

### David Klatzow's theory[edit]

David Klatzow was one of the forensic scientists who was retained to work on the case by Boeing's counsel around the time of the official enquiry.[41] He subsequently criticised the Margo commission for spending an inordinate amount of time looking into "relatively irrelevant issues" and that the commission ignored the most important question, what was the source of the fire and who had been responsible for loading it onto the aircraft? Klatzow believes that there are certain irregularities in parts of the commission transcript that indicate that something on the CVR transcript had to be concealed.[42]

Klatzow put forward a theory that the fire likely involved substances that would not normally be carried on a passenger aircraft and that the fire was not likely a wood, cardboard, or plastic fire.[7] South Africa was under an arms embargo at the time; the South African government therefore had to buy arms clandestinely.[43] Klatzow's theory postulates that the government placed a rocket system in the cargo hold, and that vibration caused the ignition of unstable ammonium perchlorate, which is a chemical compound used as a missile propellant.[44]

Klatzow contends that conversation of the crew suggests that the fire started above the South China Sea, shortly after takeoff; he believes that this indicates that the voice recorder was not working for a long period of the flight or that the crew turned it off (CVRs in aircraft at that time only recorded thirty minutes[45]). If this is the case, he says it is then likely that an unknown number of the passengers would have already died from smoke inhalation from the first fire. Klatzow believes that theory is consistent with reports that found most of the passengers were in the first class area at the front of the aircraft as smoke from the rear cabin forced them to move forward. The captain did not land the aircraft directly after the fire, Klatzow argues, because if he had he would have been arrested for endangering the lives of his passengers and it would have caused a major problem for South Africa, costing the country and SAA R400 million (approx. $200 million in 1987). Klatzow argues that the captain, who was also a reservist in the South African Air Force, would therefore have been ordered to carry on to South Africa in hopes of making it there before the aircraft's structural integrity gave in.[46] These points have been disputed.[47]

On 20 July 2011, retired SAA captain Clair Fichardt announced that he had made a statement in connection with the missing Johannesburg air traffic control tapes, after he was persuaded to do so by Klatzow.[48] Fichardt claimed that Captain James Deale admitted to handing the tapes to Captain Mickey Mitchell, who was chief pilot at the Johannesburg control centre on the night of the crash. Deale would further have stated that Gert van der Veer, head of SAA, and lawyer Ardie Malherbe were present during the transfer of the tapes. Earlier, during the Truth and Reconciliation Commission (TRC) hearings, Klatzow had cross-examined Van der Veer, Mitchell, and Vernon Nadel, the operations officer who was on duty.[49]

## Post-apartheid investigation[edit]

In 1996, the TRC, established by the post-apartheid South African government, investigated apartheid-era atrocities. In particular, Flight 295 was investigated to determine if there was any truth behind conspiracy theories that asserted that the Margo Commission had covered up or missed any evidence that might implicate the previous government.[38] Klatzow was invited by the TRC to explain his theories and cross-examine witnesses. Unlike most other hearings of the TRC, the hearing into Flight 295 was conducted in camera,[41] and without any representation from the South African Civil Aviation Authority (CAA);[47] Klatzow considered the CAA untrustworthy because it had participated in the official enquiry, which he considered flawed. A number of key aspects of Klatzow's theory hinged on his criticism of the actions of Judge Margo during the official enquiry, yet Judge Margo was not summoned to answer any of the allegations made against him.[41]

The TRC concluded that nothing listed in the flight manifest could have caused the fire, a conclusion that was met with controversy within the public. Following public pressure, the TRC records were released into the public domain in May 2000. Upon receiving the documents, Transport Minister Dullah Omar stated that the inquiry would be reopened if any fresh evidence was discovered.[50] The South African Police Service were tasked to investigate whether there was any new evidence, and to make a recommendation to the minister. In October 2002, the minister announced that no new evidence had been found to justify re-opening the enquiry.[51][38]

On the 25th anniversary of the crash, Peter Otzen Jnr, the son of one of the victims, announced that he was approaching the Constitutional Court of South Africa in an attempt to have the commission of inquiry into the disaster reopened.[52] In pursuit of this, he had obtained affidavits from former SAA employees who had never given any evidence before. An Australian national named Allan Dexter who had worked in public relations for SAA gave a sworn statement to Mr. Otzen claiming that he had been informed by the SAA manager at Taipei airport that Flight 295 was carrying rocket fuel which caused it to crash, and that the Captain had expressed concerns about the safety of the cargo but had been ordered from Johannesburg to fly the plane.[53] In a 2014 interview, some of the accusations were disputed by Tinus Jacobs, SAA's manager in Taiwan who saw Flight 295 off. Jacobs claimed that due to Taiwan's status under martial law at the time, only one telephone at the airport (located in the office of China Airlines) could be used to make international calls and that none of Flight 295's crew had access to it. Jacobs furthermore claimed that Captain Uys and the other crew members appeared relaxed and routine both the previous day and on the evening of the flight's departure.[54]

## Newer theories[edit]

In 2014, South African investigative journalist Mark D. Young presented a theory that a short circuit in the onboard electronics may have started the fire.[55][56] The so-called wet arc tracking arises from the action of moisture when the insulation of live wires is damaged. A leakage current to another damaged wire with the respective potential difference may form. The resulting flashover may reach temperatures of up to 5,000 °C (9,000 °F). This temperature is sufficient to ignite the thermal-acoustic insulation blankets that were in use at the time until the late 1990s. Such a short circuit may have caused the fire on board Swissair Flight 111, resulting in the crash of the aircraft in 1998.[57]: 253

## Passengers and crew[edit]

Passengers and crew nationalities on board SAA Flight 295:[58]

Nationality  | Passengers  | Crew  | Total

|
|
|

Australia | 2 | 0 | 2
Hong Kong | 2 | 0 | 2
Denmark | 1 | 0 | 1
Japan | 47 | 0 | 47
Mauritius | 2 | 0 | 2
Netherlands | 1 | 0 | 1
South Africa | 52 | 19 | 71
South Korea | 1 | 0 | 1
Taiwan | 30 | 0 | 30
United Kingdom | 1 | 0 | 1
West Germany | 1 | 0 | 1
Total | 140 | 19 | 159[59]

Taiwanese authorities stated that 58 passengers began flying in Taipei, including 30 Taiwanese citizens, 19 South Africans, 47 Japanese, two Mauritians, one Dane, one Dutch, one Briton, and one West German. The other passengers transferred from other flights arriving in Taipei, and as such their nationalities were not known to Taiwanese authorities.[60]

At least two passengers died of smoke inhalation. The rest died from the extreme trauma sustained in the crash.[7]

Among the passengers was Kazuharu Sonoda, a Japanese professional wrestler also known as Haru Sonoda and Magic Dragon, and his wife, who were travelling as part of their honeymoon. They were offered and sent on the flight by All Japan Pro-Wrestling president Giant Baba to appear on a wrestling show in South Africa, promoted by fellow wrestler Tiger Jeet Singh.[61]

## Dramatisation[edit]

The crash was featured in Season 5 of the Canadian-made, internationally distributed documentary series Mayday, in the episode "Fanning the Flames."[7]

## See also[edit]

* List of unrecovered and unusable flight recorders
* UPS Airlines Flight 6, another 747 that crashed because of an onboard fire

## References[edit]

Notes

1. ^ "Final Report ZS-SAS.pdf" (PDF). Archived from the original (PDF) on 14 May 2022. Retrieved 8 February 2022.
2. ^ a b Accident description at the Aviation Safety Network
3. ^ Watt 1990.
4. ^ Marsh 1994, p. 14.
5. ^ a b Marsh 1994, p. 19.
6. ^ a b c d Marsh 1994.
7. ^ a b c d e f g h i j k l m n o p q r s "Fanning the Flames / Cargo Conspiracy". Mayday (Canadian TV series) (Television production). Season 5. OCLC 829959853.
8. ^ Joubert, Jan-Jan (19 October 2014). "Helderberg captain 'quite happy to fly'". TimesLIVE. Retrieved 28 August 2022.
9. ^ Margo 1990, p. 17.
10. ^ Boyle, Brendan (29 November 1987). "Pilot of crashed plane 'one of South Africa's best'". Retrieved 28 August 2022.
11. ^ Margo 1990, pp. 20–22.
12. ^ "SAA 'murdered people aboard Helderberg'." IOL.
13. ^ a b c d Margo 1990.
14. ^ Hopkins & Hilton-Barber 2005.
15. ^ a b c Marsh 1994, p. 16.
16. ^ Dreyer 2006, p. 261.
17. ^ Thousands Rampage Through Harare, Upset Over Machel's Death, Associated Press, 21 October 1986
18. ^ a b c d e Marsh 1994, p. 18.
19. ^ a b "SAA flight 295 Helderberg crash". southafrica.to. Retrieved 12 May 2020.
20. ^ Mueller 1988.
21. ^ Kutzleb 1988.
22. ^ a b Strümpfer 2006.
23. ^ a b Marsh 1994, p. 17.
24. ^ "This Wouldn't Be The First Time A Plane Mysteriously Disappeared into The Indian Ocean". Business Insider. Retrieved 31 December 2015.
25. ^ "Selective Summary of evidence given at the inquiry on the disaster involving the Helderberg (Flight SA 295 on 28 November 1987)". South African Government. 18 August 2000. Retrieved 20 August 2008.
26. ^ Young, Mark. "The Helderberg disaster: Was this the cause of the crash?". Retrieved 1 October 2014.
27. ^ Klatzow 2010, p. 167.
28. ^ Marsh 1994, pp. 18–19.
29. ^ Bowman, Martin W. (2015). Boeing 747: A History: Delivering the Dream. Casemate Ipm.
30. ^ Cheney, Daniel I. (2010). Lessons Learned from Transport Airplane Accidents (PDF). Sixth Triennial International Fire and Cabin Safety Research Conference. Atlantic City: Federal Aviation Administration.
31. ^ "Designee Newsletter" (PDF). Transport Airplane Directorate, Federal Aviation Administration. 1 April 1989. pp. 12–14. Archived from the original (PDF) on 13 September 2012. Retrieved 21 July 2011.
32. ^ Dickerson & Blake 1993.
33. ^ "Lessons Learned From Transport Airplane Accidents: Fire". Federal Aviation Administration. Archived from the original on 25 February 2013. Retrieved 25 July 2011.
34. ^ "Airworthiness Directive 93-07-15". Federal Aviation Administration. 2 May 1993. Archived from the original on 29 January 2018. Retrieved 25 July 2011.
35. ^ "Boeing". boeing.com.
36. ^ Aerospace. Vol. 19\. Royal Aeronautical Society. January 1992. p. 4.
37. ^ Klatzow 2010, p. 168.
38. ^ a b c Omar 2002.
39. ^ Burger 2000.
40. ^ "Helderberg Conspiracy" (PDF) (PDF). Carte Blanche. 4 June 2000.
41. ^ a b c Truth and Reconciliation Commission (1 June 1998). "Special Hearing: Helderberg Flight". Department of Justice and Constitutional Development, archived on 20 May 2007. Archived from the original on 22 April 2004. Retrieved 18 February 2015.
42. ^ Klatzow 2010, p. 168,174.
43. ^ Crawford & Klotz 1999, p. 53.
44. ^ Klatzow 2010, p. 172,177,189.
45. ^ "History of Flight Recorders". L-3 Aviation Recorders (L-3AR). Archived from the original on 28 March 2014. Retrieved 1 December 2012.
46. ^ Klatzow 2010, p. 177-182,186.
47. ^ a b Kirby 1998.
48. ^ Zwecker 2011, p. 9.
49. ^ Urquhart 2000, p. 9.
50. ^ Lund 2000.
51. ^ Welsh & Whale 2001.
52. ^ "The Witness". witness.co.za. 28 November 2012.
53. ^ Ray White. "Alleged cause of Helderberg plane exposed". ewn.co.za.
54. ^ "Helderberg captain 'quite happy to fly'". Retrieved 28 August 2022.
55. ^ Homepage von M D Young
56. ^ politicsweb 20 February 2015
57. ^ "Aviation Investigation Report, In-Flight Fire Leading to Collision with Water, Swissair Transport Limited McDonnell Douglas MD-11 HB-IWF Peggy's Cove, Nova Scotia 5 nm SW 2 September 1998" (PDF). Transportation Safety Board of Canada. 27 March 2003. A98H0003. Archived (PDF) from the original on 17 October 2013. Retrieved 16 January 2016.
58. ^ "Jet debris found in Indian Ocean." Associated Press at the Houston Chronicle. Friday 29 January 1988. Page 15.
59. ^ "Five Bodies Found After Jet Crash". The New York Times. Associated Press. 30 November 1987. Retrieved 25 March 2011.
60. ^ "Plane carrying 155 crashes in Indian Ocean Archived 14 February 2009 at the Wayback Machine." Houston Chronicle.
61. ^ Kreikenbohm, Philip. "Haru Sonoda Magic Dragon – Wrestlers Database". www.cagematch.net.

Bibliography

* Burger, Marlene (20 May 2000). "Basson Link to Helderberg Crash Probed". Independent Online. Retrieved 28 November 2011.
* Crawford, Neta; Klotz, Audie (1999). How Sanctions Work: Lessons From South Africa. Palgrave Macmillan. p. 53\. ISBN 0-312-21856-7.
* Dickerson, Leroy; Blake, David (February 1993). "Effectiveness of Hand-Held Fire Extinguishers on Cargo Container Fires" (PDF). Atlantic City: Federal Aviation Administration.
* Dreyer, Nadine (2006). A Century of Sundays. Zebra. p. 261\. ISBN 1-77007-106-7. Retrieved 16 February 2009.[permanent dead link]
* Hopkins, Pat; Hilton-Barber, Bridget (2005). Worst Journeys. Zebra. ISBN 1-77007-101-6.[permanent dead link]
* Kirby, Robert (26 June 1998). "Helderberg: The Search for Invisible Blame". Mail and Guardian. Retrieved 23 July 2011.
* Klatzow, David (2010). Steeped in Blood: The Life and Times of a Forensic Scientist. Cape Town, South Africa: Zebra Press. ISBN 978-1-86872-922-7.
* Kutzleb, Michael K. (1988). "The Search for South African Airways Flight 295". Oceans '88 Proceedings: A Partnership of Marine Interests: Conference. IEEE. §4: 1444–1447. doi:10.1109/OCEANS.1988.794984. S2CID 20510767.
* Lund, Troye (24 May 2000). "Helderberg: SAA May Face R2bn in Claims". Cape Argus.
* Margo, Cecil (14 May 1990). Report of the Board of Inquiry into the Helderberg Air Disaster (PDF) (Report). Pretoria: South African Civil Aviation Authority. ISBN 0-621-13030-3. Archived from the original (PDF) on 29 September 2011. Retrieved 7 February 2019.
* Marsh, Rob (1994). Hermann, Hilda; van Rooyen, Annlerie; van der Westhuizen, Aletta (eds.). Verlore Skakels: Onverklaarde Geheime van Suider-Afrika [Lost Links: Unexplained Secrets of Southern Africa] (in Afrikaans) (1st ed.). Struik Publishers (Pty) Ltd. ISBN 1-86825-407-0.
* Mueller, A.G. (1988). Report About the Search for the Wreck of the B74 M of South African Airways, Lost Over the Indian Ocean on November 28, 1987, Flight SA295, Taipei-Mauritius (Report). Retrieved 16 March 2010.
* Omar, Dullah (11 October 2002). "Press Statement: The Enquiry into the Helderberg Disaster of 28 November 1987" (Press release). Pretoria: Ministry of Transport. Archived from the original on 17 May 2011. Retrieved 24 July 2011.
* Strümpfer, Johan (16 October 2006). "Deep Ocean Search Planning: A Case Study of problem Solving".
* Urquhart, Craig (24 May 2000). "TRC Could Reveal Truth About Crash". Cape Times. Archived from the original on 28 September 2011. Retrieved 21 July 2011.
* Watt, Ronnie (1990). "Helderberg Death Flight SA 295". Southern. Retrieved 10 February 2009.
* Welsh, J.I.; Whale, M.B. (21 May 2001). Preliminary Report: Helderberg Plane Disaster (Report). Pretoria: Directorate of Special Operations. Archived from the original on 9 August 2011. Retrieved 8 August 2011.
* Wessels, Andre (20 April 2007). "The South African Navy During The Years of Conflict in Southern Africa, 1966–1989" (PDF). Sabinet Online Ltd. Archived from the original (PDF) on 31 October 2008. Retrieved 12 May 2008.
* Zwecker, Wolfram (21 July 2011). "Helderberg: Hý vat opnames" [Helderberg: He took recordings]. Beeld (in Afrikaans). Johannesburg. Archived from the original on 14 February 2012. Retrieved 21 July 2011.

## Further reading[edit]

* Lillie, Joanne; Luck, Dominique (2014). Surviving 295: Life After the Helderberg. Cape Town: Jacana Media..

## External links[edit]

Wikimedia Commons has media related to South African Airways Flight 295.

External images

Photos at withmaliceandforethought.com/
Pre-Crash photos of ZS-SAS from Airliners.net

* Abridged ATC Recording An MP3 format of part of the actual ATC recording. The real recording starts at 21 minutes. It is slightly abridged, with some empty sound cut short.
* "'We are going to die,' said crew member". Houston Chronicle. 6 December 1987. Archived from the original on 14 February 2009. Retrieved 5 July 2017.
* Vol South African Airways 295 : Maldonne à Pretoria (French)
* "We have a smoke problem in the aeroplane!" Die "Helderberg"-Tragödie (German)
* "SAA 747 Wreckage Examined in Detail" a 1989 Flight article

* v
* t
* e

Aviation accidents and incidents in 1987 (1987)

Jan 3

Varig Flight 797

Jan 15

SkyWest Airlines Flight 1834

Jan 16

Aeroflot Flight U-505

Mar 4

Northwest Airlink Flight 2268

Apr 4

Garuda Indonesia Flight 035

May 8

American Eagle Flight 5452

May 9

LOT Flight 5055

May 19

Air New Zealand Flight 24

Jun 19

Aeroflot Flight N-528

Jun 26

Philippine Airlines Flight 206

Jul 24

Air Afrique Flight 056

Jul 30

Mexico City Boeing C-97 crash

Aug 16

Northwest Airlines Flight 255

Aug 31

Thai Airways Flight 365

Oct 15

Aero Trasporti Italiani Flight 460

Oct 20

Ramada Inn Corsair crash

Nov 15

Continental Airlines Flight 1713

Nov 28

South African Airways Flight 295

Nov 29

Korean Air Flight 858

Dec 7

Pacific Southwest Airlines Flight 1771

Dec 8

Alianza Lima disaster

Dec 13

Philippine Airlines Flight 443

Dec 23

Finnair Flight 915

1986  ◄ ► 1988

Portals:

* South Africa
* Taiwan
* Africa
* Aviation
* 1980s

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template