Skip to content
worldfires
TR · Türkiye · →

Şemdinli fire, July 2016 Şemdinli

Out · last detection 10 Jul 2016, 10:37 UTC

The fire started on 7 July 2016 in Şemdinli, Türkiye, and satellites saw it burning for 4 days. Copernicus mapped a burnt perimeter of 407 hectares from satellite imagery, spread across a single municipality.

It is the 20th largest in Hakkâri since 2016 (of 111 with a page). Number 82 in Türkiye in 2016, of 223.

The power measured by the satellite is low (20.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
407ha
Copernicus perimeter
Duration
4days
7 Jul 2016 – 10 Jul 2016
Municipalities hit
1
districts
Started on
7 Jul
2016
Heat detections
11
in a single hotspot: 20 MW
Danger at start
30
High · FWI index
Energy released
103MW
sum of detected power

Where it burned

10 Jul 2016
HOTSPOTS BY DAY 7 Jul10 Jul

How it evolved, day by day

7910

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

The weather it burned in

33°high
46km/h · peak gust
17%lowest humidity

It had gone 17 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. Şemdinli 45,117 inhabitants · 23.0 km from the town where it started
    407 ha reached on 7 Jul
    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 woodland68 %
  • Broadleaved forest25 %
  • Other natural land6.2 %

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)
7 Jul 31.1 °C 24 % 32 km/h 0.0 mm High 30
8 Jul 32.3 °C 25 % 42 km/h 0.0 mm High 31
9 Jul 32.8 °C 17 % 31 km/h 0.0 mm High 36
10 Jul 32.7 °C 22 % 46 km/h 0.0 mm Very high 38
11 Jul after 32.3 °C 19 % 43 km/h 0.0 mm Very high 39
12 Jul after 30.9 °C 27 % 45 km/h 0.0 mm High 36
13 Jul after 29.2 °C 30 % 57 km/h 0.0 mm High 37
14 Jul after 32.7 °C 26 % 46 km/h 0.0 mm High 35
15 Jul after 34.9 °C 17 % 40 km/h 0.0 mm Very high 40
16 Jul after 35.2 °C 23 % 37 km/h 0.0 mm Very high 39
17 Jul after 34.9 °C 24 % 46 km/h 0.0 mm Very high 42
18 Jul after 36.8 °C 21 % 43 km/h 0.0 mm Very high 41
19 Jul after 35.2 °C 19 % 71 km/h 0.0 mm Very high 47
20 Jul after 36.0 °C 18 % 44 km/h 0.0 mm Very high 43

Before and after, from space

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

Before · 30 Jun 2016
After · 17 Jul 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.

The smoke

CAMS · Copernicus

On 5 July 2016 the air beside the fire reached 38 µg/m³ of PM2.5. That day averaged 30: 2.0 times the WHO daily guideline (15).

PM2.5 peak38 µg/m³
Days over the guideline7 days
PM1052 µg/m³
5678910111213
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 · 11Every 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 Şemdinli fire last?
Copernicus dates it between 7 July 2016 and 10 July 2016: 4 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 407 hectares (4.1 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Şemdinli (407 ha, 0.4 %).
Did the fire reach a town?
The closest fire to a town centre came within 23.0 km of Şemdinli. 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 32.8 °C, humidity dropped to 17 % and gusts hit 46 km/h. The fire danger index (FWI) reached 38, 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.