DULUTH, MINNESOTA ~~~ June 5, 2020 (LSN) Superior National Forest fire crews and partners from the Minnesota Department of Natural Resources and local community Fire Departments have been responding to wildfires across the Forest this spring and early summer season. Conditions in northern Minnesota have been dry and continue to be dry even with some short weather events that have brought rain for a few days. As local residents, cabin owners, and visitors spend more time in the outdoors and across the Forest we continue to ask the public to be extra vigilant.
On June 2 a wildfire was reported late in the day near Thursday Bay on Crooked Lake in the Boundary Waters Canoe Area Wilderness (BWCAW). Fire crews responded and actively suppressed the fire keeping it to 5 acres in size. Crews remain on site and are actively mopping up the fire to make sure it is secure. This fire has been determined to be human caused, as an escaped “shore lunch”, not in an approved fire grate at a designated camp site. This recent BWCAW fire serves as a reminder that fire danger conditions remain high in the area and everyone needs to remember basic fire prevention practices including making sure that campfires are not left unattended and are out cold before leaving them. Since April 23rd Forest Service fire crews have responded to 18 fires across the Forest with most fires remaining small from 1/10th of an acre to 1 acre in total size, but ranging in size up to 20 acres. All of the wildfires on the Superior National Forest this season were human caused ignitions.
Please help prevent wildfires and lessen the burden on emergency responders by doing the following:
For information and daily updates on Minnesota wildfire danger, current burning restrictions or to obtain a variance burn permit, visit the Minnesota DNR website at: mndnr.gov/burnrestrictions.
For updates regarding conditions on the Superior National Forest visit www.fs.usda.gov/superior and social media sites www.facebook.com/SuperiorNF/ or https://twitter.com/SuperiorNF
A problem occurred while loading content.