Burned area
satellite only8,029ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 2 Feb 2020 – 29 Feb 2020
+− cross-check
No official record is matched to this page to compare it with.
CD · Democratic Republic of the Congo · –
Yakoma fire, 2 February 2020 Yakoma
Out · last detection 29 Feb 2020, 11:48 UTC
The fire started on 2 February 2020 in Yakoma, Democratic Republic of the Congo, and satellites saw it burning for 28 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,029 hectares from heat detections, spread across a single municipality.
It is the 4th largest in Nord-Ubangi since 2016 (of 10 with a page). Number 61 in Democratic Republic of the Congo in 2020, of 165.
Use this data
Compare with…
Suggestions: Bumba · 2024Aketi · 2024Yakoma · 2026Yakoma · 2020
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 only28days
2 Feb 2020 to 29 Feb 2020: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 29 Feb 2020, 11:48 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 only2 Feb 2020
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 2 Feb 2020
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only650
VIIRS detections at 375 m. Most intense hotspot: 134 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 2 Feb 2020 – 29 Feb 2020
+− 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 only2,057MW
Total radiative power on 14 February 2020; hotspots that day: 81.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 14 Feb 2020
+− 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
model18.5FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 0.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 2 Feb 2020, 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
model38.2°C · 21% RH
High of 38.2 °C and minimum humidity of 21% on 22 February 2020; gusts of 45 km/h on 7 February 2020.
- Source
- weather model at the fire’s grid cell
- Date
- 2 Feb 2020 – 29 Feb 2020
- 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.
Living inside
model≈ 100people
Estimated residents inside the perimeter and 0.74 ha of built-up area (100 m grid, epoch 2020).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
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
-
logLast day with fire: 23 February 2020 → 29 February 2020.
-
logStart date: 5 February 2020 → 2 February 2020.
-
· reconstructed GHSLPopulation and built-up area computed
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
- 8,029 ha
- Dates
- 2 Feb 2020 – 29 Feb 2020
- Name
- Yakoma
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/yakoma-2020-02?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 yakoma-2020-02.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020-02-02 | 7 | 63 | 33.3 | 23.4 | 41 | 9.9 | 28.8 | 0 | 18.5 | moderado | 1 |
| 2020-02-03 | 4 | 21 | 33.9 | 23.2 | 41 | 9.4 | 22.3 | 5 | 25.1 | alto | 1 |
| 2020-02-04 | 0 | 0 | 33.4 | 22.3 | 41 | 13 | 31.3 | 0 | 5.6 | bajo | 1 |
| 2020-02-05 | 1 | 7 | 31.9 | 22.1 | 49 | 11.5 | 26.3 | 0.6 | 15.5 | moderado | 1 |
| 2020-02-06 | 0 | 0 | 33.2 | 22.5 | 41 | 10.8 | 25.2 | 0 | 21.8 | alto | 1 |
| 2020-02-07 | 29 | 483 | 36.3 | 23 | 28 | 15.1 | 45 | 0 | 38.6 | muy_alto | 1 |
| 2020-02-08 | 14 | 78 | 36.9 | 23.7 | 28 | 12.5 | 34.6 | 0 | 36.8 | alto | 1 |
| 2020-02-09 | 0 | 0 | 34.9 | 23.2 | 33 | 11.5 | 25.9 | 0 | 31.8 | alto | 1 |
| 2020-02-10 | 11 | 76 | 35.9 | 23.1 | 27 | 8.9 | 30.2 | 0 | 32.2 | alto | 1 |
| 2020-02-11 | 76 | 452 | 36.1 | 21.2 | 22 | 10 | 24.1 | 0 | 36.9 | alto | 1 |
| 2020-02-12 | 33 | 405 | 34.1 | 22.3 | 31 | 11.4 | 23.8 | 0 | 29.6 | alto | 1 |
| 2020-02-13 | 38 | 227 | 35.6 | 19.7 | 21 | 9.7 | 29.5 | 0 | 40.3 | muy_alto | 1 |
| 2020-02-14 | 81 | 2,057 | 37.6 | 21.1 | 14 | 11 | 29.9 | 0 | 50.8 | extremo | 1 |
| 2020-02-15 | 72 | 107 | 36.8 | 20.3 | 23 | 12.8 | 22 | 0 | 43.3 | muy_alto | 1 |
| 2020-02-16 | 8 | 48 | 38.1 | 22.5 | 26 | 11 | 37.4 | 0 | 47.7 | muy_alto | 1 |
| 2020-02-17 | 9 | 103 | 36.7 | 23.8 | 37 | 10.9 | 44.6 | 1.5 | 31 | alto | 1 |
| 2020-02-18 | 0 | 0 | 28.3 | 22.9 | 71 | 11.2 | 34.9 | 17.7 | 3.8 | muy_bajo | 1 |
| 2020-02-19 | 4 | 76 | 32.8 | 22.1 | 49 | 8.1 | 25.9 | 3.5 | 1 | muy_bajo | 1 |
| 2020-02-20 | 1 | 1 | 33.4 | 23.2 | 50 | 9 | 31 | 2.9 | 3.4 | muy_bajo | 1 |
| 2020-02-21 | 40 | 357 | 35.5 | 23.3 | 37 | 10.9 | 36.4 | 0 | 10.6 | bajo | 1 |
| 2020-02-22 | 51 | 531 | 38.2 | 22.9 | 21 | 11.2 | 30.2 | 0 | 30.2 | alto | 1 |
| 2020-02-23 | 100 | 678 | 37.8 | 22.5 | 20 | 11.2 | 30.6 | 0 | 36.2 | alto | 1 |
| 2020-02-24 | 0 | 0 | 34.9 | 24.7 | 38 | 12 | 26.3 | 0 | 23.7 | alto | 1 |
| 2020-02-25 | 10 | 111 | 34.8 | 24.9 | 42 | 11.2 | 23 | 3 | 21.7 | alto | 1 |
| 2020-02-26 | 5 | 7 | 32.8 | 23.9 | 43 | 10.1 | 23.8 | 0.5 | 5.3 | bajo | 1 |
| 2020-02-27 | 51 | 222 | 36.8 | 23.2 | 32 | 11.8 | 22.3 | 0 | 19.2 | moderado | 1 |
| 2020-02-28 | 0 | 0 | 34 | 24.4 | 45 | 13 | 32.8 | 0 | 16.6 | moderado | 1 |
| 2020-02-29 | 5 | 33 | 36 | 24.2 | 38 | 11.3 | 27.4 | 0.3 | 20.4 | moderado | 1 |
| 2020-03-01 | 0 | 0 | 35.5 | 24.2 | 39 | 13.6 | 31.3 | 1.4 | 20.2 | 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), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 8,029ha
- GWIS perimeter (Copernicus)
- Duration
- 28days
- 2 Feb 2020 – 29 Feb 2020
- Municipalities hit
- 1
- territories
- Started on
- 2 Feb
- 2020
- Heat detections
- 650
- in a single hotspot: 134 MW
- Danger at start
- 18
- Moderate · FWI index
- Average daily power
- 279MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
2 Feb29 Feb
29 Feb 2020
How it evolved, day by day
2 Feb
10 Feb
14 Feb
21 Feb
27 Feb
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
38°high
45km/h · peak gust
14%lowest humidity
It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 1.4 mm on 1 Mar.
This area had burned before
15% of the perimeter overlaps earlier fires recorded since 2016: 36 ha in 2016, 1,168 ha in 2018.
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
-
Yakoma where it started8,080 ha reached on 2 Feb0.5 %
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 2020Built-up area0.74 ha
Residents≈ 100
Inside the perimeter there were about 0.74 hectares of built-up land and about 100 residents (GHSL 2020, 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.
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) |
|---|---|---|---|---|---|
| 2 Feb | 33.3 °C | 41 % | 29 km/h | 0.0 mm | Moderate 18 |
| 3 Feb | 33.9 °C | 41 % | 22 km/h | 5.0 mm | High 25 |
| 4 Feb | 33.4 °C | 41 % | 31 km/h | 0.0 mm | Low 6 |
| 5 Feb | 31.9 °C | 49 % | 26 km/h | 0.6 mm | Moderate 16 |
| 6 Feb | 33.2 °C | 41 % | 25 km/h | 0.0 mm | High 22 |
| 7 Feb | 36.3 °C | 28 % | 45 km/h | 0.0 mm | Very high 39 |
| 8 Feb | 36.9 °C | 28 % | 35 km/h | 0.0 mm | High 37 |
| 9 Feb | 34.9 °C | 33 % | 26 km/h | 0.0 mm | High 32 |
| 10 Feb | 35.9 °C | 27 % | 30 km/h | 0.0 mm | High 32 |
| 11 Feb | 36.1 °C | 22 % | 24 km/h | 0.0 mm | High 37 |
| 12 Feb | 34.1 °C | 31 % | 24 km/h | 0.0 mm | High 30 |
| 13 Feb | 35.6 °C | 21 % | 30 km/h | 0.0 mm | Very high 40 |
| 14 Feb | 37.6 °C | 14 % | 30 km/h | 0.0 mm | Extreme 51 |
| 15 Feb | 36.8 °C | 23 % | 22 km/h | 0.0 mm | Very high 43 |
| 16 Feb | 38.1 °C | 26 % | 37 km/h | 0.0 mm | Very high 48 |
| 17 Feb | 36.7 °C | 37 % | 45 km/h | 1.5 mm | High 31 |
| 18 Feb | 28.3 °C | 71 % | 35 km/h | 17.7 mm | Very low 4 |
| 19 Feb | 32.8 °C | 49 % | 26 km/h | 3.5 mm | Very low 1 |
| 20 Feb | 33.4 °C | 50 % | 31 km/h | 2.9 mm | Very low 3 |
| 21 Feb | 35.5 °C | 37 % | 36 km/h | 0.0 mm | Low 11 |
| 22 Feb | 38.2 °C | 21 % | 30 km/h | 0.0 mm | High 30 |
| 23 Feb | 37.8 °C | 20 % | 31 km/h | 0.0 mm | High 36 |
| 24 Feb | 34.9 °C | 38 % | 26 km/h | 0.0 mm | High 24 |
| 25 Feb | 34.8 °C | 42 % | 23 km/h | 3.0 mm | High 22 |
| 26 Feb | 32.8 °C | 43 % | 24 km/h | 0.5 mm | Low 5 |
| 27 Feb | 36.8 °C | 32 % | 22 km/h | 0.0 mm | Moderate 19 |
| 28 Feb | 34.0 °C | 45 % | 33 km/h | 0.0 mm | Moderate 17 |
| 29 Feb | 36.0 °C | 38 % | 27 km/h | 0.3 mm | Moderate 20 |
| 1 Mar after | 35.5 °C | 39 % | 31 km/h | 1.4 mm | Moderate 20 |
Its twins: fires that started in the same weather
It started with an FWI of 18.5, a minimum humidity of 41% and rain the day before. Fires in the area that started in weather like this since 2016: 8.
FWI at the start
18.5
Minimum humidity
41 %
Days without rain
0
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Yakoma fire, 2 February 2020
8,029 ha
28 days
FWI 18.5
Min. humidity 41 %
Bumba fire, February 2024
9,599 ha
3 days
FWI 25.2
Min. humidity 41 %
135 km away, in 2024
First rain (1 mm or more) after it ended: none in the following ten days.
Aketi fire, February 2024
6,338 ha
4 days
FWI 26.2
Min. humidity 41 %
121 km away, in 2024
First rain (1 mm or more) after it ended: none in the following ten days.
Basoko fire, February 2024
12,722 ha
11 days
FWI 24.4
Min. humidity 40 %
163 km away, in 2024
First rain (1 mm or more) after it ended: 2.8 mm on 19 Mar.
Basoko fire, February 2024
7,545 ha
9 days
FWI 24.4
Min. humidity 40 %
225 km away, in 2024
First rain (1 mm or more) after it ended: none in the following ten days.
Basoko fire, February 2024
15,371 ha
8 days
FWI 25.6
Min. humidity 40 %
187 km away, in 2024
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
Fires in the area that started in similar weather: 8. 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.4 mmfirst rain
1 Marthe day after it ended
45km/h · max. gust
It was considered over on 29 Feb, and on 1 Mar 1.4 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.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 26 Jan 2020
After · 7 Mar 2020
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 · 650Every 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 Yakoma fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 2 February 2020 to 29 February 2020 (28 days). The perimeter dates it from 5 February 2020 to 23 February 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 8,029 hectares (80.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Yakoma (8,080 ha, 0.5 %).
- What was the weather like?
- During the fire the temperature reached 38.2 °C, humidity dropped to 14 % and gusts hit 45 km/h. The fire danger index (FWI) reached 51, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Democratic Republic of the Congo (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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 23 February 2020 → 29 February 2020.
- Start date: 5 February 2020 → 2 February 2020.
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 5 February 2020 to 23 February 2020. 650 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 2020, 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.