Skip to content
worldfires
US · United States · →

Zink Fire, March 2023 Osage

Out · last detection 6 Apr 2023, 08:42 UTC

The fire started on 31 March 2023 in Osage, United States, and satellites saw it burning for 7 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 4,591 hectares, spread across a single county.

It is the 27th largest in Oklahoma since 2016 (of 284 with a page). Number 33 in United States in 2023, of 305.

Compare with…
Burnt area
4,591ha
official perimeter (MTBS / NIFC)
Duration
≈ 7days
31 Mar 2023 – 6 Apr 2023
Counties hit
1
counties
Started on
31 Mar
2023
Heat detections
222
in a single hotspot: 128 MW
Danger at start
8
Low · FWI index
Average daily power
402MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 31 Mar6 Apr
6 Apr 2023

How it evolved, day by day

31 Mar 2023 · 212 MW · 7 1 Apr 2023 · 462 MW · 58 2 Apr 2023 · 1,855 MW · 103 3 Apr 2023 · 207 MW · 33 4 Apr 2023 · 16 MW · 7 5 Apr 2023 · 59 MW · 13 6 Apr 2023 · 1 MW · 1
31 Mar 1 Apr 2 Apr 3 Apr 4 Apr 5 Apr 6 Apr

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

30°high
80km/h · peak gust
11%lowest humidity

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

This area had burned before

63% of the perimeter overlaps earlier fires recorded since 2016: 2,894 ha in 2016, 6 ha in 2018.

How big is it?

10 km
It burned the equivalent of 2.9% of the area of London (46 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. Osage where it started
    4,571 ha reached on 31 Mar
    0.8 %

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 2025
Built-up area1.9 ha
Residents≈ 20

Inside the perimeter there were about 1.9 hectares of built-up land and about 20 residents (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.

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)
31 Mar 25.6 °C 11 % 80 km/h 3.2 mm Low 8
1 Apr 17.5 °C 26 % 44 km/h 0.0 mm Low 7
2 Apr 26.4 °C 32 % 58 km/h 0.2 mm Moderate 11
3 Apr 30.4 °C 20 % 42 km/h 0.1 mm Moderate 16
4 Apr 28.2 °C 50 % 62 km/h 0.1 mm Moderate 14
5 Apr 23.5 °C 33 % 59 km/h 7.8 mm Very low 2
6 Apr 15.3 °C 28 % 37 km/h 0.0 mm Very low 4
7 Apr after 19.7 °C 21 % 29 km/h 0.0 mm Low 8
8 Apr after 20.9 °C 19 % 22 km/h 0.0 mm Low 10
9 Apr after 22.4 °C 43 % 32 km/h 0.0 mm Low 10
10 Apr after 23.2 °C 49 % 33 km/h 1.0 mm Low 5

Before and after, from space

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

Before · 24 Mar 2023
After · 13 Apr 2023

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

The smoke

CAMS · Copernicus

On 2 April 2023 the air beside the fire reached 68 µg/m³ of PM2.5. That day averaged 22: 1.4 times the WHO daily guideline (15).

PM2.5 peak68 µg/m³
Days over the guideline2 days
PM1097 µg/m³
Optical depth0.54
293031123
Good Fair Moderate Poor Very poor Extremely poor

Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.

Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)

Detections table · 222Every 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 Zink Fire last?
The official perimeter only gives the start date (31 March 2023). The end comes from the heat detections inside the perimeter: it burned until 6 April 2023 (7 days from 31 March 2023), 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 4,591 hectares (45.9 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Osage (4,571 ha, 0.8 %).
What was the weather like?
During the fire the temperature reached 30.4 °C, humidity dropped to 11 % and gusts hit 80 km/h. The fire danger index (FWI) reached 16, class Moderate.
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. 222 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 2025, 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.