FirstAlerts
Severe Weather

Heat Advisory in Reno, Harvey, Kingman and 8 More Kansas Counties Through 8 PM Tuesday

Heat index values up to 107 expected across 11 south central and southeast Kansas zones on Tuesday, Aug. 18, 2026, according to the National Weather Service advisory record.

By AI ReporterWritten Aug 17, 2026, 2:09 p.m. ET
Developing · checked 16h ago

Hazard products are revised and cancelled as conditions change. Check the National Weather Service for the current alert before acting on this report.

We last searched for new coverage of this at Aug 17, 2026, 5:12 p.m. ET — checked 16h ago.

A is in effect for portions of south central and southeast Kansas from 1 PM to 8 PM CDT Tuesday, Aug. 18, 2026, according to the record issued by the . The record carries the headline "" and classifies the alert at the level. The record states that heat index values up to 107 are expected, and that The covers zones: Reno, Harvey, Kingman, Sedgwick, Harper, Sumner, Cowley, Neosho, Chautauqua, Montgomery and Labette counties. Cities named in the record are Haysville, Anthony, Newton, Bel Aire, Kingman, Derby, Independence, Wellington, Parsons, Harper, Park City, Mulvane, Sedan, Cedar Vale, Valley Center, Chanute, Coffeyville, Hutchinson, Attica, Arkansas City and Winfield. The National Weather Service record tells residents to drink plenty of fluids, stay in an air-conditioned room, stay out of the sun, and check up on relatives and neighbors. To reduce risk during outdoor work, the Occupational Safety and Health Administration recommends scheduling frequent rest breaks in shaded or air conditioned environments, the record says. Anyone overcome by heat should be moved to a cool and shaded location. The record states that heat stroke is an emergency and instructs people to call 9 1 1.

Was this report accurate and useful?

Sources

Revision history

  1. Version 117 Aug 2026, 18:09current

    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.