Tlatlaya fire, June 2023 Tlalchapa, Tlatlaya
The fire started on 3 June 2023 in Tlatlaya, Mexico, and satellites saw it burning for 14 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,980 hectares from heat detections, spread across 2 municipalities.
It is the 21th largest in México since 2016 (of 27 with a page). Number 183 in Mexico in 2023, of 285.
Compare with…
- Burnt area
- 1,980ha
- GWIS perimeter (Copernicus)
- Duration
- 14days
- 3 Jun 2023 – 16 Jun 2023
- Municipalities hit
- 2
- municipalities
- Started on
- 3 Jun
- 2023
- Heat detections
- 93
- in a single hotspot: 45 MW
- Danger at start
- 35
- High · FWI index
- Average daily power
- 26MW
- 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 5 days without rain (1 mm or more) when it started. Rain came after the fire: 2.2 mm on 24 Jun.
This area had burned before
100% of the perimeter overlaps earlier fires recorded since 2016: 157 ha in 2016, 2,036 ha in 2018, 1,864 ha in 2020. Part of it burned more than once, so the yearly figures add up to more than the 1,983 ha that had burned before.
- 2,036 ha Tlalchapa fire, April 2018 10,623 ha in total; the hectares shown are those it shares with this fire
- 1,710 ha Tlalchapa fire, April 2020 3,219 ha in total; the hectares shown are those it shares with this fire
- 154 ha Tlatlaya fire, May 2020 12,344 ha in total; the hectares shown are those it shares with this fire
- 112 ha Tlalchapa fire, March 2016 2,168 ha in total; the hectares shown are those it shares with this fire
- 45 ha Tlalchapa fire, April 2016 3,255 ha in total; the hectares shown are those it shares with this fire
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,545 ha3.3 %
-
Tlatlaya where it started446 ha0.6 %
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.
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) |
|---|---|---|---|---|---|
| 3 Jun | 37.1 °C | 16 % | 28 km/h | 0.0 mm | High 35 |
| 4 Jun | 35.2 °C | 19 % | 30 km/h | 0.0 mm | High 37 |
| 5 Jun | 34.7 °C | 22 % | 38 km/h | 0.0 mm | Very high 39 |
| 6 Jun | 33.6 °C | 23 % | 32 km/h | 1.9 mm | High 23 |
| 7 Jun | 32.9 °C | 36 % | 36 km/h | 3.3 mm | Low 10 |
| 8 Jun | 34.6 °C | 31 % | 29 km/h | 0.0 mm | High 22 |
| 9 Jun | 36.4 °C | 16 % | 34 km/h | 0.0 mm | High 34 |
| 10 Jun | 35.8 °C | 23 % | 28 km/h | 0.0 mm | High 35 |
| 11 Jun | 35.9 °C | 23 % | 38 km/h | 0.0 mm | Very high 40 |
| 12 Jun | 38.0 °C | 16 % | 30 km/h | 0.0 mm | Very high 38 |
| 13 Jun | 37.8 °C | 18 % | 37 km/h | 0.0 mm | Very high 42 |
| 14 Jun | 36.7 °C | 17 % | 38 km/h | 0.0 mm | Very high 40 |
| 15 Jun | 36.2 °C | 21 % | 35 km/h | 0.0 mm | Very high 45 |
| 16 Jun | 36.1 °C | 27 % | 31 km/h | 0.0 mm | High 37 |
| 17 Jun after | 36.0 °C | 24 % | 33 km/h | 0.0 mm | Very high 39 |
| 18 Jun after | 35.7 °C | 24 % | 34 km/h | 0.0 mm | Very high 39 |
| 19 Jun after | 36.2 °C | 26 % | 35 km/h | 0.0 mm | Very high 40 |
| 20 Jun after | 35.8 °C | 28 % | 35 km/h | 0.0 mm | Very high 39 |
| 21 Jun after | 37.1 °C | 21 % | 38 km/h | 0.0 mm | Very high 41 |
| 22 Jun after | 36.8 °C | 20 % | 31 km/h | 0.0 mm | High 38 |
| 23 Jun after | 35.5 °C | 24 % | 37 km/h | 0.1 mm | Very high 41 |
| 24 Jun after | 34.2 °C | 20 % | 36 km/h | 2.2 mm | High 28 |
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 4 June 2023 the air beside the fire reached 28 µg/m³ of PM2.5. That day averaged 19: 1.2 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 · 93Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Tlatlaya fire last?
- GWIS (Copernicus) dates it between 3 June 2023 and 16 June 2023: 14 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,980 hectares (19.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Tlalchapa (1,545 ha, 3.3 %); Tlatlaya (446 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 38.0 °C, humidity dropped to 16 % and gusts hit 38 km/h. The fire danger index (FWI) reached 45, class Very 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 from the perimeter: the VIIRS detections inside it did not change them. 93 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.
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.