TerraKeepKeeping Earth within its limits
Cloud-free satellite view around Flare field near Purovsky, Yamalo-Nenets Autonomous Okrug (Russia) — 73 registered sites, with the finding area outlined
66.35°N 77.19°ENASA Blue Marble via GIBS · outline = finding area
Published

Persistent night-time heat near Purovsky, Yamalo-Nenets, sits outside the flare registry

Flare field near Purovsky, Yamalo-Nenets Autonomous Okrug (Russia) — 73 registered sites · seen · published

Night-time satellite passes (VIIRS on NOAA-20 and NOAA-21) found 17 heat clusters near Purovsky, Yamalo-Nenets Autonomous Okrug, that burned at 5 MW or more on at least 5 of the 30 nights to 27 September 2026. Of those, 13 sit more than 2 km from any site in the VNF 2023 and 2024 annual flare summaries. The strongest unregistered cluster, at 66.2472, 76.8186, was lit on 25 of the last 30 nights, peaking at 46.45 MW. A later independent pass on 27 September saw heat again at the same spot, at 13.13 MW — that confirms the heat is still there, not what is burning it.

This is not proof of a new gas flare. The same signal can come from an industrial furnace, a refinery or kiln, or from a flare simply too small or too often clouded over to enter the annual registry. Fire radiative power is not a flared volume, and unlit or vented gas leaves no heat trace at all. No operator or owner can be read from a heat cluster.

What would change our mind: a registry or asset record showing an existing facility here; high-resolution imagery of a furnace or plant rather than a flare stack; or the heat ceasing across clear nights.

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

What we saw

  • NASA fire detections — 17 night-time cluster(s) with FRP ≥ 5 MW lit on ≥ 5 of 30 nights (2026-08-29…2026-09-27); new cluster (no VNF 2023 and 2024 site within 2 km) 25 nights, max 46.45 MW at 66.2472, 76.8186. (Sep 26, 2026) See the source ↗
  • NASA fire detections — 15 night-time cluster(s) with FRP ≥ 5 MW lit on ≥ 5 of 30 nights (2026-08-30…2026-09-28); new cluster (no VNF 2023 and 2024 site within 2 km) 25 nights, max 46.45 MW at 66.2472, 76.8186. (Sep 27, 2026) See the source ↗
  • NASA fire detections — 15 night-time cluster(s) with FRP ≥ 5 MW lit on ≥ 5 of 30 nights (2026-08-31…2026-09-29); new cluster (no VNF 2023 and 2024 site within 2 km) 25 nights, max 46.45 MW at 66.2472, 76.8185. (Sep 28, 2026) See the source ↗
  • NASA fire detections — Night-time heat with FRP ≥ 5 MW again at the flagged cluster on a later pass (2026-09-27). (Sep 27, 2026) See the source ↗

What it might not be

  • Thermal sensors cannot separate a gas flare from a furnace, refinery or kiln.
  • "New" only means no VNF 2023/2024 registry site within 2 km; small or cloud-hidden flares are missing from that annual product.
  • Fire radiative power is a single-pixel estimate, not a flared gas volume.
  • Clouds and smoke hide nights, so persistence counts can be under-stated.
  • Only two passes per night (~01:30 local); brief flaring in between is missed.
  • Unlit venting and cold methane releases are invisible here; methane sensors would be needed.
  • No operator or ownership can be inferred from the location.
  • Cannot tell a gas flare from an industrial furnace, refinery, steel or cement kiln, or a volcano — only persistence and the VNF site match argue 'flare'.
  • Cloud and heavy smoke hide nights; a cloudy month under-counts persistence and can look like a flare was turned off.
  • FRP is not flared volume: the VIIRS I-band saturates on the largest flares and the FIRMS FRP is a single-pixel estimate — volumes come only from the VNF annual summary.
  • Venting and unlit (cold) methane releases are invisible to thermal sensors — pair with S5P / EMIT methane.
  • No ownership or operator attribution: a cluster is a place, not a company; attribution needs asset registries (GEM, GGFR) and human review.
  • Two VIIRS passes per night at ~01:30 local; short or intermittent flaring between passes is missed. S-NPP ends Nov 2026, so NOAA-20/21 only.
  • The VNF confirmation is an annual aggregate from a past year: it proves the site is a known flare, not that it flared this week.
  • 'New flaring' only means no site of the VNF 2023/2024 annual summaries within 2 km: a flare too small or too cloudy for EOG's annual product, or a new furnace, also qualifies.

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 01a0e076-ca82-765c-a1e3-cb1bc20f0356

Technical details rule, evidence ids, history, proof
Rule
flaring v1.0
Tier
T2
Tags
flaring, oil-gas, discovered, rus, rus_ups_76.6969e_66.5508n, new-flare
Confirmed
Yes — independent revisit signal, 2026-09-28
Rule FP rate
4.1 % · 2 of 49 decided
Location
66.35°N 77.19°E
Observed
2026-09-26
Opened
2026-09-27 by automatic rule flaring v1.0
  1. candidate
  2. confirmed
  3. published
  4. resolved

