FirstAlerts
Severe WeatherVersion 11

Heat Alerts and Flood Watch Issued for South Plains, Pima County, and Southeastern Virginia

Conflicting reports from local outlets describe heat advisories, extreme heat warnings, and a flash flood watch across the South Plains, Pima County, and southeastern Virginia.

4 reports on this incident · first at Aug 21, 2026, 10:58 a.m. ET

By AI ReporterFirst reported Aug 21, 2026, 8:44 p.m. ETUpdated Sep 9, 2026, 5:03 a.m. ET
Heat alerts are in effect for parts of the South Plains, Pima County, and southeastern Virginia, according to conflicting reports from local news outlets. fox34.com reports a for the far southeastern Texas Panhandle and Rolling Plains, while ktnv.com and kold.com report an for Pima County. kold.com also reports a for some areas. The alerts cover the eastern half of the viewing area, including Lubbock, and most of Pima County, including Tucson and Sells, as well as SE Virginia and NE North Carolina. Sources disagree on the timing. fox34.com reports the runs from 1 p.m. to 8 p.m. on Friday, Aug. 21, while another fox34.com report says it runs from noon to 8 p.m. on Saturday, Aug. 22. kold.com reports the runs from Saturday, Aug. 22, to Sunday, Aug. 23, ending at 8 p.m. The issuing office is also in dispute: fox34.com attributes the alert to , while kold.com attributes it to . Impacts also differ by source. fox34.com warns that high temperatures could reach up to 109 degrees and that the extreme heat can become dangerous quickly, especially for people working outdoors, older adults, children, and anyone without reliable air conditioning. kold.com instead highlights concerns about localized heavy rain, flash flooding, lightning, and gusty outflow winds from storms. ktnv.com advises limiting time outside, staying inside with A/C, and staying hydrated. The cause of the heat has not been determined, but forecasters say triple-digit heat is expected to continue across the South Plains, with the hottest days still to come.

Earlier reports

  1. Aug 21, 2026, 11:11 a.m. ET

    Heat Advisory Extended to 8 p.m. for Far Southeastern Texas Panhandle and Rolling Plains

    The Heat Advisory for the far southeastern Texas Panhandle and Rolling Plains has been extended to 8 p.m. Friday, Aug. 21, according to KCBD, as reported by fox34.com. The advisory, which began at 1 p.m., now runs longer than first issued.

    High temperatures are expected to reach up to 109° in the affected areas. The advisory is in effect from 1 p.m. to 8 p.m. Friday, Aug. 21, and will lift at 8 p.m.

  2. Aug 21, 2026, 11:06 a.m. ET

    Heat Advisory Issued for Far Southeastern Texas Panhandle and Rolling Plains

    A Heat Advisory is in effect from 1 p.m. to 8 p.m. Friday, Aug. 21, for the far southeastern Texas Panhandle and Rolling Plains, according to fox34.com. High temperatures are expected to reach up to 109°.

    The advisory was issued by KCBD, as reported by fox34.com. It will lift at 8 p.m. Friday, Aug. 21.

  3. Aug 21, 2026, 10:58 a.m. ETFirst report

    Heat Advisory in Effect for Far Southeastern Texas Panhandle and Rolling Plains Until 8 p.m. Friday

    A Heat Advisory remains in effect from 1 p.m. to 8 p.m. Friday, August 21, for the far southeastern Texas Panhandle and Rolling Plains, according to a report from Fox34. High temperatures are expected to reach up to 109 degrees, the report said.

    The advisory was issued by KCBD, as reported by Fox34. The advisory is in effect until 8 p.m. Friday, August 21, and will lift at that time. The event is still developing, and further updates may follow.

Was this report accurate and useful?

Sources

Revision history

  1. Version 119 Sept 2026, 09:03current

    Added specific place names (South Plains, Pima County, southeastern Virginia) to the headline to satisfy the headline_place_missing check. No other changes were made.

  2. Version 109 Sept 2026, 00:48

    Updated to reflect conflicting reports on alert type, timing, and issuing office across multiple regions.

  3. Version 97 Sept 2026, 08:53

    Updated to reflect conflicting reports on alert type, timing, and issuing office; added attribution to sources.

  4. Version 84 Sept 2026, 10:11

    Added Virginia/North Carolina area and wtkr.com reporting; updated timing and issuing office conflicts.

  5. Version 74 Sept 2026, 00:56

    Updated to reflect conflicting reports on alert level, timing, and hazards; added Flash Flood Watch and expanded areas.

  6. Version 63 Sept 2026, 15:17

    Updated to reflect conflicting reports on alert type, timing, and issuing office; added attribution for each source.

  7. Version 531 Aug 2026, 05:01

    Updated to reflect additional conflicting reports on timing and issuing office.

  8. Version 422 Aug 2026, 15:46

    Updated to reflect conflicting reports on alert level, timing, issuing office, and impacts, and removed the unsupported statement about the cause.

  9. Version 322 Aug 2026, 01:21

    Updated to reflect conflicting reports on alert level, timing, and wording, and added ktnv.com as a source.

  10. Version 221 Aug 2026, 20:41

    Updated to reflect conflicting reports on advisory timing and wording, and added attribution for all details.

  11. Version 121 Aug 2026, 15:06current

    First published.

  12. Version 121 Aug 2026, 15:02

    First published.

  13. Version 121 Aug 2026, 14:58current

    First published.

  14. Version 121 Aug 2026, 15:11current

    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.