See, that's just it. Local time just isn't all that useful, and probaby gets in the way. Think about it... on any sortie it's not unlikely at all that the plane could cross back and forth several times across the local zone boundary. Shifting the system time an hour up and down each time would just be confusing.
Sure, maybe there's a ~clock~ display that can have a local zone adjustment, but beyond that there's no purpose to it.
Of course... in new systems bugs will happen. Sometimes it's the *really* simple bugs that nobody thinks to look for. But this story isn't making any sense yet. But we'll see.
See post #90. I think it was a latitude reversal issue.
Ya know, I'd bet it was the switch from 180W to 180E that jammed things up, and the article got it wrapped up as "Dateline", perhaps not wanting to confuse the proletariat with all those numbers...........
It might not have anything to do with the date, it could be a glitch in the navigation system that has trouble handling the '180 deg' meridian....
Or, it could be that the system requires a hard start every 24 hrs and when the date rolled over, it checked its log, restarted and came up in a limited mode....
It's not hard to imagine at all how this could happen. I take it you don't work with complex SW systems.