Skip to content
worldfires
TR · Türkiye ·

Bolvadin fire, February 2024 Bolvadin

Out · last detection 24 Feb 2024, 10:18 UTC

The fire started on 24 February 2024 in Bolvadin, Türkiye, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 311 hectares from satellite imagery, spread across a single municipality.

It is the 13th largest in Afyonkarahisar since 2016 (of 41 with a page). Number 80 in Türkiye in 2024, of 271.

The power measured by the satellite is low (22.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
311ha
Copernicus perimeter
Duration
1day
24 Feb 2024 – 24 Feb 2024
Municipalities hit
1
districts
Started on
24 Feb
2024
Heat detections
2
in a single hotspot: 22 MW
Danger at start
3
Very low · FWI index
Average daily power
25MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 24 Feb24 Feb

How it evolved, day by day

24 Feb 2024 · 25 MW · 2

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

The weather it burned in

16°high
19km/h · peak gust
39%lowest humidity

It had gone 8 days without rain (1 mm or more) when it started. Rain came after the fire: 6.4 mm on 5 Mar.

This area had burned before

32% of the perimeter overlaps earlier fires recorded since 2016: 88 ha in 2020, 12 ha in 2021, 10 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 101 ha that had burned before.

What happened to each town

  1. Bolvadin 43,398 inhabitants · 13.8 km from the centre where it started
    311 ha reached on 24 Feb
    0.3 %

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

  • Other land cover100 %

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)
24 Feb 15.5 °C 39 % 19 km/h 0.0 mm Very low 3
25 Feb after 16.0 °C 40 % 20 km/h 0.0 mm Very low 3
26 Feb after 13.7 °C 45 % 27 km/h 0.0 mm Very low 4
27 Feb after 15.6 °C 48 % 16 km/h 0.0 mm Very low 3
28 Feb after 17.8 °C 32 % 18 km/h 0.0 mm Very low 4
29 Feb after 18.5 °C 29 % 21 km/h 0.0 mm Low 6
1 Mar after 17.9 °C 26 % 27 km/h 0.0 mm Low 7
2 Mar after 16.2 °C 28 % 26 km/h 0.3 mm Low 7
3 Mar after 13.6 °C 38 % 26 km/h 0.7 mm Very low 4
4 Mar after 15.4 °C 31 % 28 km/h 0.5 mm Low 6
5 Mar after 14.0 °C 45 % 64 km/h 6.4 mm Very low 1

Its twins: fires that started in the same weather

It started with an FWI of 2.9, a minimum humidity of 39% and 8 days without rain. Fires in the area that started in weather like this since 2016: 16.

FWI at the start 2.9
Minimum humidity 39 %
Days without rain 8
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Bolvadin fire, January 2020
157 ha 1 day FWI 0.7 Min. humidity 39 % 6 km away, in 2020

First rain (1 mm or more) after it ended: 2.2 mm on 28 Jan.

What happened to them

1 day
median duration
170 ha
median area
0 %
went past 1,000 ha
3.6 mm
rain at the end (median; 13 of 16 had it)

It was 1.8 times larger than the median of its twins and lasted 1 day, against 1 day.

Only 4 of its 16 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 3 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.6 mm.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

6.4 mmfirst rain
5 Mar10 days after it ended
19km/h · max. gust

It was considered over on 24 Feb, and on 5 Mar 6.4 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 13 of 16, with a median of 3.6 mm.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 17 Feb 2024
After · 2 Mar 2024

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 22 February 2024 the air beside the fire reached 20 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak20 µg/m³
Days over the guideline0 days
PM1024 µg/m³
Optical depth0.31
22 Feb24 Feb26 Feb
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 · 2Every 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 Bolvadin fire last?
Copernicus dates it between 24 February 2024 and 24 February 2024: 1 day between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 311 hectares (3.1 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Bolvadin (311 ha, 0.3 %).
Did the fire reach a town?
The fire started in Bolvadin and came within 13.8 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 15.5 °C, humidity dropped to 39 % and gusts hit 19 km/h. The fire danger index (FWI) reached 3, class Very low.
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.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 16. Their median duration was 1 day and their median area 170 ha; 0 % went past 1,000 ha. Only 4 of its 16 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 3 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.6 mm.

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.

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.

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 2 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.

How we build fire pages: methodology

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.