Idjevan fire, 28 August 2017 Idjevan
The fire started on 28 August 2017 in Idjevan, Armenia, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 374 hectares from heat detections, spread across a single municipality.
It is the 7th largest in Tavush since 2016 (of 17 with a page). Number 21 in Armenia in 2017, of 30.
The power measured by the satellite is low (13.5 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
- 374ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 28 Aug 2017 – 29 Aug 2017
- Municipalities hit
- 1
- municipalities
- Started on
- 28 Aug
- 2017
- Heat detections
- 3
- in a single hotspot: 14 MW
- Danger at start
- 24
- High · FWI index
- Average daily power
- 18MW
- detected power per day, on average
Where it burned
How it evolved, day by day
28 Aug 2017 · 18 MW · 3
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 10 days without rain (1 mm or more) when it started. Rain came after the fire: 3.1 mm on 7 Sept.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Idjevan where it started148 ha0.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.
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) |
|---|---|---|---|---|---|
| 28 Aug | 28.1 °C | 45 % | 29 km/h | 0.0 mm | High 24 |
| 29 Aug | 30.4 °C | 46 % | 26 km/h | 0.0 mm | High 22 |
| 30 Aug after | 29.7 °C | 47 % | 34 km/h | 0.0 mm | High 25 |
| 31 Aug after | 29.8 °C | 46 % | 33 km/h | 0.0 mm | High 24 |
| 1 Sept after | 29.6 °C | 45 % | 35 km/h | 0.0 mm | High 26 |
| 2 Sept after | 28.9 °C | 40 % | 27 km/h | 0.0 mm | High 23 |
| 3 Sept after | 29.3 °C | 40 % | 27 km/h | 0.0 mm | High 24 |
| 4 Sept after | 30.1 °C | 47 % | 24 km/h | 0.0 mm | High 23 |
| 5 Sept after | 30.8 °C | 45 % | 28 km/h | 0.0 mm | High 24 |
| 6 Sept after | 29.9 °C | 49 % | 35 km/h | 0.0 mm | High 25 |
| 7 Sept after | 24.1 °C | 54 % | 53 km/h | 3.1 mm | Low 8 |
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.
Detections table · 3Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Idjevan fire last?
- GWIS (Copernicus) dates it between 28 August 2017 and 29 August 2017: 2 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 374 hectares (3.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Idjevan (148 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 30.4 °C, humidity dropped to 45 % and gusts hit 29 km/h. The fire danger index (FWI) reached 24, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Armenia (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: 911 · 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.
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. 3 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.
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 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.