The NEXRAD Delay: What Your Cockpit Weather Picture Is Actually Showing You and When the Gap Can Kill You

The cockpit weather picture on your electronic flight bag is not a live feed. From the moment a ground radar beam hits precipitation to the moment color-coded blobs appear on your display, 5 to 15 minutes routinely elapse. In an active convective environment, that gap can be the difference between a navigable corridor and a closed door.

How the Ground Radar Network Builds Its Picture

The backbone of U.S. aviation weather is a network of ground-based Doppler radars officially designated the Weather Surveillance Radar 88 Doppler (WSR-88D). The “88” refers to the year the first units entered service: 1988. Roughly 160 of these stations cover the contiguous United States, Alaska, Hawaii, and several overseas territories. The National Weather Service operates most of them; the FAA and the Department of Defense operate the rest.

Each radar builds a three-dimensional picture of the atmosphere by scanning through multiple elevation angles - a full volumetric sweep that cannot be shortcut. That process takes 5 to 6 minutes in standard mode and roughly 4 to 5 minutes in the faster sampling mode used during intense weather events. The sky scanned at the start of a rotation is already 5 minutes in the past by the time the sweep completes. That latency is baked in before the data ever leaves the radar site.

Processing and the Mosaic Step

Raw scan data flows into the Next Generation Radar (NEXRAD) processing system, which converts reflectivity returns into the products pilots recognize: base reflectivity, composite reflectivity, precipitation rate estimates, and the green-through-dark-red intensity scale. That step adds 1 to 2 minutes.

What appears on your display is then a mosaic - a blended composite assembled from multiple radar sites. No single radar covers an entire route. On a flight from Atlanta to Charlotte, the picture crosses coverage footprints from several stations. Those radars did not finish their scans simultaneously; one may have completed 3 minutes ago, another 2. The blending algorithm reconciles data from different scan times and elevation angles into a single image. The mosaic can therefore represent a window of several minutes of staggered scan completions, all presented as if they were one snapshot.

SiriusXM vs. FIS-B: Two Different Clocks

After assembly, the mosaic reaches your cockpit through one of two primary pathways, each with its own latency profile.

SiriusXM Aviation Weather uses satellite radio infrastructure to push data to compatible receivers. It provides near-nationwide coverage including over water and remote terrain. Its NEXRAD composite updates on a cycle of roughly 5 minutes.

Flight Information Services-Broadcast (FIS-B) is the weather data component of the ADS-B ground station network. The FIS-B specification permits NEXRAD composite data to be up to 15 minutes old at the time it is broadcast. That is the allowable floor, not a freshness guarantee. FIS-B coverage is strong near airports and at lower altitudes but can have gaps in mountainous terrain and remote areas.

Cellular and in-flight Wi-Fi solutions represent a third pathway, with update cycles dependent on the data provider and connection quality.

Adding Up the Total Delay

Stack the layers:

• 4–6 minutes for the radar scan
• 1–2 minutes for processing
• Additional time for mosaic assembly across staggered scan completions
• Broadcast cycle latency: 2.5 to 15 minutes depending on system and standard
• Reception and rendering time on the device

In the best case - optimal coverage and a freshly updated dataset - what appears on your display is 5 to 7 minutes old. In realistic operations, particularly in high-workload weather environments when processing systems are under load, 10 to 15 minutes is common. Remote terrain, FIS-B coverage gaps, or degraded network conditions can push that further.

The data age indicator on your EFB, if it shows one, tells you when data was last received on your device. That is not the same as when the underlying radar scan was completed. Most displays show only one of those timestamps.

What 15 Minutes Means Inside a Convective Environment

A convective cell moves. In the southeastern United States during summer, a typical cell tracks at 30 to 45 knots. At 40 knots, a cell covers 10 miles in 15 minutes. A gap that appeared flyable 10 minutes ago may have narrowed by 8 miles since then. Two separate cells may have merged. A precipitation core may have expanded significantly.

Vertical development changes even faster. A rapidly intensifying cell can move from moderate to extreme radar reflectivity in under 10 minutes. The storm does not hold position while you route around the picture of where it was.

The Gap-Threading Accident Pattern

A specific failure mode recurs across NTSB accident investigation reports. The pilot observes a gap between two cells on the mosaic. The gap appears flyable. The pilot routes through it. What the pilot cannot know is that the gap closed during the 15 minutes between when the radar painted that picture and when the aircraft arrives in that airspace. A cell moved. A new cell developed. Two cells merged. The corridor no longer exists.

