Skip to content
worldfires
CM · Cameroon · →

Ngambé-Tikar fire, 6 February 2017 Ngambé-Tikar, Malentouen

Out · last detection 12 Mar 2017, 12:15 UTC

The fire started on 6 February 2017 in Ngambé-Tikar, Cameroon, and satellites saw it burning for 35 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 14,241 hectares from heat detections, spread across 2 municipalities.

It is the 6th largest in Centre since 2016 (of 200 with a page). Number 4 in Cameroon in 2017, of 294.

Compare with…
Burnt area
14,241ha
GWIS perimeter (Copernicus)
Duration
35days
6 Feb 2017 – 12 Mar 2017
Municipalities hit
2
communes
Started on
6 Feb
2017
Heat detections
1,336
in a single hotspot: 253 MW
Danger at start
46
Very high · FWI index
Average daily power
462MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 6 Feb12 Mar
12 Mar 2017

How it evolved, day by day

6 Feb 2017 · 80 MW · 10 7 Feb 2017 · 76 MW · 8 8 Feb 2017 · 41 MW · 5 9 Feb 2017 · 16 MW · 5 10 Feb 2017 · 85 MW · 11 11 Feb 2017 · 67 MW · 9 12 Feb 2017 · 84 MW · 9 13 Feb 2017 · 1,185 MW · 38 14 Feb 2017 · 80 MW · 22 15 Feb 2017 · 61 MW · 26 16 Feb 2017 · 560 MW · 40 17 Feb 2017 · 424 MW · 34 18 Feb 2017 · 391 MW · 25 19 Feb 2017 · 881 MW · 64 20 Feb 2017 · 1,438 MW · 115 21 Feb 2017 · 774 MW · 112 22 Feb 2017 · 471 MW · 38 23 Feb 2017 · 4,030 MW · 177 24 Feb 2017 · 348 MW · 69 25 Feb 2017 · 354 MW · 76 26 Feb 2017 · 322 MW · 68 27 Feb 2017 · 1,405 MW · 77 28 Feb 2017 · 1,011 MW · 60 1 Mar 2017 · 578 MW · 32 2 Mar 2017 · 457 MW · 48 3 Mar 2017 · 114 MW · 49 4 Mar 2017 · 199 MW · 29 5 Mar 2017 · 76 MW · 15 6 Mar 2017 · 303 MW · 29 7 Mar 2017 · 9 MW · 2 8 Mar 2017 · 54 MW · 6 9 Mar 2017 · 23 MW · 11 10 Mar 2017 · 77 MW · 7 11 Mar 2017 · 50 MW · 5 12 Mar 2017 · 34 MW · 5
6 Feb 11 Feb 16 Feb 21 Feb 23 Feb 26 Feb 3 Mar 8 Mar

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
7%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

59% of the perimeter overlaps earlier fires recorded since 2016: 8,462 ha in 2016.

How big is it?

