United States wildfire observations in the available snapshot
Older cached snapshot, retrieved . Up to 20 newest records from this retained snapshot are shown, not a count of distinct wildfires or a complete incident list. NASA EONET event reports and selected NASA FIRMS thermal detections have different coverage; the observation dates below are separate from the retrieval time.
Locations are selected using bundled reference map boundaries. Near borders and coasts, map geometry and satellite pixel size limit precision; a selected point does not define a fire perimeter or establish agency responsibility.
| Observation date | Record | Latitude, longitude | Source |
|---|---|---|---|
| Wildfire Wild River, Coos, New Hampshire | 44.331, -71.031 | NASA EONET | |
| Prescribed Fire Dry Lake Hills Piles RX, Coconino, Arizona | 35.267, -111.617 | NASA EONET | |
| Prescribed Fire McCarty Piles RX, Coconino, Arizona | 34.514, -111.263 | NASA EONET | |
| Prescribed Fire Freidland-Chimney Piles RX, Coconino, Arizona | 35.283, -111.667 | NASA EONET | |
| Prescribed Fire TON RX - BAILEY LOST HP, Okanogan, Washington | 48.533, -119.055 | NASA EONET | |
| Wildfire South Tank Trail, Perry, Mississippi | 31.086, -89.098 | NASA EONET | |
| Prescribed Fire Walker Hill 3 Piles RX, Coconino, Arizona | 35.260, -111.836 | NASA EONET | |
| Prescribed Fire Brie Slash Piles RX, Coconino, Arizona | 34.546, -111.316 | NASA EONET | |
| Prescribed Fire Newman 3 Piles RX, Coconino, Arizona | 35.017, -111.639 | NASA EONET | |
| Wildfire Range 47B, Forrest, Mississippi | 31.099, -89.161 | NASA EONET | |
| Wildfire BEE HAVEN (2) (24-06), Hamilton, Florida | 30.495, -82.858 | NASA EONET | |
| Prescribed Fire Frog Tank 2 Piles RX, Coconino, Arizona | 34.963, -111.657 | NASA EONET | |
| Prescribed Fire STE - Goodin Ridge RX, McCreary, Kentucky | 36.949, -84.377 | NASA EONET | |
| Wildfire Bras, Sanders, Montana | 47.278, -114.586 | NASA EONET | |
| Wildfire COOLEY, Mendocino, California | 38.820, -123.188 | NASA EONET | |
| Wildfire NORTE, Orange, California | 33.480, -117.635 | NASA EONET | |
| Prescribed Fire Rx Polk 9275, Polk, Texas | 30.571, -94.729 | NASA EONET | |
| Wildfire HENDERSON, San Diego, California | 33.343, -117.409 | NASA EONET | |
| Prescribed Fire Newman 2 Piles RX, Coconino, Arizona | 35.017, -111.650 | NASA EONET | |
| Prescribed Fire Newman Piles RX, Coconino, Arizona | 35.017, -111.650 | NASA EONET |
Start with the question, then choose the map
Are you trying to see where a satellite detected heat, whether an agency is managing a named fire, or where an official perimeter has been mapped? These are not interchangeable tasks. The NASA FIRMS service distributes active-fire detections from MODIS and VIIRS. A point indicates a thermal observation in a satellite pixel, not a confirmed incident name, property impact or evacuation boundary. Our hotspot explainer covers the measurement in detail.
For a reported US incident, go to the National Interagency Fire Center's fire information page. It points readers to InciWeb for incident-specific updates from personnel assigned to a fire. NIFC's map directory separates current large fires, historical perimeters and other map products. Check the map legend and timestamp before comparing its shape with a PocketWorld point.
Why a hotspot and a perimeter may disagree
A satellite may observe only part of a fire at an overpass. Clouds, smoke, sensor resolution and the time between overpasses can hide activity. A perimeter is compiled through a different process and can lag the changing edge of a fire. A hotspot outside a displayed perimeter is therefore a reason to check dates and providers, not proof that either map is wrong. Conversely, no point near an incident does not mean the fire is out.
The NIFC map directory also distinguishes the Incident Management Situation Report from a complete list of every small fire. Its large-fire summary has a reporting scope. Do not count markers in PocketWorld and compare that number directly with a national incident total; satellite pixels and agency incidents use different units.
Choose a regional source for California, Oregon or Washington
For a specific place, a regional incident service can be a more useful next step than another national marker count. These official starting points have different coverage:
- California: CAL FIRE's incident pages separate active incidents from year-based archives. Check which view you opened and read the incident's own update. CAL FIRE explains that many small fires contained quickly do not receive a report on this site, and updates have no guaranteed schedule. An absent report is not confirmation that no fire occurred.
- Oregon: the Department of Forestry's fire information and statistics separates current large-fire information from historical statistics. Its statistical fire records concern ODF's protection jurisdiction, rather than every fire on every type of land statewide. Check that scope before comparing an annual total with another agency's map.
- Oregon and Washington: the Northwest Coordination Center fire map explains its large-fire reporting scope. Incident points mark starting locations for general reference, not the present fire front. Some perimeters and recent updates may be missing; open the linked incident information and retain its update time.
If your question is about smoke at a community rather than the location of a fire, use the US AirNow and wildfire-smoke guide to choose the relevant pollution readings. The incident map, perimeter and particle-pollution map answer different questions.
A repeatable US checking workflow
Open the PocketWorld wildfire map to explore the broad pattern. Record the displayed provider, observation time and selected layer. If you need an agency-confirmed incident, search NIFC's linked InciWeb resource by place or incident name. If you need a perimeter, choose the relevant NIFC map product and inspect when that boundary was updated. Keeping these three records separate makes a screenshot or shared link easier to interpret later.
US wildfire response is local as well as federal. A national map cannot tell you which road is open or whether an address must evacuate. Follow the responsible state, tribal, county or municipal authority for local instructions, and verify that any message is current. PocketWorld is an informational map, not an alert service.
What to share with someone else
If you share a map observation, include the place, provider, layer and time checked. Say “satellite detection” when that is what you saw; reserve “incident” for an agency report and “perimeter” for a mapped boundary. Avoid turning a visual cluster into an estimate of burned area or affected homes. The PocketWorld methodology explains how provider data and retained snapshots are presented.
Data sources
The regional sample uses retained NASA EONET reports and selected NASA FIRMS thermal detections, with separate observation and retrieval dates. It is not a complete incident register. Official incident, perimeter and fire-weather references are linked beside the guide's explanations.