Skip to content
worldfires
BA · Bosnia & Herzegovina · →

Gacko fire, 15 August 2017 Bileća, Gacko

Out · last detection 16 Aug 2017, 01:57 UTC

The fire started on 15 August 2017 in Gacko, Bosnia & Herzegovina, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 157 hectares from satellite imagery, spread across 2 municipalities.

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

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

Burnt area
157ha
Copernicus perimeter
Duration
2days
15 Aug 2017 – 16 Aug 2017
Municipalities hit
2
municipalities
Started on
15 Aug
2017
Heat detections
12
in a single hotspot: 2 MW
Danger at start
25
High · FWI index
Average daily power
9MW
detected power per day, on average

Where it burned

16 Aug 2017
HOTSPOTS BY DAY 15 Aug16 Aug

How it evolved, day by day

15 Aug 2017 · 9 MW · 7 16 Aug 2017 · 9 MW · 5
15 Aug 16 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
27km/h · peak gust
26%lowest humidity

It had gone 11 days without rain (1 mm or more) when it started. Rain came after the fire: 1.4 mm on 17 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. 86 ha reached on 15 Aug
    0.1 %
  2. Gacko where it started
    71 ha reached on 15 Aug
    0.1 %

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 forest84 %
  • Sclerophyllous scrub16 %

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)
15 Aug 28.4 °C 26 % 27 km/h 0.0 mm High 25
16 Aug 29.1 °C 27 % 26 km/h 0.0 mm High 27
17 Aug after 28.4 °C 30 % 35 km/h 1.4 mm Moderate 19

Before and after, from space

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

Before · 8 Aug 2017
After · 23 Aug 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 · 12Every 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 15 August 2017 and 16 August 2017: 2 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 157 hectares (1.6 km²). Official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Bileća (86 ha, 0.1 %); Gacko (71 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 29.1 °C, humidity dropped to 26 % and gusts hit 27 km/h. The fire danger index (FWI) reached 27, 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. 12 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.