Skip to content
worldfires
CF · Central African Republic · →

Vassako fire, 7 January 2018 Vassako

Out · last detection 15 Jan 2018, 12:22 UTC

The fire started on 7 January 2018 in Vassako, Central African Republic, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 10,959 hectares from heat detections, spread across a single municipality.

It is the 59th largest in Bamingui-Bangoran since 2016 (of 223 with a page). Number 31 in Central African Republic in 2018, of 81.

Compare with…
Burnt area
10,959ha
GWIS perimeter (Copernicus)
Duration
9days
7 Jan 2018 – 15 Jan 2018
Municipalities hit
1
sub-prefectures
Started on
7 Jan
2018
Heat detections
413
in a single hotspot: 63 MW
Danger at start
51
Extreme · FWI index
Average daily power
310MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 7 Jan15 Jan
15 Jan 2018

How it evolved, day by day

7 Jan 2018 · 83 MW · 13 8 Jan 2018 · 986 MW · 90 9 Jan 2018 · 269 MW · 67 10 Jan 2018 · 198 MW · 26 11 Jan 2018 · 129 MW · 28 12 Jan 2018 · 436 MW · 59 13 Jan 2018 · 322 MW · 78 14 Jan 2018 · 190 MW · 35 15 Jan 2018 · 173 MW · 17
7 Jan 8 Jan 9 Jan 11 Jan 13 Jan 15 Jan

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

37°high
37km/h · peak gust
11%lowest humidity

It had gone 48 days without rain (1 mm or more) when it started.

This area had burned before

42% of the perimeter overlaps earlier fires recorded since 2016: 3,652 ha in 2016, 1,041 ha in 2017.

How big is it?

10 km
It burned the equivalent of 6.9% of the area of London (110 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.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. Vassako where it started
    11,044 ha reached on 7 Jan
    0.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 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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)
7 Jan 35.0 °C 13 % 32 km/h 0.0 mm Extreme 51
8 Jan 34.7 °C 14 % 29 km/h 0.0 mm Very high 48
9 Jan 34.3 °C 12 % 31 km/h 0.0 mm Very high 50
10 Jan 35.0 °C 13 % 30 km/h 0.0 mm Very high 50
11 Jan 35.4 °C 12 % 31 km/h 0.0 mm Extreme 51
12 Jan 35.1 °C 12 % 30 km/h 0.0 mm Extreme 50
13 Jan 35.3 °C 11 % 32 km/h 0.0 mm Extreme 53
14 Jan 35.6 °C 11 % 30 km/h 0.0 mm Extreme 52
15 Jan 37.1 °C 14 % 37 km/h 0.0 mm Extreme 57
16 Jan after 36.1 °C 12 % 31 km/h 0.0 mm Extreme 53
17 Jan after 36.1 °C 11 % 28 km/h 0.0 mm Extreme 52
18 Jan after 35.0 °C 10 % 29 km/h 0.0 mm Extreme 52
19 Jan after 35.6 °C 10 % 28 km/h 0.0 mm Extreme 52
20 Jan after 35.9 °C 12 % 32 km/h 0.0 mm Extreme 56
21 Jan after 35.9 °C 13 % 30 km/h 0.0 mm Extreme 51
22 Jan after 36.0 °C 11 % 32 km/h 0.0 mm Extreme 55
23 Jan after 36.6 °C 11 % 30 km/h 0.0 mm Extreme 54
24 Jan after 37.0 °C 10 % 24 km/h 0.0 mm Extreme 53
25 Jan after 36.9 °C 11 % 28 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.

Before · 31 Dec 2017
After · 22 Jan 2018

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 · 413Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Central African Republic ›

Frequently asked questions

How long did the Vassako fire last?
GWIS (Copernicus) dates it between 7 January 2018 and 15 January 2018: 9 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 10,959 hectares (109.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Vassako (11,044 ha, 0.5 %).
What was the weather like?
During the fire the temperature reached 37.1 °C, humidity dropped to 11 % and gusts hit 37 km/h. The fire danger index (FWI) reached 57, 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

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.

RSS Changes to this page

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 2 polygons grouped in this page.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 413 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.

How we build fire pages: methodology ›

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.