Hapag-Lloyd Flight 3378

Hapag-Lloyd Flight 3378 (HF-3378) was a passenger service operated by Hapag-Lloyd Flug from Chania, on the island of Crete, Greece, to Hannover, Germany. On 12 July 2000, the aircraft flying the route, an Airbus A310-304, registration D-AHLB, with 143 passengers and 8 crew on board, set off for Hannover leaving the landing gear fully extended, as a precaution, since a malfunction had prevented its proper retraction after take-off. The plane eventually ran out of fuel while attempting a diversion to Vienna, crash-landing just short of runway 34. No fatalities resulted, although the aircraft was written off.[1]

Hapag-Lloyd Flight 3378
Flight 3378 after crash-landing short of Vienna International Airport.
Accident
Date12 July 2000 (2000-07-12)
SummaryFuel exhaustion due to maintenance error and pilot error
SiteVienna-Schwechat Airport, Vienna, Austria
48°05′00″N 16°35′40″E
Aircraft
Aircraft typeAirbus A310-304
OperatorHapag-Lloyd Flug
RegistrationD-AHLB
Flight originChania International Airport, Chania, Greece
DestinationHannover Airport, Hannover, Germany
Occupants151
Passengers143
Crew8
Fatalities0
Injuries26 (minor)
Survivors151 (all)

Incident
D-AHLB, the aircraft involved in the accident in 1992.

Captain Wolfgang Arminger (56) was the pilot-in-command. The flight departed at 10:59 CEDT, shortly after which it was found to be impossible to fully retract the landing gear, as indicated by both the red "gear unsafe" lamp and the yellow "gear door open" lamp. After a total of four retraction attempts, the gear was left in the fully extended condition where all lights indicated a valid condition with the doors trimmed for cruise airspeed. The flight continued towards Germany, as fuel must be burned before landing in any case. The crew had to cope with a heavier cockpit workload that was aggravated by the unavailability of the airline HF radio station for technical consultation, forcing the first officer to spend almost an hour establishing alternative communications with the airline through ACARS and Stockholm Radio. Using the Flight Management System (FMS), the crew estimated the aircraft's fuel consumption, and the captain in consultation with dispatch decided to shorten the flight and divert to Munich, where another A310 would be ready to take the passengers to their final destination. However, the captain ignored the fact that the FMS was not designed to take into account the extra drag produced by the extended landing gear. In fact, Munich was not within range, as eventually became clear from the unexpectedly rapid fall in fuel reserves. At about 12:00 CEDT, this led the captain to decide to divert to Vienna-Schwechat Airport.[2]

Shortly thereafter, the first officer noted and reported to the captain that they had already consumed half of their initial fuel load, although they had progressed to only their last waypoint "YNN" still inside Greece (about a third of the total distance to Vienna).[3] At 12:34, the FMS prediction for fuel remaining upon arrival at Vienna fell to 1.9 t. Under such conditions, the airline rules require immediate diversion to the nearest suitable airport, which would have been Zagreb, 10 minutes away. The investigation report states "there was no evidence of immediate crew response to this situation." While contact with Zagreb ATC was made 9 minutes later, the crew pressed on towards Vienna, requesting the most direct access to a runway. At 12:53, the crew notified Vienna ATC that if direct runway access were not available, they would prefer to divert to closer Graz. This prompted Vienna ATC to inquire and finally learn that the flight was short of fuel, but the pilots declared no emergency, still anticipating a normal landing. When the fuel gauges fell through 1.9 t remaining, the first officer twice urged the captain to declare an emergency, but the captain postponed such action. At 13:01, the "LT-Fuel low level" warning indicated remaining fuel of 1340 kg, which automatically generates an ACARS message. At this time, the aircraft was 42 nautical miles (78 km) northeast of Zagreb, 85 nautical miles (157 km) south-east from Graz, and 131 nautical miles (243 km) from the destination Vienna. At 11:07 UTC, the crew finally declared an emergency due to lack of fuel, while still stating that they expected to reach Vienna.[2]

