NOAA‑20 Misses Ground Contact, Causing One‑Orbit Delay in Weather Data

At 8:48 p.m. UTC on April 6, a routine ground contact between the U.S. polar‑orbiting weather satellite NOAA‑20 and a McMurdo ground station in Antarctica completed — but the satellite’s stored mission data for that pass did not arrive at NOAA’s processing center.

Minutes later, the National Oceanic and Atmospheric Administration’s Office of Satellite and Product Operations (OSPO) issued an advisory flagging a delay in “stored mission data” (SMD) for a single orbit, labeled REV 43435. The notice said engineers were investigating and that the missing data would "likely be recovered on the following SVL rev 43436," referring to a replay during a subsequent pass over Svalbard, Norway.

Why the missing packets matter

NOAA‑20 (JPSS‑1) circles the globe about 14 times a day in a sun‑synchronous orbit. Its suite of instruments — including VIIRS, CrIS, ATMS, OMPS and CERES — continuously collects imagery and radiances that are stored onboard and downloaded during scheduled high‑latitude ground contacts. Those measurements feed numerical weather prediction models and a wide range of operational products used by meteorologists, aviation, shipping and emergency responders.

A single missed SMD contact removes one orbit’s worth of instrument data from the near‑real‑time stream. In practice, that means the full bundle of imagery, radiances and derived products for REV 43435 was not initially available to downstream users and visualization systems.

Recovery path and likely impact

OSPO’s advisory pointed to a familiar recovery path: replaying stored data to a different ground station on a later pass. In many past incidents, data missed during a McMurdo contact have been recovered on subsequent passes over Svalbard or McMurdo itself. The advisory did not identify a cause; similar short‑lived events have stemmed from ground‑station equipment problems, communications dropouts or data‑ingest glitches rather than instrument failures on the spacecraft.

The practical impact of a one‑orbit delay is usually limited. NOAA‑20 operates as part of a constellation that includes NOAA‑21 and Suomi‑NPP. Those satellites carry comparable instruments, and forecasting centers also ingest measurements from other international polar and geostationary platforms. If the REV 43435 data were only delayed and not permanently lost, centers can often incorporate them later for reanalysis or quality control, though they may miss the tightest deadlines for initial forecast cycles.

Operational users — from National Weather Service forecasters to airline dispatchers and shipping companies — may see a brief missing swath in imagery or delayed products. For most day‑to‑day forecasting and routing decisions a single missed orbit is unlikely to change outcomes, but gaps can matter more if they coincide with rapidly evolving storms, volcanic ash events, or simultaneous problems across multiple assets.

Context and continuity

NOAA‑20 has experienced multiple short‑lived SMD delays since its launch in November 2017. Many were resolved within one or a few orbits by replaying stored data. These recurring but usually brief glitches underscore the complexity of the satellite data supply chain: instruments in orbit, polar ground stations, relay links and processing centers all have to work together to deliver timely products.

OSPO and ground support equipment (GSE) engineers monitor such incidents and work to harden the network with redundancy and procedures that limit impact. At the time of the advisory and subsequent checks, NOAA‑20 remained listed as operational on NOAA’s Joint Polar Satellite System status dashboard, and no public alerts from major operational centers — such as the National Weather Service modeling centers or the Federal Aviation Administration — tied significant disruptions to the SMD delay.

Why it matters going forward

The episode is a reminder that the forecasts and satellite products relied upon every day are produced by a complex, distributed system with multiple potential points of failure. As society’s dependence on timely, high‑resolution satellite data grows — driven by extreme weather, wildfire monitoring, air quality management and transportation safety — the resilience of that system becomes ever more important.

For now, NOAA‑20 remains in service and the April 6 contact miss is recorded alongside prior anomalies as engineers continue routine monitoring. Most users may notice little more than a brief gap in imagery or an OSPO advisory entry; only repeated or longer disruptions across multiple satellites would pose substantial operational risks.