Anamur fire, July 2017 Anamur
The fire started on 1 July 2017 in Anamur, Türkiye, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 1,145 hectares from satellite imagery, spread across a single municipality.
It is the 6th largest in Mersin since 2016 (of 16 with a page). Number 11 in Türkiye in 2017, of 98.
- Burnt area
- 1,145ha
- Copernicus perimeter
- Duration
- 2days
- 1 Jul 2017 – 2 Jul 2017
- Municipalities hit
- 1
- districts
- Started on
- 1 Jul
- 2017
- Heat detections
- 52
- in a single hotspot: 74 MW
- Danger at start
- 38
- High · FWI index
- Energy released
- 598MW
- sum of detected power
Where it burned
How it evolved, day by day
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 9 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,147 ha reached on 1 Jul0.8 %
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
- Coniferous forest85 %
- Scrub and transitional woodland15 %
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) |
|---|---|---|---|---|---|
| 1 Jul | 37.8 °C | 18 % | 47 km/h | 0.0 mm | High 38 |
| 2 Jul | 39.6 °C | 15 % | 32 km/h | 0.0 mm | High 36 |
| 3 Jul after | 37.8 °C | 18 % | 33 km/h | 0.0 mm | High 36 |
| 4 Jul after | 35.2 °C | 13 % | 32 km/h | 0.0 mm | High 37 |
| 5 Jul after | 33.1 °C | 32 % | 29 km/h | 0.0 mm | High 29 |
| 6 Jul after | 31.8 °C | 27 % | 31 km/h | 0.2 mm | High 30 |
| 7 Jul after | 33.3 °C | 27 % | 39 km/h | 0.0 mm | High 34 |
| 8 Jul after | 32.0 °C | 20 % | 40 km/h | 0.0 mm | High 35 |
| 9 Jul after | 33.0 °C | 20 % | 39 km/h | 0.0 mm | High 35 |
| 10 Jul after | 34.1 °C | 24 % | 34 km/h | 0.0 mm | High 34 |
| 11 Jul after | 35.6 °C | 22 % | 39 km/h | 0.0 mm | High 36 |
| 12 Jul after | 36.8 °C | 22 % | 42 km/h | 0.0 mm | High 38 |
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 1 July 2017 the air beside the fire reached 30 µg/m³ of PM2.5. That day averaged 21: 1.4 times the WHO daily 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 · 52Every 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 Anamur fire last?
- Copernicus dates it between 1 July 2017 and 2 July 2017: 2 days between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 1,145 hectares (11.4 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Anamur (1,147 ha, 0.8 %).
- Did the fire reach a town?
- The closest fire to a town centre came within 15.2 km of Anamur. 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 39.6 °C, humidity dropped to 15 % and gusts hit 47 km/h. The fire danger index (FWI) reached 38, class 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
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.