Burned area
satellite only7,799ha
Perimeter published by NBAC (NRCan).
- Source
- NBAC (NRCan)
- Date
- 1 Aug 2018 – 30 Aug 2018
+− cross-check
No official record is matched to this page to compare it with.
CA · Canada · –
Bulkley-Nechako G fire, 1 August 2018 Bulkley-Nechako G
Out · last detection 30 Aug 2018, 21:47 UTC
The fire started on 1 August 2018 in Bulkley-Nechako G, Canada, and satellites saw it burning for 30 days. Canada’s CWFIS (Natural Resources Canada) mapped an official burnt perimeter of 7,799 hectares from satellite imagery, spread across a single census subdivision.
It is the 108th largest in British Columbia since 2016 (of 343 with a page). Number 47 in Canada in 2018, of 212.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches 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 only30days
1 Aug 2018 to 30 Aug 2018: first and last day with fire on the page.
- Source
- NBAC (NRCan) · NASA FIRMS · VIIRS
- Date
- last detection: 30 Aug 2018, 21:47 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 only1 Aug 2018
First day with fire seen by the satellites or the perimeter.
- Source
- NBAC (NRCan) · NASA FIRMS · VIIRS
- Date
- 1 Aug 2018
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only2,706
VIIRS detections at 375 m. Most intense hotspot: 388 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 1 Aug 2018 – 30 Aug 2018
+− 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 only1,895MW
Total radiative power on 13 August 2018; hotspots that day: 183.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 13 Aug 2018
+− 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
model13.9FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 1.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 1 Aug 2018, 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
model26.8°C · 30% RH
High of 26.8 °C and minimum humidity of 30% on 21 August 2018; gusts of 71 km/h on 9 August 2018.
- Source
- weather model at the fire’s grid cell
- Date
- 1 Aug 2018 – 30 Aug 2018
- 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.
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
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 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
- 7,799 ha
- Dates
- 1 Aug 2018 – 30 Aug 2018
- Name
- Bulkley-Nechako G
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/bulkley-nechako-g-2018-08?v=2026-10-24A 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 bulkley-nechako-g-2018-08.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2018-08-01 | 0 | 0 | 26.6 | 13.2 | 47 | 8.4 | 36.4 | 0.7 | 13.9 | moderado | 1 |
| 2018-08-02 | 28 | 146 | 20.9 | 14.8 | 55 | 15.9 | 54.4 | 0 | 12 | moderado | 1 |
| 2018-08-03 | 26 | 53 | 19.7 | 12.6 | 71 | 8.7 | 42.5 | 3.1 | 2.7 | muy_bajo | 1 |
| 2018-08-04 | 0 | 0 | 22 | 10.4 | 45 | 6.8 | 23 | 0 | 5.3 | bajo | 1 |
| 2018-08-05 | 38 | 278 | 25.1 | 13.2 | 38 | 11.9 | 36 | 0 | 13.8 | moderado | 1 |
| 2018-08-06 | 43 | 105 | 23.6 | 11.4 | 33 | 17.3 | 59 | 0 | 24.9 | alto | 1 |
| 2018-08-07 | 49 | 1,600 | 24.7 | 14.2 | 38 | 12.6 | 44.6 | 0 | 22.8 | alto | 1 |
| 2018-08-08 | 87 | 324 | 24.5 | 13.2 | 42 | 12.1 | 44.6 | 0 | 22.1 | alto | 1 |
| 2018-08-09 | 0 | 0 | 21.5 | 14 | 55 | 12 | 70.9 | 3.2 | 11.3 | moderado | 1 |
| 2018-08-10 | 36 | 219 | 19.1 | 11.9 | 39 | 12.5 | 41.8 | 3.8 | 2.8 | muy_bajo | 1 |
| 2018-08-11 | 94 | 406 | 21.7 | 7.3 | 38 | 8.3 | 23.8 | 0 | 4.3 | muy_bajo | 1 |
| 2018-08-12 | 156 | 672 | 23.1 | 12 | 39 | 12.1 | 41 | 0 | 14.3 | moderado | 1 |
| 2018-08-13 | 183 | 1,895 | 23 | 9 | 47 | 15.2 | 51.1 | 0 | 15.5 | moderado | 1 |
| 2018-08-14 | 214 | 841 | 17 | 12.2 | 69 | 11.5 | 36.4 | 0.1 | 12.5 | moderado | 1 |
| 2018-08-15 | 273 | 880 | 20.3 | 9.1 | 34 | 8.4 | 30.6 | 0 | 13.9 | moderado | 1 |
| 2018-08-16 | 133 | 402 | 20 | 6.2 | 34 | 10.1 | 36.4 | 0 | 18.8 | moderado | 1 |
| 2018-08-17 | 211 | 726 | 18.3 | 6.6 | 45 | 15.9 | 52.9 | 0 | 21.9 | alto | 1 |
| 2018-08-18 | 210 | 582 | 19.7 | 9.3 | 44 | 11 | 39.2 | 0 | 18.7 | moderado | 1 |
| 2018-08-19 | 148 | 414 | 22.8 | 6 | 35 | 7.7 | 26.6 | 0 | 17 | moderado | 1 |
| 2018-08-20 | 119 | 369 | 23.5 | 5.2 | 34 | 7.1 | 23 | 0 | 18.6 | moderado | 1 |
| 2018-08-21 | 177 | 660 | 26.8 | 10.4 | 30 | 13.3 | 42.8 | 0 | 25.3 | alto | 1 |
| 2018-08-22 | 283 | 922 | 18.9 | 10.7 | 57 | 13.3 | 45.4 | 0 | 20.5 | moderado | 1 |
| 2018-08-23 | 75 | 482 | 16.7 | 9.8 | 51 | 13 | 42.8 | 0.5 | 18.1 | moderado | 1 |
| 2018-08-24 | 91 | 192 | 15.6 | 7.1 | 58 | 11.5 | 36.4 | 1.5 | 16.2 | moderado | 1 |
| 2018-08-25 | 0 | 0 | 15.8 | 10.6 | 70 | 13.7 | 44.3 | 1.5 | 2.7 | muy_bajo | 1 |
| 2018-08-26 | 7 | 43 | 18.1 | 9.5 | 46 | 11.8 | 41.4 | 1.1 | 6.9 | bajo | 1 |
| 2018-08-27 | 5 | 6 | 18.5 | 8.5 | 54 | 14.8 | 52.2 | 0 | 9.8 | bajo | 1 |
| 2018-08-28 | 12 | 16 | 17.5 | 10.3 | 78 | 10.6 | 56.5 | 5.9 | 3.9 | muy_bajo | 1 |
| 2018-08-29 | 1 | 2 | 14.3 | 8.6 | 66 | 12.4 | 43.2 | 2.4 | 0.2 | muy_bajo | 1 |
| 2018-08-30 | 7 | 15 | 16.6 | 10.3 | 55 | 14 | 48.6 | 0.1 | 2.6 | muy_bajo | 1 |
| 2018-08-31 | 0 | 0 | 12.5 | 6.8 | 70 | 12.6 | 73.1 | 7.2 | 1.7 | 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: NBAC (NRCan), 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
- 7,799ha
- official perimeter (CWFIS)
- Duration
- 30days
- 1 Aug 2018 – 30 Aug 2018
- Census subdivisions hit
- 1
- municipalities
- Started on
- 1 Aug
- 2018
- Heat detections
- 2,706
- in a single hotspot: 388 MW
- Danger at start
- 14
- Moderate · FWI index
- Average daily power
- 471MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
1 Aug30 Aug
30 Aug 2018
How it evolved, day by day
2 Aug
13 Aug
22 Aug
29 Aug
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
27°high
71km/h · peak gust
30%lowest humidity
It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 7.2 mm on 31 Aug.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
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 census subdivision
-
Bulkley-Nechako G where it started7,932 ha reached on 2 Aug0.5 %
Burnt area inside each census subdivision, from crossing the official 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 area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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) |
|---|---|---|---|---|---|
| 1 Aug | 26.6 °C | 47 % | 36 km/h | 0.7 mm | Moderate 14 |
| 2 Aug | 20.9 °C | 55 % | 54 km/h | 0.0 mm | Moderate 12 |
| 3 Aug | 19.7 °C | 71 % | 42 km/h | 3.1 mm | Very low 3 |
| 4 Aug | 22.0 °C | 45 % | 23 km/h | 0.0 mm | Low 5 |
| 5 Aug | 25.1 °C | 38 % | 36 km/h | 0.0 mm | Moderate 14 |
| 6 Aug | 23.6 °C | 33 % | 59 km/h | 0.0 mm | High 25 |
| 7 Aug | 24.7 °C | 38 % | 45 km/h | 0.0 mm | High 23 |
| 8 Aug | 24.5 °C | 42 % | 45 km/h | 0.0 mm | High 22 |
| 9 Aug | 21.5 °C | 55 % | 71 km/h | 3.2 mm | Moderate 11 |
| 10 Aug | 19.1 °C | 39 % | 42 km/h | 3.8 mm | Very low 3 |
| 11 Aug | 21.7 °C | 38 % | 24 km/h | 0.0 mm | Very low 4 |
| 12 Aug | 23.1 °C | 39 % | 41 km/h | 0.0 mm | Moderate 14 |
| 13 Aug | 23.0 °C | 47 % | 51 km/h | 0.0 mm | Moderate 16 |
| 14 Aug | 17.0 °C | 69 % | 36 km/h | 0.1 mm | Moderate 12 |
| 15 Aug | 20.3 °C | 34 % | 31 km/h | 0.0 mm | Moderate 14 |
| 16 Aug | 20.0 °C | 34 % | 36 km/h | 0.0 mm | Moderate 19 |
| 17 Aug | 18.3 °C | 45 % | 53 km/h | 0.0 mm | High 22 |
| 18 Aug | 19.7 °C | 44 % | 39 km/h | 0.0 mm | Moderate 19 |
| 19 Aug | 22.8 °C | 35 % | 27 km/h | 0.0 mm | Moderate 17 |
| 20 Aug | 23.5 °C | 34 % | 23 km/h | 0.0 mm | Moderate 19 |
| 21 Aug | 26.8 °C | 30 % | 43 km/h | 0.0 mm | High 25 |
| 22 Aug | 18.9 °C | 57 % | 45 km/h | 0.0 mm | Moderate 20 |
| 23 Aug | 16.7 °C | 51 % | 43 km/h | 0.5 mm | Moderate 18 |
| 24 Aug | 15.6 °C | 58 % | 36 km/h | 1.5 mm | Moderate 16 |
| 25 Aug | 15.8 °C | 70 % | 44 km/h | 1.5 mm | Very low 3 |
| 26 Aug | 18.1 °C | 46 % | 41 km/h | 1.1 mm | Low 7 |
| 27 Aug | 18.5 °C | 54 % | 52 km/h | 0.0 mm | Low 10 |
| 28 Aug | 17.5 °C | 78 % | 56 km/h | 5.9 mm | Very low 4 |
| 29 Aug | 14.3 °C | 66 % | 43 km/h | 2.4 mm | Very low 0 |
| 30 Aug | 16.6 °C | 55 % | 49 km/h | 0.1 mm | Very low 3 |
| 31 Aug after | 12.5 °C | 70 % | 73 km/h | 7.2 mm | Very low 2 |
Its twins: fires that started in the same weather
It started with an FWI of 13.9, a minimum humidity of 47% and 1 day without rain. Fires in the area that started in weather like this since 2017: 14.
FWI at the start
13.9
Minimum humidity
47 %
Days without rain
1
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Bulkley-Nechako G fire, 1 August 2018
7,799 ha
30 days
FWI 13.9
Min. humidity 47 %
Peace River B fire, July 2021
7,601 ha
60 days
FWI 8.8
Min. humidity 47 %
170 km away, in 2021
First rain (1 mm or more) after it ended: 2.1 mm on 3 Sept.
Bulkley-Nechako C fire, June 2021
13,990 ha
71 days
FWI 7.2
Min. humidity 44 %
171 km away, in 2021
First rain (1 mm or more) after it ended: 9.2 mm on 15 Aug.
Stikine Region fire, June 2023
13,457 ha
23 days
FWI 9.3
Min. humidity 43 %
211 km away, in 2023
First rain (1 mm or more) after it ended: 8.8 mm on 16 Jul.
Bulkley-Nechako C fire, June 2023
4,209 ha
68 days
FWI 1.9
Min. humidity 46 %
62 km away, in 2023
First rain (1 mm or more) after it ended: 2.8 mm on 30 Aug.
Peace River B fire, June 2021
12,058 ha
46 days
FWI 18.3
Min. humidity 42 %
135 km away, in 2021
First rain (1 mm or more) after it ended: 15.2 mm on 15 Aug.
What happened to them
Fires in the area that started in similar weather: 14. With fewer than 15 we give no figures: they would be more noise than signal.
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
7.2 mmfirst rain
31 Augthe day after it ended
71km/h · max. gust
It was considered over on 30 Aug, and on 31 Aug 7.2 mm fell. We do not know whether the rain or the firefighters put it out.
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 2017.
- 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 · 25 Jul 2018
After · 6 Sept 2018
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 · 2,706Every 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 Bulkley-Nechako G fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 1 August 2018 to 30 August 2018 (30 days). The perimeter dates it from 1 August 2018 to 29 August 2018.
- How much area did it burn?
- The official perimeter mapped by Canada’s CWFIS (Natural Resources Canada) is 7,799 hectares (78.0 km²). Other tallies, such as those of provincial agencies, may give slightly different figures.
- Which census subdivisions burned?
- The fire only entered Bulkley-Nechako G (7,932 ha, 0.5 %).
- What was the weather like?
- During the fire the temperature reached 26.8 °C, humidity dropped to 30 % and gusts hit 71 km/h. The fire danger index (FWI) reached 25, class High.
- Where does this data come from?
- From the official burnt perimeter of Canada’s CWFIS (NBAC, Natural Resources Canada) or, for the current season and until NBAC publishes it, the one rebuilt by GWIS (Copernicus); from NASA FIRMS VIIRS hotspots; and from the administrative boundaries of Canada. 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: 911 · Emergency number and official warnings
- CIFFC · Canadian Interagency Forest Fire Centre ↗
- CWFIS · Canadian Wildland Fire Information System ↗
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 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: NBAC (Natural Resources Canada), official.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 1 August 2018 to 29 August 2018. 2,706 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 is official: it comes from the National Burned Area Composite (NBAC) of the Canadian Wildland Fire Information System (CWFIS), Natural Resources Canada, which maps it on satellite imagery and publishes it under the Open Government Licence – Canada. Until NBAC publishes the current season, this year’s fires carry the perimeter rebuilt from heat detections by GWIS (Copernicus, CC BY 4.0), which is approximate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Census subdivision boundaries come from geoBoundaries ADM3 (Open Data Commons Open Database License 1.0). The area per census subdivision is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.