Satellite Failure Behind GPS Timing Anomaly (itnews.com.au)

Bismillah writes: The recent 13-microsecond timing anomaly was caused by a satellite failure triggering a "software issue", the USAF 50th Space Wing has confirmed. Such an error is large enough to cause navigation errors of up to 4 km. Luckily, no issues with GPS guided munition were reported. Reader donaggie03 adds a link to the official explanation from Rick Hamilton, Executive Secretariat of the Civil Global Positioning System Service Interface Committee. From Hamilton's email: Further investigation revealed an issue in the Global Positioning System ground software which only affected the time on legacy L-band signals. This change occurred when the oldest vehicle, SVN 23, was removed from the constellation. While the core navigation systems were working normally, the coordinated universal time timing signal was off by 13 microseconds which exceeded the design specifications. The issue was resolved at 6:10 a.m. MST, however global users may have experienced GPS timing issues for several hours.

Comments

It were the russians

[Anonymous Coward]

They hacked the satellite and caused the damage. When they declare war, they will turn off GPS world-wide, and all the US nuclear rockets will be misguided and will land on American soil. We must vote trump so that putin is scared of our army.

First Post !

[psergiu]

First Post !
I'm able to post that fast 'cause i'm using a GPS-synced clock.

Re:(TFA != Headline) == 1

[ColdWetDog]

In classic Slashdot style, the headline says a hardware failure and TFA says a software bug temporarily mitigated by an operational procedures change.

Just dreaming, but it might be nice if the poster read TFA so the rest of us don't have to?

This is really a test. You just passed it.

Not sure where it gets you, but this is Slashdot, after all.

Re:(TFA != Headline) == 1

[LynnwoodRooster]

Not unexpected. /. is overwhelmingly populated by software types. The first thing they ALWAYS blame is the hardware...