Skip to content
worldfires
HR · Croatia · →

Grad Gospić fire, 29 March 2017 Grad Gospić, Općina Lovinac

Out · last detection 29 Mar 2017, 12:06 UTC

The fire started on 29 March 2017 in Grad Gospić, Croatia, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 542 hectares from satellite imagery, spread across 2 municipalities.

It is the 11th largest in Lika-Senj since 2016 (of 85 with a page). Number 34 in Croatia in 2017, of 78.

Compare with…
Burnt area
542ha
Copernicus perimeter
Duration
2days
29 Mar 2017 – 30 Mar 2017
Municipalities hit
2
municipalities
Started on
29 Mar
2017
Heat detections
17
in a single hotspot: 55 MW
Danger at start
8
Low · FWI index
Average daily power
296MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 29 Mar30 Mar

How it evolved, day by day

29 Mar 2017 · 296 MW · 17

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

The weather it burned in

20°high
48km/h · peak gust
23%lowest humidity

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

This area had burned before

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

How big is it?

10 km
It burned the equivalent of 0.3% of the area of London (5.4 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Grad Gospić where it started
    519 ha reached on 29 Mar
    0.5 %
  2. 22 ha
    0.1 %

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

  • Scrub and transitional woodland52 %
  • Agricultural areas29 %
  • Broadleaved forest19 %

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

People and buildings inside the perimeter

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

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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)
29 Mar 19.6 °C 23 % 48 km/h 0.0 mm Low 8
30 Mar 20.8 °C 31 % 50 km/h 0.0 mm Low 9
31 Mar after 21.4 °C 32 % 26 km/h 0.0 mm Low 8
1 Apr after 19.5 °C 34 % 43 km/h 0.0 mm Low 9
2 Apr after 19.8 °C 31 % 50 km/h 0.6 mm Low 10
3 Apr after 20.4 °C 34 % 39 km/h 1.5 mm Very low 3

Before and after, from space

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

Before · 22 Mar 2017
After · 6 Apr 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.

The smoke

CAMS · Copernicus

On 30 March 2017 the air beside the fire reached 17 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak17 µg/m³
Days over the guideline0 days
PM1022 µg/m³
27282930311
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 · 17Every 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 Grad Gospić fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 29 March 2017 to 30 March 2017 (2 days). The perimeter dates it from 29 March 2017 to 29 March 2017.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 542 hectares (5.4 km²). Official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Grad Gospić (519 ha, 0.5 %); Općina Lovinac (22 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 19.6 °C, humidity dropped to 23 % and gusts hit 48 km/h. The fire danger index (FWI) reached 8, class Low.
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.

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.

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

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 29 March 2017 to 29 March 2017. 17 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 2015, 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.