Re:Air traffic failure caused by two locations 3600nm apart ...
by jp57 on Monday November 18, 2024 @11:55AM
(#42174279)
I was clarifying the post title, which uses "nm".
[ Parent
| on HN ]
Re:Air traffic failure caused by two locations 3600nm apart ...
by pvitz on Monday November 18, 2024 @02:05PM
(#42175744)
Yes, it looks like they should have written "NM" instead of "nm".
Re:Air traffic failure caused by two locations 3600nm apart ...
by andkenneth on Monday November 18, 2024 @03:47PM
(#42176819)
No one is using nanometers in aviation navigation. Quite a few aviation systems are case insensitive or all caps only so you can't always make a distinction.
In fact, if you say "miles", you mean nautical miles. You have to use "sm" to mean statute miles if you're using that unit, which is often used for measuring visibility.
Re:Air traffic failure caused by two locations 3600nm apart ...
by ianferrel on Monday November 18, 2024 @04:31PM
(#42177292)
Sure but I could imagine some kind of software failure caused by trying to divide by a distance that rounded two zero because the same location was listed in two databases that were almost but not exactly the same location. In fact I did when I first read the headline, then realized that it was probably nautical miles.
That would be roughly consistent with the title and not a totally absurd thing to happen in the world.
Re:Air traffic failure caused by two locations 3600nm apart ...
by scarlehoff on Monday November 18, 2024 @10:02PM
(#42179719)
This is exactly what I thought q
when I first read the title.
Re:Air traffic failure caused by two locations 3600nm apart ...
by anigbrowl on Monday November 18, 2024 @05:02PM
(#42177604)
Indeed, but you can easily imagine a software glitch over what looks like a single location but which the computer sees as two separate ones.
Re:Air traffic failure caused by two locations 3600nm apart ...
by jp57 on Monday November 18, 2024 @06:41PM
(#42178493)
Indeed, having locations internally represented in software with a resolution of nanometers is as ridiculous as having your calendar's internal times represented as milliseconds since some arbitrary moment more than fifty years ago!