Skip to content
worldfires
en
US · United States · →

Hog Butte Fire, June 2022 Yukon-Koyukuk

Out · last detection 14 Jul 2022, 23:19 UTC

The fire started on 5 June 2022 in Yukon-Koyukuk, United States, and satellites saw it burning for 40 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 83,369 hectares, spread across a single county.

It is the 4th largest in Alaska since 2016 (of 472 with a page). Number 5 in United States in 2022, of 493.

Compare with…

Suggestions: Chleca Lakes · 2017Shellman Creek · 2021Sischu · 2021Hardscrabble Creek · 2022

Burnt area
83,369ha
official perimeter (MTBS / NIFC)
Duration
≈ 40days
5 Jun 2022 – 14 Jul 2022
Counties hit
1
counties
Started on
5 Jun
2022
Heat detections
6,494
in a single hotspot: 630 MW
Danger at start
23
High · FWI index
Average daily power
2.4GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 5 Jun14 Jul
14 Jul 2022

How it evolved, day by day

5 Jun 2022 · 2,796 MW · 45 6 Jun 2022 · 1,499 MW · 102 7 Jun 2022 · 5,220 MW · 215 8 Jun 2022 · 2,588 MW · 301 9 Jun 2022 · 847 MW · 132 10 Jun 2022 · 865 MW · 59 11 Jun 2022 · 3,597 MW · 91 12 Jun 2022 · 1,652 MW · 267 13 Jun 2022 · 416 MW · 46 14 Jun 2022 · 54 MW · 8 15 Jun 2022 · 2 MW · 1 16 Jun 2022 · 244 MW · 15 17 Jun 2022 · 7,492 MW · 88 18 Jun 2022 · 75 MW · 39 19 Jun 2022 · 197 MW · 5 20 Jun 2022 · 60 MW · 12 21 Jun 2022 · 65 MW · 16 22 Jun 2022 · 4,850 MW · 238 23 Jun 2022 · 463 MW · 110 24 Jun 2022 · 2,323 MW · 202 25 Jun 2022 · 2,627 MW · 210 26 Jun 2022 · 9,845 MW · 462 27 Jun 2022 · 3,057 MW · 428 28 Jun 2022 · 102 MW · 14 29 Jun 2022 · 2,368 MW · 267 30 Jun 2022 · 4,660 MW · 369 1 Jul 2022 · 14,963 MW · 684 2 Jul 2022 · 12,569 MW · 1168 3 Jul 2022 · 1,345 MW · 301 4 Jul 2022 · 242 MW · 118 6 Jul 2022 · 258 MW · 42 7 Jul 2022 · 9 MW · 5 8 Jul 2022 · 557 MW · 68 9 Jul 2022 · 1,776 MW · 161 10 Jul 2022 · 61 MW · 7 11 Jul 2022 · 204 MW · 36 12 Jul 2022 · 802 MW · 160 14 Jul 2022 · 8 MW · 2
5 Jun 11 Jun 17 Jun 23 Jun 29 Jun 1 Jul 6 Jul 12 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

27°high
47km/h · peak gust
23%lowest humidity

It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 18.6 mm on 15 Jul.

This area had burned before

3% of the perimeter overlaps earlier fires recorded since 2016: 1,540 ha in 2017, 614 ha in 2021.

How big is it?

10 km
It burned the equivalent of 53% of the area of London (834 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each county

  1. Yukon-Koyukuk where it started
    78,636 ha reached on 5 Jun
    0.2 %

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 2020
Built-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)

