Skip to content
worldfires
MX · Mexico · →

Palizada fire, April 2017 Palizada

Out · last detection 26 Apr 2017, 20:01 UTC

The fire started on 24 April 2017 in Palizada, Mexico, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,656 hectares from heat detections, spread across a single municipality.

It is the 98th largest in Campeche since 2016 (of 138 with a page). Number 317 in Mexico in 2017, of 375.

The power measured by the satellite is low (23.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
1,656ha
GWIS perimeter (Copernicus)
Duration
4days
24 Apr 2017 – 27 Apr 2017
Municipalities hit
1
municipalities
Started on
24 Apr
2017
Heat detections
45
in a single hotspot: 23 MW
Danger at start
12
Moderate · FWI index
Average daily power
129MW
detected power per day, on average

Where it burned

26 Apr 2017
HOTSPOTS BY DAY 24 Apr27 Apr

How it evolved, day by day

24 Apr 2017 · 109 MW · 9 25 Apr 2017 · 207 MW · 31 26 Apr 2017 · 72 MW · 5
24 Apr 25 Apr 26 Apr

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

42°high
37km/h · peak gust
29%lowest humidity

It had gone 2 days without rain (1 mm or more) when it started. Rain came after the fire: 3.8 mm on 1 May.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Palizada 30,798 inhabitants where it started
    1,664 ha
    0.8 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre 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)
24 Apr 33.1 °C 46 % 23 km/h 1.2 mm Moderate 12
25 Apr 39.2 °C 32 % 27 km/h 0.0 mm High 23
26 Apr 41.5 °C 29 % 32 km/h 0.0 mm High 31
27 Apr 39.4 °C 41 % 37 km/h 4.0 mm Moderate 14
28 Apr after 41.9 °C 32 % 34 km/h 0.0 mm High 29
29 Apr after 42.9 °C 34 % 45 km/h 0.0 mm High 32
30 Apr after 41.6 °C 32 % 38 km/h 0.0 mm High 33
1 May after 32.9 °C 57 % 35 km/h 3.8 mm Low 6

Before and after, from space

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

Before · 17 Apr 2017
After · 4 May 2017

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 · 45Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Mexico ›

Frequently asked questions

How long did the Palizada fire last?
GWIS (Copernicus) dates it between 24 April 2017 and 27 April 2017: 4 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,656 hectares (16.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Palizada (1,664 ha, 0.8 %).
What was the weather like?
During the fire the temperature reached 41.5 °C, humidity dropped to 29 % and gusts hit 37 km/h. The fire danger index (FWI) reached 31, 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

Satellite cross-check

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?

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. 45 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.

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.