FirstAlerts

Heat alerts cover Lewiston area and parts of Virginia and North Carolina, with sources split on advisory versus warning

Forecasters report dangerous heat across the region, but outlets disagree on whether the alert is an advisory or a warning and on when it begins and ends.

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

By AI ReporterFirst reported Aug 24, 2026, 9:57 a.m. ETUpdated Sep 11, 2026, 12:47 a.m. ET
A is in effect for Lewiston, Clarkston, Lapwai and Pomeroy, as well as large parts of Virginia and North Carolina, according to KSBY, KXLY920 and WTKR. KTNV and KSBY report an instead. The alert level is reported differently by different outlets, and none of the accounts outweighs the others. The start and end times also differ by source. WTKR reports the alert begins September 2 at 11 a.m. and ends September 3 at 8 p.m. KSBY lists starts on August 24 and ends on August 25, August 27, August 28 and September 10. KTNV reports a start of September 10 at 10 a.m. and an end of September 10 at 8 p.m. KXLY920 reports a start of and an end on , but the calendar date has not been established. is named as the issuing office by WTKR. Forecasters describe dangerous heat with additional humidity as the main impact this week, according to KSBY. KXLY920 reports high temperatures Tuesday afternoon reaching the mid to upper 90s across the region, with the L-C Valley peaking between 100 and 103 degrees. KTNV reports extremely hot temperatures on Thursday as high pressure remains over the region, with the triple digits continuing through Saturday. KSBY reports for interiors, 90s along the south coast and 80s for coastal valleys. WTKR reports hot and humid conditions with highs in the low 90s and an afternoon heat index in the triple digits. KSBY reports that combining those temperatures with higher humidity, sunny skies and a lack of overnight cooling makes heat stress a concern for sensitive groups across the region. KTNV advises limiting time outside, staying inside air conditioning and staying hydrated. The differing alert levels and schedules have not been reconciled.

Earlier reports

  1. Sep 2, 2026, 6:10 a.m. ET

    High Heat Advisory Issued for Lewiston, Clarkston, Lapwai, Pomeroy

    A high heat advisory has been issued for Lewiston, Clarkston, Lapwai, and Pomeroy, according to KXLY920.com and KSBY. The advisory warns of high temperatures, with KXLY920.com reporting that Tuesday afternoon highs will reach the mid to upper 90s, with the L-C Valley peaking between 100 and 103 degrees, while KSBY reports highs reaching into the triple digits.

    The advisory's start and end times differ between sources. KSBY reports the advisory begins at 12:00 a.m. on Monday, August 24, 2026, and expires at 10:00 a.m. on Tuesday, August 25, 2026. KXLY920.com reports the advisory begins at noon Tuesday and lasts through Wednesday. The exact timing has not been established due to conflicting reports.

  2. Aug 24, 2026, 11:23 a.m. ET

    High Heat Advisory Extended Through Tuesday Morning on Central Coast

    The high heat advisory for the Central Coast has been extended and now runs until 10 a.m. Tuesday, Aug. 25, according to ksby.com. The advisory began Monday, Aug. 24, and was originally set to expire earlier; officials have pushed the end time back, extending the warning period.

    Highs are expected to reach into the triple digits during the advisory period, ksby.com reported.

  3. Aug 24, 2026, 10:10 a.m. ETFirst report

    High Heat Advisory Issued for Central Coast Through Monday

    A high heat advisory is in effect for the Central Coast from Monday, August 24, through Tuesday, August 25 at 10 a.m., according to KSBY. The advisory warns of highs reaching into the triple digits.

    The advisory begins at 12 a.m. on Monday and expires at 10 a.m. on Tuesday. The event is still developing, and further updates may follow.

Was this report accurate and useful?

Sources

Revision history

  1. Version 511 Sept 2026, 04:47current

    Added the issuing office named by WTKR and KSBY's heat-stress impact detail; kept the sourced range for alert level and timing.

  2. Version 42 Sept 2026, 10:10current

    Updated to reflect the latest facts, including the advisory for the listed cities and the conflicting start/end times from KSBY and KXLY920.com.

  3. Version 410 Sept 2026, 04:23

    Added KTNV's Extreme Heat Warning and its September 10 start and end times, and added KTNV's precautions.

  4. Version 38 Sept 2026, 14:53

    Updated to reflect the published status and added the date of the event in the opening paragraph.

  5. Version 325 Aug 2026, 15:03

    Updated to reflect the published status and correct the start time attribution.

  6. Version 28 Sept 2026, 14:52

    Updated to include the full range of conflicting start and end times from all sources, and clarified that the calendar date for KXLY920's report is not established.

  7. Version 225 Aug 2026, 13:23

    Updated to reflect conflicting reports on advisory timing and temperature details from both sources.

  8. Version 124 Aug 2026, 14:22

    First published.

  9. Version 18 Sept 2026, 14:46

    First published.

  10. Version 124 Aug 2026, 14:10current

    First published.

  11. Version 124 Aug 2026, 15:23current

    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.