Day High Min. humidity Peak gust Rain Danger (FWI)
5 Jun 23.9 °C 24 % 41 km/h 0.0 mm High 23
6 Jun 23.8 °C 23 % 34 km/h 0.0 mm High 25
7 Jun 23.5 °C 23 % 32 km/h 0.0 mm High 25
8 Jun 21.1 °C 23 % 43 km/h 0.0 mm High 28
9 Jun 17.5 °C 23 % 47 km/h 0.0 mm High 29
10 Jun 19.3 °C 25 % 31 km/h 0.0 mm High 24
11 Jun 18.6 °C 35 % 33 km/h 2.7 mm Very low 5
12 Jun 17.1 °C 47 % 41 km/h 1.3 mm Low 6
13 Jun 20.0 °C 36 % 38 km/h 0.2 mm Moderate 13
14 Jun 18.6 °C 41 % 17 km/h 0.9 mm Low 9
15 Jun 20.0 °C 42 % 15 km/h 0.7 mm Low 10
16 Jun 23.2 °C 31 % 19 km/h 0.1 mm Moderate 16
17 Jun 21.7 °C 37 % 36 km/h 0.7 mm Moderate 16
18 Jun 19.1 °C 50 % 27 km/h 6.5 mm Very low 1
19 Jun 19.8 °C 49 % 22 km/h 6.7 mm Very low 0
20 Jun 21.3 °C 47 % 20 km/h 4.4 mm Very low 1
21 Jun 23.4 °C 34 % 30 km/h 0.0 mm Very low 5
22 Jun 23.1 °C 32 % 31 km/h 0.0 mm Moderate 11
23 Jun 18.6 °C 45 % 26 km/h 0.0 mm Moderate 11
24 Jun 23.4 °C 33 % 18 km/h 0.0 mm Moderate 13
25 Jun 24.2 °C 39 % 34 km/h 0.4 mm Moderate 15
26 Jun 23.4 °C 35 % 34 km/h 0.0 mm Moderate 17
27 Jun 21.7 °C 44 % 32 km/h 0.0 mm Moderate 16
28 Jun 21.7 °C 46 % 18 km/h 0.2 mm Moderate 14
29 Jun 23.6 °C 37 % 25 km/h 0.0 mm Moderate 16
30 Jun 26.7 °C 32 % 28 km/h 0.0 mm Moderate 18
1 Jul 25.7 °C 30 % 28 km/h 0.0 mm Moderate 21
2 Jul 26.6 °C 29 % 25 km/h 0.0 mm High 22
3 Jul 24.9 °C 44 % 23 km/h 0.9 mm Moderate 13
4 Jul 23.1 °C 53 % 28 km/h 4.2 mm Very low 3
5 Jul 21.9 °C 60 % 17 km/h 2.7 mm Very low 1
6 Jul 23.2 °C 48 % 32 km/h 1.8 mm Very low 3
7 Jul 20.2 °C 48 % 24 km/h 0.0 mm Low 6
8 Jul 24.9 °C 35 % 20 km/h 0.0 mm Moderate 12
9 Jul 25.9 °C 33 % 34 km/h 0.0 mm Moderate 18
10 Jul 25.9 °C 39 % 33 km/h 2.0 mm Low 8
11 Jul 26.7 °C 32 % 24 km/h 0.1 mm Moderate 16
12 Jul 24.8 °C 38 % 24 km/h 0.2 mm Moderate 17
13 Jul 20.7 °C 35 % 34 km/h 0.4 mm Moderate 17
14 Jul 21.6 °C 29 % 26 km/h 0.0 mm Moderate 18
15 Jul after 17.3 °C 51 % 38 km/h 18.6 mm Very low 0

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 29 May 2022
After · 21 Jul 2022

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 · 6,494Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in United States ›

Frequently asked questions

How long did the Hog Butte Fire last?
The official perimeter only gives the start date (5 June 2022). The end comes from the heat detections inside the perimeter: it burned until 14 July 2022 (40 days from 5 June 2022), 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 83,369 hectares (833.7 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Yukon-Koyukuk (78,636 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 26.7 °C, humidity dropped to 23 % and gusts hit 47 km/h. The fire danger index (FWI) reached 29, 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 · Emergency number and official warnings ›

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

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 911.

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. 6,494 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.

How we build fire pages: methodology ›

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.