Burned area
satellite only6,562ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 6 Sept 2022 – 10 Sept 2022
+− cross-check
No official record is matched to this page to compare it with.
KZ · Kazakhstan · –
Semipalatinskiy fire, 6 September 2022 Semipalatinskiy
Out · last detection 10 Sept 2022, 06:34 UTC
The fire started on 6 September 2022 in Semipalatinskiy, Kazakhstan, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,562 hectares from heat detections, spread across a single municipality.
It is the 27th largest in East Kazakhstan Region since 2016 (of 81 with a page). Number 11 in Kazakhstan in 2022, of 42.
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 only5days
6 Sept 2022 to 10 Sept 2022: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 10 Sept 2022, 06:34 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 only6 Sept 2022
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 6 Sept 2022
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only229
VIIRS detections at 375 m. Most intense hotspot: 182 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 6 Sept 2022 – 10 Sept 2022
+− 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 only5,755MW
Total radiative power on 7 September 2022; hotspots that day: 198.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 7 Sept 2022
+− 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
model32.8FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 16.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 6 Sept 2022, 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
model31.3°C · 14% RH
High of 31.3 °C and minimum humidity of 14% on 6 September 2022; gusts of 67 km/h on 7 September 2022.
- Source
- weather model at the fire’s grid cell
- Date
- 6 Sept 2022 – 10 Sept 2022
- 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
- 6,562 ha
- Dates
- 6 Sept 2022 – 10 Sept 2022
- Name
- Semipalatinskiy
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/semipalatinskiy-2022-09?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 semipalatinskiy-2022-09.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2022-09-06 | 30 | 71 | 31.3 | 10.1 | 14 | 12.1 | 26.3 | 0 | 32.8 | alto | 1 |
| 2022-09-07 | 198 | 5,755 | 31 | 14.1 | 16 | 34.6 | 66.6 | 0 | 57 | extremo | 1 |
| 2022-09-08 | 0 | 0 | 16 | 7.3 | 34 | 15.2 | 33.5 | 2.6 | 5.8 | bajo | 1 |
| 2022-09-09 | 0 | 0 | 15.5 | 3.1 | 26 | 12.6 | 29.2 | 0 | 12.1 | moderado | 1 |
| 2022-09-10 | 1 | 4 | 18.3 | 1.5 | 18 | 13.1 | 25.6 | 0 | 21.2 | moderado | 1 |
| 2022-09-11 | 0 | 0 | 17.1 | 7.8 | 25 | 42.3 | 78.5 | 3.6 | 13.9 | moderado | 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
- 6,562ha
- GWIS perimeter (Copernicus)
- Duration
- 5days
- 6 Sept 2022 – 10 Sept 2022
- Municipalities hit
- 1
- districts
- Started on
- 6 Sept
- 2022
- Heat detections
- 229
- in a single hotspot: 182 MW
- Danger at start
- 33
- High · FWI index
- Average daily power
- 1.9GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
6 Sept10 Sept
10 Sept 2022
How it evolved, day by day
6 Sept
7 Sept
10 Sept
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
31°high
67km/h · peak gust
14%lowest humidity
It had gone 16 days without rain (1 mm or more) when it started. Rain came after the fire: 3.6 mm on 11 Sept.
This area had burned before
12% of the perimeter overlaps earlier fires recorded since 2016: 809 ha in 2020.
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
-
Semipalatinskiy where it started6,460 ha reached on 6 Sept0.2 %
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 2020Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, 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.
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 Very dry air: 18 % of the area in Kazakhstan
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 6 Sept | 31.3 °C | 14 % | 26 km/h | 0.0 mm | High 33 |
| 7 Sept | 31.0 °C | 16 % | 67 km/h | 0.0 mm | Extreme 57 |
| 8 Sept | 16.0 °C | 34 % | 34 km/h | 2.6 mm | Low 6 |
| 9 Sept | 15.5 °C | 26 % | 29 km/h | 0.0 mm | Moderate 12 |
| 10 Sept | 18.3 °C | 18 % | 26 km/h | 0.0 mm | Moderate 21 |
| 11 Sept after | 17.1 °C | 25 % | 78 km/h | 3.6 mm | Moderate 14 |
Its twins: fires that started in the same weather
It started with an FWI of 32.8, a minimum humidity of 14% and 16 days without rain. Fires in the area that started in weather like this since 2017: 28.
FWI at the start
32.8
Minimum humidity
14 %
Days without rain
16
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Semipalatinskiy fire, 6 September 2022
6,562 ha
5 days
FWI 32.8
Min. humidity 14 %
Semipalatinskiy fire, October 2019
5,974 ha
7 days
FWI 33.0
Min. humidity 17 %
36 km away, in 2019
First rain (1 mm or more) after it ended: 4.6 mm on 15 Oct.
Zharminskiy fire, October 2018
4,004 ha
2 days
FWI 33.4
Min. humidity 14 %
224 km away, in 2018
First rain (1 mm or more) after it ended: 2.8 mm on 13 Oct.
Bayanaul`skiy fire, September 2019
12,393 ha
1 day
FWI 37.9
Min. humidity 13 %
227 km away, in 2019
First rain (1 mm or more) after it ended: 4.2 mm on 23 Sept.
Ayagozskiy fire, July 2017
5,311 ha
3 days
FWI 40.1
Min. humidity 16 %
166 km away, in 2017
First rain (1 mm or more) after it ended: 5.7 mm on 5 Aug.
Aktogayskiy fire, June 2018
9,087 ha
3 days
FWI 38.3
Min. humidity 11 %
146 km away, in 2018
First rain (1 mm or more) after it ended: 4.5 mm on 25 Jun.
What happened to them
- 3 days
- median duration
- 5,994 ha
- median area
- 14 %
- went past 10,000 ha
- 3.6 mm
- rain at the end (median; 27 of 28 had it)
It burned an area similar to its twins (6,562 ha against a median of 5,994 ha) and lasted 5 days, against 3 days.
In 1 of 28, 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
3.6 mmfirst rain
11 Septthe day after it ended
67km/h · max. gust
It was considered over on 10 Sept, and on 11 Sept 3.6 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 27 of 28, 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 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 · 30 Aug 2022
After · 17 Sept 2022
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 September 2022 the air beside the fire reached 78 µg/m³ of PM2.5. That day averaged 28: 1.9 times the WHO daily guideline (15).
PM2.5 peak78 µg/m³
Days over the guideline2 days
PM10113 µg/m³
Optical depth0.61
WHO 15
4 Sept6 Sept8 Sept10 Sept12 Sept
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 · 229Every 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
- 3,518 haSemipalatinskiy23 September 2019 · 4 days · 27 km away
- 9,054 haSemipalatinskiy23 September 2019 · 4 days · 28 km away
- 14,777 haSemipalatinskiy5 September 2022 · 3 days · 29 km away
- 3,158 haAbayskiy Абай ауданыJuly 2026 · 1 day · 30 km away
- 5,974 haSemipalatinskiyOctober 2019 · 7 days · 36 km away
Frequently asked questions
- How long did the Semipalatinskiy fire last?
- GWIS (Copernicus) dates it between 6 September 2022 and 10 September 2022: 5 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 6,562 hectares (65.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Semipalatinskiy (6,460 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 31.3 °C, humidity dropped to 14 % and gusts hit 67 km/h. The fire danger index (FWI) reached 57, class Extreme.
- 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2017 with a similar FWI, humidity and dry spell: 28. Their median duration was 3 days and their median area 5,994 ha; 14 % went past 10,000 ha. In 1 of 28, 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.
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. 229 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 2020, 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.