PDA

View Full Version : London ATC computer down 22/3/10


rayand
22nd Mar 2010, 16:51
stuck on gtound in ba275 lhr to las due to atc radar failure at 16.16

Deep and fast
22nd Mar 2010, 16:53
What's going on with London today, called back to stand with indefinate delay.

D and F

EGNT
22nd Mar 2010, 16:57
It appears all aircraft that are due to depart for any airport within the London TMA are stuck on the ground.

Hotel Tango
22nd Mar 2010, 19:29
"again" is missing from the thread title :E

ZOOKER
22nd Mar 2010, 19:56
Is this the computer/radar-system operated by the alleged "World Leader In Air Traffic Management"? :E

HEDP
22nd Mar 2010, 21:06
Maybe the computer is owned or operated by someone from the Teamsters or Unite!!!!!!!!!!!:\

HEATHROW DIRECTOR
22nd Mar 2010, 21:27
It can't possibly happen........ someone once said..

Defruiter
22nd Mar 2010, 21:32
It was nothing to do with a radar failure.

phantomlurker
22nd Mar 2010, 21:53
Once in a million years I heard...:ugh:

BigDaddyBoxMeal
22nd Mar 2010, 22:23
All very quiet on the western front... whats the story then? Hearing a computer failure not actual radar hardware (surprise surprise!).

Two Swanwick and one Prestwick failures in a very short space of time?

Although that means we're now ok for 3 million years :ok:

Brown Dogg
22nd Mar 2010, 22:30
Valid from 22/03/2010
until 22/03/2010
Released 22/03/2010 17:02
LONDON SYSTEM FAILURE
-----------------------
SYSTEM FAILURE AT LONDON AREA CONTROL IS CAUSING DISRUPTION TO
FLIGHTS ,TACTICAL MEASURES TO HOLD TRAFFIC ON THE GROUND HAVE
BEEN IMPLEMENTED AFFECTING LONDON TMA INBOUNDS AND OUTBOUNDS.NO
REGULATIONS HAVE BEEN APPLIED AT PRESENT TIME.
.
ISSUED ON BEHALF OF LONDON FMP.
.
CFMU OPS/BRUSSELS


Valid from 22/03/2010
until 22/03/2010
Released 22/03/2010 17:25
SITUATION BACK TO NORMAL IN LONDON
----------------------------------
.
THE PROBLEM IN LONDON HAVE BEEN SOLVED. THE SITUATION IS BACK
TO NORMAL WIE.
.
CFMU OPS/BRUSSELS

PeltonLevel
23rd Mar 2010, 09:28
Mr Barron aiming for a memorable last few weeks?

fchan
23rd Mar 2010, 10:04
Whilst regrettable the delay was about 30 mins and NATS induced delays are on average well below historic levels and well below its own target. Unite has more effect on schedules.

The one is a million years prediction (if such a prediction ever existed) is not for events like this but rather for very major events like loss for days or for both radar and voice going down simultaneously. That has never happened as far as I am aware.

Mr Barron has one week left only. Software failures are nothing to do with him.

Lon More
23rd Mar 2010, 10:23
very major events

Although to those actually working at the time it may have seemed major enough.
Two at Swanwick and one at Prestwick recently; seems that a major enough problem is lurking in the system. Until it's found I for one would not be happy working at 100% capacity.

Software failures are nothing to do with him

I would have thought they had EVERYTHING to do with him? The buck stops with him, not with the poor sods working for him.

PeltonLevel
23rd Mar 2010, 11:52
a major enough problem is lurking in the systemIf, by "system", you mean the collection of electronic equipment and software, I suspect that there has been a collection of unrelated incidents which have coincidentally occurred within a fairly short period, so, probably not.
If, by "system", you mean the processes by which equipment is acquired, developed, commissioned and tested, then you may well be right. AND Mr Barron and the Railway Children ARE responsible for this.

Moldioldi
23rd Mar 2010, 17:50
PL what are you doing posting on here? Thought youd be far too busy:ETotal silence on any NATS site about any incident. So whether it was NAS or SFS or something else remains a secret to the outside world. I bet the 'new boy' is glad he joined as it will be all his in eight days time. I note that the media didn't pick it up either. As far as I know there were no recent changes to any system so it could have been the temperature rise that woke a hibernating bug up.I can only conjecture that it was software related since it would have had to have been a massive hardware problem to have had that effect . Unless of couse it was 'finger trouble':\