El Al Flight 1862

El Al Flight 1862

Aftermath of the disaster
Accident summary
Date 4 October 1992
Summary Metal fatigue-induced Engine detachment and loss of control
Site Amsterdam-Zuidoost
Passengers 1
Crew 3
Fatalities 43 (all 4 on board, 39 on ground)
Injuries (non-fatal) 26 (11 serious, 15 minor, all on ground)
Aircraft type Boeing 747-258F/SCD
Operator El Al
Registration 4X-AXG
Flight origin John F. Kennedy International Airport, New York City, USA
Stopover Amsterdam Schiphol Airport, Netherlands
Destination Ben Gurion International Airport, Tel Aviv, Israel

Coordinates: 52°19′8″N 4°58′30″E / 52.31889°N 4.97500°E / 52.31889; 4.97500

On 4 October 1992, El Al Flight 1862, a Boeing 747 cargo aircraft of the state-owned Israeli airline El Al, crashed into the Groeneveen and Klein-Kruitberg flats in the Bijlmermeer (colloquially "Bijlmer") neighbourhood (part of Amsterdam-Zuidoost) of Amsterdam, the Netherlands. From the location in the Bijlmermeer, the crash is known in Dutch as the Bijlmerramp (Bijlmer disaster).

A total of 43 people were officially reported killed, including the aircraft's three crew members, a non-revenue passenger in a jump seat, and 39 people on the ground.[1][2] Many more were injured.[2][3][4] The exact number of people killed on the ground is in dispute, as the building had a high concentration of illegal immigrants.[5]

Fatal flight

4X-AXG, the aircraft involved seen at Amsterdam in 1991.

On 4 October 1992, the cargo aircraft, a Boeing 747-258F,[lower-alpha 1] registration 4X-AXG, travelling from John F. Kennedy International Airport New York to Ben Gurion International Airport in Israel made a stopover at Amsterdam Schiphol Airport. During the flight from New York to Schiphol, three issues were noted: fluctuations in the autopilot speed regulation, problems with a radio, and fluctuations in the voltage of the electrical generator on engine number three, the inboard engine on the right wing that would later detach from the aircraft and initiate the accident.

The jet landed at Schiphol at 2:31 pm local time. New cargo was loaded into the aircraft; the cargo had been approved by customs authorities, but as was realised later, had not been physically inspected. The aircraft was refuelled and the observed issues were repaired, at least provisionally. The crew consisted of Captain Yitzhak Fuchs (59), First Officer Arnon Ohad (32) and Flight Engineer Gedalya Sofer (61). A single passenger was on board, travelling to Tel Aviv to marry an El Al employee. The captain was an experienced aviator, having flown as a fighter-bomber pilot in the Israeli air force in the late 1950s.[6]

Flight

Flight 1862 was scheduled to depart at 5:30 pm, but was delayed until 6:20 pm. It departed from runway 01L (today known as runway 36C) on a northerly heading at 6:22 pm. Once airborne, the aircraft turned to the right on its departure route. Soon after the turn, at 6:27 pm, above the Gooimeer, a lake near Amsterdam, a sharp bang was heard while the aircraft was climbing through 1950 meters (6500 feet). The bang was the result of the two fuse pins attaching engine three to the right wing failing due to microscopic fatigue cracks.[4]:38 The engine separated from the right wing of the aircraft, shot forward, damaged the wing flaps, then fell back and struck engine number four, tearing it from the wing. The two engines fell away from the aircraft, also ripping out a 9-meter (30-foot) stretch of the wing's leading edge. The loud noise attracted the attention of some pleasure boaters on Gooimeer. The boaters notified the Netherlands Coastguard of two objects they had seen falling from the sky. One boater, a police officer, said he initially thought the two falling objects were parachutists, but as they fell closer he could see they were both plane engines.[7]

A map of Amsterdam showing the aircraft's flight path (marked in green)

The captain made a mayday call to air traffic control (ATC) and indicated that he wanted to return to Schiphol. At 6:28:45 pm, the captain reported: "El Al 1862, lost number three and number four engine, number three and number four engine." ATC and the flight crew did not yet grasp the severity of the situation. Although the flight crew knew they had lost power from the engines, they did not see that the engines had completely broken off and that the wing had been damaged.[lower-alpha 2] The outboard engine on the wing of a 747 is visible from the cockpit only with difficulty and the inboard engine on the wing is not visible at all. Given the choices that the captain and crew made following the loss of engine power, the Dutch parliamentary inquiry commission that later studied the crash concluded that the crew did not know that both engines had broken away from the right wing.

