Satellite revisit vs. night-flying IR: which tracks fire growth faster

When the night flight beats the satellite pass

At 2 a.m. the IR bird is still your fastest read on a run that started after the satellite's last pass. A contracted fixed-wing or rotor platform flying linescan infrared can get you a fresh perimeter in the dead of night, once smoke columns have settled and the fire's doing its real work. If the incident is active and the division needs numbers for the 0600 briefing, that flight is sometimes the only data you've got.

The catch is logistics. Night IR needs an aircraft on contract, a crew cleared to fly the TFR, workable weather, and an analyst awake to turn raw imagery into a perimeter shapefile before briefing. On a multi-fire complex with every platform in the region already tasked, you might wait two or three nights for your slot in the queue. And one flight gives you one snapshot. If the run keeps moving after the pass, you're flying blind again until the next sortie.

What satellite revisit actually buys you

A wide-swath multispectral satellite doesn't need a tasking request to fly over your fire. It's already passing. What changes with revisit cadence is how often that pass lands on your incident, and how fast the data turns into something the planning section can actually use.

With imagery that refreshes daily during an active event, you get a standing read on the fire front without competing for aircraft time against five other incidents in the region. SWIR-based indices split the actively burning edge from ground that's already cooled, so the progression line isn't just raw hotspot pixels, it's something ops can plot directly.

The resolution tradeoff is real, though. At 10 to 30 meters, satellite imagery won't catch the fine-grained spot fire detail a night IR flight resolves at close range over a small area. For a fast-moving crown run through heavy fuel, an aircraft orbiting the active edge still sees things a daily pass can't.

Use the orbit for the baseline, the plane for the spike

Most intel sections end up running both, because they answer different questions. The aircraft answers: what is this fire doing right now, tonight, on this flank. The satellite answers: where does the whole perimeter sit today, and how has severity graded out across what's already burned. One is a sortie you request and wait on. The other is a feed that's already showing up.

If your section is stretched thin managing aircraft requests across a complex, a tool like Fire Perimeter Map gives planning a daily-refreshed read on perimeter and burn severity that doesn't depend on getting a plane in the air that night. It won't replace the IR flight when you need eyes on a specific run at 0300. It does mean the morning briefing doesn't stall waiting on whichever asset happened to fly last night.

A few things to check before you pick one

Start by counting how many fires are competing for the same IR aircraft this week. Then look at whether your GIS section has the bandwidth to turn a flight into a usable shapefile inside the briefing window. Finally, weigh whether the fire is moving fast enough tonight to justify a sortie versus waiting on tomorrow's satellite pass.

None of this gets decided once at IC setup and left alone. A complex running six fires at different stages might fly IR nightly on the two still actively spreading, and lean on satellite revisit for the four that are mostly lined and in mop-up. The right mix shifts week to week, sometimes night to night.

What doesn't shift is the need for a baseline you can trust without filing a tasking request first. Daily revisit is built to cover that gap, and it's worth a look if your briefing cycle keeps waiting on whichever flight made it off the ground.