Skip to content
worldfires
ET · Ethiopia · →

Jawi fire, December 2025 Jawi, Dangura

Out · last detection 8 Jan 2026, 11:31 UTC

The fire started on 30 December 2025 in Jawi, Ethiopia, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,664 hectares from heat detections, spread across 2 municipalities.

It is the 103th largest in Amhara since 2016 (of 171 with a page). Number 72 in Ethiopia in 2025, of 127.

Burnt area
2,664ha
GWIS perimeter (Copernicus)
Duration
9days
30 Dec 2025 – 7 Jan 2026
Municipalities hit
2
districts
Started on
30 Dec
2025
Heat detections
100
in a single hotspot: 116 MW
Danger at start
46
Very high · FWI index
Energy released
1.9GW
sum of detected power

Where it burned

8 Jan 2026
HOTSPOTS BY DAY 30 Dec7 Jan

How it evolved, day by day

30312345678

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
31km/h · peak gust
12%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

66% of the perimeter overlaps earlier fires recorded since 2016: 611 ha in 2016, 355 ha in 2017, 148 ha in 2023, 990 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 1,759 ha that had burned before.

What happened to each town

  1. Jawi where it started
    1,738 ha reached on 24 Dec
    0.5 %
  2. 944 ha reached on 25 Dec
    0.2 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.

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)
30 Dec 32.1 °C 16 % 28 km/h 0.0 mm Very high 46
31 Dec 35.1 °C 14 % 31 km/h 0.0 mm Very high 47
1 Jan 33.8 °C 15 % 28 km/h 0.0 mm Very high 46
2 Jan 34.1 °C 12 % 26 km/h 0.0 mm Very high 44
3 Jan 36.1 °C 14 % 27 km/h 0.0 mm Very high 46
4 Jan 34.4 °C 14 % 25 km/h 0.0 mm Very high 45
5 Jan 34.0 °C 13 % 26 km/h 0.0 mm Very high 46
6 Jan 34.5 °C 16 % 27 km/h 0.0 mm Very high 46
7 Jan 33.2 °C 20 % 26 km/h 0.0 mm Very high 42
8 Jan after 36.1 °C 15 % 27 km/h 0.0 mm Very high 43
9 Jan after 34.4 °C 13 % 25 km/h 0.0 mm Very high 43
10 Jan after 33.2 °C 15 % 25 km/h 0.0 mm Very high 43
11 Jan after 34.1 °C 15 % 27 km/h 0.0 mm Very high 43
12 Jan after 35.7 °C 17 % 27 km/h 0.0 mm Very high 46
13 Jan after 34.4 °C 16 % 27 km/h 0.0 mm Very high 44
14 Jan after 34.8 °C 13 % 26 km/h 0.0 mm Very high 45
15 Jan after 35.1 °C 20 % 31 km/h 0.0 mm Very high 45
16 Jan after 33.9 °C 21 % 33 km/h 0.0 mm Very high 44
17 Jan after 34.4 °C 18 % 27 km/h 0.0 mm Very high 42

Before and after, from space

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

Before · 23 Dec 2025
After · 14 Jan 2026

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 7 January 2026 the air beside the fire reached 29 µg/m³ of PM2.5. That day averaged 19: 1.2 times the WHO daily guideline (15).

PM2.5 peak29 µg/m³
Days over the guideline5 days
PM1030 µg/m³
Optical depth0.35
2829303112345678910
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 · 100Every 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 Ethiopia ›

Frequently asked questions

How long did the Jawi fire last?
GWIS (Copernicus) dates it between 30 December 2025 and 7 January 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 2,664 hectares (26.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Jawi (1,738 ha, 0.5 %); Dangura (944 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 36.1 °C, humidity dropped to 12 % and gusts hit 31 km/h. The fire danger index (FWI) reached 47, class Very high.
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

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.

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.