Tulkarm fire, July 2026 Tulkarm
The fire started on 23 July 2026 in Tulkarm, Palestinian Territories, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 355 hectares from satellite imagery, spread across a single municipality.
It is the 5th largest in West Bank since 2016 (of 14 with a page). The largest in Palestinian Territories in 2026, of 2.
The power measured by the satellite is low (11.4 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 355ha
- Copernicus perimeter
- Duration
- 1day
- 23 Jul 2026 – 23 Jul 2026
- Municipalities hit
- 1
- governorates
- Started on
- 23 Jul
- 2026
- Heat detections
- 3
- in a single hotspot: 11 MW
- Danger at start
- 31
- High · FWI index
- Energy released
- 17MW
- sum of detected power
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 more than two months without rain (1 mm or more) when it started.
This area had burned before
49% of the perimeter overlaps earlier fires recorded since 2016: 173 ha in 2024.
What happened to each town
-
Tulkarm where it started354 ha reached on 24 Jul1.4 %
Burnt area inside each municipality, from crossing the official 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.
What burned
- Other natural land97 %
- Agricultural areas2.6 %
- Mixed forest0.6 %
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) |
|---|---|---|---|---|---|
| 23 Jul | 33.5 °C | 50 % | 43 km/h | 0.0 mm | High 31 |
| 24 Jul after | 31.7 °C | 51 % | 46 km/h | 0.0 mm | High 32 |
| 25 Jul after | 32.3 °C | 37 % | 38 km/h | 0.0 mm | High 31 |
| 26 Jul after | 31.7 °C | 44 % | 40 km/h | 0.0 mm | High 33 |
| 27 Jul after | 32.5 °C | 47 % | 40 km/h | 0.0 mm | High 33 |
| 28 Jul after | 32.4 °C | 48 % | 42 km/h | 0.0 mm | High 33 |
| 29 Jul after | 33.0 °C | 51 % | 38 km/h | 0.0 mm | High 30 |
| 30 Jul after | 34.2 °C | 44 % | 37 km/h | 0.0 mm | High 30 |
| 31 Jul after | 34.2 °C | 47 % | 35 km/h | 0.0 mm | High 29 |
| 1 Aug after | 35.0 °C | 43 % | 41 km/h | 0.0 mm | High 32 |
| 2 Aug after | 36.0 °C | 32 % | 47 km/h | 0.0 mm | Very high 40 |
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 23 July 2026 the air beside the fire reached 21 µg/m³ of PM2.5. That day averaged 16: 1.1 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 · 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 Tulkarm fire last?
- Copernicus dates it between 23 July 2026 and 23 July 2026: 1 day between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 355 hectares (3.6 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Tulkarm (354 ha, 1.4 %).
- What was the weather like?
- During the fire the temperature reached 33.5 °C, humidity dropped to 50 % and gusts hit 43 km/h. The fire danger index (FWI) reached 31, class High.
- Where does this data come from?
- From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Palestinian Territories (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: 102
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
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 ADM2 (Creative Commons Attribution 4.0 (CC BY 4.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.