Skip to content
worldfires
MX · Mexico · →

Tumbalá fire, April 2017 Tumbalá

Out · last detection 30 Apr 2017, 18:45 UTC

The fire started on 22 April 2017 in Tumbalá, Mexico, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,935 hectares from heat detections, spread across a single municipality.

It is the 165th largest in Chiapas since 2016 (of 265 with a page). Number 250 in Mexico in 2017, of 375.

Burnt area
1,935ha
GWIS perimeter (Copernicus)
Duration
9days
22 Apr 2017 – 30 Apr 2017
Municipalities hit
1
municipalities
Started on
22 Apr
2017
Heat detections
69
in a single hotspot: 35 MW
Danger at start
0
Very low · FWI index
Energy released
608MW
sum of detected power

Where it burned

30 Apr 2017
HOTSPOTS BY DAY 22 Apr30 Apr

How it evolved, day by day

222425262930

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

The weather it burned in

35°high
34km/h · peak gust
36%lowest humidity

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

This area had burned before

41% of the perimeter overlaps earlier fires recorded since 2016: 789 ha in 2016.

What happened to each town

  1. Tumbalá where it started
    1,945 ha reached on 22 Apr
    4.8 %

Burnt area inside each municipality, from crossing the GWIS 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)
22 Apr 28.2 °C 60 % 25 km/h 3.2 mm Very low 0
23 Apr 25.5 °C 70 % 34 km/h 3.9 mm Very low 0
24 Apr 27.0 °C 52 % 28 km/h 0.0 mm Very low 1
25 Apr 32.0 °C 46 % 24 km/h 0.0 mm Very low 4
26 Apr 35.0 °C 36 % 22 km/h 0.0 mm Low 8
27 Apr 32.4 °C 43 % 26 km/h 3.5 mm Very low 1
28 Apr 33.2 °C 53 % 26 km/h 0.0 mm Very low 5
29 Apr 34.0 °C 49 % 28 km/h 1.2 mm Very low 5
30 Apr 34.2 °C 40 % 34 km/h 0.8 mm Low 9
1 May after 26.3 °C 75 % 30 km/h 7.8 mm Very low 0

Before and after, from space

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

Before · 15 Apr 2017
After · 7 May 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 · 69Every 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 Mexico ›

Frequently asked questions

How long did the Tumbalá fire last?
GWIS (Copernicus) dates it between 22 April 2017 and 30 April 2017: 9 days between the first and last heat detection of the perimeter.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,935 hectares (19.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Tumbalá (1,945 ha, 4.8 %).
What was the weather like?
During the fire the temperature reached 35.0 °C, humidity dropped to 36 % and gusts hit 34 km/h. The fire danger index (FWI) reached 9, class Low.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Mexico (geoBoundaries). 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 comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Creative Commons Attribution 4.0 (CC BY 4.0)). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.