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 发布了一份初步报告,说明了一起导致航空旅行中断的重大技术故障。该故障是由分配飞机应答机代码时出现的竞态条件(race condition)软件缺陷引起的。 系统允许高优先级任务抢占应答机代码的分配进程。如果这种中断发生在代码处理过程中特定的 1 毫秒“暴露窗口”内,就会导致数据损坏,并波及随后的航班数据更新。 这一事件在 Hacker News 上引发了激烈的讨论。专家们认为,此类安全关键系统中的故障并非单纯的“运气不好”,而是工程实践不当的结果。评论者指出,尽管测试很重要,但预防竞态条件需要形式化验证、静态分析以及严格执行并发编码标准。许多人批评该系统未能妥善处理这些错误,并指出这并非 NATS 首次因内部软件漏洞导致重大中断。舆论普遍认为,在如此重要的基础设施中使用非原子操作是一种可以避免且不可接受的风险。
相关文章

原文

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