Zapopan fire, 2 May 2017 Zapopan
The fire started on 2 May 2017 in Zapopan, Mexico, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,612 hectares from heat detections, spread across a single municipality.
It is the 259th largest in Jalisco since 2016 (of 283 with a page). Number 326 in Mexico in 2017, of 374.
The power measured by the satellite is low (19.0 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 1,612ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 2 May 2017 – 2 May 2017
- Municipalities hit
- 1
- municipalities
- Started on
- 2 May
- 2017
- Heat detections
- 56
- in a single hotspot: 19 MW
- Danger at start
- 57
- Extreme · FWI index
- Average daily power
- 276MW
- detected power per day, on average
Where it burned
How it evolved, day by day
2 May 2017 · 276 MW · 56
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 36 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?
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
-
1,619 ha reached on 2 May1.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 2015Inside the perimeter there were about 1.8 hectares of built-up land and about 40 residents (GHSL 2015, 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 1 May 2017 and burned 924 ha (the satellite measured 1,612 ha). The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.
- Zapopan Pinar de la Venta 1 May 2017 924 ha · extinguished on 3 May 2017 · 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) |
|---|---|---|---|---|---|
| 2 May | 31.8 °C | 14 % | 48 km/h | 0.0 mm | Extreme 57 |
| 3 May after | 31.2 °C | 12 % | 45 km/h | 0.0 mm | Extreme 53 |
| 4 May after | 31.9 °C | 8 % | 35 km/h | 0.0 mm | Extreme 50 |
| 5 May after | 30.5 °C | 14 % | 44 km/h | 0.0 mm | Extreme 54 |
| 6 May after | 31.0 °C | 18 % | 52 km/h | 0.0 mm | Extreme 54 |
| 7 May after | 30.4 °C | 13 % | 44 km/h | 0.0 mm | Extreme 52 |
| 8 May after | 29.4 °C | 15 % | 45 km/h | 0.0 mm | Extreme 51 |
| 9 May after | 29.9 °C | 21 % | 47 km/h | 0.2 mm | Very high 48 |
| 10 May after | 32.0 °C | 19 % | 45 km/h | 0.0 mm | Very high 48 |
| 11 May after | 32.0 °C | 15 % | 42 km/h | 0.0 mm | Very high 47 |
| 12 May after | 32.3 °C | 15 % | 53 km/h | 0.0 mm | Extreme 50 |
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.
Detections table · 56Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,499 haZapopan1 April 2021 · 4 days · 6 km away
- 4,322 haTalaApril 2018 · 5 days · 16 km away
- 4,101 haSan Martín HidalgoApril 2017 · 6 days · 30 km away
- 4,059 haSan Cristóbal de la BarrancaApril 2019 · 11 days · 36 km away
- 14,819 haAhualulco de Mercado29 April 2017 · 20 days · 39 km away
- 4,030 haSan Cristóbal de la BarrancaApril 2016 · 12 days · 39 km away
Frequently asked questions
- How long did the Zapopan fire last?
- GWIS (Copernicus) dates it between 2 May 2017 and 2 May 2017: 1 day 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,612 hectares (16.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Zapopan (1,619 ha, 1.4 %).
- What was the weather like?
- During the fire the temperature reached 31.8 °C, humidity dropped to 14 % and gusts hit 48 km/h. The fire danger index (FWI) reached 57, class 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.
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 from the perimeter: the VIIRS detections inside it did not change them. 56 Suomi-NPP VIIRS detections on those dates.
- Compared with CONAFOR: 924 official ha against 1,612 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 2015, 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.