Skip to content
worldfires
US · United States · →

Jacobson Fire, October 2016 Tulare

Out · last detection 22 Oct 2016, 10:15 UTC

The fire started on 21 October 2016 in Tulare, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 676 hectares, spread across a single county.

It is the 348th largest in California since 2016 (of 442 with a page). Number 345 in United States in 2016, of 475.

Burnt area
676ha
official perimeter (MTBS / NIFC)
Duration
1day
21 Oct 2016 – 21 Oct 2016
Municipalities hit
1
counties
Started on
21 Oct
2016
Heat detections
136
in a single hotspot: 373 MW
Danger at start
33
High · FWI index
Energy released
2.5GW
sum of detected power

Where it burned

22 Oct 2016
HOTSPOTS BY DAY 21 Oct21 Oct

How it evolved, day by day

2122

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

The weather it burned in

22°high
66km/h · peak gust
10%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 14.1 mm on 30 Oct.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Tulare where it started
    680 ha reached on 21 Oct
    0.0 %

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)
21 Oct 21.5 °C 10 % 37 km/h 0.0 mm High 33
22 Oct after 20.2 °C 11 % 44 km/h 0.0 mm High 36
23 Oct after 17.7 °C 17 % 52 km/h 0.8 mm High 28
24 Oct after 14.1 °C 38 % 59 km/h 7.4 mm Very low 3
25 Oct after 18.4 °C 25 % 36 km/h 0.0 mm Low 6
26 Oct after 20.1 °C 24 % 31 km/h 0.0 mm Moderate 14
27 Oct after 19.0 °C 31 % 44 km/h 0.8 mm Moderate 15
28 Oct after 12.4 °C 69 % 66 km/h 17.8 mm Very low 0
29 Oct after 16.3 °C 34 % 44 km/h 0.0 mm Very low 2
30 Oct after 11.5 °C 60 % 70 km/h 14.1 mm Very low 0

Before and after, from space

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

Before · 14 Oct 2016
After · 28 Oct 2016

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 · 136Every 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 Jacobson fire last?
It burned between 21 October 2016 and 21 October 2016: 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 676 hectares (6.8 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Tulare (680 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 21.5 °C, humidity dropped to 10 % and gusts hit 66 km/h. The fire danger index (FWI) reached 36, 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

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.