Burned area
satellite only560ha
Perimeter published by MTBS (USGS/USFS).
- Source
- MTBS (USGS/USFS)
- Date
- 7 Jun 2018 – 12 Jun 2018
+− cross-check
No official record is matched to this page to compare it with.
US · United States · –
Soldier Canyon Fire, June 2018 Otero
Out · last detection 12 Jun 2018, 19:41 UTC
The fire started on 7 June 2018 in Otero, United States, and satellites saw it burning for 6 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 560 hectares, spread across a single county.
It is the 172th largest in New Mexico since 2016 (of 204 with a page). Number 440 in United States in 2018, of 511.
The power measured by the satellite is low (10.8 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only6days
7 Jun 2018 to 12 Jun 2018: first and last day with fire on the page.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- last detection: 12 Jun 2018, 19:41 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only7 Jun 2018
First day with fire seen by the satellites or the perimeter.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- 7 Jun 2018
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only61
VIIRS detections at 375 m. Most intense hotspot: 11 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 7 Jun 2018 – 12 Jun 2018
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only151MW
Total radiative power on 8 June 2018; hotspots that day: 54.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 8 Jun 2018
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model44.9FWI · very high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 0.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 7 Jun 2018, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model31.0°C · 5% RH
High of 31.0 °C and minimum humidity of 5% on 12 June 2018; gusts of 46 km/h on 10 June 2018.
- Source
- weather model at the fire’s grid cell
- Date
- 7 Jun 2018 – 12 Jun 2018
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 560 ha
- Dates
- 7 Jun 2018 – 12 Jun 2018
- Name
- Soldier Canyon
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/soldier-canyon-fire-2018-06?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire soldier-canyon-fire-2018-06.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2018-06-07 | 0 | 0 | 28.8 | 15 | 11 | 15.1 | 45.4 | 0 | 44.9 | muy_alto | 1 |
| 2018-06-08 | 54 | 151 | 28.6 | 12.2 | 11 | 10.8 | 30.2 | 0.3 | 41.7 | muy_alto | 1 |
| 2018-06-09 | 2 | 4 | 25.6 | 15 | 19 | 14.5 | 38.9 | 0 | 45.4 | muy_alto | 1 |
| 2018-06-10 | 1 | 11 | 26.5 | 14.9 | 14 | 15.5 | 46.4 | 0.2 | 51.8 | extremo | 1 |
| 2018-06-11 | 2 | 1 | 29.7 | 13.3 | 7 | 11.5 | 35.6 | 0 | 57.3 | extremo | 1 |
| 2018-06-12 | 2 | 16 | 31 | 13.9 | 5 | 10.9 | 36.7 | 0 | 55.9 | extremo | 1 |
| 2018-06-13 | 0 | 0 | 28 | 15.3 | 17 | 14.5 | 38.9 | 0.1 | 46 | muy_alto | 0 |
| 2018-06-14 | 0 | 0 | 26.4 | 12.7 | 21 | 11.8 | 37.1 | 0 | 49.3 | muy_alto | 0 |
| 2018-06-15 | 0 | 0 | 26 | 13 | 23 | 10.2 | 33.5 | 6.4 | 45.6 | muy_alto | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: MTBS (USGS/USFS), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 560ha
- official perimeter (MTBS / NIFC)
- Duration
- ≈ 6days
- 7 Jun 2018 – 12 Jun 2018
- Counties hit
- 1
- counties
- Started on
- 7 Jun
- 2018
- Heat detections
- 61
- in a single hotspot: 11 MW
- Danger at start
- 45
- Very high · FWI index
- Average daily power
- 37MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
7 Jun12 Jun
12 Jun 2018
How it evolved, day by day
8 Jun
9 Jun
10 Jun
11 Jun
12 Jun
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
31°high
46km/h · peak gust
5%lowest humidity
It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 6.4 mm on 15 Jun.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each county
-
Otero where it started564 ha reached on 8 Jun0.0 %
Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
People and buildings inside the perimeter
GHSL 2020Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
The weather day by day
ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.
Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
Started with Very dry air: 40 % of the area in United States
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 7 Jun | 28.8 °C | 11 % | 45 km/h | 0.0 mm | Very high 45 |
| 8 Jun | 28.6 °C | 11 % | 30 km/h | 0.3 mm | Very high 42 |
| 9 Jun | 25.6 °C | 19 % | 39 km/h | 0.0 mm | Very high 45 |
| 10 Jun | 26.5 °C | 14 % | 46 km/h | 0.2 mm | Extreme 52 |
| 11 Jun | 29.7 °C | 7 % | 36 km/h | 0.0 mm | Extreme 57 |
| 12 Jun | 31.0 °C | 5 % | 37 km/h | 0.0 mm | Extreme 56 |
| 13 Jun after | 28.0 °C | 17 % | 39 km/h | 0.1 mm | Very high 46 |
| 14 Jun after | 26.4 °C | 21 % | 37 km/h | 0.0 mm | Very high 49 |
| 15 Jun after | 26.0 °C | 23 % | 34 km/h | 6.4 mm | Very high 46 |
Its twins: fires that started in the same weather
It started with an FWI of 44.9, a minimum humidity of 11% and rain the day before. Fires in the area that started in weather like this since 2016: 26.
FWI at the start
44.9
Minimum humidity
11 %
Days without rain
0
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Soldier Canyon Fire, June 2018
560 ha
6 days
FWI 44.9
Min. humidity 11 %
Mixen Fire, June 2022
629 ha
1 day
FWI 46.1
Min. humidity 13 %
120 km away, in 2022
First rain (1 mm or more) after it ended: 12.2 mm on 20 Jun.
Taylor Canyon Fire, July 2017
878 ha
5 days
FWI 42.0
Min. humidity 13 %
193 km away, in 2017
First rain (1 mm or more) after it ended: 1.7 mm on 11 Jul.
Vaughn Fire, July 2018
1,106 ha
1 day
FWI 43.0
Min. humidity 13 %
176 km away, in 2018
First rain (1 mm or more) after it ended: 1.0 mm on 24 Jul.
Black Range Complex, July 2016
1,466 ha
7 days
FWI 45.6
Min. humidity 16 %
231 km away, in 2016
First rain (1 mm or more) after it ended: 1.1 mm on 17 Jul.
Loma Desert Fire, April 2023
820 ha
1 day
FWI 43.4
Min. humidity 10 %
150 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 3 days
- median duration
- 1,000 ha
- median area
- 50 %
- went past 1,000 ha
- 2.0 mm
- rain at the end (median; 20 of 26 had it)
It stayed below its twins: 560 ha against a median of 1,000 ha. It lasted 6 days, against 3 days.
In 6 of 26, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.0 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
6.4 mmfirst rain
15 Jun3 days after it ended
46km/h · max. gust
It was considered over on 12 Jun, and on 15 Jun 6.4 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 20 of 26, with a median of 2.0 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 31 May 2018
After · 19 Jun 2018
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
Detections table · 61Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV
Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Soldier Canyon Fire last?
- The official perimeter only gives the start date (7 June 2018). The end comes from the heat detections inside the perimeter: it burned until 12 June 2018 (6 days from 7 June 2018), the last day with detections before more than 10 days in a row without any, so it is approximate.
- How much area did it burn?
- The official perimeter published by United States agencies (MTBS / NIFC) is 560 hectares (5.6 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Otero (564 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 31.0 °C, humidity dropped to 5 % and gusts hit 46 km/h. The fire danger index (FWI) reached 57, class Extreme.
- Where does this data come from?
- From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. It is not an official report.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 26. Their median duration was 3 days and their median area 1,000 ha; 50 % went past 1,000 ha. In 6 of 26, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.0 mm.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 911 · Emergency number and official warnings
- NIFC · National Interagency Fire Center ↗
- InciWeb · Incident Information System ↗
- MTBS · Monitoring Trends in Burn Severity ↗
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
RSS Changes to this page With cross-checks and a citable version
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: MTBS (US Geological Survey and US Forest Service), official.
- The official perimeter has no end date: the end is the last day with VIIRS detections inside the perimeter before a gap of more than 10 days (150 days at most), so it is approximate. 61 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter is official and in the public domain. For past years it comes from MTBS (Monitoring Trends in Burn Severity), run by the U.S. Geological Survey and the USDA Forest Service, which map it on Landsat and Sentinel-2 imagery. For the current and last year it comes from WFIGS at the National Interagency Fire Center (NIFC): incident perimeters mapped by fire crews, aircraft and imagery. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. County boundaries come from geoBoundaries ADM2 (Public Domain). The area per county is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.