Burned area
satellite only40,408ha
Perimeter published by MTBS (USGS/USFS).
- Source
- MTBS (USGS/USFS)
- Date
- 21 Jun 2018 – 1 Jul 2018
+− cross-check
No official record is matched to this page to compare it with.
US · United States · –
Boxcar 0410 Rn Fire, June 2018 Wasco
Out · last detection 1 Jul 2018, 10:43 UTC
The fire started on 21 June 2018 in Wasco, United States, and satellites saw it burning for 11 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 40,408 hectares, spread across a single county.
It is the 18th largest in Oregon since 2016 (of 325 with a page). Number 13 in United States in 2018, of 511.
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 only11days
21 Jun 2018 to 1 Jul 2018: first and last day with fire on the page.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- last detection: 1 Jul 2018, 10:43 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 only21 Jun 2018
First day with fire seen by the satellites or the perimeter.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- 21 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 only916
VIIRS detections at 375 m. Most intense hotspot: 146 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 21 Jun 2018 – 1 Jul 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 only5,986MW
Total radiative power on 22 June 2018; hotspots that day: 398.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 22 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
model25.1FWI · 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
- 21 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
model33.1°C · 6% RH
High of 33.1 °C and minimum humidity of 6% on 24 June 2018; gusts of 51 km/h on 1 July 2018.
- Source
- weather model at the fire’s grid cell
- Date
- 21 Jun 2018 – 1 Jul 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
- 40,408 ha
- Dates
- 21 Jun 2018 – 1 Jul 2018
- Name
- Boxcar 0410 Rn
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/boxcar-0410-rn-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 boxcar-0410-rn-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-21 | 25 | 340 | 26.5 | 15.1 | 26 | 19 | 41 | 0 | 25.1 | alto | 1 |
| 2018-06-22 | 398 | 5,986 | 23.9 | 12.5 | 27 | 23.9 | 47.5 | 0 | 39.2 | muy_alto | 1 |
| 2018-06-23 | 336 | 3,373 | 23.3 | 11.7 | 26 | 14.8 | 32.8 | 0 | 30.4 | alto | 1 |
| 2018-06-24 | 139 | 717 | 33.1 | 11.1 | 6 | 22.1 | 41.4 | 0 | 29.9 | alto | 1 |
| 2018-06-25 | 1 | 4 | 21.9 | 12.8 | 22 | 22.5 | 45.7 | 0 | 43.6 | muy_alto | 1 |
| 2018-06-26 | 2 | 23 | 24.2 | 7.2 | 17 | 14.8 | 26.6 | 0 | 28.4 | alto | 1 |
| 2018-06-27 | 0 | 0 | 25.5 | 10 | 14 | 25.1 | 49 | 0 | 39 | muy_alto | 1 |
| 2018-06-28 | 1 | 0 | 20.5 | 9.6 | 30 | 24.5 | 48.6 | 0.3 | 47.7 | muy_alto | 1 |
| 2018-06-29 | 0 | 0 | 24.6 | 9.3 | 23 | 20.5 | 42.8 | 0 | 37.8 | alto | 1 |
| 2018-06-30 | 8 | 110 | 27 | 10.1 | 19 | 25.4 | 49.3 | 0 | 38 | alto | 1 |
| 2018-07-01 | 6 | 7 | 25.3 | 12.8 | 17 | 25.1 | 50.8 | 0 | 41.1 | muy_alto | 1 |
| 2018-07-02 | 0 | 0 | 18.8 | 8.7 | 24 | 22 | 47.5 | 0 | 49.6 | muy_alto | 0 |
| 2018-07-03 | 0 | 0 | 22.7 | 5.8 | 16 | 13 | 25.9 | 0 | 26.1 | alto | 0 |
| 2018-07-04 | 0 | 0 | 26.5 | 13.8 | 17 | 24.6 | 45.4 | 0 | 57.7 | extremo | 0 |
| 2018-07-05 | 0 | 0 | 32 | 13.3 | 10 | 27.9 | 59.8 | 0 | 38.8 | muy_alto | 0 |
| 2018-07-06 | 0 | 0 | 29.9 | 13.9 | 14 | 26.8 | 59.8 | 0 | 52 | extremo | 0 |
| 2018-07-07 | 0 | 0 | 27 | 9.7 | 16 | 17.8 | 35.6 | 0 | 33.8 | alto | 0 |
| 2018-07-08 | 0 | 0 | 31.5 | 10.6 | 12 | 20.4 | 44.3 | 0 | 35.8 | alto | 0 |
| 2018-07-09 | 0 | 0 | 28.5 | 13.5 | 20 | 24.5 | 53.6 | 0 | 34.5 | alto | 0 |
| 2018-07-10 | 0 | 0 | 24.8 | 12 | 26 | 15.9 | 36.4 | 0 | 41.8 | muy_alto | 0 |
| 2018-07-11 | 0 | 0 | 28.6 | 10.9 | 17 | 15.6 | 33.1 | 0 | 43.5 | 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
- 40,408ha
- official perimeter (MTBS / NIFC)
- Duration
- ≈ 11days
- 21 Jun 2018 – 1 Jul 2018
- Counties hit
- 1
- counties
- Started on
- 21 Jun
- 2018
- Heat detections
- 916
- in a single hotspot: 146 MW
- Danger at start
- 25
- High · FWI index
- Average daily power
- 1.2GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
21 Jun1 Jul
1 Jul 2018
How it evolved, day by day
22 Jun
25 Jun
28 Jun
1 Jul
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
33°high
51km/h · peak gust
6%lowest humidity
It had gone 0 days without rain (1 mm or more) when it started.
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
-
Wasco where it started40,258 ha reached on 21 Jun6.5 %
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 area1.4 ha
Residents< 20
Inside the perimeter there were about 1.4 hectares of 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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 21 Jun | 26.5 °C | 26 % | 41 km/h | 0.0 mm | High 25 |
| 22 Jun | 23.9 °C | 27 % | 48 km/h | 0.0 mm | Very high 39 |
| 23 Jun | 23.3 °C | 26 % | 33 km/h | 0.0 mm | High 30 |
| 24 Jun | 33.1 °C | 6 % | 41 km/h | 0.0 mm | High 30 |
| 25 Jun | 21.9 °C | 22 % | 46 km/h | 0.0 mm | Very high 44 |
| 26 Jun | 24.2 °C | 17 % | 27 km/h | 0.0 mm | High 28 |
| 27 Jun | 25.5 °C | 14 % | 49 km/h | 0.0 mm | Very high 39 |
| 28 Jun | 20.5 °C | 30 % | 49 km/h | 0.3 mm | Very high 48 |
| 29 Jun | 24.6 °C | 23 % | 43 km/h | 0.0 mm | High 38 |
| 30 Jun | 27.0 °C | 19 % | 49 km/h | 0.0 mm | High 38 |
| 1 Jul | 25.3 °C | 17 % | 51 km/h | 0.0 mm | Very high 41 |
| 2 Jul after | 18.8 °C | 24 % | 48 km/h | 0.0 mm | Very high 50 |
| 3 Jul after | 22.7 °C | 16 % | 26 km/h | 0.0 mm | High 26 |
| 4 Jul after | 26.5 °C | 17 % | 45 km/h | 0.0 mm | Extreme 58 |
| 5 Jul after | 32.0 °C | 10 % | 60 km/h | 0.0 mm | Very high 39 |
| 6 Jul after | 29.9 °C | 14 % | 60 km/h | 0.0 mm | Extreme 52 |
| 7 Jul after | 27.0 °C | 16 % | 36 km/h | 0.0 mm | High 34 |
| 8 Jul after | 31.5 °C | 12 % | 44 km/h | 0.0 mm | High 36 |
| 9 Jul after | 28.5 °C | 20 % | 54 km/h | 0.0 mm | High 34 |
| 10 Jul after | 24.8 °C | 26 % | 36 km/h | 0.0 mm | Very high 42 |
| 11 Jul after | 28.6 °C | 17 % | 33 km/h | 0.0 mm | Very high 44 |
Its twins: fires that started in the same weather
It started with an FWI of 25.1, a minimum humidity of 26% and rain the day before. Fires in the area that started in weather like this since 2016: 20.
FWI at the start
25.1
Minimum humidity
26 %
Days without rain
0
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Boxcar 0410 Rn Fire, June 2018
40,408 ha
11 days
FWI 25.1
Min. humidity 26 %
Rock Creek 0103 Rn Fire, April 2020
418 ha
1 day
FWI 21.5
Min. humidity 26 %
74 km away, in 2020
First rain (1 mm or more) after it ended: 4.9 mm on 2 May.
Poison Creek Fire, July 2024
420 ha
8 days
FWI 24.0
Min. humidity 25 %
205 km away, in 2024
First rain (1 mm or more) after it ended: 1.3 mm on 3 Aug.
Crockets Knob Fire, August 2022
1,893 ha
21 days
FWI 29.2
Min. humidity 26 %
185 km away, in 2022
First rain (1 mm or more) after it ended: 5.0 mm on 13 Sept.
Linton Creek Fire, September 2024
592 ha
5 days
FWI 27.6
Min. humidity 24 %
120 km away, in 2024
First rain (1 mm or more) after it ended: 1.5 mm on 12 Sept.
S-503 Fire, June 2021
2,853 ha
8 days
FWI 26.0
Min. humidity 20 %
34 km away, in 2021
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 8 days
- median duration
- 1,182 ha
- median area
- 60 %
- went past 1,000 ha
- 2.4 mm
- rain at the end (median; 16 of 20 had it)
It was 34.2 times larger than the median of its twins and lasted 11 days, against 8 days.
None of its 20 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 4 of 20, 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.4 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
—first rain
—no rain in ten days
51km/h · max. gust
It was considered over on 1 Jul, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 16 of 20, with a median of 2.4 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 · 14 Jun 2018
After · 8 Jul 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 · 916Every 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
- 28,349 haNena Springs WascoAugust 2017 · 11 days · 17 km away
- 17,733 ha0567 Little Buck WascoJuly 2026 · 11 days · 34 km away
- 13,620 haLong Hollow 0806 Rn WascoJuly 2018 · 3 days · 35 km away
- 17,742 haBlack Rock WascoSeptember 2025 · 5 days · 38 km away
- 38,743 haCram JeffersonJuly 2025 · 6 days · 39 km away
- 8,277 haSouth Valley Road WascoAugust 2018 · 3 days · 39 km away
Frequently asked questions
- How long did the Boxcar 0410 Rn Fire last?
- The official perimeter only gives the start date (21 June 2018). The end comes from the heat detections inside the perimeter: it burned until 1 July 2018 (11 days from 21 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 40,408 hectares (404.1 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Wasco (40,258 ha, 6.5 %).
- What was the weather like?
- During the fire the temperature reached 33.1 °C, humidity dropped to 6 % and gusts hit 51 km/h. The fire danger index (FWI) reached 48, class Very high.
- 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: 20. Their median duration was 8 days and their median area 1,182 ha; 60 % went past 1,000 ha. None of its 20 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 4 of 20, 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.4 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. 916 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.