(1992) El Al Flight Boeing 747 Loses two Engines & Crashes Into Building

The event in context

El Al Flight 1862 was a Boeing 747-258F freighter operating from New York to Tel Aviv with a stop at Amsterdam Schiphol for cargo handling, refueling and a crew change. On the evening of 4 October 1992, the aircraft departed Schiphol normally. Less than ten minutes later, at about 6,500 feet, the No. 3 engine and pylon separated from the right wing. The departing engine then struck No. 4, causing that engine and pylon to separate as well.

The crew declared an emergency and turned back toward Schiphol. From the cockpit, the situation was already extraordinary: two engines had lost thrust, the flaps were reportedly problematic and the aircraft was becoming difficult to control. What the crew could not fully appreciate was that the engines had physically separated from the wing. Damage to the wing and several aircraft systems left the 747 with severely degraded controllability.

The physical sequence is unusually well documented. The Dutch investigation found that the No. 3 engine/pylon separation began at the wing attachment structure. The departing No. 3 assembly then struck No. 4, taking the second engine and pylon with it and damaging the right-wing leading edge and systems. The investigation examined metallurgical evidence and concluded that fatigue in the pylon attachment structure was central to the initiating failure. This was therefore not simply a ‘two-engine failure’; it was a cascading structural failure that changed the aircraft’s aerodynamic and control characteristics within seconds.

Reconstructing this flight

The ATC sequence shows how quickly the problem escalated. The crew requested a return to Schiphol and asked for runway 27. Because of their altitude and position, a direct approach was not practical. Controllers issued headings and descent instructions to bring the aircraft toward the runway.

During the maneuvering, the crew reported that both No. 3 and No. 4 engines were out and that they had flap problems. The controller attempted to position the aircraft for the approach, but the 747 overshot the localizer and required further heading changes. The crew acknowledged the instructions and added that they were experiencing control problems.

As speed was reduced for the approach, the damaged aircraft could no longer maintain controlled flight. At approximately 18:35 local time, Flight 1862 crashed into the Bijlmermeer apartment complex. All four people aboard died, and 39 people on the ground were killed.

The final approach is particularly important because the crew were trying to fly an aircraft whose controllability was already marginal. The accident report concluded that reducing speed for final approach took the airplane beyond the remaining control capability. That finding changes how the ATC recording should be interpreted: the vectors and runway assignment were being given to a crew whose aircraft no longer behaved like a normal 747. The controller could provide headings, but could not see the missing engines or the extent of the wing damage.

What the evidence establishes

The important engineering lesson is that the fuse-pin concept was intended to protect the airframe during extreme loads. A controlled failure point is only safe when it fails in the conditions and manner for which it was designed. In this accident, fatigue and shortcomings in inspection and design allowed the sequence to begin during normal climb.

The crew were then left with an aircraft whose aerodynamic and hydraulic characteristics were dramatically different from those of a normal 747. Later analysis and simulation showed that the aircraft’s remaining controllability was extremely marginal. The crew were fighting an aircraft that had suffered structural damage they could not fully see from the cockpit.

The investigation also found a fleet-level problem rather than an isolated component failure. Similar pylon failures had occurred on other Boeing 747 and 707 aircraft, and the post-accident response included redesign and more intensive inspection of pylon-wing attachment components. The value of this accident therefore extends beyond El Al 1862: it shows how a single fatigue-sensitive structural detail can defeat an inspection system and create a cascade involving propulsion, hydraulics, aerodynamics and controllability.

Investigation and findings

The accident led to changes in inspection and design philosophy for engine pylon attachments. It also became a major case study in system interaction: a single structural component failed, the departing engine caused a second engine to separate, hydraulic and control capability was reduced, and the emergency workload multiplied.

The Pylon Separation and Loss of Control

The reconstructed sequence can be read as a chain of six decision points: Schiphol departure → FL65 / No.3 pylon separates → No.3 strikes No.4 → Return toward Schiphol → Control becomes marginal → Bijlmermeer impact. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.

The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from schiphol departure to bijlmermeer impact. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.

The Engine-Separation Sequence

The decisive safety issue in this incident was specific to the sequence: FL65 / No.3 pylon separates; No.3 strikes No.4; Return toward Schiphol. Treating those events as isolated anomalies would miss the way they interacted.

Sources and investigation material

• https://www.faa.gov/lessons_learned/transport_airplane/accidents/4X-AXG
• https://www.faa.gov/sites/faa.gov/files/ElAl_Accident_report.pdf

Accident Facts