Loading dispatches...
← Return to NewsroomEconomy
Spokane wildfire destroys 15 homes, forces 1,500 residents to evacuate in Eastern Washington
Breaking
Russia hits second major bridge in Ukraine's capital Kyiv
Strong winds fueled a wildfire that spread into a residential area in eastern Washington, prompting the evacuation of approximately 1,500 residents and destroying at least 15 homes, authorities said on Wednesday.During a press conference, Spokane County Sheriff John Nowels stated that a family member had reported one person missing. However, emergency crews were unable to enter the affected area to search for them because the fire conditions remained too hazardous on Wednesday afternoon, reported AP.“They have a location to look but it’s not safe to look there at the moment,” Nowels stated.According to Sheriff John Nowels, many residents of the densely populated neighbourhoods were forced to evacuate with little warning, often after being alerted by officers going door-to-door. As a result, some people had to leave behind personal belongings and even essential medications.To help residents retrieve critical items, law enforcement officers were escorting individuals back to their homes one at a time on Wednesday. After collecting necessary belongings, residents were then escorted out of the evacuation zone again.Nowels mentioned that 15 homes had been destroyed by the wildfire, though no injuries or fatalities had been recorded.Chandra Fox, deputy director of Spokane County Emergency Management, said the evacuation order affecting approximately 1,500 residents remained in place on Wednesday.“Our concern is for increased winds Wednesday afternoon,” Fox stated.The fire began shortly after noon on Tuesday and rapidly spread uphill, according to Robert Gray, a spokesperson for the local fire district. As wind conditions changed, the flames were pushed toward a nearby residential area, intensifying the threat to homes.The city of Spokane is located about 280 miles (450 kilometers) east of Seattle, close to the Idaho border.Spokane Valley Fire Department reactsJohn Leavell, a battalion chief with the Spokane Valley Fire Department, said he was among the first to notice the fire. While driving near Interstate 90, he spotted a large plume of smoke rising in the distance.“As I approached it, I thought this is going to be a big event — this is going fast. It looked like waves of fire going up the hill," he said.John Leavell discovered a home completely consumed by flames after pulling into a driveway. He immediately alerted nearby emergency agencies, and while the local fire district assumed command of the response, his crew began establishing fire lines to slow the spread of the blaze.Leavell said it was unclear whether the fire originated at the house or if the structure was quickly overtaken by flames. Investigators are still determining the cause.Firefighters from both Washington and Idaho responded to the wildfire using ground crews and aircraft. Despite their efforts, the fire rapidly expanded to about 225 acres (0.35 square miles). According to the National Interagency Fire Center, the blaze was 10% contained by Wednesday morning.As the fire advanced, utility company Avista shut off electricity in the affected area to protect firefighting personnel. Power remained unavailable in some locations on Wednesday.Officials noted that weather conditions had begun to improve, providing a more favorable environment for firefighters battling the blaze.Weather conditions became more favorable for firefighting efforts on Wednesday. According to Rachael Fewkes, a meteorologist with the National Weather Service in Spokane, winds had weakened and were expected to continue decreasing after sunset. Temperatures also cooled slightly, dropping from the mid-80s on Tuesday to around 80 degrees on Wednesday.The Federal Emergency Management Agency (FEMA) announced Wednesday that it had approved Fire Management Assistance Grant funding to help cover the costs of battling the Spokane-area wildfire. A regional FEMA official noted that the blaze had the potential to become a major disaster due to the threats it posed to homes, a school, power infrastructure,
The fireball was visible across portions of New England and quickly became a topic of discussion online, particularly among people in and around Boston. Many residents initially struggled to identify the source of the loud noise, while others shared videos and eyewitness accounts of the bright flash in the sky.Loud Boom And Bright Flash Reported Across RegionAccording to NASA, the meteor entered Earth's atmosphere at an extremely high speed before breaking apart over northeastern Massachusetts and southeastern New Hampshire.The US space agency said the fireball fragmented at approximately 2:06 pm local time on Saturday.NASA deputy news chief Jennifer Dooren told AFP that the meteor was travelling at around 75,000 mph (more than 120,000 kph) and broke apart at an altitude of 40 miles above the ground."The energy released at breakup is estimated to be equivalent to about 300 tons of TNT, which accounts for the loud booms," she said.The explosion produced a bright flash and a sonic boom that was heard across the region. Social media users reported that the noise was powerful enough to shake buildings and homes.Meteor Not Linked To Satellite Or Space DebrisNASA clarified that the object was a natural meteor and not a satellite re-entry or piece of space debris."This fireball was not associated with any currently active meteor shower, but it was a natural object and not a re-entry of space debris or a satellite," Dooren said.Scientists explained that meteors frequently enter Earth's atmosphere and burn up before reaching the ground. However, larger objects can create fireballs and sonic booms when they fragment at high altitudes.Although the explosion released a large amount of energy, it occurred far above the Earth's surface and did not result in impact damage.Experts Spotted Event Through Satellite DataThe event was also detected by weather-monitoring satellites.Nick Stewart, a spaceflight meteorologist, pointed to data from NOAA's GOES-19 satellite shortly after reports of the explosion began emerging online."Reports of an explosion hears around Boston I believe are going to be a rather significant bolide/meteor entering the atmosphere. Very large 'flash' detected by GOES-19 GLM that does not correlate with active thunderstorms," Stewart wrote on X.In a follow-up post, he added, "The flash density product really shows this anomalous 'flash' which is pretty distinctive of a bolide/meteor reentry. east of Boston. This is the likely source of the loud boom/explosion."NASA Shares Details Of The EventNASA later shared additional information on social media.“#MeteorSighting: Eyewitnesses in New England and @NOAA’s GOES-19 satellite reported a bright fireball on Saturday, May 30, at 2:06 p.m EDT accompanied by a loud noise. The meteor appears to have fragmented at an altitude of 40 miles over northeast MA and southeast NH. The energy released at breakup is estimated to be equivalent to about 300 tons of TNT, which accounts for the loud noise. Eyewitness accounts supplied by the American Meteor Society.”The United States Geological Survey (USGS) also addressed the event, describing it as a "widely felt sonic boom from a suspected bolide"."Unlike earthquakes which occur at discrete location in the earth, sonic boom events occur along a linear path in the atmosphere," the agency said.Residents Flood Social Media With ReactionsThe incident prompted numerous reactions from residents across the region, many of whom initially believed the loud noise might have been caused by an explosion or thunderstorm.Several users claimed the boom was strong enough to rattle windows and shake houses, particularly in areas around Boston.Experts noted that when larger meteors explode in the atmosphere, they can generate shockwaves that travel long distances and produce sounds resembling thunder or explosions.Comparisons With The 2013 Chelyabinsk EventWhile the latest meteor created a spectacular display, experts stressed that it was far smaller than some hi
Discussion (0)