Tailai County fire, 15 March 2026 泰来县 · Tailai County
The fire started on 15 March 2026 in Tailai County, China, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,575 hectares from heat detections, spread across a single municipality.
It is the 257th largest in Heilongjiang Province since 2016 (of 1779 with a page). Number 159 in China in 2026, of 910.
The power measured by the satellite is low (21.4 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
- 3,575ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 15 Mar 2026 – 23 Mar 2026
- Municipalities hit
- 1
- counties
- Started on
- 15 Mar
- 2026
- Heat detections
- 74
- in a single hotspot: 21 MW
- Danger at start
- 4
- Very low · FWI index
- Average daily power
- 61MW
- detected power per day, on average
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 4 days without rain (1 mm or more) when it started. Rain came after the fire: 5.2 mm on 5 Apr.
This area had burned before
81% of the perimeter overlaps earlier fires recorded since 2016: 2,858 ha in 2017, 372 ha in 2019, 74 ha in 2020, 81 ha in 2021, 767 ha in 2024, 797 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 2,880 ha that had burned before.
- 975 ha Tailai County fire, November 2017 1,640 ha in total; the hectares shown are those it shares with this fire
- 481 ha Tailai County fire, March 2025 1,509 ha in total; the hectares shown are those it shares with this fire
- 140 ha Tailai County fire, November 2017 1,646 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Beijing (Dongcheng and Xicheng) boundary: geoBoundaries · Lee Beryman, OpenStreetMap · © OpenStreetMap contributors (ODbL 1.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).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
3,566 ha0.9 %
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 2025Inside the perimeter there were about 17 hectares of built-up land and about 1,300 residents (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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 8 Mar | 0.9 °C | 19 % | 37 km/h | 0.0 mm | Very low 4 |
| 9 Mar | 3.3 °C | 21 % | 29 km/h | 0.0 mm | Very low 4 |
| 10 Mar | 4.9 °C | 23 % | 35 km/h | 0.0 mm | Very low 4 |
| 11 Mar | 4.0 °C | 29 % | 23 km/h | 0.0 mm | Very low 3 |
| 12 Mar | 7.5 °C | 24 % | 41 km/h | 0.0 mm | Very low 5 |
| 13 Mar | 5.9 °C | 28 % | 45 km/h | 0.8 mm | Very low 4 |
| 14 Mar | 2.7 °C | 11 % | 41 km/h | 0.0 mm | Low 6 |
| 15 Mar | 6.9 °C | 13 % | 38 km/h | 0.0 mm | Low 7 |
| 16 Mar | 4.3 °C | 18 % | 27 km/h | 0.0 mm | Low 6 |
| 17 Mar | 8.6 °C | 22 % | 55 km/h | 0.1 mm | Low 10 |
| 18 Mar | -2.8 °C | 17 % | 57 km/h | 0.0 mm | Low 10 |
| 19 Mar | -0.7 °C | 31 % | 46 km/h | 0.1 mm | Low 7 |
| 20 Mar | 5.9 °C | 27 % | 31 km/h | 0.0 mm | Low 6 |
| 21 Mar | 8.2 °C | 29 % | 27 km/h | 0.0 mm | Low 6 |
| 22 Mar | 11.1 °C | 14 % | 38 km/h | 0.0 mm | Low 8 |
| 23 Mar | 13.0 °C | 18 % | 30 km/h | 0.0 mm | Low 7 |
| 24 Mar after | 15.6 °C | 25 % | 48 km/h | 0.0 mm | Moderate 12 |
| 25 Mar after | 15.5 °C | 24 % | 37 km/h | 0.0 mm | Low 10 |
| 26 Mar after | 13.8 °C | 21 % | 36 km/h | 0.0 mm | Low 11 |
| 27 Mar after | 12.9 °C | 22 % | 30 km/h | 0.0 mm | Low 9 |
| 28 Mar after | 13.5 °C | 18 % | 28 km/h | 0.0 mm | Moderate 11 |
| 29 Mar after | 11.0 °C | 21 % | 55 km/h | 0.1 mm | Moderate 18 |
| 30 Mar after | 11.7 °C | 16 % | 31 km/h | 0.0 mm | Moderate 13 |
| 31 Mar after | 15.9 °C | 16 % | 51 km/h | 0.0 mm | Moderate 20 |
| 1 Apr after | 9.4 °C | 14 % | 44 km/h | 0.0 mm | Moderate 17 |
| 2 Apr after | 8.5 °C | 19 % | 35 km/h | 0.0 mm | Moderate 15 |
| 3 Apr after | 5.2 °C | 39 % | 33 km/h | 0.7 mm | Low 8 |
| 4 Apr after | 9.5 °C | 28 % | 39 km/h | 0.0 mm | Low 9 |
| 5 Apr after | 2.8 °C | 49 % | 40 km/h | 5.2 mm | Very low 0 |
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 March 2026 the air beside the fire reached 128 µg/m³ of PM2.5. That day averaged 78: 5.2 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 · 74Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,876 haTailai County 泰来县17 March 2026 · 11 days · 11 km away
- 4,314 haLongjiang County 龙江县16 March 2026 · 8 days · 34 km away
- 13,434 haDorbod-Mongol Autonomous County 杜尔伯特蒙古族自治县October 2025 · 12 days · 38 km away
- 7,524 haDorbod-Mongol Autonomous County 杜尔伯特蒙古族自治县14 February 2024 · 4 days · 38 km away
- 4,582 haZhenlai County 镇赉县28 March 2020 · 2 days · 39 km away
- 30,268 haLongjiang County 龙江县9 April 2020 · 5 days · 40 km away
Frequently asked questions
- How long did the Tailai County fire last?
- GWIS (Copernicus) dates it between 15 March 2026 and 23 March 2026: 9 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,575 hectares (35.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Tailai County (3,566 ha, 0.9 %).
- What was the weather like?
- During the fire the temperature reached 15.6 °C, humidity dropped to 11 % and gusts hit 57 km/h. The fire danger index (FWI) reached 12, class Moderate.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of China (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: 119 · 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: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 74 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 ADM3 (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.