Burned area
satellite only1,196ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 16 Feb 2020 – 25 Feb 2020
+− cross-check
No official record is matched to this page to compare it with.
PH · Philippines · –
Kibungan fire, February 2020 Kibungan, Atok
Out · last detection 25 Feb 2020, 17:13 UTC
The fire started on 16 February 2020 in Kibungan, Philippines, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,196 hectares from heat detections, spread across 2 municipalities.
It is the 21th largest in CAR since 2016 (of 29 with a page). Number 4 in Philippines in 2020, of 10.
The power measured by the satellite is low (19.4 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-25matches 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 only10days
16 Feb 2020 to 25 Feb 2020: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 25 Feb 2020, 17:13 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 only16 Feb 2020
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 16 Feb 2020
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only35
VIIRS detections at 375 m. Most intense hotspot: 19 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 16 Feb 2020 – 25 Feb 2020
+− 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 only233MW
Total radiative power on 23 February 2020; hotspots that day: 20.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 23 Feb 2020
+− 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
model1.8FWI · very low
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 7.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 16 Feb 2020, 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
model21.9°C · 67% RH
High of 21.9 °C and minimum humidity of 67% on 16 February 2020; gusts of 34 km/h on 23 February 2020.
- Source
- weather model at the fire’s grid cell
- Date
- 16 Feb 2020 – 25 Feb 2020
- 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.
Living inside
model≈ 200people
Estimated residents inside the perimeter and 0.51 ha of built-up area (100 m grid, epoch 2020).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
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
-
logStart date: 22 February 2020 → 16 February 2020.
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 25 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
- 1,196 ha
- Dates
- 16 Feb 2020 – 25 Feb 2020
- Name
- Kibungan
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/kibungan-2020-02?v=2026-10-25A 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 kibungan-2020-02.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020-02-16 | 2 | 3 | 21.9 | 15.5 | 67 | 6.4 | 30.2 | 1.2 | 1.8 | muy_bajo | 1 |
| 2020-02-17 | 0 | 0 | 19.9 | 14.5 | 71 | 5.8 | 24.8 | 1.8 | 0.7 | muy_bajo | 1 |
| 2020-02-18 | 0 | 0 | 19.4 | 14.3 | 61 | 7.3 | 29.2 | 0 | 1.6 | muy_bajo | 1 |
| 2020-02-19 | 2 | 35 | 19.6 | 12.1 | 63 | 7.2 | 27.7 | 0.6 | 2.4 | muy_bajo | 1 |
| 2020-02-20 | 0 | 0 | 20.6 | 9.8 | 58 | 7.2 | 27.7 | 0 | 3.9 | muy_bajo | 1 |
| 2020-02-21 | 0 | 0 | 20.6 | 9.7 | 56 | 8 | 33.1 | 0 | 5.3 | bajo | 1 |
| 2020-02-22 | 4 | 4 | 21.3 | 11.5 | 54 | 7.6 | 30.2 | 0 | 6.1 | bajo | 1 |
| 2020-02-23 | 20 | 233 | 20 | 10.1 | 61 | 8.3 | 33.8 | 0.1 | 6.4 | bajo | 1 |
| 2020-02-24 | 2 | 2 | 20.9 | 14.8 | 58 | 7.2 | 31.3 | 0.2 | 6.3 | bajo | 1 |
| 2020-02-25 | 5 | 16 | 20.9 | 13 | 62 | 6.9 | 30.6 | 0.6 | 5.2 | bajo | 1 |
| 2020-02-26 | 0 | 0 | 21.8 | 11 | 54 | 5.4 | 27 | 0.2 | 6 | bajo | 0 |
| 2020-02-27 | 0 | 0 | 20.7 | 14.4 | 61 | 5.8 | 27.4 | 0 | 6.3 | bajo | 0 |
| 2020-02-28 | 0 | 0 | 22 | 11.6 | 55 | 8 | 27.4 | 0 | 7.3 | bajo | 0 |
| 2020-02-29 | 0 | 0 | 22.1 | 11.6 | 62 | 4.7 | 25.9 | 0.7 | 4.7 | muy_bajo | 0 |
| 2020-03-01 | 0 | 0 | 22.2 | 14.6 | 63 | 6.5 | 29.5 | 0.1 | 5.7 | bajo | 0 |
| 2020-03-02 | 0 | 0 | 22.1 | 14.6 | 58 | 4.4 | 25.6 | 0 | 6.1 | bajo | 0 |
| 2020-03-03 | 0 | 0 | 21.7 | 12.8 | 52 | 6.8 | 25.9 | 0 | 7.7 | bajo | 0 |
| 2020-03-04 | 0 | 0 | 21.8 | 13.5 | 59 | 5.4 | 26.3 | 0 | 7.5 | bajo | 0 |
| 2020-03-05 | 0 | 0 | 22 | 15.8 | 60 | 5.8 | 27.4 | 0.3 | 7.8 | bajo | 0 |
| 2020-03-06 | 0 | 0 | 22 | 14.9 | 66 | 4.5 | 25.9 | 0.9 | 3.9 | muy_bajo | 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: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 1,196ha
- GWIS perimeter (Copernicus)
- Duration
- 10days
- 16 Feb 2020 – 25 Feb 2020
- Municipalities hit
- 2
- municipalities
- Started on
- 16 Feb
- 2020
- Heat detections
- 35
- in a single hotspot: 19 MW
- Danger at start
- 2
- Very low · FWI index
- Average daily power
- 48MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
16 Feb25 Feb
25 Feb 2020
How it evolved, day by day
16 Feb
23 Feb
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
22°high
34km/h · peak gust
54%lowest humidity
It had gone 7 days without rain (1 mm or more) when it started.
This area had burned before
14% of the perimeter overlaps earlier fires recorded since 2016: 169 ha in 2019.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Kibungan where it started787 ha reached on 19 Feb4.7 %
-
416 ha reached on 16 Feb2.3 %
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 2020Built-up area0.51 ha
Residents≈ 200
Inside the perimeter there were about 0.51 hectares of built-up land and about 200 residents (GHSL 2020, 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.
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) |
|---|---|---|---|---|---|
| 16 Feb | 21.9 °C | 67 % | 30 km/h | 1.2 mm | Very low 2 |
| 17 Feb | 19.9 °C | 71 % | 25 km/h | 1.8 mm | Very low 1 |
| 18 Feb | 19.4 °C | 61 % | 29 km/h | 0.0 mm | Very low 2 |
| 19 Feb | 19.6 °C | 63 % | 28 km/h | 0.6 mm | Very low 2 |
| 20 Feb | 20.6 °C | 58 % | 28 km/h | 0.0 mm | Very low 4 |
| 21 Feb | 20.6 °C | 56 % | 33 km/h | 0.0 mm | Low 5 |
| 22 Feb | 21.3 °C | 54 % | 30 km/h | 0.0 mm | Low 6 |
| 23 Feb | 20.0 °C | 61 % | 34 km/h | 0.1 mm | Low 6 |
| 24 Feb | 20.9 °C | 58 % | 31 km/h | 0.2 mm | Low 6 |
| 25 Feb | 20.9 °C | 62 % | 31 km/h | 0.6 mm | Low 5 |
| 26 Feb after | 21.8 °C | 54 % | 27 km/h | 0.2 mm | Low 6 |
| 27 Feb after | 20.7 °C | 61 % | 27 km/h | 0.0 mm | Low 6 |
| 28 Feb after | 22.0 °C | 55 % | 27 km/h | 0.0 mm | Low 7 |
| 29 Feb after | 22.1 °C | 62 % | 26 km/h | 0.7 mm | Very low 5 |
| 1 Mar after | 22.2 °C | 63 % | 30 km/h | 0.1 mm | Low 6 |
| 2 Mar after | 22.1 °C | 58 % | 26 km/h | 0.0 mm | Low 6 |
| 3 Mar after | 21.7 °C | 52 % | 26 km/h | 0.0 mm | Low 8 |
| 4 Mar after | 21.8 °C | 59 % | 26 km/h | 0.0 mm | Low 8 |
| 5 Mar after | 22.0 °C | 60 % | 27 km/h | 0.3 mm | Low 8 |
| 6 Mar after | 22.0 °C | 66 % | 26 km/h | 0.9 mm | Very low 4 |
Its twins: fires that started in the same weather
It started with an FWI of 1.8, a minimum humidity of 67% and 7 days without rain. Fires in the area that started in weather like this since 2016: 17.
FWI at the start
1.8
Minimum humidity
67 %
Days without rain
7
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Kibungan fire, February 2020
1,196 ha
10 days
FWI 1.8
Min. humidity 67 %
Bokod fire, April 2024
1,120 ha
5 days
FWI 0.1
Min. humidity 67 %
17 km away, in 2024
First rain (1 mm or more) after it ended: 10.4 mm on 29 Apr.
Kibungan fire, March 2023
1,196 ha
5 days
FWI 0.4
Min. humidity 67 %
2 km away, in 2023
First rain (1 mm or more) after it ended: 2.2 mm on 25 Mar.
Itogon fire, February 2024
3,875 ha
10 days
FWI 1.3
Min. humidity 69 %
48 km away, in 2024
First rain (1 mm or more) after it ended: 2.8 mm on 2 Mar.
Sigay fire, March 2023
1,170 ha
4 days
FWI 0.1
Min. humidity 68 %
39 km away, in 2023
First rain (1 mm or more) after it ended: 1.6 mm on 3 Apr.
Bokod fire, March 2023
1,766 ha
4 days
FWI 1.9
Min. humidity 63 %
22 km away, in 2023
First rain (1 mm or more) after it ended: 4.5 mm on 25 Mar.
What happened to them
- 6 days
- median duration
- 1,370 ha
- median area
- 100 %
- went past 1,000 ha
- 3.2 mm
- rain at the end (median; 15 of 17 had it)
It burned an area similar to its twins (1,196 ha against a median of 1,370 ha) and lasted 10 days, against 6 days.
In 2 of 17, 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 3.2 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
34km/h · max. gust
It was considered over on 25 Feb, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 15 of 17, with a median of 3.2 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 · 9 Feb 2020
After · 3 Mar 2020
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.
Detections table · 35Every 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
Frequently asked questions
- How long did the Kibungan fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 16 February 2020 to 25 February 2020 (10 days). The perimeter dates it from 22 February 2020 to 25 February 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,196 hectares (12.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Kibungan (787 ha, 4.7 %); Atok (416 ha, 2.3 %).
- What was the weather like?
- During the fire the temperature reached 21.9 °C, humidity dropped to 54 % and gusts hit 34 km/h. The fire danger index (FWI) reached 6, class Low.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Philippines (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: 17. Their median duration was 6 days and their median area 1,370 ha; 100 % went past 1,000 ha. In 2 of 17, 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 3.2 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: 911 · Emergency number and official warnings
Satellite cross-check
History of this page · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 22 February 2020 → 16 February 2020.
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: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 22 February 2020 to 25 February 2020. 35 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 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
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 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.