Skip to content
worldfires
BA · Bosnia & Herzegovina · →

Gacko fire, 24 January 2020 Gacko

Out · last detection 24 Jan 2020, 11:34 UTC

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

It is the 187th largest in Republika Srpska since 2016 (of 391 with a page). Number 81 in Bosnia & Herzegovina in 2020, of 183.

The power measured by the satellite is low (3.9 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
258ha
Copernicus perimeter
Duration
4days
24 Jan 2020 – 27 Jan 2020
Municipalities hit
1
municipalities
Started on
24 Jan
2020
Heat detections
5
in a single hotspot: 4 MW
Danger at start
1
Very low · FWI index
Energy released
14MW
sum of detected power

Where it burned

HOTSPOTS BY DAY 24 Jan27 Jan

How it evolved, day by day

24

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

The weather it burned in

5°high
37km/h · peak gust
32%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 2.8 mm on 28 Jan.

This area had burned before

2% of the perimeter overlaps earlier fires recorded since 2016: 4 ha in 2016.

What happened to each town

  1. Gacko where it started
    251 ha reached on 24 Jan
    0.3 %

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

  • Sclerophyllous scrub86 %
  • Other natural land14 %

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)
24 Jan 4.2 °C 32 % 30 km/h 0.0 mm Very low 1
25 Jan 4.7 °C 74 % 32 km/h 0.3 mm Very low 0
26 Jan 1.7 °C 94 % 37 km/h 13.1 mm Very low 0
27 Jan 4.3 °C 80 % 23 km/h 2.8 mm Very low 0
28 Jan after 3.0 °C 87 % 61 km/h 2.8 mm Very low 0

Before and after, from space

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

Before · 17 Jan 2020
After · 3 Feb 2020

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 · 5Every 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 24 January 2020 and 27 January 2020: 4 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 258 hectares (2.6 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Gacko (251 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 4.7 °C, humidity dropped to 32 % and gusts hit 37 km/h. The fire danger index (FWI) reached 1, class Very low.
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.

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.