Uh, you must be precise.
Are you talking about UTC(USNO) or UTC(PTB)?In any event, I do not know the answer to your question. I just skimmed the article from March GPS World to wit: Interoperability on Time. It is a great example of too many acronyms but it does illustrate the need for precision in re to time and navigation. GNSS, Galileo, GPS, GLONASS, GGTO, GST, UTC, UTC(USNO), UTC(PTB), TAI, ESA, SISNet, EGNOS, WAAS, MOPS, PTF, HPE, GPS and Galileo SIS, TWSTFT, EU, IGS, and various combinations of these acronyms are replete throughout the article. If anyone here can accurately define half of these acronyms, he is truely a nerd and needs to do more sailing.The article is a discussion of timing signal differences of nanosecond and fractions thereof and ways to combine the various satellite signals for greater accuracy in determining GPS position. I barely understand what the writer is trying to say and he concludes with a psychological interpretation which is likewise over my head.Questions for you:How accurately can you read the time displayed on your GPS? A few seconds (or in the terms of the article, a few billion nanoseconds)?If you have a GPS, why do you want to use CN or is it CNav or CelNav or what?If your GPS fails, where will you get time signals then? Why not use that time signal in the first place?