Skip to content
worldfires
US · United States · →

Beaver Mountain Fire, January 2017 Haskell, Pittsburg

Out · last detection 1 Feb 2017, 19:41 UTC

The fire started on 31 January 2017 in Haskell, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 1,924 hectares, spread across 2 counties.

It is the 72th largest in Oklahoma since 2016 (of 284 with a page). Number 265 in United States in 2017, of 619.

Burnt area
1,924ha
official perimeter (MTBS / NIFC)
Duration
1day
31 Jan 2017 – 31 Jan 2017
Municipalities hit
2
counties
Started on
31 Jan
2017
Heat detections
134
in a single hotspot: 31 MW
Danger at start
11
Low · FWI index
Energy released
844MW
sum of detected power

Where it burned

1 Feb 2017
HOTSPOTS BY DAY 31 Jan31 Jan

How it evolved, day by day

311

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

The weather it burned in

23°high
41km/h · peak gust
15%lowest humidity

It had gone 8 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.

What happened to each town

  1. Haskell where it started
    1,717 ha reached on 31 Jan
    1.1 %
  2. Pittsburg
    205 ha reached on 31 Jan
    0.1 %

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)
31 Jan 23.4 °C 15 % 29 km/h 0.0 mm Low 11
1 Feb after 19.8 °C 40 % 41 km/h 0.0 mm Low 8
2 Feb after 10.9 °C 47 % 43 km/h 0.1 mm Low 7
3 Feb after 7.6 °C 27 % 29 km/h 0.0 mm Low 6
4 Feb after 7.2 °C 37 % 33 km/h 0.0 mm Low 6
5 Feb after 15.6 °C 68 % 25 km/h 0.2 mm Very low 4
6 Feb after 22.1 °C 76 % 57 km/h 0.3 mm Very low 5
7 Feb after 23.3 °C 19 % 51 km/h 0.0 mm Moderate 13
8 Feb after 12.5 °C 45 % 59 km/h 0.0 mm Low 11
9 Feb after 12.5 °C 33 % 32 km/h 0.0 mm Low 8
10 Feb after 22.0 °C 41 % 56 km/h 0.0 mm Moderate 11
11 Feb after 28.8 °C 43 % 51 km/h 0.0 mm Moderate 13

Before and after, from space

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

Before · 24 Jan 2017
After · 7 Feb 2017

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 · 134Every 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 Beaver Mountain fire last?
It burned between 31 January 2017 and 31 January 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,924 hectares (19.2 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire entered 2 counties: Haskell (1,717 ha, 1.1 %); Pittsburg (205 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 23.4 °C, humidity dropped to 15 % and gusts hit 41 km/h. The fire danger index (FWI) reached 11, class Low.
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

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
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.

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.