On the night of the crash, the landing runway in use at Schiphol was runway 06. The crew requested runway 27 - Schiphol's longest - for an emergency landing,[4](pp41–42) even though that meant landing with a 21-knot quartering tailwind.[lower-alpha 3]

The aircraft was still too high and close in to land when it circled back to the airport. It was forced to continue circling Amsterdam until it could reduce altitude to that required for a final approach to landing. During the second circle, the wing flaps were extended. The inboard trailing edge flaps extended, since they were powered by the number one hydraulic system, which was still functioning, but the outboard trailing edge flaps did not extend, because they were powered by the number four hydraulic system, which failed when the number four engine broke away from the wing. That partial flap condition meant that the aircraft would have a higher pitch attitude than normal as it slowed down. The leading edge flaps extended on the left wing, but not on the right wing, because of the extensive damage sustained when the engines separated, which had also severely disrupted the air flow over the right wing. That differential configuration caused the left wing to generate significantly more lift than the damaged right wing, especially when the pitch attitude increased as the airspeed decreased. The increased lift on the left side increased the tendency to roll further to the right, both because the right outboard aileron was inoperative and because the thrust of the left engines was increased in an attempt to reduce the aircraft's very high sink rate. As the aircraft slowed, the ability of the remaining controls to counteract the right roll diminished. The crew finally lost all ability to prevent the aircraft from rolling to the right. The roll reached 90 degrees just before the impact with the apartment houses.[4](pp39–40)

At 6:35:25 pm, the first officer radioed to ATC: "Going down, 1862, going down, going down, copied, going down." In the background, the captain was heard instructing the first officer in Hebrew to raise the flaps and lower the landing gear.[4](p8)

Crash

The aircraft's likely position at the point of impact

At 6:35:42 pm local time, the aircraft nose-dived from the sky and slammed into two high-rise apartment complexes in the Bijlmermeer neighbourhood, at the corner of a building where the Groeneveen complex met the Klein-Kruitberg complex. It exploded in a fireball, which caused the building to partially collapse inward, destroying dozens of apartments. The cockpit came to rest east of the flats, between the building and the viaduct of Amsterdam Metro Line 53; the tail broke off and was blown back by the force of the explosion.

During the last moments of the flight, the arrival traffic controllers made several desperate attempts to contact the aircraft. The Schiphol arrival controllers work from a closed building at Schiphol-East, not from the control tower. At 6:35:45 pm, however, the control tower reported to the arrival controllers: "Het is gebeurd" (lit., "It has happened", but often meaning "It is over"). At that moment a large smoke plume emitting from the crash scene was visible from the control tower. The aircraft had disappeared from arrival control radar. The arrival controllers reported that the aircraft had last been located 1.5 kilometres (1 mile) west of Weesp and emergency personnel were sent immediately.

At the time of the crash, two police officers were in Bijlmermeer checking on a burglary report. They saw the aircraft plummet and immediately sounded an alarm. The first fire trucks and rescue services arrived within a few minutes of the crash. Nearby hospitals were advised to prepare for hundreds of casualties. The flats were partly inhabited by illegal immigrants, and the death toll would be difficult to estimate in the hours after the crash.[8][9]

Aftermath

The crash was also witnessed by a nearby fire station on Flierbosdreef street. First responders came upon a rapidly spreading fire of "gigantic proportions" that consumed all 10 floors of the buildings and was 120 meters wide, the length of a football field. There were no survivors from the crash point, only those who managed to escape from the remainder of the building.[10] Witnesses reported seeing people jumping out of the building to escape the fire.[11]

Hundreds of people were left homeless by the crash; the city's municipal buses were used to transport survivors to emergency shelters. Firefighters and police also were forced to deal with reports of looting in the area.[10]

Prime Minister Ruud Lubbers and Queen Beatrix visited the scene of the disaster the following afternoon. The prime minister said, "This is a disaster that has shaken the whole country."[9]

In the days immediately following the disaster, bodies of victims and the remains of the aircraft were recovered from the crash site. The two fallen engines were recovered from the Gooimeer, as were pieces of a 30-foot section of the right wing's leading edge.[7] The aircraft wreckage was transported to Schiphol for analysis.

The aircraft's flight data recorder was recovered from the crash site and was heavily damaged, with the tape broken in four places. The section containing the data from last two and a half minutes of the flight was particularly damaged. The recorder was sent to the United States for recovery and the data was successfully extracted.[7] Despite intensive search activities to recover the cockpit voice recorder from the wreckage area, it was never found, even though El Al employees stated that it had been installed in the aircraft.[4](p23)

