GribStream

GribStream Blog

NBM v5.1 planned for October 2026: winter guidance and new coverage

NOAA and WPC presentations point to NBM v5.1 in October 2026, with 12-hour winter guidance, precipitation-type and percentile fixes, and new Southwest Pacific coverage.

NOAA has not issued a formal Service Change Notice for NBM v5.1 yet, but two official NOAA/NWS presentation decks now give a clear planning signal: the next National Blend of Models upgrade is targeted for October 2026, with WPC's winter-weather deck calling out mid-October.

That matters for weather forecast applications because NBM is not just another model feed. It is NOAA's post-processed blend of global, regional, high-resolution, ensemble, and statistical guidance. The NBM user webinar describes hourly updates, forecasts out to roughly Day 11, and output across CONUS, Alaska, Hawaii, Puerto Rico, Guam, Oceanic, and global domains. It also covers the core product families customers build around: deterministic grids, min/max fields over time windows, percentiles, and probability-of-exceedance guidance.

The same deck notes that NBM now serves as the NWS gridded forecast for Days 4-7 over CONUS, with Alaska expected to follow. For GribStream users, the practical point is simple: NBM version changes can alter production weather forecast API results even when the dataset code stays the same.

What Is Planned

The April 15, 2026 NBM user webinar lists v5.1 planned for October 2026. The same slide says v5.1 is expected to:

  • address remaining winter-weather guidance issues left after v5.0
  • add a new NBM domain in the Southwest Pacific

The February 10, 2026 WPC Hydrometeorological Testbed winter overview adds more detail. It says NBM v5.1 is scheduled for implementation in mid-October and calls out:

  • 12-hour winter products
  • work on blocky percentile fields
  • work on precipitation-type fields

That is not the same as a final implementation notice. Treat October 2026 as a planning target until NWS publishes a formal SCN or updates the NBM versions page.

Forecast Science To Watch

The most important customer-facing theme is winter forecast quality, especially for applications that use NBM as a probabilistic weather API rather than as a single deterministic forecast.

NBM v5.0 already moved winter guidance toward better consistency between deterministic values and probabilistic distributions. The WPC deck describes several v5.0 winter changes that set up the v5.1 work: higher-resolution ECMWF ensemble input, removal of SREF inputs, higher-resolution GEFS surface fields, QMD QPF changes that feed the winter suite, weighted probabilistic output, and changes intended to preserve freezing-rain signals in inversion setups.

The v5.1 notes are narrower, but operationally meaningful. The planned work on 12-hour winter products, blocky percentiles, and precipitation-type fields points directly at high-value decision products:

  • snow and ice accumulation windows
  • precipitation-type transitions
  • exceedance probabilities for winter thresholds
  • percentile spread used in risk and alert logic
  • consistency between deterministic output and probabilistic weather guidance

If your workflow uses NBM for winter operations, routing, energy demand, insurance risk, aviation surface impacts, or automated alerting, those are the fields to compare first when parallel data appears.

A Southwest Pacific NBM Domain

The new Southwest Pacific domain is the clearest availability item in the v5.1 roadmap.

NOAA's current NBM public coverage is already broad, but many API users still think of NBM as a CONUS-first product unless they specifically need Alaska, Hawaii, Puerto Rico, Guam, Oceanic, or QMD. A Southwest Pacific domain would be a coverage expansion, not just a method update.

If NOAA publishes that domain in the public NBM distribution, GribStream will evaluate whether it should become a new dataset code. The useful questions will be: which weather parameters are included, what lead times are available, whether it has a parallel preview period, and whether the domain lands in the same public distribution path as the rest of NBM.

RRFS/REFS May Change NBM First

There may be a meaningful NBM change before v5.1.

Both decks point to a likely NBM v5.0.1 update tied to RRFS/REFS v1. The WPC winter overview says RRFS/REFS implementation was expected to force a v5.0.1, and the April webinar says RRFS/REFS integration work is complete. The April deck also says NAM and HiResW inputs will no longer be used in NBM starting in v5.0.1.

That is not a minor bookkeeping detail. Input changes can alter blended temperature, wind, precipitation, snow, and probabilistic fields. If your NBM validation depends on continuity from v5.0 to v5.1, track v5.0.1 separately.

Availability For GribStream Users

For production today, keep using the operational NBM datasets:

When NOAA exposes v5.1 in a public parallel feed, the NBM Parallel datasets are the place to watch first. That is where users should expect comparison data before an operational switch, if NOAA follows the same pattern used for NBM v5.0.

For validation, plan for at least two possible future boundaries:

  • the v5.0.1 RRFS/REFS input-change boundary, if NOAA implements it this summer
  • the v5.1 boundary, currently planned for October 2026

When dates become official, separate backtests and alert-quality comparisons by the exact model-run cycle, not just the calendar day. GribStream's operational NBM dataset codes can preserve one archive path across version changes, but the forecast system behind the values can still change at a specific run boundary.

What To Watch Next

The sources worth watching next are:

  • a formal NWS SCN/PNS for NBM v5.0.1 or v5.1
  • updates to the NOAA NBM versions page
  • new NBM parallel data in the public bucket
  • any public path or domain information for the Southwest Pacific NBM grid
  • inventory changes for 12-hour winter products and precipitation-type fields

Until those appear, this is a planning signal, not an operational switch notice.

Related reading

Sources