Ouadda fire, 17 January 2016 Ouadda
The fire started on 17 January 2016 in Ouadda, Central African Republic, and satellites saw it burning for 23 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 13,524 hectares from heat detections, spread across a single municipality.
It is the 98th largest in Haute-Kotto since 2016 (of 372 with a page). Number 47 in Central African Republic in 2016, of 165.
- Burnt area
- 13,524ha
- GWIS perimeter (Copernicus)
- Duration
- 23days
- 17 Jan 2016 – 8 Feb 2016
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 17 Jan
- 2016
- Heat detections
- 529
- in a single hotspot: 64 MW
- Danger at start
- 50
- Extreme · FWI index
- Energy released
- 2.7GW
- sum of detected power
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 45 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.
What happened to each town
-
Ouadda where it started13,617 ha reached on 17 Jan0.6 %
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) |
|---|---|---|---|---|---|
| 17 Jan | 35.5 °C | 12 % | 31 km/h | 0.0 mm | Very high 50 |
| 18 Jan | 35.6 °C | 12 % | 30 km/h | 0.0 mm | Extreme 50 |
| 19 Jan | 34.9 °C | 12 % | 34 km/h | 0.0 mm | Extreme 54 |
| 20 Jan | 34.9 °C | 12 % | 36 km/h | 0.0 mm | Extreme 56 |
| 21 Jan | 35.1 °C | 11 % | 29 km/h | 0.0 mm | Extreme 54 |
| 22 Jan | 35.6 °C | 10 % | 26 km/h | 0.0 mm | Extreme 53 |
| 23 Jan | 35.7 °C | 9 % | 26 km/h | 0.0 mm | Extreme 51 |
| 24 Jan | 35.2 °C | 10 % | 30 km/h | 0.0 mm | Extreme 58 |
| 25 Jan | 32.4 °C | 12 % | 38 km/h | 0.0 mm | Extreme 57 |
| 26 Jan | 32.5 °C | 12 % | 42 km/h | 0.0 mm | Extreme 59 |
| 27 Jan | 31.1 °C | 11 % | 42 km/h | 0.0 mm | Extreme 59 |
| 28 Jan | 32.0 °C | 12 % | 37 km/h | 0.0 mm | Extreme 57 |
| 29 Jan | 30.7 °C | 11 % | 45 km/h | 0.0 mm | Extreme 61 |
| 30 Jan | 31.2 °C | 12 % | 39 km/h | 0.0 mm | Extreme 56 |
| 31 Jan | 32.7 °C | 13 % | 40 km/h | 0.0 mm | Extreme 57 |
| 1 Feb | 33.8 °C | 14 % | 39 km/h | 0.0 mm | Extreme 56 |
| 2 Feb | 35.0 °C | 12 % | 40 km/h | 0.0 mm | Extreme 58 |
| 3 Feb | 35.5 °C | 12 % | 41 km/h | 0.0 mm | Extreme 59 |
| 4 Feb | 36.5 °C | 13 % | 33 km/h | 0.0 mm | Extreme 55 |
| 5 Feb | 37.1 °C | 11 % | 44 km/h | 0.0 mm | Extreme 60 |
| 6 Feb | 36.9 °C | 9 % | 45 km/h | 0.0 mm | Extreme 62 |
| 7 Feb | 34.9 °C | 10 % | 42 km/h | 0.0 mm | Extreme 62 |
| 8 Feb | 34.3 °C | 12 % | 37 km/h | 0.0 mm | Extreme 57 |
| 9 Feb after | 35.6 °C | 9 % | 31 km/h | 0.0 mm | Extreme 56 |
| 10 Feb after | 35.1 °C | 8 % | 35 km/h | 0.0 mm | Extreme 60 |
| 11 Feb after | 34.2 °C | 8 % | 39 km/h | 0.0 mm | Extreme 60 |
| 12 Feb after | 34.6 °C | 8 % | 37 km/h | 0.0 mm | Extreme 58 |
| 13 Feb after | 36.3 °C | 8 % | 35 km/h | 0.0 mm | Extreme 57 |
| 14 Feb after | 36.3 °C | 7 % | 34 km/h | 0.0 mm | Extreme 56 |
| 15 Feb after | 38.1 °C | 10 % | 33 km/h | 0.0 mm | Extreme 57 |
| 16 Feb after | 38.2 °C | 13 % | 45 km/h | 0.0 mm | Extreme 65 |
| 17 Feb after | 38.5 °C | 13 % | 31 km/h | 0.0 mm | Extreme 58 |
| 18 Feb after | 38.3 °C | 12 % | 27 km/h | 0.0 mm | Extreme 54 |
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.
Detections table · 529Every 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 Ouadda fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 17 January 2016 to 8 February 2016 (23 days). The perimeter dates it from 18 January 2016 to 3 February 2016.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 13,524 hectares (135.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Ouadda (13,617 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 37.1 °C, humidity dropped to 9 % and gusts hit 45 km/h. The fire danger index (FWI) reached 62, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Central African Republic (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
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
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 ADM3 (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.