Skip to content
worldfires
MX · Mexico · →

Cintalapa fire, 27 April 2016 Cintalapa

Out · last detection 2 May 2016, 18:53 UTC

The fire started on 27 April 2016 in Cintalapa, Mexico, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,990 hectares from heat detections, spread across a single municipality.

It is the 36th largest in Chiapas since 2016 (of 267 with a page). Number 35 in Mexico in 2016, of 208.

Compare with…
Burnt area
3,990ha
GWIS perimeter (Copernicus)
Duration
7days
27 Apr 2016 – 3 May 2016
Municipalities hit
1
municipalities
Started on
27 Apr
2016
Heat detections
199
in a single hotspot: 35 MW
Danger at start
17
Moderate · FWI index
Average daily power
215MW
detected power per day, on average

Where it burned

2 May 2016
HOTSPOTS BY DAY 27 Apr3 May

How it evolved, day by day

27 Apr 2016 · 14 MW · 2 28 Apr 2016 · 168 MW · 22 29 Apr 2016 · 663 MW · 64 30 Apr 2016 · 257 MW · 54 1 May 2016 · 146 MW · 33 2 May 2016 · 39 MW · 21
27 Apr 28 Apr 29 Apr 30 Apr 1 May 2 May

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
67km/h · peak gust
33%lowest humidity

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 12.3 mm on 4 May.

This area had burned before

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

How big is it?

10 km
It burned the equivalent of 2.5% of the area of London (40 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 town

  1. Cintalapa where it started
    4,014 ha
    1.6 %

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)
25 Apr 35.1 °C 33 % 32 km/h 0.1 mm Moderate 17
26 Apr 33.6 °C 41 % 45 km/h 0.0 mm High 22
27 Apr 32.4 °C 47 % 61 km/h 0.0 mm High 25
28 Apr 34.5 °C 33 % 48 km/h 0.0 mm High 25
29 Apr 33.7 °C 33 % 60 km/h 0.0 mm High 29
30 Apr 31.3 °C 42 % 67 km/h 0.0 mm High 30
1 May 34.1 °C 33 % 40 km/h 0.0 mm High 25
2 May 35.0 °C 34 % 27 km/h 0.0 mm High 22
3 May 30.6 °C 59 % 39 km/h 2.1 mm Low 7
4 May after 27.6 °C 77 % 45 km/h 12.3 mm Very low 0

Before and after, from space

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

Before · 20 Apr 2016
After · 10 May 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 · 199Every 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 Cintalapa fire last?
GWIS (Copernicus) dates it between 27 April 2016 and 3 May 2016: 7 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 3,990 hectares (39.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Cintalapa (4,014 ha, 1.6 %).
What was the weather like?
During the fire the temperature reached 35.1 °C, humidity dropped to 33 % and gusts hit 67 km/h. The fire danger index (FWI) reached 30, class High.
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.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 199 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.

How we build fire pages: methodology ›

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.