TerraKeepKeeping Earth within its limits
Cloud-free satellite view around Virunga (COD) — tile 2/2, with the finding area outlined
1.00°S 29.52°ENASA Blue Marble via GIBS · outline = finding area
Published

Six hot fire detections inside Virunga (COD) tile 2/2, confirmed by a later satellite pass

Virunga (COD) — tile 2/2 · seen · published

On 27 September 2026 the NOAA-20 VIIRS sensor logged 6 fire detections with radiative power at or above 20 MW inside the watched boundary of Virunga (COD), tile 2/2, over a 2-day window, with the strongest at 117.9 MW. That is dense for the area: 4.68 hot detections per deg² against 2.136 in the surrounding 30 km ring, a ratio of 2.191. A later pass on 29 September picked up 3 hot detections again, which is the independent confirmation. Counts kept climbing on the same rolling window: 19 detections (max 126.5 MW) by 29 September and 23 detections (max 126.5 MW) by 30 September.

What this is not: heat is not clearing, and the rule cannot separate a wildfire from managed, agricultural or legally prescribed burning. The region sits in an El Niño phase with an ONI of 1.8, a setting that favours drier fuel. The boundary used is the watchlist bounding box, not the legal park polygon, so some detections may fall outside the protected area. No natural-event record is logged nearby.

What would change our mind: a burn-permit or prescribed-fire record, a corrected boundary placing the cluster outside the park, or clear-sky imagery showing cropland rather than forest.

Written by AI, then checked by a separate reviewer before publication. Every claim points at the evidence below.

What we saw

  • NASA fire detections — 6 detections with FRP ≥ 20 MW in 2 d (max 117.9 MW). (Sep 27, 2026) See the source ↗
  • NASA fire detections — 19 detections with FRP ≥ 20 MW in 2 d (max 126.5 MW). (Sep 29, 2026) See the source ↗
  • NASA fire detections — 23 detections with FRP ≥ 20 MW in 2 d (max 126.5 MW). (Sep 30, 2026) See the source ↗
  • NASA fire detections — 3 hot detections again on a later pass (2026-09-29). (Sep 29, 2026)

What it might not be

  • Confirmation is a repeat pass from the same sensor, not a fully independent source.
  • Fire type is unknown: wildfire, agricultural burning and legal prescribed burns look alike to VIIRS.
  • The boundary is the watchlist bounding box, not the legal protected-area polygon.
  • VIIRS misses fires under cloud or smoke and short-lived fires between its roughly twice-daily overpasses.
  • A source outage on the NOAA-20 feed would look like calm, not absence of fire.
  • Nothing here speaks to cause or responsibility.
  • Cannot tell wildfire from managed burning, agricultural fire or a legal prescribed burn.
  • VIIRS misses fires under cloud/smoke and small or short-lived fires between overpasses (~2/day).
  • The watched boundary is the watchlist's bbox, not the legal polygon, until protected_areas (M3) lands.
  • S-NPP products end 1 Nov 2026 — the default source is NOAA-20; a source outage looks like calm.
  • Says nothing about cause or responsibility; attribution needs land-tenure and concession layers.

What would change our mind

Newer satellite images that show no change, a correction from the data source, or a reply with evidence from the ground. If that happens, the case is marked “Turned out wrong” — in public — and it stays on this site.

Why this was published

Two separate sources agreed — NASA fire detections, then NASA fire detections — and a reviewer checked the evidence before it went up.

Replies

Know this place? Say what you see. Replies are checked before they appear. No account, no email.

Replies are open on the interactive site (it needs JavaScript).

Ledger id 01a0e6ae-8c99-7467-adae-fbbadc53f8a3

Technical details rule, evidence ids, history, proof
Rule
fires_in_protected v1.0
Tier
T1
Tags
protected-area, discovered, cod, iucn-ii, national-park
Confirmed
Yes — independent revisit signal, 2026-09-29
Rule FP rate
0 % · 0 of 14 decided
Location
1.00°S 29.52°E
Observed
2026-09-27
Opened
2026-09-28 by automatic rule fires_in_protected v1.0
  1. candidate
  2. confirmed
  3. published
  4. resolved

