Tubutama fire, March 2016
Tubutama, Oquitoa, Altar
Out · last detection 5 Mar 2016, 09:08 UTC
The fire started on 1 March 2016 in Tubutama, Mexico, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,502 hectares from heat detections, spread across 3 municipalities.
It is the 81th largest in Sonora since 2016 (of 82 with a page). Number 202 in Mexico in 2016, of 204.
The power measured by the satellite is low (9.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Burned area
with caveats
1,502ha
Perimeter published by GWIS (Copernicus).
This page1,502CONAFOR835
Source
GWIS (Copernicus)
Date
1 Mar 2016 – 5 Mar 2016
+− cross-check
CONAFOR: 835 ha (matched records: 1). Difference between the page and the official record: +79.9%. Matched on 15 November 2026. The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.
Duration by satellite
satellite only
5days
1 Mar 2016 to 5 Mar 2016: first and last day with fire on the page.
Source
GWIS (Copernicus) · NASA FIRMS · VIIRS
Date
last detection: 5 Mar 2016, 09:08 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only
1 Mar 2016
First day with fire seen by the satellites or the perimeter.
Source
GWIS (Copernicus) · NASA FIRMS · VIIRS
Date
1 Mar 2016
+− cross-check
The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.
Hotspots
satellite only
66
VIIRS detections at 375 m. Most intense hotspot: 9 MW.
Source
NASA FIRMS · VIIRS (Suomi NPP)
Date
1 Mar 2016 – 5 Mar 2016
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only
101MW
Total radiative power on 4 March 2016; hotspots that day: 32.
Source
NASA FIRMS · VIIRS (FRP)
Date
4 Mar 2016
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model
30.7FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 28.
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings ›
Weather during the fire
model
27.2°C · 8% RH
High of 27.2 °C and minimum humidity of 8% on 3 March 2016; gusts of 40 km/h on 5 March 2016.
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
ⓘThis page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
· reconstructedofficial
Matched with the official CONAFOR record
Nearby records with very different figures: 835 ha (records: 1).
A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
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 2015
Built-up area< 0.1ha
Residents< 20
Inside 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.
According to CONAFOR, this fire started on 2 March 2016 and burned 835 ha (the satellite measured 1,502 ha). The two figures differ a lot, so these may not be exactly the same fire: take them as nearby records.
TubutamaLas Granaditas2 March 2016835 ha· extinguished on 7 March 2016· cause: unknown
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)
It started with an FWI of 30.7, a minimum humidity of 11% and 28 days without rain. Fires in the area that started in weather like this since 2016: 14.
FWI at the start30.7
Minimum humidity11 %
Days without rain28
this firechosen twinsrest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Tubutama fire, March 2016
1,502 ha5 daysFWI 30.7Min. humidity 11 %
Altar Fire, February 2018
1,381 ha3 daysFWI 31.0Min. humidity 8 %72 km away, in 2018
First rain (1 mm or more) after it ended: 3.4 mm on 14 Feb.
Fires in the area that started in similar weather: 14. With fewer than 15 we give no figures: they would be more noise than signal.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
1.8 mmfirst rain
7 Mar2 days after it ended
40km/h · max. gust
It was considered over on 5 Mar, and on 7 Mar 1.8 mm fell. We do not know whether the rain or the firefighters put it out.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
Same area: fires that have already ended, less than 250 km from this one, since 2016.
Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
They are sorted by similarity, and the outlines of the first five are drawn.
Drag the line to compare the same ground before the fire and after it.
↔
Before · 23 Feb 2016
After · 12 Mar 2016
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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· 66Every satellite heat detection, one by one, with time, satellite, power and coordinates.›
⬇ Download CSVTimes in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and time
Satellite
FRP (MW)
Lat
Lon
Frequently asked questions
How long did the Tubutama fire last?
GWIS (Copernicus) dates it between 1 March 2016 and 5 March 2016: 5 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,502 hectares (15.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 3 municipalities: Tubutama (1,119 ha, 0.6 %); Oquitoa (293 ha, 0.3 %); Altar (97 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 27.2 °C, humidity dropped to 6 % and gusts hit 40 km/h. The fire danger index (FWI) reached 55, 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.
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 errorHow 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. 66 Suomi-NPP VIIRS detections on those dates.
Compared with CONAFOR: 835 official ha against 1,502 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.
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.