At this point, the crew was still debating a possible diversion to Graz, but discovered that the approach chart for that airport was missing from the aircraft map collection. At 11:12 UTC, the crew still debated the contribution of the FMS to their plight; the first officer (correctly) distrusted its performance with gear down, while the captain still defended it. The captain instructed the first officer to request no emergency services for post-landing, and to defer deployment of the flaps, especially if the engines flamed out. At 11:26 UTC, the pressure dropped at the inlet of the right external fuel pump, but the pump was left running. Both engines flamed out 12 nautical miles (22 km) from the runway, although the first officer was able to restart them for a few more minutes of thrust. As there was no time for the final checklist, the "Land Recovery" switch was neglected, resulting in limited operation of inboard ailerons needed for stability control at low speeds. The left wing tip hit the grassy surface about 660 m short of the runway, followed by the left landing gear, which collapsed after 22 m. The aircraft skidded on the left engine and the right main landing gear, over arrays of approach lights and antennas, turning left 90°, and coming to rest off the runway near the end taxiway. About 26 passengers received minor injuries while using the escape slides.[2] Although the photographs suggest that the aircraft remained structurally intact, it was written off due to the severe damage to the underside of the fuselage. This was the sixth hull-loss of an Airbus A310.[1][4]

Investigation

The final Report on the investigation of the incident was published (only in German) on 21 March 2006 by the Air Accident Investigation Board (Flugunfalluntersuchungsstelle) of the Austrian Federal Office for Transport (Bundesanstalt für Verkehr, BAV).[2] The Report identified the cause of the failure of landing gear retraction as a minor oversight during maintenance; an inadequately secured lock nut allowed a screw to gradually turn, eventually leading to a 10 mm adjustment error that prevented complete retraction.

The Report identified several key reasons why the cockpit crew failed to adequately cope with this relatively minor technical malfunction of the landing gear, continuing the flight to engine failure due to fuel exhaustion.

  • The crew failed to comply with company regulations regarding fuel reserves, caused by several human factors, most importantly extreme work load and stress, leading to loss of situational awareness.
    • Fuel reserves were determined exclusively using the FMS, due to lack of awareness of its inapplicability with gear down.
    • The captain failed to divert to nearby Zagreb airport upon receiving the low-fuel level warning, apparently becoming excessively single-goal oriented.
  • Airbus documentation failed to adequately and clearly inform flight crew of the limitations that apply to fuel management using the FMS.
  • The airline provided insufficient documentation in the checklist for "abnormal landing gear up indication," and Operations Division provided inadequate review of fuel requirements.

The Report makes 14 recommendations for improvements in systems, documents and procedures to avoid such problems in future.

Criminal prosecution

Hapag-Lloyd reported that the Captain Wolfgang Arminger voluntarily left the airline six months after the incident. In 2004, a Hannover district court convicted Captain Arminger of "dangerous interference in the air traffic," saying he was "endangering others' lives" mainly by failing to divert to Zagreb, and gave him a six-month suspended prison sentence.[5][6] The conviction was criticized by German court reporter Gisela Friedrichsen who thought the two court sessions of the main trial were not enough to present and evaluate all evidence.[7]

A report published in 2012 by the American Bar Association argues that airline safety is undermined by such prosecutions because its threat would impede the investigative processes.[8]

gollark: No.
gollark: I use block sparse attention myself.
gollark: (Well, I suggested WASM, but this is a stack machine)
gollark: I suggested this ages ago.
gollark: The API doesn't have to do that.

See also

References
  1. "Aviation Safety Network summary". Flight Safety Foundation.
  2. Raicher, Günther (21 March 2006). "GZ. 85.007/0001-FUS/2006 Investigation Report" (PDF). Verkehrssicherheitsarbeit für Österreich (in German). Austrian Federal Institute for Transport.
  3. "Flight TRT4259". YART (Yet Another Route Tool). Myriapyle. Archived from the original on 6 April 2015. Retrieved 5 April 2015.
  4. "Aircraft Registration Database Lookup – D-AHLB". airframes.org.
  5. Kaminski-Morrow, David (18 May 2004). "Pilot lands suspended prison sentence after Vienna crash". Flightglobal. Reed Business Information. Retrieved 5 April 2015.
  6. Associated Press (11 May 2004). "Beinahe-Katastrophe: Bewährungsstrafe für Bruchpiloten von Wien" [Almost-disaster: suspended sentence for break pilots of Vienna]. Frankfurter Allgemeine Zeitung (in German). Frankfurter Allgemeine Zeitung GmbH. Retrieved 2 November 2016.
  7. Friedrichsen, Gisela (17 May 2004). "Strafjustiz: "Das liegt an Ihrer Dominanz"" [Criminal justice: "That's because of your dominance"]. Spiegel Online (in German). Spiegel-Verlag Rudolf Augstein GmbH & Co. KG. Retrieved 2 November 2016.
  8. Nemsick, Judith R.; Gogal Passeri, Sarah (21 March 2012). "Criminalizing Aviation: Placing Blame Before Safety". American Bar Association. Archived from the original on 11 April 2015. Retrieved 6 January 2015.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.