Evidence4

alertfirms-viirs_noaa20_nrt

6 detections with FRP ≥ 20 MW in 2 d (max 117.9 MW).

detections 6maxFrp 117.9
· fires_in v1.0 · firms-viirs_noaa20_nrt-wdpa-166889-2-2026-09-27
Source ↗
alertfirms-viirs_noaa20_nrt

19 detections with FRP ≥ 20 MW in 2 d (max 126.5 MW).

detections 19maxFrp 126.5
· fires_in v1.0 · firms-viirs_noaa20_nrt-wdpa-166889-2-2026-09-29
Source ↗
alertfirms-viirs_noaa20_nrt

23 detections with FRP ≥ 20 MW in 2 d (max 126.5 MW).

detections 23maxFrp 126.5
· fires_in v1.0 · firms-viirs_noaa20_nrt-wdpa-166889-2-2026-09-30
Source ↗
alertfirms-viirs_noaa20_nrtConfirming signal

3 hot detections again on a later pass (2026-09-29).

detections 3
· fires_in v1.0 · firms-viirs_noaa20_nrt-wdpa-166889-2-2026-09-29-revisit

Context

2.19×
AOI vs its 30 km neighbourhood
AOI
4.68
Ring
2.136
Metric
hot detections per deg²
ENSO El Niño · ONI +1.8

Publication gates

  • Evidence — 3 pieces from firms-viirs_noaa20_nrt — met
  • Independent confirmation — a different revisit (firms-viirs_noaa20_nrt), 2026-09-29 — met
  • Human approval — 1 of 1 needed at tier 1 — met
  • Narration — AI-drafted by claude-opus-5 — met
Published
2026-10-01 by AI model
Narrated By
AI model
Reviewed By
AI model
Policy
2026-09-26-autonomous
Note
autonomous publish: narrated by model:claude-opus-5, reviewed by model:claude-sonnet-5 (policy 2026-09-26-autonomous)

History7

  1. status changed → publishedAI model
  2. reviewed → confirmedAI model
  3. narrated → confirmedAI model
  4. evidence added → confirmedautomatic rule fires_in_protected v1.0
  5. evidence added → confirmedautomatic rule fires_in_protected v1.0
  6. confirmed → confirmedautomatic rule fires_in_protected v1.0
  7. created → candidateautomatic rule fires_in_protected v1.0

Verify

Checkpoint
earthdeck.dev/findings/v1 · 1104 entries
Signed root
2d46ab865c78…d5686a
This case
7 signed events
Leaf
#1061 of 1104 — this case’s latest event
Leaf hash
b961af196abf…c34e53
Proof
8-hash audit path
  1. fe79f2ef2f30ff52965a008d3d02befe1067063a78b57b3ef5ad32e31512f887
  2. a2d418ff96b1905d8d461300c94e66cb8101af68aa78f00f94f8ef15a6262fb1
  3. 634cea39ffad8cd6ca64a61a978472de885229f18900b07276d05bb63ebca441
  4. 5d6ad5934cef6c5c6f6e8fd06a2587f724f01181f08383644dcc254da076b662
  5. 19527bd7103a88bea6823300d2b5e27043c6e89e467417e2f10e3f87a795191f
  6. 90a6a1c0a261ad9f9f60e788c08236eafd993fb4cdb01ea5b4a58da45af5ae7a
  7. 64decc40b792c748c3c5f5f534f82c6ed232929960b40f30a38f3d6c3404d29f
  8. 8c9c126ddde5463be4c66b848b31cefa5e2e8b034ab906e8158680a170325566
Last event
2126609d44af…74603d
Note
Checkpoint text
earthdeck.dev/findings/v1
1104
LUarhlx4E7iZHtDXE5BrFb7xMhoCK404KhBp2snVaGo=

— earthdeck TkCXv/sH/NTGvayZVEMmgP9cZnDpvpCaJ9kK+Cb/ptytbf1au9W9DoMBSvoBcBgV8vaL/MaVF3YesXBKf/3RqhoFSgA=

Re-derive every entry, signature and trust rule yourself:

npx -y earthdeck ledger verify --remote https://vitalearth.io