LANDFIRE refresh cycle vs. annual satellite fuel layers

If you've ever pulled the LANDFIRE fuel model layer for a planning unit and found a stand that burned two fire seasons ago still showing as untouched timber, you already know the problem this post is about. LANDFIRE is the backbone dataset most fuels programs grew up on, and it's still free, national, and consistent from unit to unit. But "current" is doing a lot of work in that sentence, and it's worth being precise about what LANDFIRE refreshes every year and what it doesn't.

How current is LANDFIRE, really

LANDFIRE isn't static. The program does run annual disturbance updates that pull in known wildfire perimeters, fuel treatments, and other mapped events to patch the existing base layers. That's useful: if a fire burned through part of your district last season and got reported through the normal channels, there's a decent chance it shows up in the next disturbance pass.

What doesn't happen every year is a full rebuild of the underlying vegetation and fuel model classification across the whole landscape. Canopy growth, insect and disease mortality that never got formally mapped, drought-stressed stands, brush encroachment into old burn scars: these pile up between the comprehensive remaps, which land on a multi-year cycle rather than an annual one, and none of it changes the classification code on the map until that remap runs. A unit can carry the same fuel model for years after the vegetation on the ground has changed. For a planner building a fuel break alignment or scoping a burn unit, that gap is exactly where surprises live: understory that's denser than the layer suggests, or a classification that no longer matches what a field crew finds when they walk it.

LANDFIRE was built to give the whole country a common reference layer. Tracking year-to-year change in one district was never the job it was designed for, and it does the job it was built for well. It just doesn't answer the question a fuels planner asks every spring: what changed on my unit since last season.

Fuel map update frequency, and why annual matters for siting

This is where the refresh cycle question turns practical. A fuel break alignment or a burn plan depends on current structure, canopy density, ladder fuels, the stuff that determines whether a break will actually hold or a prescribed fire will behave the way the plan says it should. If the base fuel layer predates the last two fire seasons, a beetle outbreak, or a wet year of brush growth, the planner is working from a picture that's already out of date before the first field visit.

An annual satellite-based fuel layer closes that gap on a different schedule than a disturbance patch does. Instead of waiting for a mapped event to trigger an update, the whole planning unit gets reclassified from new high-resolution imagery every year; canopy structure and dryness indices run back through standard fuel model classes on the same cadence every season. That means the layer reflects what's standing and how dry it is this year, not whatever conditions were on the ground when the last comprehensive remap ran.

That doesn't stand in for LANDFIRE as a national reference, and it doesn't stand in for field transects as ground truth either. What it adds is a second data point that moves at the speed fuel conditions change, instead of the speed a national mapping program can afford to remap at. Pulled against the field crew's transect notes and the agency's existing fuels layer, it narrows down where reality has drifted furthest from the map before anyone drives out to check.

Fuel Load Mapping builds that annual layer from high-resolution multispectral imagery, classifying canopy structure and dryness into standard fuel model classes across the planning unit every year, so the picture you're siting a break or scoping a burn against is this season's, not whenever the last full remap happened to run.

If your fuel break alignment or burn unit scoping is riding on a layer that's a few fire seasons behind, it might be worth seeing what an annual refresh looks like for your district.