Burned area
satellite only1,054ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 24 Jul 2017 – 27 Jul 2017
+− cross-check
No official record is matched to this page to compare it with.
CG · Republic of the Congo · –
Mayama fire, 24 July 2017 Mayama
Out · last detection 27 Jul 2017, 23:46 UTC
The fire started on 24 July 2017 in Mayama, Republic of the Congo, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,054 hectares from heat detections, spread across a single municipality.
It is the 177th largest in Pool since 2016 (of 202 with a page). Number 64 in Republic of the Congo in 2017, of 71.
The power measured by the satellite is low (7.5 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-26matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only4days
24 Jul 2017 to 27 Jul 2017: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 27 Jul 2017, 23:46 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 only24 Jul 2017
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 24 Jul 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only28
VIIRS detections at 375 m. Most intense hotspot: 7 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 24 Jul 2017 – 27 Jul 2017
+− 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 only55MW
Total radiative power on 27 July 2017; hotspots that day: 15.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 27 Jul 2017
+− 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
model12.2FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 47.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 24 Jul 2017, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
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
model29.1°C · 54% RH
High of 29.1 °C and minimum humidity of 54% on 27 July 2017; gusts of 31 km/h on 24 July 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 24 Jul 2017 – 27 Jul 2017
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
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
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logStart date: 25 July 2017 → 24 July 2017.
What was saved on 26 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 1,054 ha
- Dates
- 24 Jul 2017 – 27 Jul 2017
- Name
- Mvouti
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/mayama-2017-07-14?v=2026-10-26A 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
CSV for this fire mayama-2017-07-14.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-07-24 | 1 | 1 | 25.2 | 18.5 | 62 | 13.5 | 31 | 0 | 12.2 | moderado | 1 |
| 2017-07-25 | 2 | 14 | 26.9 | 18.5 | 54 | 13.2 | 29.5 | 0 | 14 | moderado | 1 |
| 2017-07-26 | 10 | 33 | 28.4 | 17.7 | 53 | 10.4 | 25.2 | 0 | 14 | moderado | 1 |
| 2017-07-27 | 15 | 55 | 29.1 | 17.9 | 54 | 7.4 | 27.7 | 0 | 13.2 | moderado | 1 |
| 2017-07-28 | 0 | 0 | 29 | 19.2 | 57 | 10 | 23.8 | 0.4 | 14.5 | moderado | 0 |
| 2017-07-29 | 0 | 0 | 22.5 | 19.8 | 75 | 11.9 | 26.6 | 0 | 10.7 | bajo | 0 |
| 2017-07-30 | 0 | 0 | 24.5 | 18.3 | 70 | 11 | 26.3 | 0 | 10.5 | bajo | 0 |
| 2017-07-31 | 0 | 0 | 24.6 | 18.6 | 63 | 12.8 | 29.9 | 0 | 11.9 | moderado | 0 |
| 2017-08-01 | 0 | 0 | 24.9 | 18.6 | 62 | 11 | 26.6 | 0 | 11.9 | moderado | 0 |
| 2017-08-02 | 0 | 0 | 26.9 | 18.3 | 59 | 14.3 | 30.2 | 0 | 14.3 | moderado | 0 |
| 2017-08-03 | 0 | 0 | 28.4 | 18.6 | 58 | 10.3 | 23.8 | 0 | 13.7 | moderado | 0 |
| 2017-08-04 | 0 | 0 | 25.2 | 19.5 | 66 | 12.5 | 28.8 | 0.6 | 11.8 | moderado | 0 |
| 2017-08-05 | 0 | 0 | 23.7 | 19.7 | 70 | 12.1 | 29.5 | 0 | 11.8 | moderado | 0 |
| 2017-08-06 | 0 | 0 | 26.8 | 18.6 | 62 | 10 | 23 | 0 | 12.1 | moderado | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 1,054ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 24 Jul 2017 – 27 Jul 2017
- Municipalities hit
- 1
- districts
- Started on
- 24 Jul
- 2017
- Heat detections
- 28
- in a single hotspot: 7 MW
- Danger at start
- 12
- Moderate · FWI index
- Average daily power
- 26MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
24 Jul27 Jul
27 Jul 2017
How it evolved, day by day
24 Jul
25 Jul
26 Jul
27 Jul
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
29°high
31km/h · peak gust
53%lowest humidity
It had gone 47 days without rain (1 mm or more) when it started.
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
-
Mayama where it started1,061 ha reached on 24 Jul0.1 %
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.
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 Jul | 25.2 °C | 62 % | 31 km/h | 0.0 mm | Moderate 12 |
| 25 Jul | 26.9 °C | 54 % | 30 km/h | 0.0 mm | Moderate 14 |
| 26 Jul | 28.4 °C | 53 % | 25 km/h | 0.0 mm | Moderate 14 |
| 27 Jul | 29.1 °C | 54 % | 28 km/h | 0.0 mm | Moderate 13 |
| 28 Jul after | 29.0 °C | 57 % | 24 km/h | 0.4 mm | Moderate 14 |
| 29 Jul after | 22.5 °C | 75 % | 27 km/h | 0.0 mm | Low 11 |
| 30 Jul after | 24.5 °C | 70 % | 26 km/h | 0.0 mm | Low 10 |
| 31 Jul after | 24.6 °C | 63 % | 30 km/h | 0.0 mm | Moderate 12 |
| 1 Aug after | 24.9 °C | 62 % | 27 km/h | 0.0 mm | Moderate 12 |
| 2 Aug after | 26.9 °C | 59 % | 30 km/h | 0.0 mm | Moderate 14 |
| 3 Aug after | 28.4 °C | 58 % | 24 km/h | 0.0 mm | Moderate 14 |
| 4 Aug after | 25.2 °C | 66 % | 29 km/h | 0.6 mm | Moderate 12 |
| 5 Aug after | 23.7 °C | 70 % | 30 km/h | 0.0 mm | Moderate 12 |
| 6 Aug after | 26.8 °C | 62 % | 23 km/h | 0.0 mm | Moderate 12 |
Its twins: fires that started in the same weather
It started with an FWI of 12.2, a minimum humidity of 62% and 47 days without rain. Fires in the area that started in weather like this since 2016: 18.
FWI at the start
12.2
Minimum humidity
62 %
Days without rain
47
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Mayama fire, 24 July 2017
1,054 ha
4 days
FWI 12.2
Min. humidity 62 %
Mayama fire, July 2016
1,279 ha
3 days
FWI 13.5
Min. humidity 62 %
17 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
Kindamba fire, August 2021
1,012 ha
2 days
FWI 14.3
Min. humidity 64 %
9 km away, in 2021
First rain (1 mm or more) after it ended: none in the following ten days.
Mayama fire, July 2020
1,339 ha
4 days
FWI 12.2
Min. humidity 59 %
35 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Sibiti fire, July 2020
1,143 ha
3 days
FWI 11.5
Min. humidity 62 %
209 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Djambala fire, July 2020
1,067 ha
1 day
FWI 10.8
Min. humidity 59 %
53 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 4 days
- median duration
- 1,148 ha
- median area
- 100 %
- went past 1,000 ha
- —
- rain at the end (median; 0 of 18 had it)
It burned an area similar to its twins (1,054 ha against a median of 1,148 ha) and lasted 4 days, against 4 days.
In none of them did 1 mm fall in the ten days after the end: they all went out without rain.
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
—first rain
—no rain in ten days
31km/h · max. gust
It was considered over on 27 Jul, and not even 1 mm fell in the following ten days: it went out without rain. None of its 18 twins had rain when they ended.
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.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 17 Jul 2017
After · 3 Aug 2017
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 · 28Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Mayama fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 24 July 2017 to 27 July 2017 (4 days). The perimeter dates it from 25 July 2017 to 27 July 2017.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,054 hectares (10.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mayama (1,061 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 29.1 °C, humidity dropped to 53 % and gusts hit 31 km/h. The fire danger index (FWI) reached 14, class Moderate.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Republic of the Congo (geoBoundaries ADM2). It is not an official report.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 18. Their median duration was 4 days and their median area 1,148 ha; 100 % went past 1,000 ha. In none of them did 1 mm fall in the ten days after the end: they all went out without rain.
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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 25 July 2017 → 24 July 2017.
RSS Changes to this page With cross-checks and a citable version
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 adjusted with the VIIRS detections inside the perimeter, which said 25 July 2017 to 27 July 2017. 28 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 (Map Library 2007, nombres de Wikidata) (Public Domain). 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.