Skip to content
worldfires
MX · Mexico · –

Casas Grandes fire, May 2019 Casas Grandes

Out · last detection 29 May 2019, 19:59 UTC

The fire started on 26 May 2019 in Casas Grandes, Mexico, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,551 hectares from heat detections, spread across a single municipality.

It is the 220th largest in Chihuahua since 2016 (of 229 with a page). Number 342 in Mexico in 2019, of 363.

The power measured by the satellite is low (29.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
1,551ha
GWIS perimeter (Copernicus)
Duration
4days
26 May 2019 – 29 May 2019
Municipalities hit
1
municipalities
Started on
26 May
2019
Heat detections
85
in a single hotspot: 29 MW
Danger at start
73
Very extreme · FWI index
Average daily power
145MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 26 May29 May
29 May 2019

How it evolved, day by day

26 May 2019 · 64 MW · 3 27 May 2019 · 222 MW · 21 28 May 2019 · 153 MW · 38 29 May 2019 · 140 MW · 23
26 May 27 May 28 May 29 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

23°high
91km/h · peak gust
12%lowest humidity

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

How big is it?

10 km
It burned the equivalent of 1% of the area of London (16 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. Casas Grandes where it started
    1,556 ha reached on 26 May
    0.4 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.

People and buildings inside the perimeter

GHSL 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

Official record

According to CONAFOR, this fire started on 26 May 2019 and burned 724 ha (the satellite measured 1,551 ha). The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.

CONAFOR (Comisión Nacional Forestal), estadística de incendios forestales en datos.gob.mx (CC BY 4.0). This is the agency’s consolidated statistic: it measures the area in its own way, which is why it can differ from the satellite.

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)

Started with Extreme FWI: 19 % of the area in Mexico Strong wind: 19 % of the area in Mexico

Day High Min. humidity Peak gust Rain Danger (FWI)
26 May 22.2 °C 19 % 91 km/h 0.1 mm Very extreme 73
27 May 23.0 °C 12 % 78 km/h 0.0 mm Very extreme 72
28 May 21.6 °C 13 % 65 km/h 0.0 mm Extreme 61
29 May 21.7 °C 14 % 46 km/h 0.0 mm Very high 49
30 May after 24.5 °C 14 % 48 km/h 0.0 mm Extreme 52
31 May after 27.0 °C 14 % 51 km/h 0.0 mm Very high 48
1 Jun after 27.2 °C 20 % 54 km/h 0.0 mm Extreme 55
2 Jun after 26.5 °C 20 % 58 km/h 0.0 mm Extreme 57
3 Jun after 25.5 °C 21 % 63 km/h 0.1 mm Extreme 56
4 Jun after 24.9 °C 26 % 63 km/h 0.2 mm Extreme 55
5 Jun after 25.1 °C 19 % 44 km/h 0.0 mm Very high 44
6 Jun after 27.8 °C 20 % 40 km/h 0.0 mm High 36
7 Jun after 28.3 °C 19 % 50 km/h 0.0 mm Very high 49
8 Jun after 27.1 °C 19 % 49 km/h 0.0 mm Extreme 55

Its twins: fires that started in the same weather

It started with an FWI of 72.7, a minimum humidity of 19% and 13 days without rain. Fires in the area that started in weather like this since 2016: 11.

FWI at the start 72.7
Minimum humidity 19 %
Days without rain 13
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Cuauhtémoc fire, May 2017
8,344 ha 7 days FWI 71.7 Min. humidity 21 % 200 km away, in 2017

First rain (1 mm or more) after it ended: none in the following ten days.

What happened to them

Fires in the area that started in similar weather: 11. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

—first rain
—no rain in ten days
91km/h · max. gust

It was considered over on 29 May, and not even 1 mm fell in the following ten days: it went out without rain.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 19 May 2019
After · 5 Jun 2019

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 · 85Every 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 Casas Grandes fire last?
GWIS (Copernicus) dates it between 26 May 2019 and 29 May 2019: 4 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,551 hectares (15.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Casas Grandes (1,556 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 23.0 °C, humidity dropped to 12 % and gusts hit 91 km/h. The fire danger index (FWI) reached 73, class Very extreme.
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 · Emergency number and official warnings

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

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. 85 Suomi-NPP VIIRS detections on those dates.
  • Compared with CONAFOR: 724 official ha against 1,551 ha of perimeter; similar, but with reservations.
  • Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

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.