Skip to content
worldfires
NP · Nepal · →

Bardibas fire, March 2016 Bardibas, Kamalamai, Lalbandi

Out · last detection 24 Mar 2016, 20:02 UTC

The fire started on 17 March 2016 in Bardibas, Nepal, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,330 hectares from heat detections, spread across 4 municipalities.

It is the 11th largest in Province 2 since 2016 (of 20 with a page). Number 13 in Nepal in 2016, of 47.

The power measured by the satellite is low (10.1 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
4,330ha
GWIS perimeter (Copernicus)
Duration
7days
17 Mar 2016 – 23 Mar 2016
Municipalities hit
4
municipalities
Started on
17 Mar
2016
Heat detections
155
in a single hotspot: 10 MW
Danger at start
21
Moderate · FWI index
Energy released
247MW
sum of detected power

Where it burned

24 Mar 2016
HOTSPOTS BY DAY 17 Mar23 Mar

How it evolved, day by day

1718192021222324

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

The weather it burned in

32°high
41km/h · peak gust
21%lowest humidity

It had gone 2 days without rain (1 mm or more) when it started. Rain came after the fire: 12.2 mm on 27 Mar.

This area had burned before

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

What happened to each town

  1. Bardibas where it started
    1,851 ha reached on 17 Mar
    5.8 %
  2. 1,430 ha reached on 17 Mar
    3.0 %
  3. 752 ha reached on 17 Mar
    3.2 %
  4. 316 ha reached on 21 Mar
    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)
17 Mar 28.5 °C 35 % 30 km/h 0.0 mm Moderate 21
18 Mar 30.0 °C 28 % 32 km/h 0.0 mm High 23
19 Mar 32.0 °C 28 % 30 km/h 0.0 mm High 24
20 Mar 31.8 °C 29 % 29 km/h 0.2 mm High 24
21 Mar 31.5 °C 21 % 41 km/h 0.2 mm High 31
22 Mar 29.7 °C 23 % 31 km/h 0.0 mm High 29
23 Mar 29.9 °C 26 % 31 km/h 0.0 mm High 28
24 Mar after 30.7 °C 29 % 24 km/h 0.0 mm High 27
25 Mar after 32.5 °C 30 % 26 km/h 0.0 mm High 28
26 Mar after 33.1 °C 29 % 28 km/h 0.0 mm High 30
27 Mar after 31.8 °C 47 % 28 km/h 12.2 mm Very low 3

Before and after, from space

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

Before · 10 Mar 2016
After · 30 Mar 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 · 155Every 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 Bardibas fire last?
GWIS (Copernicus) dates it between 17 March 2016 and 23 March 2016: 7 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 4,330 hectares (43.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 4 municipalities: Bardibas (1,851 ha, 5.8 %); Kamalamai (1,430 ha, 3.0 %); Lalbandi (752 ha, 3.2 %); Ishworpur (316 ha, 1.9 %).
What was the weather like?
During the fire the temperature reached 32.5 °C, humidity dropped to 21 % and gusts hit 41 km/h. The fire danger index (FWI) reached 31, class High.
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.