Skip to content
worldfires
BA · Bosnia & Herzegovina · →

Tomislavgrad fire, 22 December 2016 Tomislavgrad

Out · last detection 23 Dec 2016, 12:07 UTC

The fire started on 22 December 2016 in Tomislavgrad, Bosnia & Herzegovina, and satellites saw it burning for 3 days. Copernicus mapped a burnt perimeter of 224 hectares from satellite imagery, spread across a single municipality.

It is the 271th largest in Federation of Bosnia and Herzegovina since 2016 (of 520 with a page). Number 49 in Bosnia & Herzegovina in 2016, of 73.

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

Compare with…
Burnt area
224ha
Copernicus perimeter
Duration
3days
22 Dec 2016 – 24 Dec 2016
Municipalities hit
1
municipalities
Started on
22 Dec
2016
Heat detections
5
in a single hotspot: 9 MW
Danger at start
2
Very low · FWI index
Average daily power
28MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 22 Dec24 Dec

How it evolved, day by day

23 Dec 2016 · 28 MW · 5

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

The weather it burned in

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

It had gone 24 days without rain (1 mm or more) when it started. Rain came after the fire: 1.9 mm on 27 Dec.

This area had burned before

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

What happened to each town

  1. Tomislavgrad where it started
    223 ha reached on 23 Dec
    0.2 %

Burnt area inside each municipality, from crossing the official perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.

What burned

  • Broadleaved forest47 %
  • Scrub and transitional woodland43 %
  • Other natural land9.3 %

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 Dec 6.7 °C 53 % 25 km/h 0.0 mm Very low 2
23 Dec 7.9 °C 58 % 34 km/h 0.0 mm Very low 2
24 Dec 9.1 °C 57 % 31 km/h 0.0 mm Very low 2
25 Dec after 6.3 °C 62 % 24 km/h 0.0 mm Very low 1
26 Dec after 11.1 °C 48 % 28 km/h 0.0 mm Very low 1
27 Dec after 6.9 °C 51 % 46 km/h 1.9 mm Very low 0

Before and after, from space

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

Before · 15 Dec 2016
After · 31 Dec 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 · 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 Tomislavgrad fire last?
Copernicus dates it between 22 December 2016 and 24 December 2016: 3 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 224 hectares (2.2 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Tomislavgrad (223 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 9.1 °C, humidity dropped to 53 % and gusts hit 34 km/h. The fire danger index (FWI) reached 2, 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 · Emergency number and official warnings ›

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

No changes since 24 October 2026.

RSS Changes to this page

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. 5 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.