How long did the Cabo Corrientes fire last?

GWIS (Copernicus) dates it between 30 April 2023 and 12 May 2023: 13 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 6,135 hectares (61.4 km²). It is an estimate: official national figures may differ.

Which municipalities burned?

The fire only entered Cabo Corrientes (6,166 ha, 4.0 %).

What was the weather like?

During the fire the temperature reached 29.1 °C, humidity dropped to 15 % and gusts hit 39 km/h. The fire danger index (FWI) reached 34, 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.

MX · Mexico · 2023-04-30 → 2023-05-12

Cabo Corrientes fire, April 2023 Cabo Corrientes

Out · last detection 12 May 2023, 09:11 UTC

The fire started on 30 April 2023 in Cabo Corrientes, Mexico, and satellites saw it burning for 13 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,135 hectares from heat detections, spread across a single municipality.

It is the 27th largest in Jalisco since 2016 (of 283 with a page). Number 30 in Mexico in 2023, of 285.

Compare with…

Suggestions: Talpa de Allende · 2023 Talpa de Allende · 2020 Talpa de Allende · 2023 Tomatlán · 2025

Burnt area: 6,135ha; GWIS perimeter (Copernicus)
Duration: 13days; 30 Apr 2023 – 12 May 2023
Municipalities hit: 1; municipalities
Started on: 30 Apr; 2023
Heat detections: 342; in a single hotspot: 123 MW
Danger at start: 25; High · FWI index
Average daily power: 241MW; detected power per day, on average

HOTSPOTS BY DAY 30 Apr12 May

Play back 12 May 2023

How it evolved, day by day

30 Apr 2 May 4 May 6 May 8 May 10 May 12 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

29°high

39km/h · peak gust

15%lowest humidity

It had gone more than two months 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?

It burned the equivalent of 3.9% of the area of London (61 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

Cabo Corrientes where it started

6,166 ha reached on 30 Apr

4.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 2025

Built-up area< 0.1 ha

Residents< 20

Inside 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

Official record

According to CONAFOR, this fire started on 30 April 2023 and burned 3,494 ha (the satellite measured 6,135 ha). The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.

Cabo Corrientes La Cruz De Fierro 30 April 2023 3,494 ha · extinguished on 10 May 2023 · cause: arson

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)

Day	High	Min. humidity	Peak gust	Rain	Danger (FWI)
30 Apr	24.4 °C	45 %	39 km/h	0.0 mm	High 25
1 May	24.6 °C	23 %	36 km/h	0.0 mm	High 28
2 May	26.3 °C	15 %	32 km/h	0.0 mm	High 34
3 May	26.3 °C	29 %	32 km/h	0.0 mm	High 32
4 May	26.5 °C	34 %	32 km/h	0.0 mm	High 30
5 May	27.8 °C	38 %	32 km/h	0.0 mm	High 28
6 May	27.9 °C	37 %	32 km/h	0.0 mm	High 29
7 May	28.0 °C	35 %	37 km/h	0.0 mm	High 28
8 May	27.7 °C	36 %	38 km/h	0.0 mm	High 30
9 May	27.8 °C	37 %	37 km/h	0.0 mm	High 30
10 May	29.1 °C	29 %	38 km/h	0.0 mm	High 30
11 May	28.3 °C	33 %	36 km/h	0.0 mm	High 30
12 May	26.8 °C	33 %	32 km/h	0.0 mm	High 30
13 May after	26.3 °C	35 %	37 km/h	0.0 mm	High 30
14 May after	26.9 °C	30 %	34 km/h	0.0 mm	High 31
15 May after	27.1 °C	37 %	31 km/h	0.0 mm	High 28
16 May after	27.6 °C	41 %	40 km/h	0.8 mm	High 22
17 May after	27.2 °C	40 %	36 km/h	0.5 mm	High 24
18 May after	26.9 °C	43 %	35 km/h	0.1 mm	High 23
19 May after	27.4 °C	39 %	29 km/h	0.0 mm	High 24
20 May after	26.3 °C	43 %	17 km/h	0.0 mm	High 23
21 May after	29.8 °C	35 %	34 km/h	0.0 mm	High 27
22 May after	27.4 °C	41 %	35 km/h	0.3 mm	High 28

Before and after, from space

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

↔

Before · 23 Apr 2023

After · 19 May 2023

Before After

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 · Copernicus

On 4 May 2023 the air beside the fire reached 169 µg/m³ of PM2.5. That day averaged 110: 7.3 times the WHO daily guideline (15).

PM2.5 peak169 µg/m³

Days over the guideline10 days

PM10242 µg/m³

Optical depth1.23

WHO 15

282930123456789101112131415

Good Fair Moderate Poor Very poor Extremely poor

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 · 342Every 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 time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in Mexico ›

Frequently asked questions

How long did the Cabo Corrientes fire last?: GWIS (Copernicus) dates it between 30 April 2023 and 12 May 2023: 13 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 6,135 hectares (61.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?: The fire only entered Cabo Corrientes (6,166 ha, 4.0 %).
What was the weather like?: During the fire the temperature reached 29.1 °C, humidity dropped to 15 % and gusts hit 39 km/h. The fire danger index (FWI) reached 34, 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 ›

CONAFOR · Comisión Nacional Forestal ↗
CENAPRED ↗

Satellite cross-check

NASA FIRMS ↗
GWIS · Copernicus ↗

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.

RSS Changes to this page

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?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

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. 342 Suomi-NPP VIIRS detections on those dates.
Compared with CONAFOR: 3,494 official ha against 6,135 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 2025, 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.

Where it burned