Burned area
satellite only3,340ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 1 Apr 2023 – 3 Apr 2023
+− cross-check
No official record is matched to this page to compare it with.
KZ · Kazakhstan · –
Ayagozskiy fire, April 2023 Alakolskiy, Ayagozskiy
Out · last detection 3 Apr 2023, 07:31 UTC
The fire started on 1 April 2023 in Ayagozskiy, Kazakhstan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,340 hectares from heat detections, spread across 2 municipalities.
It is the 76th largest in East Kazakhstan Region since 2016 (of 81 with a page). Number 10 in Kazakhstan in 2023, of 13.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only3days
1 Apr 2023 to 3 Apr 2023: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 3 Apr 2023, 07:31 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only1 Apr 2023
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 1 Apr 2023
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only109
VIIRS detections at 375 m. Most intense hotspot: 121 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 1 Apr 2023 – 3 Apr 2023
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only1,612MW
Total radiative power on 2 April 2023; hotspots that day: 71.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 2 Apr 2023
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model11.7FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 19.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 1 Apr 2023, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model10.0°C · 23% RH
High of 10.0 °C and minimum humidity of 23% on 3 April 2023; gusts of 60 km/h on 2 April 2023.
- Source
- weather model at the fire’s grid cell
- Date
- 1 Apr 2023 – 3 Apr 2023
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed GHSLPopulation and built-up area computed
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 3,340 ha
- Dates
- 1 Apr 2023 – 3 Apr 2023
- Name
- Ayagozskiy
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/ayagozskiy-2023-04?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire ayagozskiy-2023-04.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2023-04-01 | 28 | 732 | 5 | -5.1 | 26 | 31.7 | 52.2 | 0 | 11.7 | moderado | 1 |
| 2023-04-02 | 71 | 1,612 | 6.9 | -6.7 | 24 | 36.1 | 59.8 | 0 | 13.7 | moderado | 1 |
| 2023-04-03 | 10 | 54 | 10 | -4.8 | 23 | 31.3 | 51.8 | 0 | 13 | moderado | 1 |
| 2023-04-04 | 0 | 0 | 15 | 0.5 | 17 | 40.4 | 64.8 | 0 | 21.5 | alto | 0 |
| 2023-04-05 | 0 | 0 | 18 | -0.3 | 16 | 26.8 | 43.9 | 0 | 17.6 | moderado | 0 |
| 2023-04-06 | 0 | 0 | 19.3 | 0.2 | 18 | 23.6 | 38.9 | 0 | 17.4 | moderado | 0 |
| 2023-04-07 | 0 | 0 | 17 | 4.5 | 40 | 23.8 | 41.4 | 3.4 | 2.2 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 3,340ha
- GWIS perimeter (Copernicus)
- Duration
- 3days
- 1 Apr 2023 – 3 Apr 2023
- Municipalities hit
- 2
- districts
- Started on
- 1 Apr
- 2023
- Heat detections
- 109
- in a single hotspot: 121 MW
- Danger at start
- 12
- Moderate · FWI index
- Average daily power
- 799MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
1 Apr3 Apr
3 Apr 2023
How it evolved, day by day
1 Apr
2 Apr
3 Apr
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
10°high
60km/h · peak gust
23%lowest humidity
It had gone 19 days without rain (1 mm or more) when it started. Rain came after the fire: 3.4 mm on 7 Apr.
This area had burned before
2% of the perimeter overlaps earlier fires recorded since 2016: 58 ha in 2017.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Alakolskiy Алакөл ауданы1,992 ha reached on 2 Apr0.0 %
-
Ayagozskiy where it started1,357 ha reached on 1 Apr0.0 %
Burnt area inside each municipality, from crossing the GWIS 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.
People and buildings inside the perimeter
GHSL 2025Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
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)
Started with Strong wind: 19 % of the area in Kazakhstan
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 1 Apr | 5.0 °C | 26 % | 52 km/h | 0.0 mm | Moderate 12 |
| 2 Apr | 6.9 °C | 24 % | 60 km/h | 0.0 mm | Moderate 14 |
| 3 Apr | 10.0 °C | 23 % | 52 km/h | 0.0 mm | Moderate 13 |
| 4 Apr after | 15.0 °C | 17 % | 65 km/h | 0.0 mm | High 22 |
| 5 Apr after | 18.0 °C | 16 % | 44 km/h | 0.0 mm | Moderate 18 |
| 6 Apr after | 19.3 °C | 18 % | 39 km/h | 0.0 mm | Moderate 17 |
| 7 Apr after | 17.0 °C | 40 % | 41 km/h | 3.4 mm | Very low 2 |
Its twins: fires that started in the same weather
It started with an FWI of 11.7, a minimum humidity of 26% and 19 days without rain. Fires in the area that started in weather like this since 2017: 13.
FWI at the start
11.7
Minimum humidity
26 %
Days without rain
19
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Ayagozskiy fire, April 2023
3,340 ha
3 days
FWI 11.7
Min. humidity 26 %
Ayagozskiy fire, March 2020
4,473 ha
8 days
FWI 7.1
Min. humidity 29 %
25 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Urdzharskiy fire, May 2023
5,259 ha
5 days
FWI 13.6
Min. humidity 29 %
172 km away, in 2023
First rain (1 mm or more) after it ended: 2.7 mm on 20 May.
Sarkandskiy fire, November 2017
3,550 ha
2 days
FWI 8.9
Min. humidity 27 %
189 km away, in 2017
First rain (1 mm or more) after it ended: 6.2 mm on 3 Nov.
Alakolskiy fire, October 2017
6,069 ha
4 days
FWI 16.1
Min. humidity 29 %
157 km away, in 2017
First rain (1 mm or more) after it ended: 7.4 mm on 20 Oct.
Urdzharskiy fire, October 2017
4,589 ha
5 days
FWI 8.0
Min. humidity 20 %
130 km away, in 2017
First rain (1 mm or more) after it ended: 4.6 mm on 18 Oct.
What happened to them
Fires in the area that started in similar weather: 13. With fewer than 15 we give no figures: they would be more noise than signal.
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
3.4 mmfirst rain
7 Apr4 days after it ended
60km/h · max. gust
It was considered over on 3 Apr, and on 7 Apr 3.4 mm fell. We do not know whether the rain or the firefighters put it out.
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 2017.
- 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.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 25 Mar 2023
After · 10 Apr 2023
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 6 April 2023 the air beside the fire reached 18 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
PM2.5 peak18 µg/m³
Days over the guideline0 days
PM1041 µg/m³
Optical depth0.69
WHO 15
30 Mar1 Apr3 Apr5 Apr
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 · 109Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Ayagozskiy fire last?
- GWIS (Copernicus) dates it between 1 April 2023 and 3 April 2023: 3 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 3,340 hectares (33.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Alakolskiy (1,992 ha, 0.0 %); Ayagozskiy (1,357 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 10.0 °C, humidity dropped to 23 % and gusts hit 60 km/h. The fire danger index (FWI) reached 14, class Moderate.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Kazakhstan (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.
RSS Changes to this page With cross-checks and a citable version
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: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 109 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.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. 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 from each country’s official figure.