Conrad Fire, July 2018 Yakima
The fire started on 1 July 2018 in Yakima, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 1,865 hectares, spread across a single county.
It is the 147th largest in Washington since 2016 (of 285 with a page). Number 212 in United States in 2018, of 511.
- Burnt area
- 1,865ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 1 Jul 2018 – 1 Jul 2018
- Municipalities hit
- 1
- counties
- Started on
- 1 Jul
- 2018
- Heat detections
- 24
- in a single hotspot: 66 MW
- Danger at start
- 37
- High · FWI index
- Energy released
- 401MW
- sum of detected power
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 14 days without rain (1 mm or more) when it started.
This area had burned before
1% of the perimeter overlaps earlier fires recorded since 2016: 11 ha in 2017.
What happened to each town
-
Yakima where it started1,868 ha reached on 1 Jul0.2 %
Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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) |
|---|---|---|---|---|---|
| 1 Jul | 25.6 °C | 24 % | 50 km/h | 0.0 mm | High 37 |
| 2 Jul after | 19.6 °C | 26 % | 54 km/h | 0.0 mm | High 37 |
| 3 Jul after | 24.7 °C | 24 % | 45 km/h | 0.0 mm | High 32 |
| 4 Jul after | 25.3 °C | 25 % | 44 km/h | 0.0 mm | High 35 |
| 5 Jul after | 33.4 °C | 16 % | 46 km/h | 0.0 mm | Very high 48 |
| 6 Jul after | 30.3 °C | 16 % | 50 km/h | 0.0 mm | Very high 48 |
| 7 Jul after | 28.4 °C | 17 % | 37 km/h | 0.0 mm | Very high 43 |
| 8 Jul after | 31.2 °C | 13 % | 36 km/h | 0.0 mm | Very high 43 |
| 9 Jul after | 31.6 °C | 19 % | 52 km/h | 0.0 mm | Extreme 52 |
| 10 Jul after | 26.0 °C | 30 % | 54 km/h | 0.0 mm | Very high 44 |
| 11 Jul after | 30.3 °C | 24 % | 36 km/h | 0.0 mm | High 35 |
| 12 Jul after | 34.7 °C | 19 % | 30 km/h | 0.0 mm | High 38 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · 24Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 30,871 haEvans Canyon YakimaAugust 2020 · 1 day · 8 km away
- 2,420 haPipeline YakimaJuly 2019 · 1 day · 12 km away
- 2,463 haCow Canyon YakimaAugust 2022 · 1 day · 20 km away
- 18,077 haRetreat YakimaJuly 2024 · 1 day · 21 km away
- 3,218 haBurbank YakimaJuly 2021 · 1 day · 22 km away
- 2,963 haNorth Brownstown 3 YakimaAugust 2020 · 1 day · 26 km away
Frequently asked questions
- How long did the Conrad fire last?
- It burned between 1 July 2018 and 1 July 2018: 1 day, according to the start date recorded by United States agencies (MTBS / NIFC) and the heat detections seen by satellite.
- How much area did it burn?
- The official perimeter published by United States agencies (MTBS / NIFC) is 1,865 hectares (18.6 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Yakima (1,868 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 25.6 °C, humidity dropped to 24 % and gusts hit 54 km/h. The fire danger index (FWI) reached 37, class 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.
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
- NIFC · National Interagency Fire Center ↗
- InciWeb · Incident Information System ↗
- MTBS · Monitoring Trends in Burn Severity ↗
Satellite cross-check
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
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.