Extreme Heat Warning Covers Phoenix, Scottsdale, Tucson and Yuma County
An Extreme Heat Warning runs from 10:00 AM on Aug. 17, 2026, through 8:00 PM on Aug. 21, 2026, taking in Buckeye/Avondale, the Northwest Valley, Scottsdale/Paradise Valley, the Tucson Metro Area and Yuma County.
3 reports on this incident · first at Aug 17, 2026, 10:46 a.m. ET
Earlier reports
Aug 18, 2026, 8:00 p.m. ET
Extreme Heat Warning Extended Across Arizona Through August 21
An Extreme Heat Warning covering broad portions of Arizona has been extended and will run longer than first issued, according to reporting by FOX 10 Phoenix. The warning begins at 10:00 AM on August 17, 2026, and expires at 8:00 PM on August 21, 2026.
The affected areas include Central Phoenix, North Phoenix/Glendale, East Valley, Northwest Valley, Deer Valley, Scottsdale/Paradise Valley, South Mountain/Ahwatukee, Fountain Hills/East Mesa, Cave Creek/New River, Buckeye/Avondale, Aguila Valley, Tonopah Desert, Gila Bend, Sonoran Desert National Monument, Yuma County, Southeast Yuma County, Central La Paz, Parker Valley, Kofa, West Pinal County, Northwest Pinal County, Apache Junction/Gold Canyon, and Southeast Valley/Queen Creek.
Additional regions covered under the warning include South Central Pinal County (including Eloy and Picacho Peak State Park), Southeast Pinal County (including Kearny, Mammoth, and Oracle), Tohono O'odham Nation (including Sells), Western Pima County (including Ajo and Organ Pipe Cactus National Monument), Tucson Metro Area (including Tucson, Green Valley, Marana, and Vail), Upper Gila River and Aravaipa Valleys (including Clifton and Safford), Gila River Valley, and San Carlos.
Aug 17, 2026, 10:46 a.m. ETFirst report
Extreme Heat Warning Set for Phoenix, Tucson and Yuma County Areas Starting August 17
An Extreme Heat Warning has been issued for parts of Arizona, including Central Phoenix, the Tucson Metro Area and Yuma County, according to FOX 10 Phoenix. The warning begins on August 17, 2026, at 10:00 a.m. and expires on August 21, 2026, at 8:00 p.m.
Areas covered by the warning include Buckeye/Avondale, Northwest Valley, Scottsdale/Paradise Valley, Gila River Valley, Deer Valley, Tonopah Desert, Yuma County, Central La Paz, Gila Bend, South Mountain/Ahwatukee, Cave Creek/New River, Aguila Valley, Southeast Yuma County, North Phoenix/Glendale, West Pinal County, Sonoran Desert Natl Monument, East Valley, Kofa, Southeast Valley/Queen Creek, Fountain Hills/East Mesa, Central Phoenix, Northwest Pinal County, Apache Junction/Gold Canyon, Parker Valley, Tohono O'odham Nation, Southeast Pinal County, Western Pima County, Upper Gila River and Aravaipa Valleys, Tucson Metro Area, and South Central Pinal County.
Cities affected by the alert include Sells, Kearny, Mammoth, Oracle, Ajo, Clifton, Safford, Tucson, Green Valley, Marana, Vail, and Eloy.
Was this report accurate and useful?
Sources
Revision history
- Version 319 Aug 2026, 00:22current
Headline now names Phoenix, Scottsdale, Tucson and Yuma County instead of only "Arizona." Dek adds Buckeye/Avondale, Northwest Valley, Scottsdale/Paradise Valley, Tucson Metro Area and Yuma County, and prints the start and end times exactly as given in the record. Lead sentence anchors the alert to specific named areas. Restored the record's exact wording "Sonoran Desert Natl Monument." All attribution to fox10phoenix.com and all listed areas retained unchanged.
- Version 217 Aug 2026, 14:46current
Headline now names specific places from the record (Phoenix, Tucson, Yuma County) instead of the generic "Arizona Areas." Dek expanded to name Buckeye/Avondale, Northwest Valley, Scottsdale/Paradise Valley and the Tucson Metro Area alongside the unchanged dates. First body paragraph now cites the same anchor locations. All figures, dates, times, area names and city names, plus the FOX 10 Phoenix attribution, are unchanged.
- Version 219 Aug 2026, 00:11
Reorganized location lists into distinct regional paragraphs for clarity.
- Version 119 Aug 2026, 00:00current
First published.
- Version 116 Aug 2026, 04:05
First published.
- Version 118 Aug 2026, 23:57
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.