The ninth Global Positioning System (GPS) IIF reached orbit about three hours, 20 minutes after launching Wednesday aboard a United Launch Alliance (ULA) Delta IV rocket from Cape Canaveral Air Force Station, Fla., and sent signals confirming its health.
“Boeing, ULA and the Air Force successfully launched four GPS IIFs last year, the highest operations tempo in over 20 years, and today’s mission marks the first of three launches planned in 2015,” said Dan Hart, vice president, Boeing Government Space Systems. “As they enter service, the IIFs are advancing and modernizing the GPS constellation by improving accuracy, signal strength and anti-jamming capability. We are also introducing the L-5 civilian ‘safety-of-life’ signal intended mainly for aviation and transportation.”
The GPS IIF-9, designated as SVN-71, will undergo on-orbit testing and checkout before beginning full operation.
Boeing has served as a prime contractor on GPS since the program’s inception, contributing multiple generations of GPS satellites and accruing more than 525 years of on-orbit operation.
Wednesday, March 25, 2015
Tuesday, March 24, 2015
Video: Ship 279, the last C-17 Globemaster III
Monday, March 23, 2015
Air Force taking steps to correct GPS satellite error
A Global Positioning System (GPS)
message indexing issue was recently identified that affects a limited
number of active GPS IIF satellites, but does not degrade the
accuracy of the GPS signal received by users around the globe, Air Force officials said on Monday.
The
result is an occasional broadcast not in accordance with U.S.
technical specifications. The issue appears to be related to
the ground software that builds and uploads messages transmitted by
the GPS constellation during regular system operations, although the
Air Force continues to investigate all possible causes.
Although the issue was brought to light in the last few days, a close examination of archived GPS message data reveals that the message indexing error has gone unnoticed since 2013. Air Force Space Command has implemented a workaround to prevent further message indexing violations and is taking steps to permanently correct the error.
Subscribe to:
Posts (Atom)