Burning 4.9 miles north of Sprague River and 14.6 miles north-west of Beatty, since Saturday 26 September.
The fire sits 68 miles from Medford and 107 miles from Bend.
0
acres burned so far
18
days burning so far
—
no share of the perimeter reported held yet
The picture as of 9:09am today
The 383 Fire is still listed as active, and has not been looked at lately. The last heat was seen 18 hours ago.
No fresh look at this fire for 18 hours. Everything on the map below was seen before then.
Heat in the last dayHigher ground pale, valleys darkWhere another fire is recorded
18hours
since anything was last seen giving off heat — about 3:35pm on Wednesday, local time.
2readings
of heat in the last day. There is not yet an earlier stretch of record to compare that against.
6.2miles
is how close the heat has come to Sprague River at any point in the record. In the last day the nearest heat has been 6.2 miles from it, and the closest this fire has come to Beatty is 15.7 miles, 15.7 in the last day. The two figures are the same because the record is barely a day long: the last day is very nearly all of it.
1.8miles
is the furthest any heat has been seen from the point on the
official record — the width of the ground involved so far.
Six other fires are burning inside the same view. 344 Fire started on Monday 7 September, 3.0 miles west, and has reached 0 acres. 349 Fire started on Thursday 10 September, 2.3 miles south-east, and has reached 0 acres. 358 Fire started on Thursday 17 September, 2.2 miles north-east, and has reached 0 acres. 381 Fire started 299 minutes before this one, 1.0 miles east, and has reached 0 acres. Forty Four Fire started on Wednesday 14 October, 1.5 miles north-west, and has reached 9 acres. Nfca #24 Fire started on Tuesday 8 September, 2.2 miles south-east, and has reached 0 acres. Their heat is counted against them, not against this fire, and the pale rings on the map mark where they are recorded.
One larger fire is burning outside this frame: Wrights Spring Fire 10.5 miles west at 55,134 acres. None of their heat is counted here.
Smoke has been recorded lying over this ground two times so far. The thickest of it was thin between 1:10pm and 4:30pm local time. The last of those windows closed 185 hours ago, so what is overhead now is not known.
Where the heat is
No cluster large enough to call a separate front. The heat is in one piece.
Conditions measured 7.6 miles from the fire: 49°F, air at 51% humidity, a 11 mph wind out of the south-east.
How it got here
One day of record on a day-20 fire
The record here begins at 3:37pm on 14 Oct and runs to 3:37pm on 14 Oct — 0 hours, 2 readings of heat. The fire is on day 20, so the first 19 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. There is no long arc to draw yet. What follows is what has actually happened.
The whole record, 7 frames at
1 hour
a frame. The bar along the bottom is energy released; the moving line is the clock.
Hour by hour local time
Wed 3:00pmWed 3:00pm
Each bar is one hour of local time, sized by how much energy the
fire gave off in it. This fire is too young for a day-against-day comparison to say
anything, so the hours are shown instead.
Day by day 1 day of record
Wed14 Octlatest
First readings
2 heat readings
Heat from 3:37pm to 3:37pm
Spread 1.8 miles from the recorded point at its furthest
Burning through the afternoon
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 26 September
First reported
Saturday 26 September
0 acres on record
0 ac
No containment figure has been reported for it yet. 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 18 hours, and the record still lists it as active.