Causes

In the event of excessive loads on the Boeing 747 engines or engine pylons, the fuse pins holding the engine nacelle to the wing are designed to fracture cleanly, allowing the engine to fall away from the aircraft without damaging the wing or wing fuel tank. Airliners are generally designed to remain airworthy in the event of an engine failure, so that they can be landed safely. Damage to a wing or wing fuel tank can have disastrous consequences. The Netherlands Aviation Safety Board found, however, that the fuse pins had not failed properly, but instead had suffered metal fatigue prior to overload failure.[7] The Safety Board pieced together a probable sequence of events for the loss of engine three:

  1. Gradual failure by fatigue and then overload failure of the inboard mid-spar fuse pin at the inboard thin-walled location.
  2. Overload failure of the outer lug of the inboard mid-spar pylon fitting.
  3. Overload failure of the outboard mid-spar fuse pin at the outboard thin-walled and fatigue-cracked location.
  4. Overload failure of the outboard mid-spar fuse pin at the inboard thin-walled location.[4](p46)

This sequence of consecutive failures caused the inboard engine and pylon to break free. Its trajectory after breaking off the wing caused it to slam into the outboard engine and rip it and its pylon off the wing. Serious damage was also caused to the leading edge of the right wing.[7] Both loss of hydraulic power and damage to the right wing prevented correct operation of the flaps that the crew later tried to extend in flight.

Research indicated that the aircraft had only managed to maintain level flight at first due to its high air speed (280 knots). The damage to the right wing, resulting in reduced lift, had made it much more difficult to keep it level. At 280 knots (520 km/h), there was nevertheless sufficient lift on the right wing to keep the aircraft aloft. Once it had to reduce speed for landing, however, it was doomed; there was too little lift on the right wing to enable stable flight, and the aircraft banked sharply to the right without any chance of recovery.

The official probable causes were determined to be:[4](p46)

The design and certification of the Boeing-747 pylon was found to be inadequate to provide the required level of safety. Furthermore the system to ensure structural integrity by inspection failed. This ultimately caused – probably initiated by fatigue in the inboard midspar fuse-pin – the no. 3 pylon and engine to separate from the wing in such a way that the no. 4 pylon and engine were torn off, part of the leading edge of the wing was damaged and the use of several systems was lost or limited.

This subsequently left the flight crew with very limited control of the airplane. Because of the marginal controllability a safe landing became highly improbable, if not virtually impossible.

Victims

Memorial for the victims next to "The tree that saw everything"
Flight 1862 Memorial by Herman Hertzberger

43 people died in the accident: the four occupants of the aircraft (three crew and one non-revenue passenger) and 39 people on the ground.[4](p9) This was considerably lower than expected: the police had originally estimated a death toll of over 200,[11] and Amsterdam Mayor Ed van Thijn had said that 240 people were missing.[8][9] At the time of the crash many potential victims were not at home, possibly because of the pleasant weather on the evening of the crash. Twenty-six people sustained non-fatal injuries; 11 of these were injured seriously enough to require hospital treatment.[4](p9)

The belief has persisted that the actual number of victims killed in the crash was considerably higher. Bijlmermeer has a high number of residents living there illegally, particularly from Ghana and Suriname, and members of the Ghanaian community stated they lost a considerable number of undocumented occupants who were not counted among the dead.[12]

A 2013 film, In Het Niets ("Into Nothing"), tells the fictional story of two such illegal immigrants from Ghana living in the building at the time.[13]

Memorial

A memorial, designed by architects Herman Hertzberger and Georges Descombes, was built near the crash site with the names of the victims.[14] Flowers are laid at a tree that survived the disaster, referred to as "the tree that saw it all" (de boom die alles zag). A public memorial is held annually to mark the disaster; no planes fly over the area for one hour out of respect for the victims.[5][15]

Health issues

Mental health care was available after the crash to all affected residents and service personnel. After about a year, however, many residents and service personnel began approaching doctors with physical health complaints, which the affected patients blamed on the El Al crash. Insomnia, chronic respiratory infections, general pain and discomfort, impotence, flatulence, and bowel complaints were all reported. 67% of the affected patients were found to be infected with Mycoplasma, and suffered from symptoms similar to the Gulf War Syndrome or Chronic Fatigue Syndrome-like symptoms.