10 km
It burned the equivalent of 9% of the area of London (142 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. Ngambé-Tikar where it started
    14,323 ha reached on 6 Feb
    2.1 %
  2. 15 ha reached on 8 Feb
    0.0 %

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 2015
Built-up area2.4 ha
Residents≈ 250

Inside the perimeter there were about 2.4 hectares of built-up land and about 250 residents (GHSL 2015, 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)
6 Feb 35.9 °C 15 % 20 km/h 0.0 mm Very high 46
7 Feb 35.9 °C 14 % 19 km/h 0.0 mm Very high 49
8 Feb 36.8 °C 14 % 26 km/h 0.0 mm Extreme 53
9 Feb 37.0 °C 11 % 21 km/h 0.0 mm Very high 45
10 Feb 36.0 °C 10 % 26 km/h 0.0 mm Very high 48
11 Feb 37.0 °C 15 % 20 km/h 0.0 mm Extreme 50
12 Feb 37.2 °C 10 % 25 km/h 0.0 mm Very high 47
13 Feb 36.8 °C 14 % 21 km/h 0.0 mm Very high 47
14 Feb 37.4 °C 7 % 22 km/h 0.0 mm Extreme 50
15 Feb 36.4 °C 12 % 22 km/h 0.0 mm Very high 50
16 Feb 34.8 °C 18 % 23 km/h 0.0 mm Very high 48
17 Feb 34.4 °C 12 % 24 km/h 0.0 mm Very high 44
18 Feb 35.0 °C 12 % 23 km/h 0.0 mm Very high 47
19 Feb 35.3 °C 11 % 22 km/h 0.0 mm Very high 46
20 Feb 36.4 °C 11 % 23 km/h 0.0 mm Very high 45
21 Feb 36.4 °C 11 % 23 km/h 0.0 mm Very high 46
22 Feb 36.9 °C 12 % 22 km/h 0.0 mm Very high 45
23 Feb 38.1 °C 11 % 25 km/h 0.0 mm Very high 48
24 Feb 38.0 °C 7 % 23 km/h 0.0 mm Extreme 54
25 Feb 37.1 °C 11 % 25 km/h 0.0 mm Extreme 53
26 Feb 34.6 °C 22 % 25 km/h 0.0 mm Very high 47
27 Feb 37.1 °C 14 % 25 km/h 0.0 mm Very high 45
28 Feb 37.7 °C 9 % 25 km/h 0.0 mm Very high 47
1 Mar 36.8 °C 16 % 24 km/h 0.0 mm Very high 48
2 Mar 36.3 °C 20 % 25 km/h 0.0 mm Very high 46
3 Mar 37.3 °C 14 % 25 km/h 0.0 mm Very high 45
4 Mar 38.2 °C 12 % 25 km/h 0.0 mm Very high 46
5 Mar 37.4 °C 20 % 29 km/h 0.0 mm Extreme 52
6 Mar 37.4 °C 18 % 40 km/h 0.0 mm Extreme 57
7 Mar 37.6 °C 24 % 35 km/h 0.0 mm Very high 49
8 Mar 37.8 °C 12 % 30 km/h 0.0 mm Very high 47
9 Mar 37.8 °C 18 % 34 km/h 0.0 mm Extreme 54
10 Mar 36.0 °C 19 % 26 km/h 0.0 mm Very high 48
11 Mar 36.5 °C 18 % 45 km/h 0.0 mm Extreme 62
12 Mar 34.8 °C 21 % 40 km/h 0.0 mm Extreme 56
13 Mar after 36.5 °C 25 % 26 km/h 0.7 mm High 37
14 Mar after 36.7 °C 22 % 34 km/h 0.0 mm Very high 44
15 Mar after 38.0 °C 14 % 28 km/h 0.0 mm Very high 46
16 Mar after 36.9 °C 12 % 22 km/h 0.0 mm Very high 49
17 Mar after 37.3 °C 18 % 30 km/h 0.0 mm Extreme 52
18 Mar after 38.0 °C 19 % 30 km/h 0.0 mm Very high 50
19 Mar after 35.2 °C 32 % 34 km/h 0.0 mm Very high 43
20 Mar after 37.0 °C 14 % 35 km/h 0.0 mm Very high 50
21 Mar after 37.4 °C 21 % 45 km/h 0.1 mm Extreme 53
22 Mar after 34.5 °C 41 % 35 km/h 0.0 mm High 38

Before and after, from space

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

Before · 30 Jan 2017
After · 19 Mar 2017

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 · 1,336Every 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 Cameroon ›

Frequently asked questions

How long did the Ngambé-Tikar fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 6 February 2017 to 12 March 2017 (35 days). The perimeter dates it from 13 February 2017 to 5 March 2017.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 14,241 hectares (142.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Ngambé-Tikar (14,323 ha, 2.1 %); Malentouen (15 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 38.2 °C, humidity dropped to 7 % 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 Cameroon (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.
  1. Last day with fire: 5 March 2017 → 12 March 2017.
  2. Start date: 13 February 2017 → 6 February 2017.

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; 3 polygons grouped in this page.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 13 February 2017 to 5 March 2017. 1,336 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 2015, 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 (Open Data Commons Open Database License 1.0). 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.