The technical glitch which caused widespread disruption to flights last week was a “one in 15 million” occurrence, an air traffic control (ATC) boss said.
National Air Traffic Services (Nats) chief executive Martin Rolfe said one of its systems failed after it “didn’t process (a) flight plan properly”.
The plan submitted by the airline – which has not been named – was “not faulty”, he added.
The problem led to Nats being unable to process flight plans automatically for several hours on August 28, a bank holiday Monday and a peak period for air travel.
The subsequent switch to manual processing meant the average number of plans it could handle dropped from around 400 per hour to as few as 60, leading to restrictions on flights to and from UK airports.
More than a quarter of flights were cancelled that day, affecting around 250,000 people.
Cancellations continued for two more days as planes and crews were out of position.
Asked what the odds of this happening were, Mr Rolfe replied: “We know it’s at least one in 15 million, because we’ve had 15 million flight plans through this system and we can be absolutely certain that we’ve never seen this set of circumstances before.”
In a preliminary report shared with Transport Secretary Mark Harper, Nats did not identify the route of the flight plan which led to the chaos but stated the aircraft was scheduled to enter UK airspace during an 11-hour journey.
Airlines’ flight plans feature waypoints, which represent locations and are identified by a combination of letters and numbers.
The flight plan which caused last week’s disruption was submitted to Eurocontrol – which oversees ATC across Europe – before being passed on to Nats.
The process led to the plan featuring two waypoints around 4,000 nautical miles apart but with identical names.
This meant Nats’ software was unable to extract a valid UK portion of the flight plan and reacted by shutting down.
A back-up system followed the same steps and also stopped working.
Nats said an “operating instruction” has been put in place to allow the “prompt recovery” of the system if there is a repeat of these circumstances. A “permanent software change” to prevent it shutting down in such an event is expected to be…
Click Here to Read the Full Original Article at The Independent Travel…