The NTSB’s findings in these cases commonly include language indicating the pilot used cockpit-displayed weather data as a primary means of convective weather avoidance without adequate understanding of that data’s latency characteristics. That language is not unique to one report. It recurs across multiple investigations across multiple years.

Why the Layered Display Hides the Problem

Your EFB weather overlay is likely a collage of products, each operating on a different update cycle:

• Lightning strike data: often updated in near real time
• NEXRAD composite reflectivity: 5 to 15 minutes, depending on pathway
• Cloud tops (satellite imagery): a separate, slower cycle
• Icing forecasts and graphical turbulence products: sometimes updated on cycles measured in hours

Most displays do not make those different ages visually distinct. The overlay looks like a unified picture. It is not.

SiriusXM and FIS-B also behave differently in terrain. SiriusXM’s satellite delivery provides geographic consistency but adds satellite link latency. FIS-B ground stations are strong near airports but can leave gaps over mountain ranges. In those areas, a pilot may be looking at data from the last ground station contact with no indicator of when that contact occurred.

How to Use Cockpit Weather Data Correctly

Cockpit weather data is a strategic planning tool. Use it to understand where significant weather is generally located, to identify regions to route around, and to brief yourself on developing systems well ahead of departure. That is the appropriate use case, and it delivers genuine value there.

What it should not drive is tactical threading of convective weather. The decision to split two cells, to fly a narrow corridor between areas of precipitation, to thread a gap that appears passable on the display - none of those decisions can be made safely on the basis of a 15-minute-old mosaic. The cells do not hold still.

The established visual standard carries more operational weight than many modern pilots grant it: 20 nautical miles of lateral separation from any visible convective activity. That margin is conservative because it accounts for the fact that turbulence, hail, and lightning extend well beyond the visible precipitation core - and because the display is not showing the current core.

For aircraft with onboard weather radar, the calculus changes significantly. Airborne radar paints the atmosphere directly ahead with data that is seconds old, not minutes. Its principal limitation is attenuation - heavy precipitation can obscure additional weather behind it - but latency is not the problem. For those aircraft, cockpit datalink weather should supplement the onboard picture, not substitute for it.

Where the Technology Is Heading

GOES-16 and GOES-17, the current generation of geostationary weather satellites operated by NOAA, represent a meaningful improvement over their predecessors. The older generation updated visible and infrared imagery every 15 to 30 minutes. GOES-16 updates the full continental United States every 5 minutes and targeted mesoscale sectors every 30 seconds to 1 minute. For storm tracking and development analysis, that is a qualitatively different tool.

The Geostationary Lightning Mapper aboard GOES-16 detects total lightning - both cloud-to-ground and intra-cloud - at update rates measured in seconds. That near-real-time lightning data is increasingly integrated into EFB weather overlays, and it matters: lightning activity is a direct indicator of convective vigor that often precedes the most intense radar returns by several minutes.

Several EFB developers are also moving toward more explicit data-age display, showing not just when the device last received an update but the actual age of the underlying radar scan. A pilot who sees that their NEXRAD composite is 12 minutes old makes different decisions than a pilot who assumes the picture is current.

None of these improvements eliminate the fundamental physics of ground-based radar. Scan times will always be measured in minutes. Processing and broadcast add more. The question is whether the display makes that delay visible enough that pilots factor it into their decisions.

Key Takeaways

• In the best case, cockpit weather displays show data 5 to 7 minutes old; in realistic operations, 10 to 15 minutes is common, and that delay is the sum of radar scan time, processing, mosaic assembly, and broadcast latency.
• FIS-B permits NEXRAD data up to 15 minutes old at broadcast time; SiriusXM’s NEXRAD composite updates on roughly a 5-minute cycle - but neither is live.
• A convective cell moving at 40 knots covers 10 miles in 15 minutes, enough to close a gap that appeared flyable on the mosaic.
• The NTSB has documented a recurring accident pattern: pilots threading convective gaps based on mosaic weather without accounting for data latency.
• Use cockpit weather for strategic routing decisions, not for splitting cells. Maintain 20 nautical miles of lateral separation from any visible convective activity.
• Onboard airborne radar provides seconds-old data and should be the primary tool for tactical weather avoidance when available; datalink weather supplements it.