<story><title>UK air traffic control meltdown</title><url>https://jameshaydon.github.io/nats-fail/</url></story><parent_chain><item><author>sam0x17</author><text>Why on earth do they not have GUIDs for these navigation points if the names are not globally unique and inter-region routes are commonplace?</text></item><item><author>reactordev</author><text>So they forgot to &amp;quot;geographically disparate&amp;quot; fence their queries. Having built a flight navigation system before, I know this bug. I&amp;#x27;ve seen this bug. I&amp;#x27;ve followed the spec to include a geofence to avoid this bug.</text></item></parent_chain><comment><author>nwallin</author><text>1. Pilots occasionally have to fat finger them into ruggedized I&amp;#x2F;O devices and read them off to ATC over radios.&lt;p&gt;2. These are defined by the various regional aviation authorities. The US FAA will define one list, (and they&amp;#x27;ll be unique in the US) the EU will have one, (EASA?) etc.&lt;p&gt;The AA965 crash (1995-12-20) was due to an aliased waypoint name. Colombia had two waypoints with the same name within 150 nautical miles of each other. (the name was &amp;#x27;R&amp;#x27;) This was in violation of ICAO regulations from like the &amp;#x27;70s.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;American_Airlines_Flight_965&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;American_Airlines_Flight_965&lt;/a&gt;</text></comment>
<story><title>UK air traffic control meltdown</title><url>https://jameshaydon.github.io/nats-fail/</url></story><parent_chain><item><author>sam0x17</author><text>Why on earth do they not have GUIDs for these navigation points if the names are not globally unique and inter-region routes are commonplace?</text></item><item><author>reactordev</author><text>So they forgot to &amp;quot;geographically disparate&amp;quot; fence their queries. Having built a flight navigation system before, I know this bug. I&amp;#x27;ve seen this bug. I&amp;#x27;ve followed the spec to include a geofence to avoid this bug.</text></item></parent_chain><comment><author>amoerie</author><text>Long story: because changing identifiers is a considerable refactoring, and it takes coordination with multiple worldwide distributed partners to transition safely from the old to the new system, all to avoid a hypothetical issue some software engineer came up with&lt;p&gt;Short story: money. It costs money to do things well.</text></comment>