TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Coincidentally-identical waypoint names foxed UK air traffic control system

34 点作者 simonjgreen超过 1 年前

12 条评论

KuiN超过 1 年前
Here&#x27;s the full preliminary incident report if anyone wants to read it:<p><a href="https:&#x2F;&#x2F;publicapps.caa.co.uk&#x2F;docs&#x2F;33&#x2F;NERL%20Major%20Incident%20Investigation%20Preliminary%20Report.pdf" rel="nofollow noreferrer">https:&#x2F;&#x2F;publicapps.caa.co.uk&#x2F;docs&#x2F;33&#x2F;NERL%20Major%20Incident...</a><p>Obviously concerning that a single (perfectly valid) flight plan can take down both the primary and backup. Reject the flight plan that the system can&#x27;t understand, you&#x27;ve got 4 hours for someone on front-line support to be able to work out the correct path and enter it manually? Meanwhile it&#x27;d be good if the system continued to operate.<p>Futher concerns about first and second line support being unable to find in the logs the cause or even the flight plan being processed when the systems failed. Had to bring in the 3rd party developers to look at &quot;lower-level&quot; logs to find out what happened. If your monitoring&#x2F;logging isn&#x27;t good enough that the first responder can&#x27;t work out at least what the system was doing when it failed, that&#x27;s a significant problem.
评论 #37432069 未加载
评论 #37432080 未加载
atcalan超过 1 年前
I&#x27;ve literally chased this kind of bug down in our ATC simulation tool. People don&#x27;t think Adaptation be like it is, but it do. Just wait till they hear of context dependent fixes with the same name. I.E. airport, airway, fix, all named &#x27;BUD&#x27;. This stuff was written when airplanes were bicycles with handmade motors and canvas covered wings.
doctor_eval超过 1 年前
“Myths engineers believe about waypoint names…”
zarzavat超过 1 年前
&gt; Given that the system could not reconcile the error, the fail-safe software logic intervened to prevent the incorrect data being passed to air traffic controllers, and the FPRSA-R primary system – as designed – suspended its functioning and handed its tasks to a back-up system. But the back-up system applied the same logic to the flightplan, with the same result, and similarly suspended itself.<p>This seems to be the root cause. My reading of this is that the system initially validated the flight plan, but while processing the plan it hit something it didn’t understand. It should have treated this as a late validation error, rejected the plan and continued its work, but instead it treated it as an internal error and crashed. I guess it probably hit some kind of assertion.
评论 #37431936 未加载
wkat4242超过 1 年前
So what was the waypoint I wonder? And who filed it?<p>Not that they did anything wrong, I&#x27;m just wondering why it&#x27;s so scarce on details.
评论 #37431373 未加载
Closi超过 1 年前
All the articles I read on this state that the issue was that a flight plan had ambiguous data.<p>The real issue is that a single erroneous flight plan should not stop the full system.
评论 #37431632 未加载
评论 #37431332 未加载
评论 #37431625 未加载
评论 #37430872 未加载
评论 #37432077 未加载
roydivision超过 1 年前
I&#x27;m guessing a software test plan has been updated recently with a new case.
Taniwha超过 1 年前
At least it didn&#x27;t lock up following the flightplan in a loop ...... (or is that why it really shut down)
amacalac超过 1 年前
This reads like a 0-day exploit bringing down an entire system.<p>I’m usually not the paranoid type :D
评论 #37431608 未加载
评论 #37431900 未加载
matthewsinclair超过 1 年前
It turns out, naming things is hard [0].<p>[0]: <a href="https:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;TwoHardThings.html" rel="nofollow noreferrer">https:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;TwoHardThings.html</a>
评论 #37432351 未加载
robin_reala超过 1 年前
You’d hope that the people building these systems have now got a staging server running with AFL or another fuzzer pointed at it.
edwinjm超过 1 年前
&quot;which were 4,000nm apart&quot;<p>This is written by Americans, right?