Eaton Fire

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Eaton Fire
Part of the January 2025 Southern California wildfires
File:Eaton Fire 2025-01-08.jpg
Smoke from the fire on January 8, with smoke from the Palisades Fire to its southwest
Location Los Angeles County, California, United States
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Statistics
Date(s)
  • January 7, 2025 (2025-01-07) – present
  • (3 days)
Burned area >14,117 acres (5,713 ha; 22 sq mi; 57 km2)
Cause Unknown
Buildings
destroyed
7000+
Injuries 1+
Fatalities 8[1]

<mapframe width="300" latitude="34.19" text="Interactive perimeter map of Eaton Fire (map data)" longitude="-118.088" height="200" zoom="11">{"type":"ExternalData","service":"page","title":"2025 United States wildfires.map","properties":{"stroke-width":6,"title":"Eaton Fire","stroke":"#ff0000"}}</mapframe> The Eaton Fire is an active wildfire burning in the Altadena area of Los Angeles County in Southern California. It began in the evening on January 7, 2025, in Eaton Canyon in the San Gabriel Mountains.[2] As of January 8, 2025, at 10:36 a.m. PST (UTC–8), the fire had spread to approximately 14,117 acres (5,713 ha). It is one of several fires being driven by the extremely powerful Santa Ana winds, along with the larger Palisades Fire.[3]

Evacuation orders have been sent out to the residents of Altadena, Kinneloa Mesa, La Cañada Flintridge, northern portions of Sierra Madre, Pasadena, Arcadia, and Monrovia, and northeastern portions of Glendale, including most of the San Rafael Hills.[4]

The cause of the fire is under investigation.[5]

Progression

The fire began on January 7, 2025, at 6:15 p.m. PST in Eaton Canyon.[6] It rapidly expanded to over 1,000 acres (400 ha) by 12:07 a.m., fueled by a strong Santa Ana wind event,[7] with wind gusts of up to 100 mph (160 km/h) reported at the nearby Mount Lukens Truck Trail north of La Cañada Flintridge.[8] By 6:30 a.m., the fire had further grown to over 2,227 acres (901 ha), with 0% containment.[7]

The fire continued to grow quickly, and by 10:36 a.m., the fire had grown to over 10,600 acres (4,300 ha), still with 0% containment.[9]

1,527 firefighting personnel have been assigned, along with 79 engines, 8 bulldozers, and 2 water tenders as of 5:00 p.m., January 9.[10]

Cause

Residents of a home abutting Eaton Canyon who were some of the first people to report the fire to authorities told Pasadena Now that the fire began in proximity to electrical towers above the canyon.[6] According to the California Department of Forestry and Fire Protection (Cal Fire), the cause of the fire is under investigation.[5]

File:20240107-Eaton-Fire-Washington-Blvd-Start.jpg
The fire approximately 90 minutes after it began as viewed from the Eaton Canyon reservoir basin, already obscured by heavy smoke

Effects

As of 4:00 a.m. PST on January 8, 52,314 residents and 20,890 structures had been placed under evacuation orders, with a further 46,847 residents and 18,051 structures placed under evacuation warnings. Numerous homes and cars in Altadena were destroyed; up to "90 to 95 percent" of Altadena residents had been evacuated as of 7 a.m..[7]

As of 8:10 a.m. on January 8, one firefighter injury had been reported,[11] over 200 structures had been destroyed,[12] and two civilians had died in the fire, along with "a number of significant injuries."[7] Later in the afternoon, sheriff Robert Luna reported five civilian fatalities in a press conference, and the estimated number of evacuees was raised to over 100,000.[13][7]

By the afternoon of January 8, over 100 animals had been received at the Pasadena Humane animal shelter, many of which had received burn injuries.[14]

The Pasadena Unified School District, the Los Angeles Unified School District, and 23 other surrounding school districts, announced the closure of all schools in the district for Wednesday, January 8 in response to the fire.[15] Closures for January 8 were also announced by Pasadena City College, Fuller Theological Seminary, and the California Institute of Technology.[16][17][18] Many of these closures were extended to Thursday, January 9, and Friday, January 10.[19]

Flames on Mount Wilson may be affecting local broadcast signals; Mount Wilson Observatory has been evacuated.[20] Local broadcasters KLOS-FM, KABC-TV, and PBS SoCal temporarily lost over-the-air signals on January 9.[21] The NASA Jet Propulsion Laboratory (JPL) was also evacuated, with operations for the NASA Deep Space Network moved to a back-up command center offsite.[22]

File:Nat guard chp jan 9 2025.jpg
Law enforcement and National Guard standing guard in northern Pasadena on January 10

By January 10, a 6 p.m. to 6 a.m. curfew was implemented for the evacuated areas of Altadena and roadblocks into the area were put in place by the California National Guard.[23]

Starting on January 10,[24] thousands of volunteers and donators convened at the Santa Anita Park parking lot to assist those displaced and impacted by the fire.[25]

Structures destroyed

About 7,000 structures had been destroyed as of January 10.[26] The fire destroyed residential sections of Altadena that were settled by African-Americans who moved west in the 1920s and 1930s, during the Great Migration, and had created a working and middle-class neighborhood that had persisted for over a century.[27]

Among the historic or culturally significant structures destroyed are:

Actress Mandy Moore lost her home in the wildfire.[34]

<mapframe width="300" latitude="34.195" text="Affected area of Altadena by Eaton Fire (map data)" align="center" longitude="-118.137" height="300" zoom="13">{"type":"ExternalData","service":"page","title":"2025 United States wildfires.map","properties":{"stroke-width":6,"title":"Eaton Fire","stroke":"#ff0000"}}</mapframe>

See also

References

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />
  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 26.2 26.3 26.4 26.5 Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.00 28.01 28.02 28.03 28.04 28.05 28.06 28.07 28.08 28.09 28.10 28.11 28.12 28.13 28.14 Lua error in package.lua at line 80: module 'strict' not found.
  29. 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 30.2 30.3 Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 31.2 Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.