Burned area
satellite only248ha
Perimeter published by EFFIS (Copernicus).
- Source
- EFFIS (Copernicus)
- Date
- perimeter revised on 26 January 2022
+− cross-check
No official record is matched to this page to compare it with.
DZ · Algeria · –
Ain Zana fire, 11 July 2017 عين زانة · Ain Zana
Out · last detection 12 Jul 2017, 12:36 UTC
The fire started on 11 July 2017 in Ain Zana, Algeria, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 248 hectares from satellite imagery, spread across a single municipality.
Number 74 in Algeria in 2017, of 173.
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 only2days
11 Jul 2017 to 12 Jul 2017: first and last day with fire on the page.
- Source
- EFFIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 12 Jul 2017, 12:36 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 only11 Jul 2017
First day with fire seen by the satellites or the perimeter.
- Source
- EFFIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 11 Jul 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only7
VIIRS detections at 375 m. Most intense hotspot: 117 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 11 Jul 2017 – 12 Jul 2017
+− 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 only412MW
Total radiative power on 11 July 2017; hotspots that day: 6.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 11 Jul 2017
+− 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
model49.3FWI · very high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 13.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 11 Jul 2017, 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
model40.0°C · 18% RH
High of 40.0 °C and minimum humidity of 18% on 11 July 2017; gusts of 38 km/h on 12 July 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 11 Jul 2017 – 12 Jul 2017
- 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 weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed perimeterEFFIS (Copernicus) revises the perimeter
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
- 248 ha
- Dates
- 11 Jul 2017 – 12 Jul 2017
- Name
- Ain Zana
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/ain-zana-2017-07-2?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 ain-zana-2017-07-2.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-07-11 | 6 | 412 | 40 | 20.9 | 18 | 9.4 | 27.7 | 0 | 49.3 | muy_alto | 1 |
| 2017-07-12 | 1 | 9 | 37.7 | 22.6 | 19 | 13.9 | 37.8 | 0 | 57.4 | extremo | 1 |
| 2017-07-13 | 0 | 0 | 33.8 | 21.1 | 28 | 14.6 | 41.4 | 0 | 54.7 | extremo | 0 |
| 2017-07-14 | 0 | 0 | 31.9 | 18.8 | 30 | 15.5 | 42.5 | 0 | 48.7 | muy_alto | 0 |
| 2017-07-15 | 0 | 0 | 30 | 18.9 | 32 | 16.7 | 45.4 | 0 | 48.4 | muy_alto | 0 |
| 2017-07-16 | 0 | 0 | 28.2 | 18.1 | 44 | 20.1 | 48.2 | 0 | 47 | muy_alto | 0 |
| 2017-07-17 | 0 | 0 | 28.7 | 17.2 | 38 | 14.4 | 39.2 | 0 | 32.2 | alto | 0 |
| 2017-07-18 | 0 | 0 | 32 | 17 | 29 | 12.2 | 32.4 | 0 | 31.1 | alto | 0 |
| 2017-07-19 | 0 | 0 | 33.9 | 20.2 | 25 | 12 | 33.5 | 0.3 | 41.4 | muy_alto | 0 |
| 2017-07-20 | 0 | 0 | 36.1 | 20.5 | 21 | 12.3 | 38.2 | 0 | 46.3 | muy_alto | 0 |
| 2017-07-21 | 0 | 0 | 34.6 | 22.1 | 34 | 9.3 | 29.9 | 0.5 | 40.1 | muy_alto | 0 |
| 2017-07-22 | 0 | 0 | 34.6 | 22.2 | 34 | 10.3 | 33.1 | 0.5 | 27.7 | 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: EFFIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 248ha
- Copernicus perimeter
- Duration
- 2days
- 11 Jul 2017 – 12 Jul 2017
- Municipalities hit
- 1
- communes
- Started on
- 11 Jul
- 2017
- Heat detections
- 7
- in a single hotspot: 117 MW
- Danger at start
- 49
- Very high · FWI index
- Average daily power
- 210MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
11 Jul12 Jul
12 Jul 2017
How it evolved, day by day
11 Jul
12 Jul
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
40°high
38km/h · peak gust
18%lowest humidity
It had gone 13 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
249 ha reached on 11 Jul1.5 %
Burnt area inside each municipality, from crossing the official 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.
What burned
- Other natural land49 %
- Mixed forest46 %
- Broadleaved forest4.8 %
Land cover inside the perimeter as reported by Copernicus EFFIS (outside the Corine Land Cover area).
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) |
|---|---|---|---|---|---|
| 11 Jul | 40.0 °C | 18 % | 28 km/h | 0.0 mm | Very high 49 |
| 12 Jul | 37.7 °C | 19 % | 38 km/h | 0.0 mm | Extreme 57 |
| 13 Jul after | 33.8 °C | 28 % | 41 km/h | 0.0 mm | Extreme 55 |
| 14 Jul after | 31.9 °C | 30 % | 42 km/h | 0.0 mm | Very high 49 |
| 15 Jul after | 30.0 °C | 32 % | 45 km/h | 0.0 mm | Very high 48 |
| 16 Jul after | 28.2 °C | 44 % | 48 km/h | 0.0 mm | Very high 47 |
| 17 Jul after | 28.7 °C | 38 % | 39 km/h | 0.0 mm | High 32 |
| 18 Jul after | 32.0 °C | 29 % | 32 km/h | 0.0 mm | High 31 |
| 19 Jul after | 33.9 °C | 25 % | 34 km/h | 0.3 mm | Very high 41 |
| 20 Jul after | 36.1 °C | 21 % | 38 km/h | 0.0 mm | Very high 46 |
| 21 Jul after | 34.6 °C | 34 % | 30 km/h | 0.5 mm | Very high 40 |
| 22 Jul after | 34.6 °C | 34 % | 33 km/h | 0.5 mm | High 28 |
Its twins: fires that started in the same weather
It started with an FWI of 49.3, a minimum humidity of 18% and 13 days without rain. Fires in the area that started in weather like this since 2016: 26.
FWI at the start
49.3
Minimum humidity
18 %
Days without rain
13
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Ain Zana fire, 11 July 2017
248 ha
2 days
FWI 49.3
Min. humidity 18 %
Ain Zana fire, July 2020
119 ha
2 days
FWI 49.4
Min. humidity 17 %
10 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Ain Charchar fire, July 2020
205 ha
4 days
FWI 49.4
Min. humidity 17 %
87 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Ain Zana fire, July 2020
219 ha
2 days
FWI 48.5
Min. humidity 16 %
2 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Medjez Sfa fire, July 2017
100 ha
2 days
FWI 50.5
Min. humidity 18 %
25 km away, in 2017
First rain (1 mm or more) after it ended: 1.0 mm on 5 Aug.
Chihani fire, August 2017
271 ha
3 days
FWI 45.7
Min. humidity 18 %
29 km away, in 2017
First rain (1 mm or more) after it ended: 1.0 mm on 31 Aug.
What happened to them
- 2 days
- median duration
- 223 ha
- median area
- 8 %
- went past 1,000 ha
- 1.4 mm
- rain at the end (median; 16 of 26 had it)
It burned an area similar to its twins (248 ha against a median of 223 ha) and lasted 2 days, against 2 days.
In 10 of 26, 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 1.4 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
—first rain
—no rain in ten days
38km/h · max. gust
It was considered over on 12 Jul, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 16 of 26, with a median of 1.4 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 2016.
- 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 · 4 Jul 2017
After · 19 Jul 2017
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 11 July 2017 the air beside the fire reached 41 µg/m³ of PM2.5. That day averaged 28: 1.9 times the WHO daily guideline (15).
PM2.5 peak41 µg/m³
Days over the guideline3 days
PM1053 µg/m³
WHO 15
9 Jul11 Jul13 Jul15 Jul
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 · 7Every 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,193 haMedjez Sfa مجاز الصفاءAugust 2022 · 2 days · 20 km away
- 5,857 haBeni Salah BoucheghoufAugust 2021 · 4 days · 27 km away
- 4,488 haBoucheghoufAugust 2017 · 6 days · 27 km away
- 3,550 haساقية سيدي يوسفJuly 2021 · 5 days · 27 km away
- 13,434 haساقية سيدي يوسفJuly 2026 · 10 days · 30 km away
- 6,254 haZaarouria الزعروريةAugust 2022 · 3 days · 30 km away
Frequently asked questions
- How long did the Ain Zana fire last?
- Copernicus dates it between 11 July 2017 and 12 July 2017: 2 days between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 248 hectares (2.5 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Ain Zana (249 ha, 1.5 %).
- Did the fire reach a town?
- The fire started in Ain Zana and came within 3.6 km of its centre. That is the distance from the perimeter, or the nearest hotspot, to the point marking the centre; it does not mean it entered the houses.
- What was the weather like?
- During the fire the temperature reached 40.0 °C, humidity dropped to 18 % and gusts hit 38 km/h. The fire danger index (FWI) reached 57, class Extreme.
- Where does this data come from?
- From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Algeria (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 2016 with a similar FWI, humidity and dry spell: 26. Their median duration was 2 days and their median area 223 ha; 8 % went past 1,000 ha. In 10 of 26, 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 1.4 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: 14 · 1021 · 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: EFFIS (Copernicus), mapped on satellite imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 7 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 and land cover come from the Copernicus European Forest Fire Information System (EFFIS), measured on MODIS and Sentinel-2 imagery and published under CC BY 4.0. 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 (Creative Commons Attribution-ShareAlike 2.0). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from each country’s official figure.