Skip to content
worldfires
TR · Türkiye · →

Beytüşşebap fire, June 2016 Beytüşşebap, Uludere

Out · last detection 29 Jun 2016, 10:43 UTC

The fire started on 28 June 2016 in Beytüşşebap, Türkiye, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 185 hectares from satellite imagery, spread across 2 municipalities.

It is the 125th largest in Şırnak since 2016 (of 192 with a page). Number 157 in Türkiye in 2016, of 223.

The power measured by the satellite is low (23.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
185ha
Copernicus perimeter
Duration
2days
28 Jun 2016 – 29 Jun 2016
Municipalities hit
2
districts
Started on
28 Jun
2016
Heat detections
13
in a single hotspot: 23 MW
Danger at start
40
Very high · FWI index
Energy released
120MW
sum of detected power

Where it burned

29 Jun 2016
HOTSPOTS BY DAY 28 Jun29 Jun

How it evolved, day by day

2829

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
55km/h · peak gust
16%lowest humidity

It had gone 6 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. Beytüşşebap 16,317 inhabitants · 51.5 km from the town where it started
    122 ha reached on 28 Jun
    0.1 %
  2. Uludere 46,040 inhabitants · 20.6 km from the town
    63 ha reached on 28 Jun
    0.1 %

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

  • Other natural land72 %
  • Broadleaved forest18 %
  • Scrub and transitional woodland9.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)
28 Jun 33.9 °C 16 % 55 km/h 0.0 mm Very high 40
29 Jun 32.6 °C 17 % 35 km/h 0.0 mm High 36
30 Jun after 32.8 °C 21 % 42 km/h 0.0 mm Very high 38
1 Jul after 31.7 °C 18 % 38 km/h 0.0 mm Very high 38
2 Jul after 33.3 °C 18 % 35 km/h 0.0 mm Very high 38
3 Jul after 33.9 °C 20 % 37 km/h 0.0 mm Very high 39
4 Jul after 33.9 °C 21 % 42 km/h 0.0 mm Very high 42
5 Jul after 32.6 °C 22 % 49 km/h 0.0 mm Very high 45
6 Jul after 30.7 °C 26 % 33 km/h 0.0 mm High 36
7 Jul after 32.1 °C 26 % 32 km/h 0.0 mm High 35
8 Jul after 32.9 °C 23 % 43 km/h 0.0 mm Very high 38
9 Jul after 32.7 °C 20 % 45 km/h 0.0 mm Very high 40

Before and after, from space

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

Before · 21 Jun 2016
After · 6 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 26 June 2016 the air beside the fire reached 23 µg/m³ of PM2.5. That day averaged 20: 1.4 times the WHO daily guideline (15).

PM2.5 peak23 µg/m³
Days over the guideline3 days
PM1036 µg/m³
262728293012
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 · 13Every 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 Beytüşşebap fire last?
Copernicus dates it between 28 June 2016 and 29 June 2016: 2 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 185 hectares (1.8 km²). Official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Beytüşşebap (122 ha, 0.1 %); Uludere (63 ha, 0.1 %).
Did the fire reach a town?
The closest fire to a town centre came within 20.6 km of Uludere. 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 33.9 °C, humidity dropped to 16 % and gusts hit 55 km/h. The fire danger index (FWI) reached 40, 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.