MediumSatellite heat detectionCS: 68 · v5

Satellite heat detection near Iranduba

CareiroBrazilNASA FIRMS (VIIRS)

Right now

The most recent data we hold from NASA FIRMS (VIIRS) arrived 10 minutes ago, and this point is not in it. We record detections, not passes: an absence is not proof that nothing is there.

Nothing else has been detected within 20 km in the last 24 hours.

Distance and hazards
Only these hazards

Tick none to hear about every hazard.

One message per event, not per detection. We send a confirmation first, and every message carries a link to stop them. We store the address and the place, nothing else.

Recorded by satellite 18 days ago.

A thermal anomaly is a snapshot of one satellite pass, not a record of a fire’s life: we cannot say whether it kept burning after that pass.

It is the 4th strongest of the 19 detections recorded within 20 km of this point since 5 July 2026. The last comparable one was on 12 September 2026. 10 more were recorded here in the fortnight before it.

What the source measured

NASA FIRMS (VIIRS) reported 106 fire pixels with a combined fire radiative power of 1209 MW, at high confidence, 14 km from Iranduba.

The 106 pixels cover about 14.8 km² — that is the footprint of the detection grid at 375 m resolution, not an estimate of how much land burned.

FIRMS does not report burned area, and neither do we.

Urban PEI: 647,172 within a heuristic 50 km radius; not unique people.

Nearby, since 5 July 2026

How we know

One source: NASA FIRMS (VIIRS). Not yet confirmed by a second, independent source.

Our own score for this event is 68 out of 100.

This is our versioned heuristic index, not source severity or a calibrated probability. Urban PEI does not count unique people.

Computed under scoring rules v5. Rows carrying other versions were judged by different rules and are not directly comparable.

Archived as “Critical” under the rule in force until 4 October 2026, which read the radiative power and the people nearby. A satellite sees heat, not an emergency: since then every detection is shown as low or medium; this one as “Medium”.

Event Data

TypeSatellite heat detection
SeverityMedium
Calamity Score (ours)68 / 100
Legacy data-support index0.74/1
Coordinates-3.4030, -60.1516
Nearest CityIranduba (14 km)
Urban exposure index (PEI)647.2K within 50 km
Impact Tiercatastrophic
Timestamp2026-09-15T17:11:00.000Z
Sourcehttps://firms.modaps.eosdis.nasa.gov/map/#d:24hrs;@-60.152,-3.403,9z

Physical priority index · v5. Heuristic priority, not calibrated probability, predictive accuracy or damage. The legacy data-support index combines assigned source support and field availability. Urban PEI is distance-weighted and does not count unique people; zero does not establish that nobody is present. Model cards.

Source and revision timeline

Source: firms. Occurrence: 2026-09-15T17:11:00.000Z.

First archived: 2026-09-15T19:31:16.827Z. Material modification: not recorded.

Retained revisions are prospective; earlier versions may be unavailable. No revision entry does not prove that a record never changed.

Score Breakdown

95
intensity
85
Urban PEI term
0
Scenario weight
48
Recorded reference / batch anomaly

Technical Details

Brightness367
Frp1209.22
PixelCount106
Confidencehigh

Safety Information

A satellite saw heat here. It cannot tell a wildfire from a controlled burn or an industrial flame, and it sees nothing under thick cloud. If you see smoke or flames, call the local emergency number and follow the fire service. Evacuation orders come from local authorities, not from this page.

Series begins 8 March 2026. Comparisons refer to that period only. Collection gap: 14-26 August 2026.

This data is aggregated algorithmically from scientific sources. Not a replacement for official emergency warnings.

Follow this area

Review the area, threshold and delivery channel in your account.

In the news nearby

A list of links found by GDELT for this place and this hazard in the last seven days. External, not ours: we have not read them and do not vouch for them.

No news is listed: GDELT was not available when this page was rendered.

GDELT Project · gdeltproject.org