Cargolux Flight 7933

Cargolux Flight 7933 was a cargo flight which was involved in a serious incident on 21 January 2010 in which it landed on a vehicle that was on an active runway. The vehicle suffered major damage while the aircraft had damage to a tire. Three investigations were launched into the incident. The cause was found to be errors by Air Traffic Control.

Cargolux Flight 7933
The aircraft involved in the incident, LX-OCV, in 2005.
Serious Incident
Date21 January 2010
SummaryGround collision with vehicle caused by Air Traffic Control error.
Aircraft
Aircraft typeBoeing 747-4R7F (SCD)
Aircraft nameCity of Differdange
OperatorCargolux
RegistrationLX-OCV
Flight originHong Kong International Airport
1st stopoverHeydar Aliyev International Airport
2nd stopoverBarcelona–El Prat Airport
DestinationLuxembourg Findel Airport
Occupants3
Passengers1
Crew2
Fatalities0
Injuries0
Survivors3
Ground casualties
Ground injuries1

Aircraft

The aircraft involved was a Boeing 747-4R7F (SCD) LX-OCV, c/n 29731,[1] line number 1222. The aircraft first flew on 25 June 1999 and was delivered to Cargolux on 13 July 1999.[2]

History

Flight 7933 departed Hong Kong International Airport on 20 January 2010 bound for Luxembourg Findel Airport via Heydar Aliyev International Airport, Baku, Azerbaijan and Barcelona–El Prat Airport, Barcelona, Spain. On the final leg, there were two crew and one passenger on board.[3] On arrival at Luxembourg the aircraft was cleared to land on Findel Airport's runway 24.[4] The weather at the time was foggy, with visibility reduced to 330 feet (100 m) and a runway visual range of 1,150 feet (350 m).[1] At 12:53 local time (11:53 UTC), one of the aircraft's tires came into contact with the roof of a van which was on the runway while maintenance of the runway lighting was performed. The driver of the van was shocked as a result of the collision. The van was severely damaged, with the roof pushed in and a lighting bar destroyed. A tyre on the aircraft was also damaged.[4]

On 9 February 2010, disciplinary action was started against the controllers on duty at the time the incident occurred. The need for the van to be on the runway at a time of low visibility is also being investigated.[4]

Investigation

Luxembourg's Ministry of transport stated that three investigations into the incident had been launched. It did not state whether the van had permission to be on the active runway or not.[4] The investigations are being carried out by Luxembourg's Administration Des Enquêtes Techniques, Directorate of Civil Aviation and Administration of Air Navigation (AET).[5] A preliminary report revealed that the van had been given permission to be on the active runway. The clearance had been issued before Flight 7933 started its approach. Flight 7933 also had permission to land on the runway that the van was on. Representatives from the NTSB and the Association Luxembourgeoise des Pilotes de Ligne assisted the AET in their investigation.[3][4] The event was initially classed by the AET as an accident but was downgraded to a serious incident as the damage to the aircraft involved was not structural.[3]

The AETs final report into the incident was released on 10 December 2012. The report revealed that the cause of the incident was errors by Air Traffic Control (ATC). The van had been instructed to vacate the runway but ATC had failed to confirm that the instruction had been received and executed before giving the aircraft permission to land. The van and aircraft were using different radio frequencies and therefore each was unaware of the other. A failure to use standard radio phraseology was found to have been a contributory factor in the incident. The van had been seen by the crew just before they landed but it was assessed that a collision would still have occurred had a go-around been initiated. Twelve recommendations were made in the AETs final report. These included the installation of equipment that was capable of recording ATC communications with at least the previous 24 hours recordings being retained.[3]

gollark: It shouldn't be. You can have a replacement name from the GTech™ AutoName5000™™™.
gollark: Alternatively, negotiation with the Old Ones may be entered into.
gollark: Interesting question! We may have to take the required 15.32%* and give you negative amounts of soul to ensure conservation.
gollark: Weird.
gollark: But first, how did you become aware of heavserver?

See also

References
  1. "Landing Cargolux 747 hits van on Luxembourg runway". Flight Global. 22 January 2010. Retrieved 23 January 2010.
  2. "LX-OCV Cargolux Airlines International Boeing 747-4R7F(SCD) - cn 29731 / ln 1222". Planespotters. Archived from the original on 10 June 2011. Retrieved 23 January 2010.
  3. "Final report on a collision between a Cargolux Boeing 747-400F registered LX-OCV and a maintenance van at Luxembourg Airport (ELLX) on 21 January 2010, 11:53 UTC" (PDF). Administration des Enquêtes Techniques. 10 December 2012. Archived from the original (PDF) on 13 October 2013. Retrieved 28 December 2012.
  4. Hradecky, Simon. "Incident: Cargolux B744 at Luxemburg on Jan 21st 2010, touched van on runway during landing". The Aviation Herald. Retrieved 23 January 2010.
  5. "Cargolux plane accident at Luxembourg Airport". 352 Lux Mag. Archived from the original on 9 August 2011. Retrieved 23 January 2010.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.