No cluster large enough to call a separate front. The heat is in one piece.
How it got here
Five days of record on a day-55 fire
The record here begins at 4:07pm on 24 Aug and runs to 3:13am on 20 Sep — 635 hours, 46 readings of heat. The fire is on day 55, so the first 50 days are missing: nothing showed up from above until the fire was large enough and the sky over it clear enough for it to be seen.
Day by day 5 days of record
-
Mon24 Aug
First readings
- 2 heat readings
- Heat from 4:07pm to 9:19pm
- Spread 0.5 miles from the recorded point at its furthest
- Burning through the afternoon and night
-
Tue25 Aug
The fiercest day
- 27 heat readings — the most of any day
- Energy 23.2 times the day before
- Heat from 2:15am to 2:25pm
- Spread 0.7 miles from the recorded point at its furthest
- Burning through the pre-dawn, morning and afternoon
-
Wed26 Aug
Cooling off
- 15 heat readings
- Energy 96% down on the day before
- Heat from 1:56am to 3:38am
- Spread 0.5 miles from the recorded point at its furthest
- Burning through the pre-dawn
-
Thu27 Aug
Cooling off
- 1 heat readings
- Energy 97% down on the day before
- Heat from 3:17am to 3:17am
- Spread 0.4 miles from the recorded point at its furthest
- Burning through the pre-dawn
-
Sun20 Seplatest
Today so far
- 1 heat readings
- Energy 1.0 times the day before
- Heat from 3:13am to 3:13am
- Spread 0.5 miles from the recorded point at its furthest
- Burning through the pre-dawn
How the record has moved
Each step is a change on the interagency incident record — acreage, containment or crews — with the date it was reported. No satellite reading is involved.
-
Saturday 22 August
First reported
-
Sunday 23 August
0 acres on record
0 ac -
Monday 24 August
Revised to 0 acres — containment 0%
0 ac · 0% held -
Thursday 27 August
Grew to 0 acres
0 ac · 0% held
None of the perimeter is being reported as held. No crew count has been published for it yet. It has grown from 0 acres when it was first written down to 0 now. Nothing has looked at it for 606 hours, and the record still lists it as active.