Burned area
satellite only7,432ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 13 Feb 2026 – 5 Mar 2026
+− cross-check
No official record is matched to this page to compare it with.
ET · Ethiopia · –
Yaso fire, 13 February 2026 Gida Ayana, Yaso, Ibantu
Out · last detection 5 Mar 2026, 10:41 UTC
The fire started on 13 February 2026 in Yaso, Ethiopia, and satellites saw it burning for 21 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,432 hectares from heat detections, spread across 3 municipalities.
Number 14 in Ethiopia in 2026, of 201.
GWIS near-real-time perimeter, from the layer that changed in August 2025: this fire is not compared with fires from earlier years, because since then the GWIS layer gives more and larger perimeters.
Use this data
Compare with…
Suggestions: Yaso · 2017Yaso · 2016Yaso · 2020Yaso · 2021
Use this data
Fire page data · version 2026-10-27matches 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 only21days
13 Feb 2026 to 5 Mar 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 5 Mar 2026, 10:41 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 only13 Feb 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 13 Feb 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only224
VIIRS detections at 375 m. Most intense hotspot: 41 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 13 Feb 2026 – 5 Mar 2026
+− 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 only305MW
Total radiative power on 22 February 2026; hotspots that day: 58.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 22 Feb 2026
+− 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
model46.0FWI · very high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 60.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 13 Feb 2026, 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
model35.8°C · 13% RH
High of 35.8 °C and minimum humidity of 13% on 18 February 2026; gusts of 44 km/h on 19 February 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 13 Feb 2026 – 5 Mar 2026
- 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.
Living inside
model≈ 40people
Estimated residents inside the perimeter and 0.11 ha of built-up area (100 m grid, epoch 2025).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
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 weatherWeather and FWI computed from the ERA5 reanalysis
-
logStart date: 20 February 2026 → 13 February 2026.
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 27 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
- 7,432 ha
- Dates
- 13 Feb 2026 – 5 Mar 2026
- Name
- Yaso
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/yaso-2026-02-6?v=2026-10-27A 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 yaso-2026-02-6.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-02-13 | 5 | 16 | 34.5 | 22.6 | 13 | 12.5 | 40 | 0 | 46 | muy_alto | 1 |
| 2026-02-14 | 0 | 0 | 32.8 | 20.6 | 14 | 11.3 | 40.3 | 0 | 45.1 | muy_alto | 1 |
| 2026-02-15 | 1 | 6 | 35.1 | 20.7 | 14 | 11.6 | 38.9 | 0 | 45.7 | muy_alto | 1 |
| 2026-02-16 | 0 | 0 | 32.7 | 21.2 | 15 | 12.5 | 36 | 0 | 46.9 | muy_alto | 1 |
| 2026-02-17 | 0 | 0 | 34.2 | 20.5 | 18 | 12.7 | 40 | 0 | 47.4 | muy_alto | 1 |
| 2026-02-18 | 0 | 0 | 35.8 | 19.2 | 13 | 13.4 | 40.3 | 0 | 48.5 | muy_alto | 1 |
| 2026-02-19 | 6 | 7 | 34.7 | 20.9 | 15 | 15.3 | 43.6 | 0 | 51 | extremo | 1 |
| 2026-02-20 | 5 | 17 | 33.6 | 20.6 | 18 | 10.4 | 38.5 | 0 | 45.3 | muy_alto | 1 |
| 2026-02-21 | 38 | 151 | 32.6 | 19.5 | 16 | 14.1 | 43.6 | 0 | 49.7 | muy_alto | 1 |
| 2026-02-22 | 58 | 305 | 34.3 | 19.9 | 17 | 14.3 | 41 | 0 | 50.2 | extremo | 1 |
| 2026-02-23 | 27 | 117 | 34.5 | 20.1 | 15 | 14.3 | 40.7 | 0 | 50.5 | extremo | 1 |
| 2026-02-24 | 5 | 35 | 31.7 | 17.2 | 15 | 13.5 | 38.9 | 0 | 49.8 | muy_alto | 1 |
| 2026-02-25 | 2 | 6 | 32.7 | 17.5 | 17 | 13.2 | 41 | 0 | 48.9 | muy_alto | 1 |
| 2026-02-26 | 2 | 14 | 31.5 | 21.2 | 23 | 10 | 35.3 | 0 | 41.2 | muy_alto | 1 |
| 2026-02-27 | 7 | 49 | 31.7 | 20.9 | 21 | 7.5 | 33.1 | 0 | 39 | muy_alto | 1 |
| 2026-02-28 | 15 | 135 | 32 | 21.8 | 18 | 11 | 34.6 | 0 | 42.6 | muy_alto | 1 |
| 2026-03-01 | 14 | 13 | 32.1 | 21.2 | 16 | 11.7 | 33.8 | 0 | 43.6 | muy_alto | 1 |
| 2026-03-02 | 1 | 3 | 32.1 | 18.9 | 14 | 12.9 | 39.6 | 0 | 45.1 | muy_alto | 1 |
| 2026-03-03 | 7 | 13 | 31 | 16.9 | 15 | 14 | 41.8 | 0 | 46.5 | muy_alto | 1 |
| 2026-03-04 | 29 | 168 | 33 | 16.3 | 13 | 13.8 | 40 | 0 | 47.3 | muy_alto | 1 |
| 2026-03-05 | 2 | 9 | 32.8 | 16.3 | 10 | 12.5 | 36.4 | 0 | 48.4 | muy_alto | 1 |
| 2026-03-06 | 0 | 0 | 32.4 | 16.8 | 12 | 13.4 | 40 | 0 | 49.7 | muy_alto | 0 |
| 2026-03-07 | 0 | 0 | 33.2 | 17.6 | 12 | 11.7 | 33.1 | 0 | 48 | muy_alto | 0 |
| 2026-03-08 | 0 | 0 | 33.8 | 18.3 | 12 | 12.4 | 35.3 | 0 | 49 | muy_alto | 0 |
| 2026-03-09 | 0 | 0 | 34.2 | 18.1 | 12 | 13.9 | 40.7 | 0 | 51 | extremo | 0 |
| 2026-03-10 | 0 | 0 | 34.1 | 18.7 | 13 | 12.3 | 34.9 | 0 | 49.4 | muy_alto | 0 |
| 2026-03-11 | 0 | 0 | 31.9 | 19.1 | 18 | 9.5 | 27.4 | 0 | 44.4 | muy_alto | 0 |
| 2026-03-12 | 0 | 0 | 32.9 | 19.8 | 18 | 11.3 | 32.8 | 0 | 46.3 | muy_alto | 0 |
| 2026-03-13 | 0 | 0 | 34.5 | 19.2 | 20 | 7.4 | 25.6 | 0 | 41.9 | muy_alto | 0 |
| 2026-03-14 | 0 | 0 | 35.3 | 20.9 | 14 | 8.1 | 25.6 | 0 | 42.8 | muy_alto | 0 |
| 2026-03-15 | 0 | 0 | 35 | 20.5 | 11 | 10.1 | 37.4 | 0 | 46.6 | muy_alto | 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
- 7,432ha
- GWIS perimeter (Copernicus)
- Duration
- 21days
- 13 Feb 2026 – 5 Mar 2026
- Municipalities hit
- 3
- districts
- Started on
- 13 Feb
- 2026
- Heat detections
- 224
- in a single hotspot: 41 MW
- Danger at start
- 46
- Very high · FWI index
- Average daily power
- 63MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
13 Feb5 Mar
5 Mar 2026
How it evolved, day by day
13 Feb
22 Feb
25 Feb
1 Mar
5 Mar
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
36°high
44km/h · peak gust
10%lowest humidity
It had gone more than two months without rain (1 mm or more) when it started.
This area had burned before
100% of the perimeter overlaps earlier fires recorded since 2016: 5,579 ha in 2016, 5,711 ha in 2017, 6,093 ha in 2019, 4,513 ha in 2020, 3,825 ha in 2021, 780 ha in 2022, 336 ha in 2024, 3,984 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 7,472 ha that had burned before.
- 3,738 ha Yaso fire, January 2017 11,905 ha in total; the hectares shown are those it shares with this fire
- 3,361 ha Yaso fire, January 2016 8,766 ha in total; the hectares shown are those it shares with this fire
- 2,791 ha Yaso fire, February 2020 7,039 ha in total; the hectares shown are those it shares with this fire
- 2,323 ha Yaso fire, January 2021 8,938 ha in total; the hectares shown are those it shares with this fire
- 2,305 ha Yaso fire, January 2019 4,409 ha in total; the hectares shown are those it shares with this fire
- 2,285 ha Yaso fire, February 2025 3,770 ha in total; the hectares shown are those it shares with this fire
- 2,026 ha Gida Ayana fire, February 2016 4,320 ha in total; the hectares shown are those it shares with this fire
- 1,942 ha Gida Ayana fire, February 2019 3,686 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).
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
-
3,873 ha reached on 13 Feb2.2 %
-
Yaso where it started3,259 ha reached on 13 Feb1.2 %
-
354 ha reached on 15 Feb0.4 %
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 area0.11 ha
Residents≈ 40
Inside the perimeter there were about 0.11 hectares of built-up land and about 40 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)
Started with Very dry air: 26 % of the area in Ethiopia 60 days without rain: 37 % of the area in Ethiopia
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 13 Feb | 34.5 °C | 13 % | 40 km/h | 0.0 mm | Very high 46 |
| 14 Feb | 32.8 °C | 14 % | 40 km/h | 0.0 mm | Very high 45 |
| 15 Feb | 35.1 °C | 14 % | 39 km/h | 0.0 mm | Very high 46 |
| 16 Feb | 32.7 °C | 15 % | 36 km/h | 0.0 mm | Very high 47 |
| 17 Feb | 34.2 °C | 18 % | 40 km/h | 0.0 mm | Very high 47 |
| 18 Feb | 35.8 °C | 13 % | 40 km/h | 0.0 mm | Very high 48 |
| 19 Feb | 34.7 °C | 15 % | 44 km/h | 0.0 mm | Extreme 51 |
| 20 Feb | 33.6 °C | 18 % | 38 km/h | 0.0 mm | Very high 45 |
| 21 Feb | 32.6 °C | 16 % | 44 km/h | 0.0 mm | Very high 50 |
| 22 Feb | 34.3 °C | 17 % | 41 km/h | 0.0 mm | Extreme 50 |
| 23 Feb | 34.5 °C | 15 % | 41 km/h | 0.0 mm | Extreme 50 |
| 24 Feb | 31.7 °C | 15 % | 39 km/h | 0.0 mm | Very high 50 |
| 25 Feb | 32.7 °C | 17 % | 41 km/h | 0.0 mm | Very high 49 |
| 26 Feb | 31.5 °C | 23 % | 35 km/h | 0.0 mm | Very high 41 |
| 27 Feb | 31.7 °C | 21 % | 33 km/h | 0.0 mm | Very high 39 |
| 28 Feb | 32.0 °C | 18 % | 35 km/h | 0.0 mm | Very high 43 |
| 1 Mar | 32.1 °C | 16 % | 34 km/h | 0.0 mm | Very high 44 |
| 2 Mar | 32.1 °C | 14 % | 40 km/h | 0.0 mm | Very high 45 |
| 3 Mar | 31.0 °C | 15 % | 42 km/h | 0.0 mm | Very high 46 |
| 4 Mar | 33.0 °C | 13 % | 40 km/h | 0.0 mm | Very high 47 |
| 5 Mar | 32.8 °C | 10 % | 36 km/h | 0.0 mm | Very high 48 |
| 6 Mar after | 32.4 °C | 12 % | 40 km/h | 0.0 mm | Very high 50 |
| 7 Mar after | 33.2 °C | 12 % | 33 km/h | 0.0 mm | Very high 48 |
| 8 Mar after | 33.8 °C | 12 % | 35 km/h | 0.0 mm | Very high 49 |
| 9 Mar after | 34.2 °C | 12 % | 41 km/h | 0.0 mm | Extreme 51 |
| 10 Mar after | 34.1 °C | 13 % | 35 km/h | 0.0 mm | Very high 49 |
| 11 Mar after | 31.9 °C | 18 % | 27 km/h | 0.0 mm | Very high 44 |
| 12 Mar after | 32.9 °C | 18 % | 33 km/h | 0.0 mm | Very high 46 |
| 13 Mar after | 34.5 °C | 20 % | 26 km/h | 0.0 mm | Very high 42 |
| 14 Mar after | 35.3 °C | 14 % | 26 km/h | 0.0 mm | Very high 43 |
| 15 Mar after | 35.0 °C | 11 % | 37 km/h | 0.0 mm | Very high 47 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 6 Feb 2026
After · 12 Mar 2026
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 25 February 2026 the air beside the fire reached 78 µg/m³ of PM2.5. That day averaged 57: 3.8 times the WHO daily guideline (15).
PM2.5 peak78 µg/m³
Days over the guideline19 days
PM10106 µg/m³
Optical depth0.76
WHO 15
18 Feb22 Feb26 Feb2 Mar6 Mar
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 · 224Every 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 Yaso fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 13 February 2026 to 5 March 2026 (21 days). The perimeter dates it from 20 February 2026 to 5 March 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,432 hectares (74.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Gida Ayana (3,873 ha, 2.2 %); Yaso (3,259 ha, 1.2 %); Ibantu (354 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 35.8 °C, humidity dropped to 10 % and gusts hit 44 km/h. The fire danger index (FWI) reached 51, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Ethiopia (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.
Satellite cross-check
History of this page · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 20 February 2026 → 13 February 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 adjusted with the VIIRS detections inside the perimeter, which said 20 February 2026 to 5 March 2026. 224 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.