Burning 0.4 miles west of Days Creek and 6.2 miles north-east of Canyonville, since Saturday 30 May.
The fire sits 47 miles from Medford and 75 miles from Eugene.
0
acres burned so far
137
days burning so far
—
no share of the perimeter reported held yet
The picture as of 9:09am today
The Days Creek Bridge Fire is still listed as active, and has not been looked at lately. Nothing has given off fresh heat for 188 hours.
No fresh look at this fire for 188 hours. Everything on the map below was seen before then.
Heat in the last dayHigher ground pale, valleys darkWhere another fire is recorded
188hours
since anything was last seen giving off heat — about 1:15pm on Wednesday, local time.
0readings
of heat in the last day. There is not yet an earlier stretch of record to compare that against.
1.2miles
is how close the heat has come to Days Creek at any point in the record. In the last day the nearest heat has been None miles from it, and the closest this fire has come to Canyonville is 5.5 miles, None in the last day.
0.9miles
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. Beckworth Fire started on Monday 6 July, 1.7 miles west, and has reached an unrecorded size. Days Creek Cutoff Fire started on Friday 12 June, 2.9 miles north-west, and has reached 0 acres. Dietch Creek Fire started on Friday 15 May, 0.9 miles south, and has reached an unrecorded size. Gazley Rd. Fire started on Tuesday 16 June, 3.6 miles west, and has reached 0 acres. Little Gazley Fire started on Thursday 24 September, 3.9 miles south-west, and has reached an unrecorded size. Packard Gulch Fire started on Sunday 6 September, 3.5 miles west, and has reached an unrecorded size. Their heat is counted against them, not against this fire, and the pale rings on the map mark where they are recorded.
Smoke has been recorded lying over this ground five times so far. The thickest of it was thin between 1:10pm and 4:30pm local time. The last of those windows closed 23 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.
Nothing close enough to the fire has reported the conditions on the ground.
How it got here
One day of record on a day-139 fire
The record here begins at 1:17pm on 7 Oct and runs to 1:17pm on 7 Oct — 0 hours, 1 readings of heat. The fire is on day 139, so the first 138 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 1:00pmWed 1: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
Wed7 Octlatest
First readings
1 heat readings
Heat from 1:17pm to 1:17pm
Spread 0.9 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 30 May
First reported
Monday 31 August
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 188 hours, and the record still lists it as active.
