Skip to content
worldfires
BA · Bosnia & Herzegovina · →

Gacko fire, 22 August 2017 Gacko

Out · last detection 26 Aug 2017, 11:54 UTC

The fire started on 22 August 2017 in Gacko, Bosnia & Herzegovina, and satellites saw it burning for 4 days. Copernicus mapped a burnt perimeter of 394 hectares from satellite imagery, spread across a single municipality.

It is the 129th largest in Republika Srpska since 2016 (of 391 with a page). Number 47 in Bosnia & Herzegovina in 2017, of 102.

Compare with…
Burnt area
394ha
Copernicus perimeter
Duration
4days
22 Aug 2017 – 25 Aug 2017
Municipalities hit
1
municipalities
Started on
22 Aug
2017
Heat detections
92
in a single hotspot: 106 MW
Danger at start
19
Moderate · FWI index
Average daily power
137MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 22 Aug25 Aug
26 Aug 2017

How it evolved, day by day

24 Aug 2017 · 33 MW · 9 25 Aug 2017 · 39 MW · 9 26 Aug 2017 · 341 MW · 19
24 Aug 25 Aug 26 Aug

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
58km/h · peak gust
14%lowest humidity

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

This area had burned before

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

What happened to each town

  1. Gacko where it started
    394 ha reached on 19 Aug
    0.5 %

Burnt area inside each municipality, from crossing the official 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.

What burned

  • Broadleaved forest58 %
  • Other natural land31 %
  • Scrub and transitional woodland8.4 %
  • Agricultural areas2.8 %

Land cover inside the perimeter according to Corine Land Cover, as reported by Copernicus.

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)
22 Aug 19.3 °C 29 % 58 km/h 0.0 mm Moderate 19
23 Aug 22.3 °C 22 % 28 km/h 0.0 mm Moderate 21
24 Aug 26.1 °C 20 % 31 km/h 0.0 mm High 27
25 Aug 28.9 °C 14 % 20 km/h 0.0 mm High 29
26 Aug after 29.0 °C 17 % 34 km/h 0.0 mm High 34
27 Aug after 29.0 °C 14 % 28 km/h 0.0 mm High 34
28 Aug after 26.0 °C 32 % 38 km/h 0.2 mm High 32
29 Aug after 21.5 °C 39 % 50 km/h 0.3 mm High 29
30 Aug after 26.0 °C 10 % 29 km/h 0.0 mm High 34
31 Aug after 25.0 °C 21 % 34 km/h 0.0 mm High 35
1 Sept after 25.4 °C 27 % 35 km/h 0.0 mm High 33
2 Sept after 24.0 °C 38 % 54 km/h 7.2 mm Very low 5

Before and after, from space

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

Before · 15 Aug 2017
After · 1 Sept 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 · 92Every 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 Bosnia & Herzegovina ›

Frequently asked questions

How long did the Gacko fire last?
Copernicus dates it between 22 August 2017 and 25 August 2017: 4 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 394 hectares (3.9 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Gacko (394 ha, 0.5 %).
What was the weather like?
During the fire the temperature reached 28.9 °C, humidity dropped to 14 % and gusts hit 58 km/h. The fire danger index (FWI) reached 29, class High.
Where does this data come from?
From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Bosnia & Herzegovina (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: 123 · 112

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 123 · 112.

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 92 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.

How we build fire pages: methodology ›

Where this data comes from

The perimeter and land cover come from the Copernicus European Forest Fire Information System (EFFIS), measured on MODIS and Sentinel-2 imagery and published under CC BY 4.0. 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 slightly from each country’s official figure.