Skip to content
worldfires
TR · Türkiye · →

Derecik fire, August 2017 Derecik

Out · last detection 24 Aug 2017, 09:08 UTC

The fire started on 22 August 2017 in Derecik, Türkiye, and satellites saw it burning for 3 days. Copernicus mapped a burnt perimeter of 207 hectares from satellite imagery, spread across a single municipality.

It is the 54th largest in Hakkâri since 2016 (of 111 with a page). Number 59 in Türkiye in 2017, of 98.

The power measured by the satellite is low (9.1 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
207ha
Copernicus perimeter
Duration
3days
22 Aug 2017 – 24 Aug 2017
Municipalities hit
1
districts
Started on
22 Aug
2017
Heat detections
16
in a single hotspot: 9 MW
Danger at start
48
Very high · FWI index
Energy released
63MW
sum of detected power

Where it burned

24 Aug 2017
HOTSPOTS BY DAY 22 Aug24 Aug

How it evolved, day by day

222324

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

The weather it burned in

34°high
44km/h · peak gust
7%lowest humidity

It had gone 21 days without rain (1 mm or more) when it started.

This area had burned before

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

What happened to each town

  1. Derecik 25,907 inhabitants · 8.1 km from the town where it started
    208 ha reached on 22 Aug
    0.4 %

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

  • Scrub and transitional woodland95 %
  • Broadleaved forest5.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 Aug 34.1 °C 18 % 44 km/h 0.0 mm Very high 48
23 Aug 33.1 °C 15 % 42 km/h 0.0 mm Very high 47
24 Aug 34.4 °C 7 % 39 km/h 0.0 mm Very high 50
25 Aug after 34.3 °C 15 % 45 km/h 0.0 mm Very high 50
26 Aug after 33.3 °C 16 % 47 km/h 0.0 mm Very high 48
27 Aug after 32.2 °C 17 % 39 km/h 0.0 mm Very high 47
28 Aug after 32.6 °C 15 % 52 km/h 0.0 mm Very high 50
29 Aug after 32.6 °C 17 % 57 km/h 0.0 mm Very high 49
30 Aug after 32.2 °C 13 % 62 km/h 0.0 mm Extreme 52
31 Aug after 33.0 °C 19 % 42 km/h 0.0 mm Very high 45
1 Sept after 33.9 °C 13 % 50 km/h 0.0 mm Very high 48
2 Sept after 32.1 °C 19 % 60 km/h 0.0 mm Very high 49
3 Sept after 31.4 °C 12 % 39 km/h 0.0 mm Very high 44

Before and after, from space

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

Before · 15 Aug 2017
After · 31 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.

The smoke

CAMS · Copernicus

On 26 August 2017 the air beside the fire reached 20 µg/m³ of PM2.5. That day averaged 16: 1.1 times the WHO daily guideline (15).

PM2.5 peak20 µg/m³
Days over the guideline2 days
PM1028 µg/m³
2021222324252627
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 · 16Every 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 Türkiye ›

Frequently asked questions

How long did the Derecik fire last?
Copernicus dates it between 22 August 2017 and 24 August 2017: 3 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 207 hectares (2.1 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Derecik (208 ha, 0.4 %).
Did the fire reach a town?
The closest fire to a town centre came within 8.1 km of Derecik. That is the distance to the perimeter or nearest hotspot; it does not mean it entered the houses.
What was the weather like?
During the fire the temperature reached 34.4 °C, humidity dropped to 7 % and gusts hit 44 km/h. The fire danger index (FWI) reached 50, class Very high.
Where does this data come from?
From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Türkiye (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

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 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 ADM2 (Open Data Commons Open Database License 1.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.