Skip to content
worldfires
NP · Nepal · →

Mandavi fire, April 2016 Mandavi, Banglachuli, Sworgadwary

Out · last detection 27 Apr 2016, 06:59 UTC

The fire started on 23 April 2016 in Mandavi, Nepal, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,405 hectares from heat detections, spread across 3 municipalities.

It is the 34th largest in Lumbini since 2016 (of 49 with a page). Number 34 in Nepal in 2016, of 47.

Burnt area
2,405ha
GWIS perimeter (Copernicus)
Duration
5days
23 Apr 2016 – 27 Apr 2016
Municipalities hit
3
municipalities
Started on
23 Apr
2016
Heat detections
91
in a single hotspot: 47 MW
Danger at start
48
Very high · FWI index
Energy released
425MW
sum of detected power

Where it burned

27 Apr 2016
HOTSPOTS BY DAY 23 Apr27 Apr

How it evolved, day by day

23242527

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

37°high
62km/h · peak gust
12%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 5.7 mm on 3 May.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Mandavi where it started
    1,490 ha reached on 23 Apr
    13 %
  2. 500 ha reached on 24 Apr
    2.0 %
  3. 424 ha reached on 25 Apr
    1.9 %

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)
23 Apr 36.3 °C 16 % 58 km/h 0.0 mm Very high 48
24 Apr 35.0 °C 12 % 62 km/h 0.0 mm Extreme 54
25 Apr 35.8 °C 14 % 47 km/h 0.0 mm Very high 48
26 Apr 36.6 °C 14 % 45 km/h 0.0 mm Extreme 50
27 Apr 36.9 °C 16 % 52 km/h 0.0 mm Extreme 51
28 Apr after 37.1 °C 15 % 50 km/h 0.0 mm Extreme 52
29 Apr after 37.3 °C 14 % 50 km/h 0.0 mm Extreme 52
30 Apr after 35.9 °C 14 % 48 km/h 0.0 mm Extreme 51
1 May after 36.6 °C 18 % 43 km/h 0.0 mm Very high 49
2 May after 33.1 °C 37 % 33 km/h 0.0 mm High 35
3 May after 33.1 °C 40 % 36 km/h 5.7 mm Low 6

Before and after, from space

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

Before · 16 Apr 2016
After · 4 May 2016

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 · 91Every 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 Nepal ›

Frequently asked questions

How long did the Mandavi fire last?
GWIS (Copernicus) dates it between 23 April 2016 and 27 April 2016: 5 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,405 hectares (24.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 3 municipalities: Mandavi (1,490 ha, 13 %); Banglachuli (500 ha, 2.0 %); Sworgadwary (424 ha, 1.9 %).
What was the weather like?
During the fire the temperature reached 37.3 °C, humidity dropped to 12 % and gusts hit 62 km/h. The fire danger index (FWI) reached 54, class Extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Nepal (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: 101

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

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 (Creative Commons Attribution-ShareAlike 4.0 International License). 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.