Muñoz fire, 7 February 2025 Muñoz
The fire started on 7 February 2025 in Muñoz, Venezuela, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,583 hectares from heat detections, spread across a single municipality.
It is the 823th largest in Apure since 2016 (of 919 with a page). Number 121 in Venezuela in 2025, of 139.
The power measured by the satellite is low (16.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…
Suggestions: Muñoz · 2024Muñoz · 2022Muñoz · 2020Muñoz · 2020
- Burnt area
- 1,583ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 7 Feb 2025 – 10 Feb 2025
- Municipalities hit
- 1
- municipalities
- Started on
- 7 Feb
- 2025
- Heat detections
- 37
- in a single hotspot: 16 MW
- Danger at start
- 30
- High · FWI index
- Average daily power
- 55MW
- 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 7 days without rain (1 mm or more) when it started.
This area had burned before
99% of the perimeter overlaps earlier fires recorded since 2016: 152 ha in 2019, 983 ha in 2020, 1,227 ha in 2022, 1,411 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 1,560 ha that had burned before.
- 1,319 ha Muñoz fire, January 2024 3,157 ha in total; the hectares shown are those it shares with this fire
- 887 ha Muñoz fire, March 2022 2,079 ha in total; the hectares shown are those it shares with this fire
- 824 ha Muñoz fire, March 2020 2,247 ha in total; the hectares shown are those it shares with this fire
- 158 ha Muñoz fire, March 2020 4,051 ha in total; the hectares shown are those it shares with this fire
- 152 ha Muñoz fire, February 2019 3,022 ha in total; the hectares shown are those it shares with this fire
- 92 ha Muñoz fire, March 2024 2,567 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,593 ha reached on 7 Feb0.2 %
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) |
|---|---|---|---|---|---|
| 7 Feb | 36.2 °C | 30 % | 40 km/h | 0.0 mm | High 30 |
| 8 Feb | 35.5 °C | 38 % | 40 km/h | 0.1 mm | High 29 |
| 9 Feb | 36.1 °C | 34 % | 40 km/h | 0.0 mm | High 32 |
| 10 Feb | 35.1 °C | 37 % | 50 km/h | 0.0 mm | High 34 |
| 11 Feb after | 36.8 °C | 28 % | 44 km/h | 0.0 mm | High 36 |
| 12 Feb after | 35.8 °C | 35 % | 44 km/h | 0.0 mm | High 36 |
| 13 Feb after | 37.0 °C | 27 % | 42 km/h | 0.0 mm | High 37 |
| 14 Feb after | 37.2 °C | 30 % | 43 km/h | 0.0 mm | High 36 |
| 15 Feb after | 36.8 °C | 26 % | 41 km/h | 0.0 mm | High 37 |
| 16 Feb after | 36.6 °C | 31 % | 41 km/h | 0.0 mm | High 37 |
| 17 Feb after | 37.0 °C | 25 % | 41 km/h | 0.0 mm | Very high 38 |
| 18 Feb after | 36.6 °C | 33 % | 44 km/h | 0.0 mm | Very high 41 |
| 19 Feb after | 35.4 °C | 39 % | 38 km/h | 0.0 mm | High 34 |
| 20 Feb after | 35.5 °C | 37 % | 39 km/h | 0.0 mm | High 34 |
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 9 February 2025 the air beside the fire reached 21 µg/m³ of PM2.5, but no daily average passed the WHO 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 · 37Every 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 Muñoz fire last?
- GWIS (Copernicus) dates it between 7 February 2025 and 10 February 2025: 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,583 hectares (15.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Muñoz (1,593 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 36.2 °C, humidity dropped to 30 % and gusts hit 50 km/h. The fire danger index (FWI) reached 34, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Venezuela (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
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. 37 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 (Open Data Commons Open Database License 1.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.