Oks - Beaver Fire, March 2017 Beaver
The fire started on 7 March 2017 in Beaver, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 1,283 hectares, spread across a single county.
It is the 112th largest in Oklahoma since 2016 (of 284 with a page). Number 333 in United States in 2017, of 619.
We have the official perimeter (MTBS / NIFC) for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by county is there.
- Burnt area
- 1,283ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 7 Mar 2017 – 7 Mar 2017
- Municipalities hit
- 1
- counties
- Started on
- 7 Mar
- 2017
- Danger at start
- 35
- High · FWI index
Where it burned
The weather it burned in
It had gone 21 days without rain (1 mm or more) when it started. Rain came after the fire: 1.9 mm on 12 Mar.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Beaver where it started1,276 ha0.3 %
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) |
|---|---|---|---|---|---|
| 7 Mar | 16.5 °C | 7 % | 44 km/h | 0.0 mm | High 35 |
| 8 Mar after | 21.7 °C | 12 % | 47 km/h | 0.0 mm | Very high 42 |
| 9 Mar after | 26.5 °C | 10 % | 34 km/h | 0.0 mm | High 35 |
| 10 Mar after | 13.3 °C | 41 % | 49 km/h | 0.0 mm | High 26 |
| 11 Mar after | 6.3 °C | 50 % | 39 km/h | 0.7 mm | Moderate 12 |
| 12 Mar after | 15.1 °C | 47 % | 53 km/h | 1.9 mm | Low 7 |
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.
Other fires nearby
- 8,932 ha412 Fire BeaverMarch 2020 · 1 day · 3 km away
- 8,303 haBeaver River Fire BeaverApril 2022 · 1 day · 21 km away
- 971 haClearlake 149/22 BeaverNovember 2016 · 1 day · 22 km away
- 1,095 ha23 Fire BeaverApril 2022 · 1 day · 23 km away
- 2,730 haWolf Canyon Ok BeaverMay 2026 · 1 day · 30 km away
- 3,595 ha23 And Dd MeadeApril 2022 · 1 day · 34 km away
Frequently asked questions
- How long did the Oks - Beaver fire last?
- It burned between 7 March 2017 and 7 March 2017: 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,283 hectares (12.8 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Beaver (1,276 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 16.5 °C, humidity dropped to 7 % and gusts hit 44 km/h. The fire danger index (FWI) reached 35, 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.