Skip to content
worldfires
BO · Bolivia · →

Ixiamas fire, 2 October 2017 Ixiamas

Out · last detection 10 Oct 2017, 17:40 UTC

The fire started on 2 October 2017 in Ixiamas, Bolivia, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 22,697 hectares from heat detections, spread across a single municipality.

It is the 9th largest in La Paz since 2016 (of 115 with a page). Number 6 in Bolivia in 2017, of 123.

Burnt area
22,697ha
GWIS perimeter (Copernicus)
Duration
9days
2 Oct 2017 – 10 Oct 2017
Municipalities hit
1
municipalities
Started on
2 Oct
2017
Heat detections
608
in a single hotspot: 355 MW
Danger at start
2
Very low · FWI index
Energy released
8.0GW
sum of detected power

Where it burned

10 Oct 2017
HOTSPOTS BY DAY 2 Oct10 Oct

How it evolved, day by day

245678910

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

The weather it burned in

35°high
53km/h · peak gust
39%lowest humidity

It had gone 2 days without rain (1 mm or more) when it started. Rain came after the fire: 9.3 mm on 11 Oct.

This area had burned before

20% of the perimeter overlaps earlier fires recorded since 2016: 4,502 ha in 2016.

What happened to each town

  1. Ixiamas 11,828 inhabitants where it started
    22,821 ha
    0.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)
2 Oct 32.7 °C 51 % 53 km/h 5.2 mm Very low 2
3 Oct 26.7 °C 59 % 37 km/h 1.7 mm Very low 1
4 Oct 30.5 °C 50 % 20 km/h 0.0 mm Very low 4
5 Oct 32.2 °C 53 % 38 km/h 0.0 mm Low 7
6 Oct 33.8 °C 52 % 39 km/h 0.4 mm Low 8
7 Oct 32.1 °C 55 % 41 km/h 2.1 mm Very low 3
8 Oct 35.4 °C 39 % 36 km/h 0.0 mm Low 11
9 Oct 34.8 °C 43 % 38 km/h 0.0 mm Low 11
10 Oct 31.7 °C 58 % 46 km/h 3.0 mm Very low 3
11 Oct after 34.4 °C 48 % 31 km/h 9.3 mm Very low 1

Before and after, from space

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

Before · 25 Sept 2017
After · 17 Oct 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 · 608Every 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 Bolivia ›

Frequently asked questions

How long did the Ixiamas fire last?
GWIS (Copernicus) dates it between 2 October 2017 and 10 October 2017: 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 22,697 hectares (227.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Ixiamas (22,821 ha, 0.6 %).
What was the weather like?
During the fire the temperature reached 35.4 °C, humidity dropped to 39 % and gusts hit 53 km/h. The fire danger index (FWI) reached 11, class Low.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Bolivia (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: 119 · 110

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 119 · 110.

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 (Public Domain). 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.