Midyat fire, July 2025 Midyat
The fire started on 20 July 2025 in Midyat, Türkiye, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 108 hectares from satellite imagery, spread across a single municipality.
It is the 130th largest in Mardin since 2016 (of 131 with a page). Number 168 in Türkiye in 2025, of 184.
The power measured by the satellite is low (13.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 108ha
- Copernicus perimeter
- Duration
- 1day
- 20 Jul 2025 – 20 Jul 2025
- Municipalities hit
- 1
- districts
- Started on
- 20 Jul
- 2025
- Heat detections
- 12
- in a single hotspot: 13 MW
- Danger at start
- 58
- Extreme · FWI index
- Average daily power
- 71MW
- detected power per day, on average
Where it burned
How it evolved, day by day
20 Jul 2025 · 71 MW · 12
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 4 days without rain (1 mm or more) when it started.
This area had burned before
78% of the perimeter overlaps earlier fires recorded since 2016: 84 ha in 2016.
What happened to each town
-
109 ha reached on 20 Jul0.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 woodland86 %
- Agricultural areas14 %
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) |
|---|---|---|---|---|---|
| 20 Jul | 38.7 °C | 15 % | 38 km/h | 0.0 mm | Extreme 58 |
| 21 Jul after | 38.5 °C | 14 % | 33 km/h | 0.0 mm | Extreme 55 |
| 22 Jul after | 39.5 °C | 12 % | 34 km/h | 0.0 mm | Extreme 57 |
| 23 Jul after | 40.6 °C | 13 % | 23 km/h | 0.0 mm | Extreme 50 |
| 24 Jul after | 43.4 °C | 10 % | 30 km/h | 0.0 mm | Extreme 53 |
| 25 Jul after | 44.1 °C | 9 % | 31 km/h | 0.0 mm | Extreme 57 |
| 26 Jul after | 43.2 °C | 11 % | 23 km/h | 0.0 mm | Extreme 56 |
| 27 Jul after | 42.8 °C | 11 % | 24 km/h | 0.0 mm | Extreme 58 |
| 28 Jul after | 40.9 °C | 13 % | 35 km/h | 0.0 mm | Extreme 62 |
| 29 Jul after | 40.8 °C | 12 % | 29 km/h | 0.0 mm | Extreme 58 |
| 30 Jul after | 42.4 °C | 10 % | 30 km/h | 0.0 mm | Extreme 62 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · CopernicusOn 21 July 2025 the air beside the fire reached 15 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
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 · 12Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Midyat fire last?
- Copernicus dates it between 20 July 2025 and 20 July 2025: 1 day between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 108 hectares (1.1 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Midyat (109 ha, 0.1 %).
- Did the fire reach a town?
- The fire started in Midyat and came within 15.7 km of its centre. That is the distance from the perimeter, or the nearest hotspot, to the point marking the centre; it does not mean it entered the houses.
- What was the weather like?
- During the fire the temperature reached 38.7 °C, humidity dropped to 15 % and gusts hit 38 km/h. The fire danger index (FWI) reached 58, class Extreme.
- 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 · 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.
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
How we know this
- Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 12 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.
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.