Skip to content
worldfires
PK · Pakistan · →

Sanni Sub fire, September 2023 Sanni Sub

Out · last detection 30 Sept 2023, 21:55 UTC

The fire started on 27 September 2023 in Sanni Sub, Pakistan, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,050 hectares from heat detections, spread across a single municipality.

Number 3 in Pakistan in 2023, of 3.

The power measured by the satellite is low (15.2 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…

Suggestions: Gazg · 2025

Burnt area
1,050ha
GWIS perimeter (Copernicus)
Duration
4days
27 Sept 2023 – 30 Sept 2023
Municipalities hit
1
subdistricts
Started on
27 Sept
2023
Heat detections
54
in a single hotspot: 15 MW
Danger at start
44
Very high · FWI index
Average daily power
97MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 27 Sept30 Sept
30 Sept 2023

How it evolved, day by day

27 Sept 2023 · 7 MW · 1 29 Sept 2023 · 106 MW · 20 30 Sept 2023 · 179 MW · 30
27 Sept 29 Sept 30 Sept

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

It had gone 58 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.

How big is it?

10 km
It burned the equivalent of 0.7% of the area of London (10 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Sanni Sub where it started
    1,053 ha reached on 25 Sept
    0.7 %

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 2025
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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)

Day High Min. humidity Peak gust Rain Danger (FWI)
27 Sept 39.3 °C 21 % 24 km/h 0.0 mm Very high 44
28 Sept 40.0 °C 13 % 27 km/h 0.0 mm Extreme 51
29 Sept 39.6 °C 13 % 20 km/h 0.0 mm Very high 49
30 Sept 37.2 °C 11 % 26 km/h 0.0 mm Very high 50
1 Oct after 37.6 °C 9 % 26 km/h 0.0 mm Extreme 55
2 Oct after 38.3 °C 8 % 28 km/h 0.0 mm Extreme 56
3 Oct after 39.5 °C 9 % 25 km/h 0.0 mm Extreme 55
4 Oct after 41.1 °C 12 % 26 km/h 0.0 mm Extreme 56
5 Oct after 40.9 °C 17 % 26 km/h 0.0 mm Extreme 56
6 Oct after 41.1 °C 24 % 25 km/h 0.0 mm Extreme 51
7 Oct after 41.7 °C 25 % 29 km/h 0.0 mm Very high 49
8 Oct after 40.7 °C 20 % 27 km/h 0.0 mm Very high 48
9 Oct after 40.2 °C 12 % 25 km/h 0.0 mm Extreme 50
10 Oct after 38.3 °C 16 % 31 km/h 0.0 mm Extreme 56

Before and after, from space

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

Before · 20 Sept 2023
After · 7 Oct 2023

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 3 October 2023 the air beside the fire reached 193 µg/m³ of PM2.5. That day averaged 53: 3.5 times the WHO daily guideline (15).

PM2.5 peak193 µg/m³
Days over the guideline9 days
PM10998 µg/m³
Optical depth0.73
252627282930123
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 · 54Every 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 Pakistan ›

Frequently asked questions

How long did the Sanni Sub fire last?
GWIS (Copernicus) dates it between 27 September 2023 and 30 September 2023: 4 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 1,050 hectares (10.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Sanni Sub (1,053 ha, 0.7 %).
What was the weather like?
During the fire the temperature reached 40.0 °C, humidity dropped to 11 % and gusts hit 27 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 Pakistan (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: 1122 · 16 · 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

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. This is not an emergency service: if there is a fire now, call 1122 · 16.

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. 54 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.

How we build fire pages: methodology ›

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.