A GPS III launch places a new navigation spacecraft on the path toward service. Useful navigation also depends on orbit and clock determination, payload testing, ground control, declared health and compatible receivers. Follow those milestones separately to understand what a launch changes for a GPS user.
Read the milestone, not just the launch headline
Scroll the table horizontally on small screens. Keyboard users can focus the table region and use the arrow keys.
| Stage | What it establishes | What to check next |
|---|---|---|
| Launch and separation | The spacecraft has been delivered to its initial spaceflight phase. | Deployment, orbit acquisition and spacecraft health. |
| On-orbit checkout | Teams assess the spacecraft, payload, clocks and links. | Completion of testing and integration with ground control. |
| Operational availability | The satellite is accepted or declared usable under the relevant process. | Current health, user notices and any signal-specific restrictions. |
| Receiver use | A compatible receiver can track and use supported healthy signals. | Antenna, firmware, enabled signals, geometry and application requirements. |
GPS III's first satellite launched in December 2018, according to GPS.gov's civil-signal history. Lockheed Martin's February 2020 report records that GPS III SV01 was set healthy and active on January 13, 2020. These two dates illustrate why launch and service milestones should appear separately in a timeline.
Operational acceptance of a spacecraft and operational declaration of a newly introduced signal are different statements. Read which satellite, signal and ground-system capability a release actually describes.
Identify the signal and the receiving equipment
GPS III introduced L1C, a civil signal designed for interoperability with other global navigation satellite systems. L1C and the long-established L1 C/A share the L1 frequency band but are distinct signals. A specification that merely says “L1” needs closer inspection before you infer L1C support.
GPS.gov's new civil signals page explains the purposes of L2C, L5 and L1C and notes the need for compatible equipment. Several status counts and forecasts on that page are explicitly dated. Treat those dates as part of the evidence and consult current user notices before reporting present availability.
For an existing receiver, record model, firmware, antenna and the signals actually enabled or used. Multi-constellation and multi-frequency are different capabilities: a receiver can support several constellations without supporting every frequency or new signal.
Interpret accuracy claims at the right level
Satellite clock and orbit errors contribute to the ranging signal, but the final position also depends on satellite geometry, propagation effects, local reflections, obstructions and receiver processing. GPS.gov's accuracy explanation distinguishes signal-in-space performance from the accuracy a person sees on a device.
Translate a satellite ranging claim into a receiver-level expectation only with evidence for the complete solution. Compare complete solutions under similar conditions and keep the stated metric—range error, horizontal position, vertical position or timing—attached to the number.
For precise work, use the required reference system, corrections and independent checks. The GPS surveying guide explains why a reported coordinate needs more context than a satellite-generation label.
Follow current status through NAVCEN
- Open the U.S. Coast Guard Navigation Center's GPS constellation page and record the displayed status date.
- Identify the spacecraft by SVN and the broadcast code by PRN. Retain both where provided.
- Read the relevant Notice Advisory to Navstar Users (NANU), including its type, affected period and any follow-up.
- Separate a forecast outage from its later outcome and from general test-signal notices.
- Record the conclusion narrowly: which signal or spacecraft is covered, at what time, and under what stated limits.
NAVCEN cautions that its orbital slot graphic does not itself establish operational status. Use the accompanying status information and notices. Keep UTC event times distinct from the local time of a launch report.
Maintain a concise launch-to-service record
Use the GPS III status worksheet to record launch, checkout, operational and receiver milestones with a separate source and date for each. Leave an unknown field explicitly unresolved instead of filling it from a projection.
Recheck after a new official operational notice, a signal declaration or a receiver firmware change. A durable record preserves completed historical events while letting current usability change independently. For the receiver side, continue with GPS chipsets and GNSS modules; for the wider space system, explore satellite guides.
Sources and further reading
Source links reviewed September 28, 2026. Check current service terms, equipment documents and operational notices when applying the guide.