Cabo Corrientes fire, May 2026 Cabo Corrientes, Talpa de Allende
The fire started on 20 May 2026 in Cabo Corrientes, Mexico, and satellites saw it burning for 11 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,544 hectares from heat detections, spread across 2 municipalities.
It is the 121th largest in Jalisco since 2016 (of 283 with a page). Number 48 in Mexico in 2026, of 145.
Compare with…
- Burnt area
- 2,544ha
- GWIS perimeter (Copernicus)
- Duration
- 11days
- 20 May 2026 – 30 May 2026
- Municipalities hit
- 2
- municipalities
- Started on
- 20 May
- 2026
- Heat detections
- 147
- in a single hotspot: 48 MW
- Danger at start
- 16
- Moderate · FWI index
- Average daily power
- 81MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 3 days without rain (1 mm or more) when it started. Rain came after the fire: 2.9 mm on 31 May.
This area had burned before
23% of the perimeter overlaps earlier fires recorded since 2016: 592 ha in 2022.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Cabo Corrientes where it started2,530 ha reached on 20 May1.6 %
-
24 ha0.0 %
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 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
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
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 May | 30.7 °C | 55 % | 30 km/h | 0.1 mm | Moderate 16 |
| 22 May | 31.1 °C | 53 % | 35 km/h | 0.8 mm | Moderate 15 |
| 23 May | 30.8 °C | 46 % | 33 km/h | 0.0 mm | Moderate 18 |
| 24 May | 31.9 °C | 43 % | 31 km/h | 0.0 mm | Moderate 20 |
| 25 May | 32.3 °C | 43 % | 35 km/h | 0.0 mm | High 22 |
| 26 May | 31.1 °C | 53 % | 35 km/h | 0.0 mm | High 21 |
| 27 May | 31.4 °C | 52 % | 37 km/h | 0.3 mm | High 21 |
| 28 May | 31.6 °C | 51 % | 35 km/h | 0.3 mm | Moderate 21 |
| 29 May | 30.9 °C | 49 % | 37 km/h | 0.0 mm | High 23 |
| 30 May | 31.5 °C | 45 % | 35 km/h | 0.0 mm | High 22 |
| 31 May after | 30.3 °C | 53 % | 34 km/h | 2.9 mm | Low 6 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 19 May 2026 the air beside the fire reached 79 µg/m³ of PM2.5. That day averaged 51: 3.4 times the WHO daily guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 147Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 11,252 haTalpa de AllendeMarch 2023 · 37 days · 10 km away
- 7,150 haTomatlánApril 2026 · 50 days · 10 km away
- 6,135 haCabo CorrientesApril 2023 · 13 days · 12 km away
- 14,196 haTalpa de Allende7 May 2019 · 25 days · 18 km away
- 12,266 haTalpa de Allende19 April 2023 · 26 days · 19 km away
- 7,719 haTomatlánApril 2025 · 15 days · 21 km away
Frequently asked questions
- How long did the Cabo Corrientes fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 20 May 2026 to 30 May 2026 (11 days). The perimeter dates it from 21 May 2026 to 30 May 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 2,544 hectares (25.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Cabo Corrientes (2,530 ha, 1.6 %); Talpa de Allende (24 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 32.3 °C, humidity dropped to 43 % and gusts hit 37 km/h. The fire danger index (FWI) reached 23, 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 · 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.
No changes 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
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 21 May 2026 to 30 May 2026. 147 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.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
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.