(Translated by https://www.hiragana.jp/)
Accident: Cargolux B744 at Luxembourg on Jan 21st 2010, touched van on runway during landing
The Aviation Herald Last Update: Tuesday, May 21st 2024 14:45Z
30424 Articles available
Events from Mar 23rd 1994 to May 21st 2024
 
www.avherald.comIncidents and News in Aviation 
 
  Next Earlier ArticleNext Later ArticleList by: Sort list by Occurrence dateList currently sorted by UpdateFilter: Crashes OnAccidents OnIncidents OnNews OffReports Off 
 

 

Accident: Cargolux B744 at Luxembourg on Jan 21st 2010, touched van on runway during landing
By Simon Hradecky, created Thursday, Jan 21st 2010 21:15Z, last updated Wednesday, Feb 24th 2010 21:12Z

The roof of the van (Photo: ChristiaanJ)
The roof of the van (Photo: ChristiaanJ
A Cargolux Boeing 747-400 freighter, registration LX-OCV performing flight CV-7933 from Barcelona,SP (Spain) to Luxembourg (Luxembourg) with 3 crew, was cleared to land on Luxembourg's runway 24 in low visibility due to fog (RVR 350 meters), when one of the tyres impacted the roof of a van parked on the runway at 12:53L (11:53Z). The airplane landed safely, the driver of the van escaped with just a shock, the van received substantial damage, the airplane suffered damage to the tyre.

Luxembourg's Ministry of Transport reported, that the van had entered the runway to perform maintenance work at the runway ground lighting. Three investigations have been initiated. The Ministry did not tell, whether the van had been cleared to enter the runway.

First preliminary results of the investigations into the incident were released on Saturday (Jan 23rd) stating, that the van had been cleared to enter the runway to perform maintenance work. At that time the Cargolux Boeing had not yet begun its approach.

On Feb 9th Luxembourg's Ministry of Transport initiated disciplinary action against tower controllers following further results of the investigation into the ocurrence. The investigation confirmed an operating irregularity had occured at the tower when the Boeing 747 received landing clearance despite the runway being occupied by the maintenance workers and their van. In addition, the investigation puts into doubt, that the maintenance work was necessary, particularly at a time when low visibility procedures were in effect.

The NTSB reported on Feb 24th, that CATIIIb conditions prevailed at the time of the landing. The van received substantial, the aircraft minor damage. The 3 crew on board of the aircraft and two maintenance workers on the runway remained uninjured. The occurrence has been rated an accident, the NTSB has assigned an Accredited Representative to participate in the investigation by the Luxembourg Administration Des Enquêtes Techniques.


Metars:
ELLX 211420Z VRB01KT 0100 R24/0375N FG OVC001 01/01 Q1020 NOSIG
ELLX 211350Z VRB02KT 0100 R24/0350N FG OVC001 01/01 Q1019 NOSIG
ELLX 211320Z VRB03KT 0100 R24/0225N FG OVC001 01/01 Q1019 NOSIG
ELLX 211250Z 13002KT 0100 R24/0250N FG OVC001 01/01 Q1019 NOSIG
ELLX 211220Z VRB03KT 0100 R24/0275N FG OVC001 01/01 Q1020 NOSIG
ELLX 211150Z 12003KT 0100 R24/0350N FG OVC001 01/01 Q1020 NOSIG
ELLX 211120Z VRB03KT 0150 R24/0375N FG OVC001 01/01 Q1020 NOSIG
ELLX 211050Z 12003KT 0150 R24/0375N FG OVC001 00/00 Q1020 NOSIG
ELLX 211020Z VRB03KT 0100 R24/0275N FG -DZ OVC001 00/00 Q1020 0619//86 NOSIG
ELLX 210950Z VRB03KT 0150 R24/0275N FZFG OVC001 00/00 Q1019 0619//86 NOSIG



By Simon Hradecky, created Tuesday, Dec 18th 2012 00:43Z, last updated Tuesday, Dec 18th 2012 00:43Z

Luxembourg's Administration des Enquêtes Techniques (AET) released their final report concluding the probable causes were:

The impaired operational readiness of the ELE department (editorial note: electrical department of the air navigation service provider) due to a manning shortcoming, combined with the lack of provisions to appoint external workforce if necessary, prevented ANA (editorial note: air navigation service provider) to schedule preventive maintenance work outside of normal operating hours (i.e. during the curfew);

- The decision to carry out preventive maintenance work in low visibility conditions without hampering air traffic gave priority to flight operations over safety aspects;

- The lack of adequate co-ordination between aerodrome control tower and ELE department with regard to the preventive maintenance work contributed to a reduced situational and organizational awareness of the TWR control staff;

- Inadequate procedures for the access of vehicles to the RWY and ILS sensitive area during LVP contributed to the development of an unsafe condition;

- Read-back procedures were not adequately applied by aerodrome control tower on ground control frequency, making this procedural safety net ineffective;

- Low visibility weather conditions, associated with the lack of supplementary ground traffic control and surveillance equipment, limited the capability of aerodrome control tower to identify and correct a developing unsafe condition;

- The use of different frequencies for air traffic and ground traffic on the manoeuvring area reduced the situational awareness of ELE 23 maintenance crew working on the RWY, preventing them to take avoiding action.


The AET reported that based on national law and initial assessment the occurrence was originally rated an accident, but following the investigation was rated a serious incident.

Low visibility procedures were in use at the time of the serious incident. Upon contacting Luxembourg approach, while descending through FL154, the crew was told the cloud base was at 100 feet overcast, visibility was 100 meters/330 feet, temperature and dewpoint were at +1 degree Centigrade. The aircraft was vectored for an ILS approach to runway 24, runway visual ranges were reported as 350 meters/250 meters/350 meters.

At that time a maintenance team, callsign ELE 23, was on ground frequency already on the runway after having been cleared directly onto the runway by ground control 22 minutes earlier. The maintenance team parked the van on the runway, had the side doors open while working to be able to hear any radio transmission. The AET reported, there was no other communication on the ground frequency until after the collision over the entire period of more than 22 minutes.

When the Boeing contacted tower, part of the transmission was blocked by another aircraft requesting taxi clearance from the apron to runway 24. Tower cleared that aircraft to taxi from the apron to the CAT III holding point runway 24, then issued landing clearance to the arriving 747, that was about 4.5nm before touchdown at that point. About 2 minutes after receiving landing clearance the aircraft descended through 17 feet AGL, decision height, the pilot flying called "Landing". During the flare the aircraft impacted the roof of the van, which was parked 340 meters past the runway threshold slightly to the right of the runway center line, the roofline at 8 feet above runway surface. The right hand body gear of the 747 hit the van slightly below the roof line and rolled over the entire length of the roof, light bar and antennas were ripped off the vehicle. The two maintenance crew, who had been working on the runway center line lights and had become aware of the arriving aircraft by the noise of the engines, ran off the side of the runway upon the increasing sound. 5 seconds after hitting the van the aircraft touched down on the runway and rolled out without further incident. The pilot flying notice the vehicle and commented during roll out, the pilot monitoring had been watching the instruments and did not notice the van. While vacating the runway the pilot flying radioed tower and reported the vehicle on the runway, the controller asked whether there was any problem which was answered in the negative. The crew taxied the airplane to the parking position.

The AET annotated the crew was not aware of the collision at that time until after arriving at the stand.

After running to the side of the runway and passing of the aircraft the maintenance crew returned to the vehicle and drove it off the runway onto a service road, then attempted to call tower on radio, then, about 3 minutes after landing, called the tower from a mobile phone and reported the collision, the aircraft had ripped the lightbar and antenna of the roof, the pieces of which were on the runway. The crew reported the aircraft had hit the roof with its landing gear and requested the aircraft to be inspected. The tower assistant receiving the call immediately commented that the departure should not be permitted and requested emergency services to perform a runway inspection especially of the first half of runway 24.

The van received substantial damage to its roof structure, superstructure on the roof had been ripped off when the right body gear rolled over the roof.

Tyre #12 on the right body gear sustained multiple cuts and needed to be replaced, the aircraft did not receive any other damage.

The AET reported that the recording equipment of ground frequency was checked for any defects, no anomaly was found within the system. Following the clearance to ELE 23 to enter runway 24 there was no communication on that frequency until after the aircraft had landed.

The AET were not able to establish, whether a runway incursion alert had been triggered or not. The investigation found, that even if a runway incursion alert had been triggered, the aural alert would not be clearly identifyable on the ATC recordings.

The aerodrome data display, which was in evaluation phase and had no operational status, showed the runway had not been blocked at the time of the occurrence, specifically not at the time when the van was cleared onto the runway until emergency services entered the runway to remove the debris from the collision. Two more possibilities existed to mark a runway being in use: a runway incursion alert and a strip marker.

The runway incursion alert would cause the runway display to turn red upon activation of the radio talk button, if the runway had been blocked from that frequency. However, if the runway had been blocked from the other frequency, no alert would occur. Tower and ground were operating on different frequencies.

The report does not mention that a strip marker had been placed to mark the runway blocked.

The ELE department had 7 staff, 2 of them were on sick leave due to an incident that had occurred during maintenance of runway center line lighting earlier. Several incidents regarding runway center line lighting had prompted the air navigation service provider to conduct a meeting with the manufacturer of the runway center lighting which resulted in the decision to conduct preventive maintenance including replacement of the lights. 114 of 161 center line lights had already been replaced when a gas combustion occurred during replacement of another light causing two maintenance workers to receive injuries. This incident prompted ANA to give priority to replacing the remaining 47 lights, however, without hampering air traffic.

The tower controller said in his post incident testimony that he was not aware of the extent of the maintenance work, he had understood in general there had been an accident which required the remaining runway center line lights to be replaced with priority. The tower assistant coordinated with the controller prior to radioing clearance to ELE 23 to enter the runway, the controller however still had no understanding of what ELE 23 was attempting to do and how long they would stay on the runway. The controller remembered that he instructed the assistant to have ELE 23 vacate the runway, when the 747 was about 16-18nm from the runway. He subsequently heard a noise similiar to a portable transceiver and interpreted the sound as confirmation the van had cleared the runway, at the same time there was noise of an incoming telephone call.

The controller further stated that ELE 23 usually consisted of a crew that monitored both ground and tower frequencies. The crew thus would proactivately clear the runway on incoming traffic without tower needing to instruct them vacate the runway. The controller believed the assistant and he therefore believed the noise of the transceiver was the acknowledgement ELE 23 had vacated the runway.

The assistant provided testimony that he had activated the runway incursion function and placed a runway blocked strip marker indicating the presence of the van on the runway. When he saw the 747 inbound to the runway he instructed the van to vacate the runway, heard a radio noise which he interpreted as confirmation the runway was vacated, then was distracted by the incoming phone call. He was astonished that the runway incursion alert activated when he transmitted on the ground frequency for the first time after landing of the 747. The assistant recalled, that during that transmission (recorded by the recording system) he had heard two distinct clicks from the microphone button, one when the button was pushed out of his extended position and another one when the button reached the full down position. It may have been possible that the button was not fully pressed when the instruction to vacate the runway should have been transmitted, the instruction would only be transmitted with the button fully down.

The AET analysed that "it was reasonable to assume that he thought the runway was clear of obstacles and the sensitive area was unobstructed" upon issuing the landing clearance, there was no possibility to visually verify the runway status in the prevailing weather conditions.

There was no communication on ground frequency for 30 minutes after the van was cleared onto the runway.

The AET continued analysis: "Accepting a ‘carrier wave’ type signal as a confirmation that ELE 23 had vacated the runway and not requiring a proper read-back of the given instruction can be qualified as inappropriate, especially with LVP in force and no visual contact with the van. ... In the present case, not applying standard phraseology to confirm that the runway was effectively vacated rendered that safety barrier ineffective and the lack of additional ‘engineered’ defences (e.g. rec. LU-AC-2012/003) or ‘soft’ (e.g. rec. LU-AC-2012/004) defences opened the way to an unsafe condition."

The AET analysed that a Advanced Surface Movement Guidance and Control System Level 2 would have added an active defense alerting the controller of a potentially unsafe condition. Such a system had not been implemented at the time of the occurrence however, though a tender of such implementation had been published.

The AET analysed that even if the crew of the 747 had seen the van at decision height and initiated a go-around, the aircraft would not have avoided ground contact and a collision with the van. The crew could reasonably assume however that the runway was free of obstacles and was focussed to detect visual cues necessary for the landing and did not look out of possible obstacles.

The AET analysed that according to ICAO recommendations all communication associated with the use of a runway should be conducted on the same frequency used for takeoff or landing of aircraft. The use of tower frequency for clearing the van onto the runway would have reduced coordination efforts and the maintenance crew would most likely have heard the communication with the inbound aircraft enabling the maintenance crew to alert tower of their presence and speed the vehicle off the runway.

The AET stated: "Communicating on the same frequency increases the situational awareness for all operators on the same part of the manoeuvring area by providing first hand access to all information transmitted on that frequency."

12 safety recommendations were issued as result of the investigation.

Damage of the van (Photos: AET):
Damage of the van (Photos: AET)

Aerodrome chart and map (Graphics: AET):
Aerodrome chart and map (Graphics: AET)


Reader Comments: (the comments posted below do not reflect the view of The Aviation Herald but represent the view of the various posters)

Gas Combustion
By (anonymous) on Thursday, Dec 20th 2012 23:43Z

Actually, halogen lamps are filled with halogens, which are usually iodine, bromine and chlorine. They're very not inert, the purpose is to react with the filament.

Perhaps it's a mistranslate of "gas explosion". Halogen lamps do explode. One common problem is if water touches the quartz envelope, the thermal shock will cause the bulb to explode.


Gas combustion
By Stefano on Thursday, Dec 20th 2012 11:04Z

Gas combustion ?

On halogen lamps only the bulb is filled with "inert" gas (kripton, xenon etc) so them can never burn even if you try with a lighter.

Otherwise can you imagine what could happen in case of a damaged lamp for whatever reason on an airport wunway ?

That gas are dangerous only only indoors if they comes out in high concentration since they reduce oxygen


"gas combustion"? By Brian on Wednesday, Dec 19th 2012 15:13Z
By Bravo India on Thursday, Dec 20th 2012 09:32Z

@Brian

I'd say there would have been a gas combustion in the front of the van if the two workers had of been inside it :-) a brown moment to say the least.... Still, It worked out ok so that's the main thing !


"gas combustion"?
By Brian on Wednesday, Dec 19th 2012 15:13Z

Two members of the maintenance department were on sick leave due to a "gas combustion" that occurred during earlier replacement of centre line lights.

How could this occur? I thought they were relatively small halogen bulbs?

Any runway lighting experts out there?


Standards slipping...
By WorldWideWelshman on Wednesday, Dec 19th 2012 12:43Z

I don't get it. Why do this kind of work in such low viz? Why tolerate less than full readback, especially in low viz? And why oh why not have a single freq for the sterile runway area? It smells of standards being allowed to slip...and the stars all aligning as they tend to do just prior to the creation of a smoking hole...

The van crew will dine out on the story for a while ... if the safety recommendations aren't executed, they might not be so lucky next time.


ELE23 B744F Garprints
By David Connolly on Tuesday, Dec 18th 2012 22:02Z

“Luxembourg / Luxemburg French/German/English who really cares”, right said Fred. It could have been a Luxemmorgue in this case, in the twitch of a flaring pitch. I do hope this van and its damage have been preserved, it is a scarred survivor of the laws of physics. After all, it was an honest mistake and nothing hit the turbofans.



By (anonymous) on Tuesday, Dec 18th 2012 20:35Z

Too bad it wasn't a Ford van otherwise Simon could have written "Gear in Transit"


Autoland
By Autoland on Tuesday, Dec 18th 2012 17:44Z

This was an real "Autoland"....


ATC
By werner on Tuesday, Dec 18th 2012 15:23Z

Joking controllers in the tower woundering about their own nonprofessional work...
LUX is not busy at all, even not in "rush hours". maybe that's the problem why it always happen on such airports. time to replace the human factor from the control tower by a system called remote tower.


Runway Work
By Vulcanrider on Tuesday, Dec 18th 2012 12:52Z

Pics remind me of a Bruce Willis movie. As someone else stated, good thing the Boeing wasn't 5 feet lower.

And, it also reminds me of working on the runway when I was AF. We often wondered if anyone really remembered we'd been cleared to the runway when we didn't hear anything from the tower for several minutes. Used to torque them off when WE called to check in. It's a nervous enviornment when you're out there in a little truck with fighters and tankers operating with nothing but a radio. I always thought there should be some kind of ground ops transponder that would let/remind ATC we were in the operating area. Seem it might still be a good idea.


Jokes apart...
By Stefano on Tuesday, Dec 18th 2012 11:59Z

...had been the plane just a couple of feet lower, and it could be a totally different story.



By Stefano on Tuesday, Dec 18th 2012 11:55Z

Curious to know what they told to the Insurance Company

"Guys,I swear, a 747 tried to land on my roof"

:)


GPS
By Ross on Tuesday, Dec 18th 2012 10:59Z

Morning all,
not working in aviation at the moment, so i haveno idea if this is already in practice!
Would it not be work considering getting all ground vehicles equipped with GPS linked up to a map of the aerodrome in the tower showing exactly where each vehicle is? In this day and age, i dont suspect the cost would be great. what costs more, a life or fitting a fleet of ground vehicles with GPS?
cheers
Ross



By @B. B. Sveins on Tuesday, Dec 18th 2012 10:16Z

@B. B. Sveins, you are a shmuck!!! check your post again and have a look how many typos you have done :D

"Sir's.!
-- After working for CV, for 23 years, I can assure you, that company don't oporate B-744, and your spelling of Luxembourg is not correct ! If you are so interested in reporting incidents, be assure to do it correctly ! Bj."


B.B. Sveins
By TAHOE on Tuesday, May 29th 2012 12:26Z

i only came across this page today, but, even over 2 years later, Mr Sveins, i (working now for more than 21.5 years for CV) can tell you, that your ignorance and this stupid post (where is the fault in the spelling of Luxembourg, i can't find it ?) is a shame for all CV employees ! Meanwhile, you may pretend that we do not operate B748 aswell... the 4th one was received some days ago. oh, we also operate 2 leased B744 BCF ... you may think now: what the heck is that ... ?
If i possibly made some wrong spellings, may everyone please excuse me :-)



Mexico Crash
By Toni on Saturday, Feb 27th 2010 09:41Z

The mexico crash was a Western DC-10, Flight 2605 (LAX-MEX) tecolote (redeye) flight. The AC landed in a runaway being paved. Almost all in that plane died -including a friend :( -. Both, plane and van occupants were extremely lucky. BTW: My english is not good neither but i enjoy your job Simon, keep it that way!!


Runway Collision
By Chris R on Thursday, Feb 25th 2010 00:20Z

Don't remember quite well but I recall an A/C (¿¿AA, Eastern, United or maybe Braniff??) smashing into a dump truck in Mexico City during a runway rfurbushing process. Sad issues, fortunately in the CargoLux accident a shot of Brandy for the scare and cleaning out the van will do!


Dumb
By Jason on Wednesday, Feb 24th 2010 23:41Z

Don't know, you tell us.


Runway Collision
By Roly on Wednesday, Feb 24th 2010 21:59Z

How dumb can you get?



Similar but not the same....
By WorldWideWelshman on Thursday, Feb 11th 2010 21:42Z

(From the Airsafe site) Small regional airport, no licensed TWR controller (just a Unicom/FSS), crew didn't announce themselves at the NDB on the approach and (after ETA calculated incorrectly by Calgary ATC) kinda appeared before they were expected and, yes, a snowplough on the runway (who was there legitimately). As you say, a series of bad coincidences. The aircraft crashed on the go around due to the thrust reversers failing to fully stow. Terrible tragedy, but only time will tell how close in fact it is to this incident, and whether learnings should have influenced behaviour in this case.


Its happened before
By AnonymousP on Thursday, Feb 11th 2010 17:20Z

I noticed 32 Years ago today 11 FEB 1978 a Pacific Western Boeing 737 crashed during a go-around at Cranbrook, Canada,killing 42 people.This was because there was a snowplough on the runway.There was a string of things that day,that should not have happened,and things that did happen. The bottomline is,that that accident was preventable,and in 32 years we have not learnt much,because its still happening....


One approach
By Jason on Wednesday, Feb 10th 2010 22:34Z

Agreed that one entity needs to be in control of the runway.

It is the same as airport security. You have the police, rent a cop security, government agents, airport staff, military, etc. They are all on separate frequencies, so when it hits the fan, no one can call each other for backup or to alert of a situation. This is called stovepiping. This isn't every airport, but many of them, and it increases reaction times to incidents, and allows gaps in the system that dirtbags and terrorists can exploit.

If you have one person or department in control of the runway, you eliminate the additional risk with errors in communication or contradicting clearances.



By on Wednesday, Feb 10th 2010 19:57Z


One butt to kick....
By WorldWideWelshman on Wednesday, Feb 10th 2010 15:51Z

No crucifixion necessary... :-)

I've got a different view. The TWR controller needs to "own" the runway, and the procedures in use need to be designed to ensure that the TWR controller has complete control of everything (wheeled or winged) that spends time on it. Add another frequency/controller and you add risk of incursion. The report will tell all in due course, but I suspect the controller might simply have forgotten that he/she cleared the van on some time previously. I'd say that the driver may have some culpability too, as he should at least be listening out on the TWR frequency so that when he hears the CV get a landing clearance, he either hot foots it off the runway, or announces his presence so the TWR controller can tell CV to go around. The more people involved, the more potential risk, it seems to me....


ATC and VTC
By AnonymousP on Tuesday, Feb 9th 2010 22:06Z

Crucify me if you want to,but in the big picture of SAFETY, I would have thought that the last thing an ATController wants to worry about, between shuffling all his/her planes for T/off and landing,is PERMISSION for a little yellow van to enter a busy runway?
This should be co-ordinated between ATC management and possibly a seperate "body" called VTC (Vehicle Traffic Control). I really personally do not think an Air traffic controllers "mindset" is to worry about little yellow vans,especially if not even URGENT.Again we are talking about RISK here.


for BB SVEINS
By Luca on Tuesday, Feb 9th 2010 20:21Z

Dear MR SVEINS,

Before telling someone how to spell a name of city correctly maybe you should learn how to write in English first! Your comment is difficult to understand and the punctuation a disaster. And as others have said, respect should always go first. Simon does a great job with this website and if he makes mistakes I'm sure that he is more than willing to accept corrections. KEEP IT UP SIMON!


cargolux
By regis on Tuesday, Feb 9th 2010 08:59Z

they will be the first to receive the new 747-8F at the end of the year


imagine...
By tanka on Tuesday, Jan 26th 2010 00:48Z

..some guy in a bar tells you after a few drinks that once a jumbo jet had landed on the roof of his van! i hope the guy will not fall into depression caused by the reactions of the non-believers :D


vehicle with LVP in progress ?
By Rogerio Tadeu on Monday, Jan 25th 2010 12:59Z

Why did a vehicle stand parked onto a runway ? Why was it cleared to go beyond ILS critical area ?

In my point of view, absence of radio wasn't a causal factor because the great problem was concerning about vehicle traffic.

Chers,


Van for sale?
By Travis on Sunday, Jan 24th 2010 18:58Z

I want to buy that van!

It has a story to tell. :))


Only the most recent 30 comments are shown to reduce server load. Click here to show the remaining comments

Add your comment: (max 1024 characters)
Your IP address 210.158.71.88 is being tracked. We reserve the right to remove any comment
for any reason. Profanities, personal attacks (against any physical or legal person),
discussions about site policies, false statements or similiar as well as copyrighted
materials from third parties will not be tolerated, those messages will summarily be
deleted. Links and mail addresses are not permitted and will not appear in the display,
posts trying to circumvent the restriction of links/mail addresses will be removed.
We ask for your valid e-mail address in the email field. This address is only used by
us to establish contact with you in case of further questions, it will not be
displayed anywhere or be used otherwise.
Your Name:
Your Email:
Subject:
Your comment:
Aircraft Cabin Air Conference 2024

The Aviation Herald Apps
Android and iOS

AVHAPP on Android and iOS
Support The Aviation Herald

Euro

US$

Interview:
 

  Get the news right onto your desktop when they happenSubscribe   Login FAQ Contact Impressum  

dataimage