| Eaton Fire | |
|---|---|
| Part of the January 2025 Southern California wildfires | |
.jpg) Aerial photo of the Eaton Fire on the slopes of Mount Wilson on January 8 | |
| Date(s) |
|
| Location | Los Angeles County, California, United States |
| Coordinates | 34°12′18″N 118°05′17″W / 34.205°N 118.088°W |
| Statistics[1] | |
| Status | Extinguished |
| Burned area | 14,021 acres (5,674 ha) |
| Impacts | |
| Deaths | 17 |
| Non-fatal injuries | 8 |
| Missing people | 24 |
| Evacuated | 100,000+ |
| Structures destroyed | 9,418 (1,071 damaged) |
| Ignition | |
| Cause | Under investigation
|
| Map | |
 Interactive perimeter map of Eaton Fire (map data) | |
  Location of the fire in Greater Los Angeles  The location of the fire in southern California | |
The Eaton Fire was a highly-destructive wildfire in Los Angeles County, Southern California. The fire began on the evening of January 7, 2025, in the Eaton Canyon in the San Gabriel Mountains, and was driven by powerful Santa Ana winds into foothill communities, particularly Altadena. The fire killed at least 17 people and destroyed more than 9,000 buildings, becoming the fifth deadliest and the second most destructive wildfire in the history of the state of California. The cause of the fire is under investigation; news reports and lawsuits have focused on the possible involvement of power lines operated by electrical utility Southern California Edison. The fire was fully contained on January 31 after burning for 24 days.[3]
The Eaton Fire was one of multiple large wildfires in Southern California in January 2025, and burned simultaneously with the deadly and destructive Palisades Fire in the Santa Monica Mountains.
- ^ "Eaton Fire". California Department of Forestry and Fire Protection. January 13, 2025. Retrieved January 13, 2025.
- ^ Baker, Liz; Meyers, Zoe (January 13, 2025). "Lawsuits allege power company involvement in LA wildfires". NPR. Los Angeles & Washington, D.C. Archived from the original on January 14, 2025.
- ^ Cite error: The named reference
nbcnews20250201was invoked but never defined (see the help page).