NATS 发布 9 月 8 日技术事故的初步报告
NATS publishes preliminary report on technical incident of 8 September

原始链接: https://www.nats.aero/news/nats-publishes-preliminary-report-on-technical-incident-of-8-september/

英国主要空中交通服务提供商NATS发布了一份初步报告,解释了近期大范围的旅行中断事件。首席执行官马丁·罗尔夫(Martin Rolfe)澄清,此次发生于9月8日的事件是由国家空域系统中的特定软件缺陷引起的,与2023年的系统中断或军事活动无关。 该问题出现在一次针对飞机识别码的手动请求过程中。由于优先级冲突导致请求暂停,在恢复时,编码错误损坏了数据输出。这一故障仅持续了毫秒级,却影响了管制员可获取的信息。因此,英国各地实施了为期六小时的安全限制以重启系统,导致大量航班取消和延误,且耗时两天方才清理完毕。 罗尔夫向受影响的乘客致歉,并强调尽管系统故障是“毁灭性”的,但航空安全从未受到影响。NATS已采取缓解措施,同时永久性修复方案正在进行安全测试。该组织在过去十年中已在技术上投资超过10亿英镑,并计划到2033年再投资10亿英镑,以进一步实现基础设施的现代化。

英国空中交通管制服务机构 NATS 发布了一份关于导致大范围航班中断的技术故障的初步报告。故障原因是“应答机代码”(squawk code)分配过程中出现的竞态条件,特定的软件模块中存在一个一毫秒的脆弱时间窗口。 该问题发生时,一条高优先级的系统消息中断了一次常规的手动应答机代码请求。由于软件未能在此毫秒内正确处理状态变更,导致数据损坏,进而影响了后续的航班数据更新。 Hacker News 的评论者们对该事件展开了讨论,许多人指出,安全关键型系统中出现此类错误表明该系统缺乏形式化验证和稳健的并发处理。虽然有人认为此次故障是由于时间窗口极短而导致的“运气不佳”,但也有人批评该机构的工程设计“业余”,指出系统容易受到单点故障的影响,并认为此类关键基础设施应具备更好的容错性和错误恢复能力。此次事件发生之前已有多起备受关注的故障,这加剧了人们对现代空中交通管制软件老化及可靠性的广泛担忧。
相关文章

原文

NATS, the UK’s major provider of air traffic services, has today published a preliminary report into the events which led to widespread disruption to travellers earlier this month.

This initial report was requested by Heidi Alexander, Secretary of State for Transport. It describes what caused the problem and its resolution, with a full report to follow.

Martin Rolfe, Chief Executive Officer, confirmed that this incident was unrelated to the major system outage in August 2023. He also dismissed speculation that it was caused by military intervention.

“This was a software issue in a specific part of our flight data system, that we have traced to a small subsection of coding,” he said. “The issue has been identified and mitigation is in place while a permanent fix is safety tested and deployed.”

The preliminary report reveals that the incident on Tuesday 8 September was caused by a software defect in a small part of the National Airspace System (NAS), which underpins the management of UK airspace. The software in question allocates codes to individual aircraft when manual requests are made; these are usually allocated automatically. These codes are used to identify flights on radar when they are airborne.

While a manual request for an aircraft code was being processed, the system received a message for a higher priority activity which resulted in the aircraft code request being paused. When processing of the aircraft code request resumed, the software defect meant it did not resume correctly and the resulting output was corrupted, and affected some subsequent flight data updates. This happened in the space of a millisecond.

With reduced information available to controllers, restrictions were put in place to limit air traffic to maintain safety. Although the software issue only affected flights in the London Area Control centre – higher level flights operating mainly above 24,500ft – the restrictions had to be placed across the UK so that the NAS could be restarted and flight data reloaded.

Restrictions were in place for some six hours and while NATS operations returned to normal the same evening, it took more than two days for the backlog of passenger disruption to be cleared, with hundreds of thousands of passengers’ travel plans disrupted.

Mr Rolfe said: “I would like to apologise again, very sincerely, to everyone who was affected last week. It’s our job to get people where they want to go, quickly and without delay and we are devastated when that goes wrong. However, our primary role is to keep our skies safe, and everyone who flies through them. At no point last week was safety in question.”

Over the past 10 years, NATS has invested well over one billion pounds in systems and technology, and we will soon submit plans to the Civil Aviation Authority to invest a further billion pounds by the end of 2033.

联系我们 contact @ memedata.com