Dutch officials from government departments of transport and of public health asserted that at the time of the crash it was understood that there were no health risks from any cargo on the aircraft; Els Borst, minister of public health, stated that "geen extreem giftige, zeer gevaarlijke of radioactieve stoffen" ("no extremely toxic, very dangerous, or radioactive materials") had been on board. However, in October 1993, the nuclear energy research foundation Laka reported that the tail contained 282 kilograms (622 lb) of depleted uranium as trim weight, as did all Boeing 747s at the time; this was not known during the rescue and recovery process.[16][17]

It was suggested that studies be undertaken on the symptoms of the affected survivors and service personnel, but for several years these suggestions were ignored on the basis that there was no practical reason to believe in any link between the health complaints of the survivors and the Bijlmer crash site. In 1997, however, an expert testified in the Israeli parliament that dangerous products would have been released during combustion of the depleted uranium in the tail of the Boeing 747.

The first studies on the symptoms reported by survivors, performed by the Academisch Medisch Centrum, began in May 1998. The AMC eventually concluded that up to a dozen cases of auto-immune disorders among the survivors could be directly attributed to the crash, and health notices were distributed to doctors throughout the Netherlands requesting that extra attention be paid to symptoms of auto-immune disorder, particularly if the patient had a link with the Bijlmer crash site. Another study, performed by the Rijks Instituut voor Volksgezondheid en Milieuhygiene, concluded that although toxic products had been released at the time of the crash, the added risks of cancer were small, approximately one or two additional cases per ten thousand exposed persons. The RIVM also concluded that the chances of uranium poisoning were minimal.

Cargo

Soon after the disaster it was announced that the El Al Boeing 747 had contained fruit, perfumes, and computer components. Dutch Minister Hanja Maij-Weggen asserted that she was certain that it contained no military cargo.

The survivors' health complaints following the crash increased the number of questions about the cargo. In 1998 it was publicly revealed by El-Al spokesman Nachman Klieman that 190 litres of dimethyl methylphosphonate, a CWC schedule 2 chemical which, among many other uses, can be used for the synthesis of Sarin nerve gas, had been included in the cargo. Israel stated that the material was non-toxic, was to have been used to test filters that protect against chemical weapons, and that it had been clearly listed on the cargo manifest in accordance with international regulations. The Dutch foreign ministry confirmed that it had already known about the presence of chemicals on the aircraft. The shipment was from a US chemical plant to the Israel Institute for Biological Research under a US Department of Commerce license.[18][19] According to the Chemical weapons site CWInfo the quantity involved was "too small for the preparation of a militarily useful quantity of Sarin, but would be consistent with making small quantities for testing detection methods and protective clothing".[20]

Alterations to Boeing aircraft

After the crash investigation, Boeing issued a service directive to all airlines regarding the faulty fuse pins on Boeing 747 aircraft. Engines had to be removed from 747s and the pylons examined for cracks in the fuse pins. If cracks were present, the fuse pins were to be replaced.

Related accidents

This was one of several accidents in the early 1990s caused by problems with Boeing 707 and 747 engine pylons.[lower-alpha 4] In December of the previous year, engine #3 had separated from China Airlines Flight 358 shortly after take off from Taipei, taking the #4 engine with it, and resulting in the death of all five occupants.[4](p32)[21] An identical scenario - separation of the #3 and #4 engines - this time on a Boeing 707, occurred on a Trans-Air cargo flight in March 1992; on this occasion, the crew were able to land safely at Istres Air Base in the south of France.[4](p32)[22] The following month, a Tampa Colombia 707 cargo flight was forced to return to Miami, when the #3 engine separated shortly after take-off.[4](p32)[23] And in March 1993, a Japan Air Lines 747 cargo flight similarly returned to Anchorage, after the #2 engine separated.[4](p33)[24]

Earlier an engine and pylon had fallen off a BOAC Boeing 707 in April 1968, resulting in five deaths.

See also

Notes

  1. ↑ The aircraft was a Boeing 747-200F (for Freighter) model; Boeing assigns a unique customer code for each company that buys one of its aircraft, which is applied as an infix in the model number at the time the aircraft is built. The code for El Al is "58", hence "747-258F".
  2. ↑ In aviation, the term "lost" usually means "engine failure", referring to an engine having mechanical issues and ceasing to provide thrust, rather than physically separating from the aircraft.
  3. ↑ The wind was initially from 40 degrees at 21 kt, and then 50 at 22. Runway 27 is aligned due west.
  4. ↑ The Boeing 747 pylon uses a nearly identical design to the 707 [4](p38)

