Skip to content
worldfires
CI · Côte d’Ivoire · →

Nassian fire, January 2026 Nassian

Out · last detection 27 Jan 2026, 13:57 UTC

The fire started on 24 January 2026 in Nassian, Côte d’Ivoire, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,213 hectares from heat detections, spread across a single municipality.

It is the 547th largest in Zanzan since 2016 (of 774 with a page). Number 92 in Côte d’Ivoire in 2026, of 136.

The power measured by the satellite is low (22.3 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Compare with…
Burnt area
1,213ha
GWIS perimeter (Copernicus)
Duration
5days
24 Jan 2026 – 28 Jan 2026
Municipalities hit
1
sub-prefectures
Started on
24 Jan
2026
Heat detections
26
in a single hotspot: 22 MW
Average daily power
42MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 24 Jan28 Jan
27 Jan 2026

How it evolved, day by day

24 Jan 2026 · 5 MW · 1 25 Jan 2026 · 82 MW · 9 26 Jan 2026 · 52 MW · 10 27 Jan 2026 · 28 MW · 6
24 Jan 25 Jan 26 Jan 27 Jan

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 0.8% of the area of London (12 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. Nassian where it started
    1,221 ha reached on 24 Jan
    1.0 %

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.

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 17 Jan 2026
After · 4 Feb 2026

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 · Copernicus

On 28 January 2026 the air beside the fire reached 87 µg/m³ of PM2.5. That day averaged 64: 4.2 times the WHO daily guideline (15).

PM2.5 peak87 µg/m³
Days over the guideline10 days
PM10285 µg/m³
Optical depth0.72
22232425262728293031
Good Fair Moderate Poor Very poor Extremely poor

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 · 26Every 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 Côte d’Ivoire ›

Frequently asked questions

How long did the Nassian fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 24 January 2026 to 28 January 2026 (5 days). The perimeter dates it from 24 January 2026 to 27 January 2026.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,213 hectares (12.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Nassian (1,221 ha, 1.0 %).
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Côte d’Ivoire (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.

Emergency number: 180

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

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 180.

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 24 January 2026 to 27 January 2026. 26 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.

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.