Morondava fire, July 2024 Morondava, Mahabo
The fire started on 29 July 2024 in Morondava, Madagascar, and satellites saw it burning for 16 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,617 hectares from heat detections, spread across 2 municipalities.
It is the 50th largest in Menabe since 2016 (of 98 with a page). Number 25 in Madagascar in 2024, of 54.
Compare with…
- Burnt area
- 2,617ha
- GWIS perimeter (Copernicus)
- Duration
- 16days
- 29 Jul 2024 – 13 Aug 2024
- Municipalities hit
- 2
- districts
- Started on
- 29 Jul
- 2024
- Heat detections
- 141
- in a single hotspot: 174 MW
- Danger at start
- 37
- High · FWI index
- Average daily power
- 151MW
- 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 more than two months without rain (1 mm or more) when it started.
This area had burned before
97% of the perimeter overlaps earlier fires recorded since 2016: 42 ha in 2016, 1,072 ha in 2017, 2,483 ha in 2018, 284 ha in 2019, 2,529 ha in 2020, 3,102 ha in 2021, 508 ha in 2022, 1,337 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 2,539 ha that had burned before.
- 2,272 ha Morondava fire, October 2018 5,771 ha in total; the hectares shown are those it shares with this fire
- 1,687 ha Morondava fire, October 2021 2,354 ha in total; the hectares shown are those it shares with this fire
- 1,305 ha Mahabo fire, September 2020 6,536 ha in total; the hectares shown are those it shares with this fire
- 1,203 ha Morondava fire, June 2023 2,165 ha in total; the hectares shown are those it shares with this fire
- 874 ha Morondava fire, June 2021 2,395 ha in total; the hectares shown are those it shares with this fire
- 542 ha Mahabo fire, June 2021 2,489 ha in total; the hectares shown are those it shares with this fire
- 464 ha Mahabo fire, October 2017 2,123 ha in total; the hectares shown are those it shares with this fire
- 54 ha Morondava fire, October 2019 2,408 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
-
Morondava where it started2,264 ha reached on 30 Jul0.4 %
-
359 ha reached on 30 Jul0.0 %
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 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
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
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) |
|---|---|---|---|---|---|
| 29 Jul | 32.4 °C | 25 % | 30 km/h | 0.0 mm | High 37 |
| 30 Jul | 34.2 °C | 17 % | 24 km/h | 0.0 mm | Very high 42 |
| 31 Jul | 33.4 °C | 14 % | 25 km/h | 0.0 mm | Very high 45 |
| 1 Aug | 34.2 °C | 18 % | 21 km/h | 0.0 mm | Very high 44 |
| 2 Aug | 33.8 °C | 16 % | 23 km/h | 0.0 mm | Very high 45 |
| 3 Aug | 32.6 °C | 29 % | 30 km/h | 0.0 mm | Very high 40 |
| 4 Aug | 32.3 °C | 23 % | 26 km/h | 0.0 mm | Very high 39 |
| 5 Aug | 33.6 °C | 22 % | 29 km/h | 0.0 mm | Very high 40 |
| 6 Aug | 32.8 °C | 21 % | 27 km/h | 0.0 mm | Very high 40 |
| 7 Aug | 34.9 °C | 19 % | 22 km/h | 0.0 mm | Very high 41 |
| 8 Aug | 32.8 °C | 31 % | 32 km/h | 0.0 mm | Very high 39 |
| 9 Aug | 33.5 °C | 37 % | 33 km/h | 0.0 mm | High 37 |
| 10 Aug | 35.1 °C | 25 % | 24 km/h | 0.0 mm | High 35 |
| 11 Aug | 34.2 °C | 30 % | 29 km/h | 0.0 mm | Very high 38 |
| 12 Aug | 34.4 °C | 29 % | 29 km/h | 0.0 mm | Very high 39 |
| 13 Aug | 36.0 °C | 20 % | 24 km/h | 0.0 mm | Very high 41 |
| 14 Aug after | 33.8 °C | 30 % | 39 km/h | 0.0 mm | Very high 42 |
| 15 Aug after | 35.0 °C | 20 % | 32 km/h | 0.0 mm | Very high 41 |
| 16 Aug after | 34.3 °C | 21 % | 34 km/h | 0.0 mm | Very high 45 |
| 17 Aug after | 34.4 °C | 21 % | 28 km/h | 0.0 mm | Very high 42 |
| 18 Aug after | 34.4 °C | 22 % | 32 km/h | 0.0 mm | Very high 42 |
| 19 Aug after | 34.8 °C | 20 % | 32 km/h | 0.0 mm | Very high 43 |
| 20 Aug after | 33.6 °C | 19 % | 33 km/h | 0.0 mm | Very high 45 |
| 21 Aug after | 33.7 °C | 17 % | 38 km/h | 0.0 mm | Very high 47 |
| 22 Aug after | 33.2 °C | 24 % | 37 km/h | 0.0 mm | Very high 47 |
| 23 Aug after | 32.8 °C | 19 % | 37 km/h | 0.0 mm | Very high 47 |
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 2 August 2024 the air beside the fire reached 38 µg/m³ of PM2.5. That day averaged 19: 1.3 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 · 141Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 5,771 haMorondava17 October 2018 · 15 days · 1 km away
- 6,536 haMahabo22 September 2020 · 40 days · 4 km away
- 10,941 haMahabo8 October 2016 · 27 days · 8 km away
- 7,808 haMorondavaAugust 2026 · 11 days · 13 km away
- 6,286 haBelo Sur Tsiribihina4 October 2017 · 20 days · 22 km away
- 13,063 haBelo Sur Tsiribihina13 October 2018 · 16 days · 26 km away
Frequently asked questions
- How long did the Morondava fire last?
- GWIS (Copernicus) dates it between 29 July 2024 and 13 August 2024: 16 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,617 hectares (26.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Morondava (2,264 ha, 0.4 %); Mahabo (359 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 36.0 °C, humidity dropped to 14 % and gusts hit 33 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 Madagascar (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.
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. 141 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.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 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 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.