Skip to content
worldfires
HR · Croatia · –

Općina Gračac fire, 31 March 2019 Općina Gračac

Out · last detection 2 Apr 2019, 11:04 UTC

The fire started on 31 March 2019 in Općina Gračac, Croatia, and satellites saw it burning for 3 days. Copernicus mapped a burnt perimeter of 317 hectares from satellite imagery, spread across a single municipality.

It is the 21th largest in Zadar County since 2016 (of 55 with a page). Number 10 in Croatia in 2019, of 32.

The power measured by the satellite is low (12.6 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
317ha
Copernicus perimeter
Duration
3days
31 Mar 2019 – 2 Apr 2019
Municipalities hit
1
municipalities
Started on
31 Mar
2019
Heat detections
6
in a single hotspot: 13 MW
Danger at start
7
Low · FWI index
Average daily power
20MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 31 Mar2 Apr
2 Apr 2019

How it evolved, day by day

1 Apr 2019 · 29 MW · 3 2 Apr 2019 · 10 MW · 3
1 Apr 2 Apr

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

The weather it burned in

18°high
40km/h · peak gust
24%lowest humidity

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

This area had burned before

41% of the perimeter overlaps earlier fires recorded since 2016: 130 ha in 2016.

What happened to each town

  1. Općina Gračac where it started
    317 ha reached on 1 Apr
    0.3 %

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 forest50 %
  • Other natural land47 %
  • Scrub and transitional woodland2.5 %

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

People and buildings inside the perimeter

GHSL 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

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)
31 Mar 17.6 °C 25 % 24 km/h 0.0 mm Low 7
1 Apr 17.0 °C 24 % 40 km/h 0.0 mm Moderate 12
2 Apr 16.0 °C 33 % 31 km/h 0.0 mm Low 10
3 Apr after 11.6 °C 50 % 55 km/h 0.7 mm Low 8
4 Apr after 11.4 °C 58 % 78 km/h 1.7 mm Very low 4

Its twins: fires that started in the same weather

It started with an FWI of 6.6, a minimum humidity of 25% and 4 days without rain. Fires in the area that started in weather like this since 2016: 16.

FWI at the start 6.6
Minimum humidity 25 %
Days without rain 4
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Općina Gračac fire, March 2017
1,680 ha 5 days FWI 5.3 Min. humidity 25 % 6 km away, in 2017

First rain (1 mm or more) after it ended: 3.0 mm on 26 Mar.

What happened to them

2 days
median duration
152 ha
median area
12 %
went past 1,000 ha
3.0 mm
rain at the end (median; 15 of 16 had it)

It was 2.1 times larger than the median of its twins and lasted 3 days, against 2 days.

Only 5 of its 16 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 1 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.0 mm.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

1.7 mmfirst rain
4 Apr2 days after it ended
40km/h · max. gust

It was considered over on 2 Apr, and on 4 Apr 1.7 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 15 of 16, with a median of 3.0 mm.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 24 Mar 2019
After · 9 Apr 2019

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

The smoke

CAMS · Copernicus

On 1 April 2019 the air beside the fire reached 26 µg/m³ of PM2.5. That day averaged 21: 1.4 times the WHO daily guideline (15).

PM2.5 peak26 µg/m³
Days over the guideline4 days
PM1033 µg/m³
29 Mar31 Mar2 Apr4 Apr
Good Fair Moderate Poor Very poor Extremely poor

Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.

Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)

Detections table · 6Every 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 Croatia

Frequently asked questions

How long did the Općina Gračac fire last?
Copernicus dates it between 31 March 2019 and 2 April 2019: 3 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 317 hectares (3.2 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Općina Gračac (317 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 17.6 °C, humidity dropped to 24 % and gusts hit 40 km/h. The fire danger index (FWI) reached 12, class Moderate.
Where does this data come from?
From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Croatia (geoBoundaries). It is not an official report.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 16. Their median duration was 2 days and their median area 152 ha; 12 % went past 1,000 ha. Only 5 of its 16 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 1 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.0 mm.

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: 112 · 193 · 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.

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

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 6 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.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

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 ADM2 (Creative Commons Attribution-ShareAlike 2.0). 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.