Skip to content
worldfires
TR · Türkiye · →

Silvan fire, 23 August 2020 Silvan

Out · last detection 24 Aug 2020, 09:58 UTC

The fire started on 23 August 2020 in Silvan, Türkiye, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 370 hectares from satellite imagery, spread across a single municipality.

It is the 38th largest in Diyarbakır since 2016 (of 110 with a page). Number 60 in Türkiye in 2020, of 212.

The power measured by the satellite is low (18.2 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
370ha
Copernicus perimeter
Duration
2days
23 Aug 2020 – 24 Aug 2020
Municipalities hit
1
districts
Started on
23 Aug
2020
Heat detections
21
in a single hotspot: 18 MW
Danger at start
40
Very high · FWI index
Energy released
152MW
sum of detected power

Where it burned

24 Aug 2020
HOTSPOTS BY DAY 23 Aug24 Aug

How it evolved, day by day

2324

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

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

This area had burned before

48% of the perimeter overlaps earlier fires recorded since 2016: 164 ha in 2016, 54 ha in 2018. Part of it burned more than once, so the yearly figures add up to more than the 176 ha that had burned before.

What happened to each town

  1. Silvan 86,672 inhabitants · 0.7 km from the town where it started
    370 ha reached on 23 Aug
    0.3 %

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

  • Agricultural areas100 %

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)
23 Aug 32.6 °C 19 % 31 km/h 0.0 mm Very high 40
24 Aug 33.8 °C 14 % 27 km/h 0.0 mm Very high 42
25 Aug after 35.3 °C 13 % 28 km/h 0.0 mm Very high 45
26 Aug after 36.1 °C 12 % 19 km/h 0.0 mm Very high 45
27 Aug after 36.9 °C 11 % 20 km/h 0.0 mm Very high 47
28 Aug after 38.2 °C 9 % 20 km/h 0.0 mm Very high 47
29 Aug after 38.8 °C 9 % 19 km/h 0.0 mm Extreme 52
30 Aug after 40.0 °C 10 % 20 km/h 0.0 mm Very high 48
31 Aug after 39.8 °C 9 % 20 km/h 0.0 mm Extreme 50
1 Sept after 39.9 °C 8 % 35 km/h 0.0 mm Extreme 57
2 Sept after 37.7 °C 13 % 35 km/h 0.0 mm Extreme 60
3 Sept after 38.8 °C 10 % 33 km/h 0.0 mm Extreme 59

Before and after, from space

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

Before · 16 Aug 2020
After · 31 Aug 2020

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 21 August 2020 the air beside the fire reached 19 µg/m³ of PM2.5. That day averaged 15: 1.0 times the WHO daily guideline (15).

PM2.5 peak19 µg/m³
Days over the guideline1 day
PM1023 µg/m³
21222324252627
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 · 21Every 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 Silvan fire last?
Copernicus dates it between 23 August 2020 and 24 August 2020: 2 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 370 hectares (3.7 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Silvan (370 ha, 0.3 %).
Did the fire reach a town?
The closest fire to a town centre came within 0.7 km of Silvan. 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.8 °C, humidity dropped to 14 % and gusts hit 31 km/h. The fire danger index (FWI) reached 42, 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.