Evidence4

alertfirms-viirs_noaa20_nrt+viirs_noaa21_nrt

17 night-time cluster(s) with FRP ≥ 5 MW lit on ≥ 5 of 30 nights (2026-08-29…2026-09-27); new cluster (no VNF 2023 and 2024 site within 2 km) 25 nights, max 46.45 MW at 66.2472, 76.8186.

hotNightDetections 959maxFrp 46.45maxNights 25newClusters 13new_flare 1persistentClusters 17vnfMatched 4vnfTopBcm 0.005vnfTopKm 1.88vnfYear 2024
· flaring v1.0 · firms-flaring-flare-rus-66p6n-76p7e-2026-08-29-2026-09-27
Source ↗
alertfirms-viirs_noaa20_nrt+viirs_noaa21_nrt

15 night-time cluster(s) with FRP ≥ 5 MW lit on ≥ 5 of 30 nights (2026-08-30…2026-09-28); new cluster (no VNF 2023 and 2024 site within 2 km) 25 nights, max 46.45 MW at 66.2472, 76.8186.

hotNightDetections 952maxFrp 46.45maxNights 25newClusters 11new_flare 1persistentClusters 15vnfMatched 4vnfTopBcm 0.005vnfTopKm 1.88vnfYear 2024
· flaring v1.0 · firms-flaring-flare-rus-66p6n-76p7e-2026-08-30-2026-09-28
Source ↗
alertfirms-viirs_noaa20_nrt+viirs_noaa21_nrt

15 night-time cluster(s) with FRP ≥ 5 MW lit on ≥ 5 of 30 nights (2026-08-31…2026-09-29); new cluster (no VNF 2023 and 2024 site within 2 km) 25 nights, max 46.45 MW at 66.2472, 76.8185.

hotNightDetections 930maxFrp 46.45maxNights 25newClusters 11new_flare 1persistentClusters 15vnfMatched 4vnfTopBcm 0.005vnfTopKm 1.88vnfYear 2024
· flaring v1.0 · firms-flaring-flare-rus-66p6n-76p7e-2026-08-31-2026-09-29
Source ↗
alertfirms-viirs_noaa20_nrt+viirs_noaa21_nrtConfirming signal

Night-time heat with FRP ≥ 5 MW again at the flagged cluster on a later pass (2026-09-27).

clusters 1maxFrp 13.13
· flaring v1.0 · firms-flaring-flare-rus-66p6n-76p7e-2026-09-27-revisit
Source ↗

Context

ENSO El Niño · ONI +1.8

Publication gates

  • Evidence — 3 pieces from firms-viirs_noaa20_nrt+viirs_noaa21_nrt — met
  • Independent confirmation — a different revisit (firms-viirs_noaa20_nrt+viirs_noaa21_nrt), 2026-09-28 — met
  • Human approval — 1 of 2 needed at tier 2 — not met
  • Narration — AI-drafted by claude-opus-5 — met
Published
2026-09-29 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 flaring v1.0
  5. evidence added → confirmedautomatic rule flaring v1.0
  6. confirmed → confirmedautomatic rule flaring v1.0
  7. created → candidateautomatic rule flaring v1.0

Verify

Checkpoint
earthdeck.dev/findings/v1 · 854 entries
Signed root
842817ab26f9…f7aace
This case
7 signed events
Leaf
#850 of 854 — this case’s latest event
Leaf hash
20ba75c1bbb6…3c9332
Proof
7-hash audit path
  1. e41ec0106301c553befcce0bc042183ec15d200f6c443cef0d75e72cbec54088
  2. aa4246821d33d5c8fbbe7210e0872f1968a644316c49cb3bc7a186debb5ff2fc
  3. 7d3d4aaec5fcb45234ba41da4675c173cd89e1da62e2fbffc9d04b96b9d692bf
  4. aea69075b9d095d178d2edc12756df29bc1989f8abdec24102807ec1963252c1
  5. 71a85e208c2f8dc340522e3deb6239caf3cc060a8c75b6fd8407e3d5de5d060d
  6. b151de5eaefddf3d1cfc86f94cdbc3995ed5d406a6c0acfc99649a5d48d50794
  7. 5f7580b7f5a7f09ff7675565fb36c19876079a6c101f721419a5a07a7a23b1c1
Last event
76bc951e3677…ba70e6
Note
Checkpoint text
earthdeck.dev/findings/v1
854
hCgXqyb5olIe961gFNy5VKlZ6TWfV4qJ9cOpLH33qs4=

— earthdeck TkCXv4aDxvyvQYJRvBgPtDUJOpfIw1HGQb9y5odOvbIhnVuG/sWj9/xVVekah5GQglG6yeUuq+KqfNruZfqFA2D32Qg=

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

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