Skip to content
worldfires
MZ · Mozambique · →

Balama fire, 28 July 2016 Balama

Out · last detection 3 Aug 2016, 11:13 UTC

The fire started on 28 July 2016 in Balama, Mozambique, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,879 hectares from heat detections, spread across a single municipality.

It is the 64th largest in Cabo Delgado since 2016 (of 120 with a page). Number 116 in Mozambique in 2016, of 194.

Burnt area
3,879ha
GWIS perimeter (Copernicus)
Duration
6days
28 Jul 2016 – 2 Aug 2016
Municipalities hit
1
districts
Started on
28 Jul
2016
Heat detections
106
in a single hotspot: 96 MW
Danger at start
25
High · FWI index
Energy released
1.7GW
sum of detected power

Where it burned

3 Aug 2016
HOTSPOTS BY DAY 28 Jul2 Aug

How it evolved, day by day

2829303113

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

The weather it burned in

29°high
34km/h · peak gust
29%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started. Rain came after the fire: 1.8 mm on 7 Aug.

This area had burned before

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

What happened to each town

  1. Balama where it started
    3,899 ha reached on 28 Jul
    0.7 %

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)
28 Jul 27.1 °C 46 % 22 km/h 0.2 mm High 25
29 Jul 29.4 °C 34 % 23 km/h 0.0 mm High 28
30 Jul 27.5 °C 34 % 24 km/h 0.0 mm High 28
31 Jul 28.0 °C 29 % 31 km/h 0.0 mm High 32
1 Aug 26.5 °C 36 % 34 km/h 0.0 mm High 35
2 Aug 26.6 °C 38 % 25 km/h 0.0 mm High 30
3 Aug after 26.0 °C 41 % 31 km/h 0.0 mm High 29
4 Aug after 26.4 °C 41 % 29 km/h 0.0 mm High 30
5 Aug after 25.2 °C 33 % 41 km/h 0.0 mm High 35
6 Aug after 25.8 °C 40 % 45 km/h 0.0 mm High 37
7 Aug after 22.8 °C 53 % 37 km/h 1.8 mm Moderate 11

Before and after, from space

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

Before · 21 Jul 2016
After · 9 Aug 2016

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 · 106Every 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 Mozambique ›

Frequently asked questions

How long did the Balama fire last?
GWIS (Copernicus) dates it between 28 July 2016 and 2 August 2016: 6 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 3,879 hectares (38.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Balama (3,899 ha, 0.7 %).
What was the weather like?
During the fire the temperature reached 29.4 °C, humidity dropped to 29 % and gusts hit 34 km/h. The fire danger index (FWI) reached 35, class High.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Mozambique (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
What do you think is wrong?

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

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.