References

  1. ↑ NASB final report, page 9
  2. 1 2 Accident description at the Aviation Safety Network
  3. ↑ "Two engines separate from the right wing and result in loss of control and crash of Boeing 747 freighter" (PDF). flightsafety.org. Flight Safety Foundation.
  4. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 "Aircraft accident report 92-11 : El Al Flight 1862 Boeing 747-258F 4X-AXG Bijlmermeer, Amsterdam 4 October 1992" (PDF). Nederlands Aviation Safety Board. 24 February 1994. Archived from the original on 26 June 2008.
  5. 1 2 "20 jaar Bijlmerramp" (in Dutch). Nederlandse Omroep Stichting (NOS). 4 October 2012. Retrieved 7 January 2015.
  6. ↑ Aloni, Shlomo. "Last of the fighting 'Wooden Wonders': The DH Mosquito in Israeli service" September/October 1999 article with photo in Air Enthusiast No. 83.
  7. 1 2 3 4 5 "Amsterdam Air Crash" Seconds From Disaster Season 2, Episode 15
  8. 1 2 "The El Al Crash; In the Netherlands, The Struggle of Immigrants And Sudden Disaster". The New York Times. 11 October 1992. Retrieved 7 January 2015.
  9. 1 2 3 Paul L. Montgomery (6 October 1992). "Dutch Search for Their Dead Where El Al Plane Fell". The New York Times. Retrieved 7 January 2015.
  10. 1 2 "Bijlmerramp". National Fire Service Documentation Centre (in Dutch). Retrieved 7 January 2015.
  11. 1 2 "El Al jumbo crashes in Amsterdam". BBC News. 4 October 1992. Retrieved 6 January 2015.
  12. ↑ "The Bijlmer". Amsterdam Tourism. Retrieved 7 January 2015.
  13. ↑ "Emotionele vertoning film Bijlmerramp". AT5. 23 October 2013. Retrieved 7 January 2015.
  14. ↑ http://www.mrld.net/pdfs/descombes.pdf
  15. ↑ "Bijlmerramp voor zestiende keer herdacht" (in Dutch). 4 October 2008. Retrieved 7 January 2015.
  16. ↑ Uijt de Haag P.A. and Smetsers R.C. and Witlox H.W. and Krus H.W. and Eisenga A.H. (28 August 2000). "Evaluating the risk from depleted uranium after the Boeing 747-258F crash in Amsterdam, 1992" (PDF). Journal of Hazardous Materials. 76 (1): 39–58. doi:10.1016/S0304-3894(00)00183-7. PMID 10863013. Retrieved 16 May 2007.
  17. ↑ Henk van der Keur (May 1999). "Uranium Pollution from the Amsterdam 1992 Plane Crash". Laka Foundation. Retrieved 16 May 2007.
  18. ↑ "Israel says El Al crash chemical 'non-toxic'". BBC. 2 October 1998. Archived from the original on 18 August 2003. Retrieved 2 July 2006.
  19. ↑ Greenberg, Joel (2 October 1998). "Nerve-Gas Element Was in El Al Plane Lost in 1992 Crash". New York Times. Retrieved 11 October 2007.
  20. ↑ http://cbwinfo.com/Chemical/Precursors/p3.html Archived 4 September 2013 at the Wayback Machine.
  21. ↑ "Accident description, Sunday 29 December 1991, China Airlines Boeing 747-2R7F". ASN. Retrieved 20 March 2015.
  22. ↑ "Accident description, Tuesday 31 March 1992, Trans-Air Service Boeing 707-321C". ASN. Retrieved 20 March 2015.
  23. ↑ "Accident description, Saturday 25 April 1992, Tampa Columbia Boeing 707-324C". ASN. Retrieved 20 March 2015.
  24. ↑ "Accident description, Wednesday 31 March 1993, Japan Air Lines Boeing 747-121". ASN. Retrieved 20 March 2015.

Further reading

Dramatization

Mayday a document series released a documentary 'Amsterdam Crash' based on this crash and shows the aftermath. The computer graphics in the documentary wrongly painted the aircraft in question with El Al's standard passenger aircraft livery (at the time of the accident, El Al's cargo aircraft contains no airline identity and the painting of an Israel flag; only the word "Cargo" appears on both sides of the aircraft).

External links

Wikimedia Commons has media related to El Al Flight 1862.
This article is issued from Wikipedia - version of the 11/30/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.