FlyerTalk Forums - View Single Post - Milan - Linate or Malpensa
View Single Post
Old Dec 31, 2003 | 8:30 am
  #13  
Globaliser
FlyerTalk Evangelist
All eyes on you!
20 Years on Site
 
Join Date: Aug 2002
Location: London
Programs: Mucci. Nothing else matters.
Posts: 38,752
<font face="Verdana, Arial, Helvetica, sans-serif" size="2">Originally posted by GreatDane:
I think it goes a bit beyond that as you may read here: http://www.iasa.com.au/folders/Safet...okingback.html </font>
From the less impassioned summary at http://aviation-safety.net/database/2001/011008-0.htm (which from memory is a reasonably accurate reflection of the accident reports):-
<font face="Verdana, Arial, Helvetica, sans-serif" size="2">Visibility was poor with a Runway Visual Range of approx. 225m/735ft as MD-87 "Lage Viking" taxied to runway 36R for departure. Around the same time Cessna 525A CitationJet 2 D-IEVX received instructions to taxi out from the general aviation ramp ... "North via Romeo 5". The Citation crew were instructed to "call back at the stop bar of the main runway extension." The Citation pilot acknowledged: "Roger, via Romeo 5 ... and call you back before reaching main runway", omitting the words North, stop bar and extension. Unchallenged by the controller, the Citation taxied out to the East via taxiway Romeo 6 (R6). At 06.07h the MD-87 was instructed to line up and wait on Runway 36R. At 06.08h the Citation crew reported approaching Sierra 4 and they were told to hold at the stop bar. At 06.09:19h the ground controller cleared them to "continue your taxi on the main apron". Just ten seconds later Flight SK686 was cleared for takeoff. At 06.10:21, immediately after rotation, the MD-87 collided with the CitationJet.</font>
That's why it's unfair to to say that the accident was caused by a combination of fog and appalling ground control glitches - with the implication that there was nothing else.
Globaliser is offline