Silacayoápam fire, March 2017 Silacayoápam, San Francisco Tlapancingo
The fire started on 27 March 2017 in Silacayoápam, Mexico, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,733 hectares from heat detections, spread across 2 municipalities.
It is the 71th largest in Oaxaca since 2016 (of 204 with a page). Number 148 in Mexico in 2017, of 374.
The power measured by the satellite is low (19.4 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
- 2,733ha
- GWIS perimeter (Copernicus)
- Duration
- 7days
- 27 Mar 2017 – 2 Apr 2017
- Municipalities hit
- 2
- municipalities
- Started on
- 27 Mar
- 2017
- Heat detections
- 193
- in a single hotspot: 19 MW
- Danger at start
- 28
- High · FWI index
- Average daily power
- 100MW
- 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 11 days without rain (1 mm or more) when it started. Rain came after the fire: 1.2 mm on 7 Apr.
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
-
Silacayoápam where it started2,496 ha reached on 27 Mar5.8 %
-
250 ha reached on 28 Mar2.5 %
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 was no noticeable built-up land and almost nobody lived there (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 26 March 2017 and burned 1,700 ha (the satellite measured 2,733 ha). The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.
- Silacayoápam San Jerónimo Progreso 26 March 2017 1,700 ha · extinguished on 1 April 2017 · cause: negligence
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) |
|---|---|---|---|---|---|
| 27 Mar | 28.3 °C | 20 % | 37 km/h | 0.2 mm | High 28 |
| 28 Mar | 25.5 °C | 31 % | 42 km/h | 1.3 mm | Moderate 15 |
| 29 Mar | 27.1 °C | 23 % | 33 km/h | 0.3 mm | High 24 |
| 30 Mar | 27.6 °C | 18 % | 41 km/h | 0.0 mm | High 27 |
| 31 Mar | 26.4 °C | 21 % | 45 km/h | 0.0 mm | High 31 |
| 1 Apr | 27.4 °C | 13 % | 51 km/h | 0.0 mm | High 38 |
| 2 Apr | 26.9 °C | 16 % | 44 km/h | 0.0 mm | High 35 |
| 3 Apr after | 27.3 °C | 21 % | 29 km/h | 0.0 mm | High 32 |
| 4 Apr after | 28.3 °C | 21 % | 38 km/h | 0.0 mm | High 35 |
| 5 Apr after | 29.0 °C | 13 % | 33 km/h | 0.0 mm | High 34 |
| 6 Apr after | 27.5 °C | 28 % | 30 km/h | 0.3 mm | High 30 |
| 7 Apr after | 28.2 °C | 22 % | 43 km/h | 1.2 mm | High 25 |
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 · 193Every 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 Silacayoápam fire last?
- GWIS (Copernicus) dates it between 27 March 2017 and 2 April 2017: 7 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 2,733 hectares (27.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Silacayoápam (2,496 ha, 5.8 %); San Francisco Tlapancingo (250 ha, 2.5 %).
- What was the weather like?
- During the fire the temperature reached 28.3 °C, humidity dropped to 13 % and gusts hit 51 km/h. The fire danger index (FWI) reached 38, 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 from the perimeter: the VIIRS detections inside it did not change them. 193 Suomi-NPP VIIRS detections on those dates.
- Compared with CONAFOR: 1,700 official ha against 2,733 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.