Author: William Tygart

Storm Updates: Eastern Nebraska–Iowa Slight Risk, Watch 668 Kansas–Nebraska, Iowa Flood Moderate — Monday, September 14, 2026

This is a live Monday afternoon snapshot of local storm-type events across the United States as of Monday, September 14, 2026. The Storm Prediction Center 2000 UTC Day 1 Convective Outlook holds a Slight Risk of severe thunderstorms across northern Kansas and southern and eastern Nebraska into western and central Iowa. Severe Thunderstorm Watch 668, issued at 3:45 p.m. CDT, covers western and northern Kansas and south-central Nebraska until 10:00 p.m. CDT. The Weather Prediction Center Day 1 Excessive Rainfall Outlook, valid 12 UTC Monday through 12 UTC Tuesday, keeps a Moderate Risk over portions of central and southwestern Iowa.

These are county-scale thunderstorms and flash-flood pulses, not a U.S. mainland hurricane landfall. Restoration exposure tonight is wind-driven roof and tree work in the watch, isolated hail, a conditional tornado in the eastern Nebraska–western Iowa corridor if a surface-based supercell holds, and interior water where Iowa cells train. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this afternoon

Watch 668 is the organized wind desk. SPC issued it at 3:45 p.m. CDT Monday, September 14, 2026, for portions of western and northern Kansas and south-central Nebraska, effective until 10:00 p.m. CDT. Primary threat language is scattered damaging winds and isolated significant gusts to 80 mph, plus isolated large hail to 1.5 inches. High-based storms are expected to continue in a hot, well-mixed environment and spread northeast near a pre-frontal trough.

The 2000 UTC Day 1 outlook, issued 3:00 p.m. CDT by Karstens and Wendt, did not change the categorical Slight Risk. Summary language: scattered strong to severe thunderstorms should occur across parts of eastern Nebraska into western and central Iowa this afternoon and evening. Large hail, severe wind gusts, and tornadoes all appear possible. Severe thunderstorm winds will also be possible across northern and western Kansas. An 18z Omaha sounding showed about 2,232 J/kg MUCAPE as destablization spread north into central and eastern Nebraska. SPC still expects an elongated area of convection from north-central Kansas into south-central and eastern Nebraska and west-central Iowa, favoring supercells early, then a quick transition to clusters and line segments. Exact initiation remains uncertain in recent HRRR and RRFS runs. No SPC mesoscale discussion was in effect as of mid-afternoon UTC; Watch 668 is the current watch product.

WPC’s Day 1 excessive-rainfall discussion, issued 3:40 a.m. EDT Monday, September 14, 2026, maintains a Moderate Risk over portions of central and southwestern Iowa, coordinated with the Des Moines forecast office. HREF blended-mean QPF of 3–5 inches is cited near Des Moines and points south and southwest, with neighborhood probabilities of 60–80 percent for more than 3 inches and 3-hour flash-flood-guidance exceedance probabilities of 50–70 percent. A broad Slight Risk still covers much of the Midwest from the Door Peninsula through eastern Nebraska, plus a separate Slight Risk over the Southwest west of the I-25 corridor.

Hotspot 1 — Eastern Nebraska into western and central Iowa

This is the Slight Risk core. SPC places 5 percent tornado probabilities over parts of eastern Nebraska near Omaha, Lincoln, Council Bluffs, Bellevue, and Fremont, with 2 percent tornado probabilities extending toward Des Moines, Sioux City, Ames, West Des Moines, and Ankeny. Fifteen-percent wind and hail contours overlap the Omaha–Lincoln–Council Bluffs corridor. A 40–50 kt nocturnal low-level jet is forecast to increase effective storm-relative helicity this evening. SPC notes lingering low-level inhibition on RAP soundings and says it remains unclear whether convection will fully tap that shear. A sustained surface-based supercell in that environment would conditionally be capable of a strong tornado. Weak instability farther east in eastern Iowa should limit the severe risk deeper into the night.

Cities and counties to watch: Omaha, Lincoln, Bellevue, Fremont, and Council Bluffs; Sioux City, Fort Dodge, Ames, Des Moines, West Des Moines, and Ankeny; counties along and just ahead of the cold front from southeast Nebraska into west-central Iowa.

Restoration read: wind and hail first if supercells hold, then water if the same cells train on the WPC Moderate footprint. Stage tarps, generators, and extraction pumps before dark. Treat a tornado warning as a narrow local survey, not a regional event.

Hotspot 2 — Watch 668: western and northern Kansas, south-central Nebraska

The watch box runs roughly 45 miles north and south of a line from 145 miles southwest of Hill City, Kansas, to 50 miles east of Hastings, Nebraska. That is high-based, mixed-layer convection along the pre-frontal trough, not the same supercell corridor as Omaha. Primary threats are damaging wind, isolated 80 mph gusts, and hail to about 1.5 inches through 10:00 p.m. CDT.

Cities and counties to watch: Hill City, Hays, and northern Kansas counties in the watch outline; Hastings, Grand Island, and south-central Nebraska counties in and near the box. Confirm the county list on the Watch 668 outline update at SPC before you pre-position.

Restoration read: dry-microburst and outflow wind on roofs, siding, and center-pivot country. Photograph in remaining daylight only if it is safe. Hail claims will be isolated, not a swath unless a cell stays surface-based longer than expected.

Hotspot 3 — Central and southwestern Iowa flood Moderate, plus Southwest rain

The flood desk is Iowa. WPC introduced a small Moderate Risk for this Day 1 period because CAM guidance clustered 3–6 inch totals south of I-80, with urban streets and low-water crossings the first failures. A broader Slight Risk still covers eastern Nebraska through much of the Midwest. Expectation is scattered flash flooding tonight into early Tuesday morning.

The Southwest Slight Risk covers eastern Arizona, much of New Mexico west of I-25, and southwestern Colorado. PWATs are cited near the 95th–99th percentile. That is monsoon-style heavy rain on complex terrain and remnant burn scars, plus strong outflow, not the Plains watch.

Restoration read: Iowa is water and a 24–48 hour mold clock if 3-inch cores verify in town. The Southwest is localized washouts and urban flooding, not a CAT roster.

Just hit

SPC storm reports for the 12 UTC Monday, September 14, 2026 through 12 UTC Tuesday window showed no tornado, hail, or wind LSRs at the time of this afternoon desk. That is a quiet start to the convective day, not a forecast of a quiet evening. Last night’s 12 UTC Sunday–Monday window still holds the tickets already on the board: tree and wire work across Ohio, Pennsylvania, New York, and West Virginia from Sunday’s upper Ohio Valley–Northeast line; a roof peeled in Fox Township, Carroll County, Ohio; microburst-style trees and minor roof damage near Cloverport, Hardeman County, Tennessee; 1.00-inch hail near Sterling, Johnson County, Nebraska, and in Cascade and Judith Basin counties, Montana; a 61 mph gust near Patagonia, Arizona.

Sunday’s organized wind corridor is yesterday. Today’s new work, if it verifies, is Watch 668 and the eastern Nebraska–Iowa Slight Risk plus Iowa flash flooding.

Pulse table

Region	Main threats	SPC / NWS level	Status this afternoon
Eastern NE / western–central IA	Hail, damaging wind, conditional tornado	SPC Slight (2000 UTC)	Live Slight; initiation still uncertain
Western / northern KS, south-central NE	Damaging wind to 80 mph, hail to 1.5 in	Watch 668 to 10 p.m. CDT	Live watch
Central / southwestern Iowa	Flash flood, 3–6 in cores possible	WPC Moderate excessive rainfall	Tonight into Tuesday morning
Midwest Slight (Door Peninsula to eastern NE)	Scattered flash flood	WPC Slight	Overnight
E AZ / NM west of I-25 / SW CO	Heavy rain, outflow, burn-scar flood	WPC Slight	Afternoon–evening cells
Eastern North Carolina	Isolated gusty wind, small hail	Local / no categorical severe area	Isolated
Atlantic / Gulf vs. U.S. mainland	No landfalling tropical cyclone	NHC: no Atlantic TCs	Quiet on the mainland coast

What this means for restoration teams

Watch 668 wind at 65–80 mph is roof, siding, gutter, and tree-on-structure work in Kansas and south-central Nebraska. The Slight Risk east of that box is the same plus a conditional tornado and large hail if a supercell holds from Lincoln–Omaha into western Iowa. Iowa’s Moderate flood risk is wet drywall and a same-night extraction clock if the 3-inch HREF signal verifies south of I-80. Do not send one crew to both the watch box and Des Moines without checking which county has a warning now.

For teams in or near Watch 668: stage before sunset, not after the first warning. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. National Hurricane Center products as of Monday afternoon, September 14, 2026, show no tropical cyclones in the Atlantic. Tropical Storm Norbert is in the east-central Pacific about 1,125 miles east of Hilo, Hawaii, with 40 mph winds and a weakening trend. Tropical Depression Fifteen-E is about 785 miles southwest of the southern tip of Baja California. Neither threatens U.S. mainland land. The work tonight, if it comes, will be scattered: a wind swath in the Kansas–Nebraska watch, a hail or tornado report in the eastern Nebraska Slight Risk, flooded intersections south of I-80 in Iowa.

Looking ahead

The SPC Day 2 Convective Outlook issued 12:14 p.m. CDT Monday, September 14, 2026 (valid 12 UTC Tuesday through 12 UTC Wednesday) is a Marginal Risk in a corridor from Kansas into western Ohio. Summary language: scattered strong thunderstorms may occur from the Great Lakes southwestward through the lower Missouri Valley Tuesday afternoon and evening, with at least isolated damaging wind gusts possible. Shear is forecast to be weak. Storms should be primarily short-lived, with a few clusters near the front. Watch the next Storm Tracker update rather than assuming Watch 668 is the last line of the week.

Sources and how to verify

Primary sources dated Monday, September 14, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook; Severe Thunderstorm Watch 668; SPC current watches and today’s LSR page (no reports in the 12 UTC Monday window at desk time); Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0733 UTC; National Hurricane Center Atlantic and East Pacific public pages. Morning desk on the same calendar day: Storm Updates: Eastern Nebraska–Iowa Slight Risk, Iowa Flood Moderate — Monday, September 14, 2026 (Morning).

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, Watch 668, and WPC excessive rainfall for the flood overlay.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 14, 2026

The Best Delay Product Tells You Cash Is Owed Before You Take the Voucher
The travel idea mill keeps shipping seat-map tools and expense apps. The actual product this year is narrower. It tells a passenger, in the gate line, whether the delay already triggered a cash refund under federal rules — before they tap the voucher.

That is not a travel dashboard. It is a verdict on money that already left the card.

The rule is not a rumor

In April 2024 the U.S. Department of Transportation issued the Refunds and Other Consumer Protections final rule. It is now 14 CFR Part 260. For a scheduled flight to, from, or within the United States, a cancellation or a significant delay or change can trigger a full refund of the fare plus taxes and ancillary fees when the passenger does not take the new itinerary and does not accept a voucher, credit, or other substitute.

The refund is supposed to be automatic. Credit-card refunds have a seven-business-day clock. Other payment methods have twenty calendar days. Carriers must tell the passenger that cash is an option before they pitch miles.

DOT later carved a narrow exception. A July 8, 2026 notice of enforcement discretion, extending a December 5, 2025 pause, says the Department will not treat a mere flight-number change as a cancellation if the passenger is rebooked and the trip has no significant change or delay. Three hours or more on a domestic departure or arrival still counts. A different airport still counts. A class downgrade still counts. The exception is the number on the ticket, not the time on the board.

The volume is not a vibe

Bureau of Transportation Statistics TranStats, marketing-carrier view, January through June: 85,998 cancelled operations in 2026, or 2.23 percent of 3,856,905 flights. Same window in 2025: 59,609 cancellations, 1.56 percent. Arrival delays sat at 823,345 flights, 21.35 percent. On-time share slipped to 76.14 percent from 76.67 percent a year earlier.

Refunds are already the loudest complaint line. DOT’s April 2026 Air Travel Consumer Report logged 7,278 complaint cases. Refunds ranked first at 2,296. Flight schedule was second at 1,323. On August 1, 2025 the Department opened ACERS, the new Aviation Complaint, Enforcement, and Reporting System. The intake pipe exists. Most passengers never find it because the airline app offers a credit first.

A DOT Office of Inspector General audit published in 2025 noted that OACP took more than 139,000 refund complaints between 2020 and 2022, against 1,568 refund complaints in all of 2019. The Bureau assessed more than $155 million in civil penalties across 14 airlines for slow refunds, while still relying on carrier self-certification for the offsets. The enforcement story is not theoretical. The noticing job is still on the passenger.

Stop treating these as separate products

The X idea mill splits this into four micro names. One app reads a confirmation email. One flags EU261-style delay hours. One drafts a DOT complaint. One tracks unused travel credits that expire. Cute. Wrong cut.

The passenger does not wake up wanting a “consumer-protection copilot.” They wake up because the board flipped and the app is offering $150 in wallet credit against a $640 fare. The category is the same leakage pattern as unused SaaS seats and short-paid claims: money left, the file is a PDF in Gmail, and nobody owns the next click.

Greg Isenberg’s Duo list put a tow-truck intake and an on-site adjuster on opposite screens. Same primitive. The object in the hand is the proof. The other pane is the rule. Combine the itinerary-as-data exhaust with the delay-board photo and you have one checker, not two startups.

The wedge is a free checker. Not a platform.

Do not start with a travel profile. Start with the email they already have.

Paste the confirmation. Paste the delay SMS. Upload the photo of the gate screen. Thirty seconds later: cash owed, voucher trap, or not significant. If it is fine, you still captured a labeled itinerary. If it is not fine, you draft the carrier request or the DOT filing — and a person hits send.

That is the only honest offer. Pure upside for the passenger. You get paid when the cash posts, or on a cut of recovered ancillaries: bag fees for bags that never rode, seat fees on a cancelled segment, Wi-Fi that was not provided. Part 260 already names those ancillary refunds. Almost nobody files them because the receipt is three emails deep.

Do not let the model file the complaint. ACERS and carrier portals are irreversible enough. The model drafts. A human owns the send. Same rule as a customs protest or a medical claim letter.

Why this is buildable now

Two years ago the input was slop. Airline PDFs, codeshare itineraries, and screenshots of a split board were a weekend of data entry. Multimodal models can pull a PNR, a flight number, and a new departure time off a photo. They still invent policy. They do not need to be trusted with the card. They need to be trusted with the first pass against a published rule: three hours domestic, different airport, cancelled and not accepted, ancillary not provided.

The other half of why now is the rule plus the cancellation bump. Automatic refunds are on the books. Cancellations in the first half of 2026 ran well above the same stretch of 2025. The voucher button is still the default UI. That gap is the company.

How the company actually compounds

The first dollar is the refund. That is not the business. The business is the labeled corpus.

After a few thousand pastes you know which carriers convert a three-hour delay into a travel credit at the highest rate. You know which codeshare legs drop the refund obligation into a foreign operator that the passenger never contracted with. You know which bag-fee SKUs never auto-refund even when the segment dies. That scoreboard is a B2B product for OTAs, TMCs, and card issuers. They already sit on the itinerary feed. They do not sit on the outcome map.

Consumer volume trains the classifier. Enterprise contracts pay for the map. Do not sell the map before cash has posted to real people. A dashboard of “possible passenger savings” is how this idea dies in a pitch deck.

What not to build

Do not build another trip organizer that wants calendar access on day one. You will lose to TripIt on the people who already care, and you will never reach the person staring at a red board in Terminal B.

Do not pretend a language model is a DOT lawyer. Part 260 has definitions. Significant change is not a vibe. The July 2026 discretion on renumbered flights is a real carve-out. Get that wrong and you train customers to ignore you.

Do not brand this as agentic travel ops. Brand the outcome. Cash that should have come back, before the voucher ate it.

A build order that will survive contact
- Week 1–2: one checker. Itinerary in, verdict out. No account required to see the first answer.
- Week 3–4: a carrier request and an ACERS draft with a human signer. Contingency fee only.
- Month 2: add the second document in the same drawer — bag-fee receipt, seat-fee receipt, hotel that was booked because the inbound died.
- Month 3: publish the first ugly internal scoreboard. Which carriers, which delay bands, which ancillary SKUs stall. That scoreboard is the seed of the B2B SKU.
If you cannot get a stranger to paste one confirmation email this week, you do not have a company. You have a thesis.

Why this is worth writing, and building

Most idea-mill posts describe a feature. This one describes a shift in who does the tedious work of noticing. The noticing used to require a travel agent, a weekend, and a willingness to sit on hold. It now requires a model that can read the page and a person who will sign the filing.

Recovery businesses endure because the customer has nothing to lose. Most software asks for a seat fee before it has proven a dollar. This one pays for itself on the first posted refund or it does not deserve a second conversation.

Someone will own the system of record for delays that should have been cash. The threads will keep proposing a new .ai name for each document type. Ignore the names. Check first. Keep the map.

Will Tygart — Tygart Media.
This is the idea-mill series.
September 14, 2026

3,222 Requests an Hour. Six Login Posts. That Is Not the Same Event.

This morning, about 7:10 AM PDT on 14 September 2026, the knowledge cluster showed a fresh spike: roughly 3,222 requests in an hour, and six POST hits on wp-login.php. Same box. Same shape as the 11–13 September run. Slightly hotter on volume. Cooler on the login door.

That is the whole alert. It is not a breach report. It is not a reason to open the firewall. It is two numbers that most dashboards smash into one word — “attack” — and then the operator starts changing things they cannot undo cleanly.

Mixed spike. A mixed spike is a short window where total request volume jumps while a sensitive path such as wp-login.php only sees a handful of POSTs. The volume is usually crawlers, scanners, or cheap probes. The login count is the part that can become hostile. Treat them as two events until the logs prove they are one.

What does a 3,222 request-per-hour spike actually mean?

It means the box was busy. It does not mean someone is in the admin. On this stack, an hour in the low thousands is loud enough to page a human and too coarse to name a cause. AI crawlers, feed fetchers, uptime checks, and junk scanners all land in the same request counter. We already showed that GA4 misses crawler traffic and that server logs are the only honest desk for that layer in Server Log Analysis for AI Search.

The 11 September field note left this card open. That write-up recorded an earlier pulse on the same cluster at about 1:51 PT: roughly 2,487 requests per hour and nine wp-login POSTs. The instruction then was a read-only log pull and a one-paragraph verdict. No firewall change, no plugin change, no credential change without a named gate. That card is the parent of this morning. See The 1 MB Limit Ate the Clips.

Why are six wp-login POSTs the number that matters?

Because that path is the door. A GET to wp-login.php is usually a probe. A POST is a credential attempt. Six POSTs in an hour is not a brute-force campaign. A campaign that is actually trying passwords does not stop at six. It stacks POSTs until a rate limit, a WAF, or a 429 answers.

Six against 3,222 is the tell. Login is about two-tenths of one percent of the hour. If the spike were “someone hammering wp-login,” the login count would be the spike. Here the spike is everything else, and the door got a light knock.

Window	Requests / hour	wp-login POSTs	What it looks like so far
11 September 2026, ~1:51 PT (public card)	~2,487	9	Open patch. Verdict not written yet.
14 September 2026, ~7:10 AM PDT	~3,222	6	Same shape, hotter volume, fewer POSTs.

Those two rows are first-party. They come from the ops cards and this morning’s alert. They are not a full log dump. They are enough to stop the sentence “we are under attack” from shipping as fact.

How do you tell bot noise from a hostile login event?

You do not tell from a single request-per-hour number. You tell from five columns that have to sit on one page: top source networks, paths, methods, status codes, and whether any POST to an auth endpoint returned a success path instead of a fail, a 403, a 429, or a challenge.

If volume is high and wp-login.php / xmlrpc.php POSTs are near zero, start with crawler or scanner noise.
If POSTs to the login door climb while other paths stay flat, start with credential stuffing or a cheap brute-force kit.
If one network owns both the volume and the POSTs, treat that network as the subject of the verdict, not the whole internet.
If status codes are 200 on a login POST, do not celebrate. WordPress often returns 200 on a failed login because it re-renders the form. You still need the auth result, not the HTTP code alone.
If you cannot see whether rate limiting or the WAF fired, you do not have a close. You have a draft.

That list is the desk, not a product. It is the same discipline we use when we refuse to treat Bing AI citations as sessions in How to Read Bing Webmaster Tools AI Citations. Wrong unit, wrong decision.

What is the one-paragraph verdict from this morning’s numbers alone?

Provisional, read-only: this morning looks like bot noise with opportunistic login probes, not a concentrated hostile event. The volume rose from the mid-2,000s last week to the low-3,000s. The login door went from nine POSTs to six. That is the opposite of a campaign that is finding a seam. Nothing in the alert says a login reached a successful auth. Nothing in the alert says the WAF or a rate limit fired. Until those two facts are in the log extract, the box stays as-is.

What to do from this paragraph: pull the hour. Rank source networks, paths, methods, and status codes. Confirm whether any login POST crossed into an authenticated session. Write the close in one paragraph. Do not touch firewall, plugins, credentials, DNS, or WAF from the spike number alone.

Why does this belong on an AEO and GEO desk?

Because the same operators who publish for answer engines also run the origin those engines crawl. A spike that is actually GPTBot or a citation crawler is the retrieval layer working. A spike that is actually wp-login.php is the origin under cheap pressure. If you flatten both into “bots,” you will rate-limit the crawler you spent a year trying to attract. We mapped that split in The AI Crawler Hierarchy and in Google vs Bing vs OpenAI.

SEO still needs the URL up. AEO still needs a clean block a snippet can lift. GEO still needs a page a model will cite without inventing a second sentence. None of those layers survive an origin that treats every request burst as an incident and starts flipping controls. The cited-answer work on this site — Your Website Doesn’t Need More Traffic. It Needs to Be the Answer. — assumes the box that serves the sentence stays boring.

What we would not claim

That we have this morning’s full access log in this article. We have the alert counts. The path table and the auth result are the next pull, not this page.
That six POSTs means zero risk. It means the door was tried. It does not mean the door opened.
That 3,222 requests per hour is a universal threshold. It is the number on this box, this hour.
That hiding wp-login.php is the fix. Obscurity is not the close, and this post is not a plugin recommendation.
That any named source network belongs in a public URL. Publishing attacker addresses helps the next scanner more than it helps the reader.

What we would do again

Keep the two counts separate on the card. Request volume on the left. Auth-path POSTs on the right. Write the verdict in one paragraph before anyone is allowed to change a control. Leave the change list empty until the named gate says yes. Publish the method, not the address list.

The 11 September card said a spike is not automatically an attack and it is not automatically “leave it.” It is a log plus a verdict. This morning’s numbers did not close the log. They did close the panic sentence. The door was quiet. The weather was not.

FAQ

Is a WordPress request spike the same thing as a brute-force attack?

No. A request spike is total traffic in a window. A brute-force event is repeated credential POSTs against an auth path such as wp-login.php or xmlrpc.php. This morning’s hour had both a spike and six login POSTs. Those are adjacent facts, not proof they are the same campaign.

How many wp-login POSTs should trigger a change?

There is no public magic number that authorizes a firewall, plugin, credential, DNS, or WAF change on this stack. The trigger is a log extract that shows concentrated POSTs, a repeated source network, and either a successful auth or a clear miss by the existing limiters. Six POSTs in an hour does not clear that bar.

Can AI crawlers cause a 3,000-request hour?

Yes. On this network we have already logged hours where a single AI crawler family mapped tags, feeds, and endpoints at four-figure rates. That traffic belongs in the server log, not in GA4. Confirm the user-agent and the path list before you treat the hour as hostile.

Should you publish the source IP addresses from a spike?

No. A public post can carry the counts, the method, and the verdict. It should not carry a live target list. The addresses live in the private log pull.

Sources: Tygart Media ops alert, knowledge cluster, ~7:10 AM PDT, 14 September 2026 (about 3,222 requests/hour and 6 wp-login POSTs). Prior public card in The 1 MB Limit Ate the Clips (~2,487 requests/hour and 9 wp-login POSTs, ~1:51 PT). Method context: server log analysis for AI search, AI crawler hierarchy. Will Tygart, Tygart Media, 14 September 2026.

September 14, 2026

Storm Updates: Eastern Nebraska–Iowa Slight Risk, Iowa Flood Moderate — Monday, September 14, 2026 (Morning)

This is a live Monday morning snapshot of local storm-type events across the United States as of Monday, September 14, 2026. Overnight the organized wind corridor that ran the upper Ohio Valley into New York is down. No Storm Prediction Center watches are currently valid. The Day 1 Convective Outlook issued 0746 AM CDT holds a Slight Risk of severe thunderstorms across parts of eastern Nebraska into western and central Iowa this afternoon and evening. Large hail, severe gusts, and a few tornadoes all appear possible. The Weather Prediction Center overlays a Moderate Risk of excessive rainfall on central and southwestern Iowa, with a broader Slight Risk from eastern Nebraska through the Midwest and a separate Slight Risk over the Southwest monsoon corridor.

These are county- and ZIP-scale thunderstorms and flash-flood pulses, not a U.S. mainland hurricane landfall. Restoration exposure today is wind and hail on the Nebraska–Iowa Slight, interior water where Iowa cells train south of I-80 tonight, and leftover tree-and-roof work from Sunday evening in Ohio, Pennsylvania, West Virginia, and New York. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this morning

SPC lists no current convective watches. The most recently issued watch was number 667 earlier in the week; Sunday’s Ohio Valley–Northeast slight-risk corridor produced local severe thunderstorm warnings and wind damage but did not carry an overnight watch into Monday morning.

The 1300 UTC Day 1 outlook (valid 1300Z Monday through 1200Z Tuesday) draws the Slight Risk from roughly Grand Island and Hastings east-northeast through Omaha and Lincoln into western and central Iowa, including the Des Moines metro on the eastern edge. A Marginal Risk wraps a wider ring from the Dakotas and Minnesota south through Kansas. Elevated convection is already ongoing this morning across the central Plains and mid Missouri Valley on a strong low-level jet. SPC expects that band to stay mostly sub-severe and weaken late morning, then a new surface-based corridor to fire along or just ahead of a cold front across eastern Nebraska by late afternoon.

WPC’s Day 1 Excessive Rainfall Outlook, updated 0733 UTC, is the louder product this morning: Moderate Risk over portions of central and southwestern Iowa, with locally 3 to 6 inches possible south of I-80 toward Des Moines and points southwest. A broad Slight Risk still covers much of the Midwest from eastern Nebraska through southern Minnesota and the Door Peninsula, plus a separate Slight over eastern Arizona, New Mexico, and southwestern Colorado.

Hotspot 1 — Eastern Nebraska into western and central Iowa

This is today’s organized severe desk. A mid-level shortwave and 50–70-plus kt mid-level jet move east-northeast across the northern Plains. Rich low-level moisture is forecast to stream north into eastern Nebraska and western Iowa after morning convection clears. SPC allows a narrow corridor of 2,000–3,000+ J/kg MLCAPE if surface temperatures reach the low to mid 80s by late afternoon. Initial storms should be supercellular enough for large hail. Mode is expected to transition quickly to clusters and line segments. A 40–50 kt nocturnal low-level jet supports ample storm-relative helicity this evening; a sustained surface-based supercell would conditionally be capable of a strong tornado. That is the official language, not a guarantee that one occurs.

Cities and counties to watch: Lincoln, Omaha, Council Bluffs, Sioux City, Des Moines, Ames, and the I-80 belt from Grand Island through western Iowa. Watch issuance, if it comes, is an afternoon product — not a morning one.

Restoration read: hail and wind first on the Nebraska side; water second once the same storms cluster over Iowa after dark. Stage tarps and generators before 4 p.m. local. If a warning includes both wind and heavy rain, treat the ZIP as a dual ticket by morning.

Hotspot 2 — Central and southwestern Iowa flood overlay

WPC introduced a small Moderate Risk for D1 in coordination with the Des Moines office. HREF blended mean QPF runs 3–5 inches over the area encompassing Des Moines and points south and southwest. Neighborhood probabilities for more than 3 inches are 60–80 percent in that pocket, with 25–30 percent for more than 5 inches. Three-hour flash-flood guidance exceedance sits 50–70 percent. The main concerns are urban footprints and low-water crossings south of I-80. Heavy rain is expected to linger into early Tuesday morning.

A broader Slight still covers eastern Nebraska into southern Minnesota. Isolated flash-flood concerns this morning ride the progressive elevated band; the more appreciable footprint is the evening and overnight wave.

Restoration read: this is tonight’s water ticket. Extraction and drying clocks start the same night water is inside. Do not wait for a river flood warning if streets and finished basements are already taking the 1-inch-per-hour cores.

Hotspot 3 — Sunday just-hit and Southwest scatter

Overnight LSRs from the 1200 UTC Sunday–Monday window show the Ohio Valley–Northeast slight-risk corridor verified as wind, not tornadoes. Preliminary reports include a roof ripped off a home and multiple trees down in Fox Township, Carroll County, Ohio; trees and wires across Lawrence, Butler, Crawford, McKean, and Clearfield counties in Pennsylvania; trees on structures and roads in Washington County, Ohio, and Wood County, West Virginia; and additional tree and wire damage in Onondaga, Oneida, Franklin, Fulton, and Saratoga counties in New York. Isolated 1.00-inch hail fell near Monarch and Raynesford, Montana, and 2 south of Sterling, Nebraska, after midnight. A 61 mph gust was measured near Patagonia, Arizona.

Today the Southwest stays a flood-and-outflow desk. WPC keeps a Slight Risk of excessive rainfall over eastern Arizona, much of New Mexico, and southwestern Colorado on monsoon-style cells, burn scars, and slot canyons. SPC does not carry 5 percent severe probabilities there, but isolated strong gusts and small to near-severe hail are possible where heating is strongest. Eastern North Carolina sits under a cold front with only a low-end isolated wind/hail mention.

Just hit

Sunday’s upper Ohio Valley–central New York Slight Risk is yesterday’s ticket: trees, wires, and isolated roof work from eastern Ohio through northwest Pennsylvania into central New York. Watch 667 from Saturday is long expired. There is no named tropical cyclone threatening U.S. land this morning. National Hurricane Center discussion shows no Atlantic tropical cyclones; Tropical Storm Norbert and a weakening eastern Pacific depression are well offshore and not a mainland or Hawaii landfall problem today.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this morning
Eastern NE / western–central IA	Large hail, damaging wind, few tornadoes possible	SPC Slight (1300Z)	Afternoon–evening; no watch yet
SW / central Iowa south of I-80	Flash flood, 3–6″ local totals	WPC Moderate excessive rainfall	Evening into Tuesday morning
OH / PA / WV / NY from Sunday	Trees, wires, isolated roof damage	LSRs; watches expired	Aftermath
Eastern CO / western–northern KS	Isolated severe gusts, high-based cells	SPC Marginal	Afternoon scatter
AZ / NM / SW CO	Flash flood, strong outflow	WPC Slight	Afternoon–evening cells
Atlantic / Gulf vs. U.S. mainland	No landfalling tropical cyclone	NHC quiet on the mainland	Quiet

What this means for restoration teams

Eastern Nebraska this evening is hail and wind: roofs, siding, screens, and vehicles. Western and central Iowa is the dual ticket — the same storms that throw hail west of the Missouri River can train 3-plus inches of rain over Des Moines and counties southwest of I-80 after dark. A brief tornado, if one occurs, is a narrow swath. Staff it as a local damage survey, not a regional outbreak.

Sunday’s Ohio–Pennsylvania–New York wind is already on the books: tree-on-structure, service drops, and isolated roof peel. Photograph remaining damage in daylight if it is safe, then move crews toward the Nebraska–Iowa corridor rather than chasing last night’s counties unless a specific claim is already open.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. The work today, if it verifies, will be scattered: a hail swath through an eastern Nebraska county, a flooded intersection south of I-80 in Iowa, leftover trees in Ohio or New York. That is the local-storm pattern this desk should staff.

Looking ahead

SPC Day 2 is a Marginal Risk as the same trough lifts toward the Upper Great Lakes. Day 3 currently carries no severe area. WPC language keeps heavy rain lingering into early Tuesday over the same Iowa footprint. Watch the afternoon Storm Tracker rather than assuming the 1300Z Slight is the last line of the day — a watch can still go up if the warm sector destabilizes as drawn.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center 1300 UTC Day 1 Convective Outlook for Monday, September 14, 2026 (Gleason/Lyons); SPC current watch page (no watches valid as of 1010 UTC); SPC preliminary local storm reports for the 13/1200Z–14/1159Z window; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0733 UTC; National Hurricane Center Atlantic and East Pacific discussions this morning.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watches, and LSRs, and WPC excessive rainfall for the flood overlay. Prior desk: Sunday afternoon, September 13 storm updates.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 14, 2026

Storm Updates: Rio Blanco County Colorado Flash Flood Warning — Sunday, September 13, 2026

This is a live storm update and search demand pulse for Sunday night, September 13, 2026. The National Weather Service in Grand Junction, Colorado, issued a severe Flash Flood Warning for Rio Blanco County at 8:25 PM MDT, valid through 11:30 PM MDT. While localized runoff, wash flooding, and steep-terrain drainage pose immediate hazards across northwest Colorado’s Grand Junction–Montrose designated market area (DMA), search behavior across the wider state indicates a tightening baseline for water mitigation and flood repair demand.

Flash flooding in high-desert and mountainous terrain moves fast and creates sudden structural washouts. Property owners and municipal managers must verify local conditions with the National Weather Service before traveling. Turn around, don’t drown.

The Warning: Rio Blanco County, CO

The Grand Junction weather forecast office issued the severe Flash Flood Warning following heavy rainfall over saturated soils and drainage basins in Rio Blanco County. Flash flooding in this geography typically impacts low-water crossings, county access roads, oil and gas pad infrastructure, and residential basements situated along creekbeds and alluvial fans.

Official NWS Alert identifier: urn:oid:2.49.0.1.840.0.8acebba0f7c98d0a6a7482a49c065131956af988.001.1. The active warning contour spans uninhabited ranch land as well as municipal corridors, requiring local operators to track specific drainage axes rather than treating the county as a single uniform polygon.

Colorado Search Demand & Trend Signal

Search trend monitoring captured live query volume across Colorado within 40 minutes of warning issuance. Because hyper-local search volume for sudden events requires a 24- to 72-hour window to register on 7-day rising metrics, demand analysis looks at the broader 30-day baseline across Colorado to measure the demand basin pulling into regional contractor rosters.

Breakout search terms across the state show intense user focus on contractor vetting and direct proximity queries:

Breakout Search Query (Past 30d)	Seed Topic	Demand Context
flood restoration companies	flood restoration	High commercial & residential intent
flood restoration company near me	flood restoration	Immediate emergency lookup
flood damage restoration service	flood restoration	Full-scope service inquiry
water damage restoration aurora	water damage restoration	Front Range demand corridor
water damage restoration aurora co	water damage restoration	Geo-specific contractor intent
water damage restoration company near me	water damage restoration	Mobile emergency conversion query
water mitigation companies	water mitigation	Early-stage carrier / extraction focus

By growth percentage, high-velocity queries across Colorado include water damage restoration service near me (+70%), restoration water damage company (+70%), and water damage restoration denver (+60%). Subregional activity highlights Denver, Colorado Springs–Pueblo, and Grand Junction–Montrose as the three most active DMAs in the state.

What This Means for Restoration Teams

Flash flood events in western Colorado create rapid silt, sediment, and Category 3 blackwater contamination when surface runoff penetrates crawlspaces, basements, and foundation slabs. Even if localized rainfall totals appear moderate, runoff volume through desert washes can breach grade rapidly.

Key operational takeaways:

Immediate Containment: Mud and silt must be extracted before drying equipment is placed; running air movers over sediment aerosolizes particulate and bio-contaminants.
Moisture Mapping: Test perimeter subflooring and framing immediately. In dry climates like western Colorado, rapid surface evaporation frequently hides deep structural saturation behind baseboards and insulation.
Proximity Positioning: The breakout surge in “near me” search terms demonstrates that consumers call the first local verified provider they can reach. Verified phone lines and dispatch triage are critical.

Sources and Verification

Official data verified against: National Weather Service Grand Junction (weather.gov/gjt); NOAA National Weather Service Alerts API; Google Trends Colorado Regional Dataset (Past 7d and Past 30d windows).

Informational brief only — not an official warning broadcast. Monitor NOAA Weather Radio and local county emergency management for evacuation and shelter orders.

September 14, 2026

Storm Updates: Upper Ohio Valley–Central New York Slight Risk — Sunday, September 13, 2026

This is a live Sunday afternoon snapshot of local storm-type events across the United States as of Sunday, September 13, 2026. The Storm Prediction Center 2000 UTC Day 1 Convective Outlook holds a Slight Risk of severe thunderstorms from the upper Ohio Valley into central New York, covering about 43,500 square miles and 8.3 million people, with Pittsburgh, Rochester, Akron, Syracuse, and Canton inside the higher contour. A broader Marginal Risk wraps Columbus, Cincinnati, Buffalo, Dayton, and Albany. No convective watches and no mesoscale discussions were in effect on the afternoon check. Restoration exposure this window is wind-driven roof and tree work on the Ohio–Pennsylvania–New York corridor, leftover Saturday water in the Appalachians and Mid-Atlantic, and a separate WPC flood Slight over southern New England plus eastern Kansas into western Missouri.

These are county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this afternoon

SPC upgraded portions of the corridor to Slight earlier Sunday with the 1630 UTC package and held that upgrade in the 2000 UTC update issued 2:57 p.m. CDT by forecaster Wendt. The language is isolated to widely scattered severe storms this afternoon and evening, mainly damaging wind along a cold front moving east through the Great Lakes, Ohio Valley, and Northeast. Deep-layer shear of 35–45 kt is enough for organized bands, short bowing segments, and a few initial supercells. Hail is secondary because lapse rates aloft are only about 6–6.5 C/km. Storms are expected to weaken with eastward extent this evening as nocturnal cooling and a less unstable airmass take over.

As of the afternoon product cycle, SPC listed no watches valid (most recent issued watch was 667 on a prior day) and no mesoscale discussions in effect (most recent MD 2291). Today’s official LSR page covering 1200 UTC September 13 through 1159 UTC September 14 still showed no tornado, hail, or wind reports at the afternoon check — the front had not yet produced a logged severe report in that window.

Weather Prediction Center Day 1 Excessive Rainfall Outlook, valid 12 UTC September 13 through 12 UTC September 14 and issued 3:46 a.m. EDT, keeps Slight Risk areas over portions of the Northeast and the Central Plains. Southern New England language focuses on Long Island and coastal Connecticut and Rhode Island, with the threat expected to exit late afternoon. Central Plains language favors eastern Kansas and western Missouri overnight as a low-level jet strengthens. A Marginal Risk remains over the Southern Rockies and Four Corners on monsoon moisture and already-wet soils.

Hotspot 1 — Upper Ohio Valley into central New York

This is the live Slight contour. SPC expects widely scattered thunderstorms along and ahead of the front from parts of Ohio into western New York by mid-afternoon, then a quick eastward sweep across the upper Ohio Valley into the Northeast. Population centers inside the Slight: Pittsburgh, Rochester, Akron, Syracuse, Canton. Marginal ring includes Columbus, Cincinnati, Buffalo, Dayton, Albany.

Counties to watch: Allegheny, Beaver, Butler, Westmoreland, and neighboring southwest Pennsylvania counties; Summit, Stark, Portage, and adjacent northeast Ohio counties; Monroe, Livingston, Ontario, Onondaga, and neighboring western and central New York counties. Lake-effect is not the story — this is a progressive cold-front band.

Restoration read: wind first. Stage tarps, generators, and tree crews before dark even without a watch. If a warning includes heavy rain on soils already wet from Saturday, treat the same ZIP as a water job by morning. Photograph roofs in remaining daylight only if it is safe.

Hotspot 2 — Southern New England flood leftover plus Mid-Atlantic runoff

WPC’s Slight Risk for excessive rainfall over the Northeast is the second desk. Discussion from the 0748 UTC Sunday package: precipitable water up to about 2.25 inches, efficient rainfall rates, and concern for Long Island and coastal Connecticut and Rhode Island through mid-to-late morning into afternoon before the axis exits offshore. Flash Flood Warning text earlier Sunday covered eastern Worcester County, Maryland, including Ocean City and Berlin, with 1–2 inches already down and rates near 2 inches in 30 minutes. That warning window closed in the morning; the afternoon desk treats it as runoff and urban ponding unless a new warning fires.

Saturday’s heavy rain is still in Appalachian channels. Overnight and early-Sunday Flood Warning and Flash Flood Statement text from Charleston, West Virginia, and Pittsburgh referenced lingering high water after 1–6 inches Saturday in pieces of Kanawha, Clay, Braxton, Gilmer, Lewis, Harrison, Doddridge, and southern Clarion County, Pennsylvania. Those are aftermath tickets, not a new Slight Risk.

Restoration read: southern New England is today’s water if cells trained this morning. West Virginia and western Pennsylvania are yesterday’s water still in the street and the basement. Do not send the same crew to both stories without checking which county actually has a warning now.

Hotspot 3 — High Plains scatter and Central Plains flood overnight

SPC keeps isolated strong-to-severe storms possible across parts of the central and northern High Plains this afternoon and evening — southern Wyoming, northeast Colorado, and the Nebraska Panhandle in a modest upslope regime — then elevated storms increasing over western and central South Dakota toward the mid-Missouri Valley late tonight. Hail and gusts are the local threats, not a watch-scale line.

WPC’s second Slight Risk sits on the Central Plains overnight. Guidance favors eastern Kansas and western Missouri, including low-to-moderate chances of more than 3 inches near the Kansas City metro in some 00Z HREF members. That is a Monday-morning extraction desk if cells train on the front.

Restoration read: High Plains is isolated hail and wind. Kansas City–eastern Kansas–western Missouri is the overnight flood watch list, not this afternoon’s Ohio Valley wind list.

Just hit

Saturday’s (September 12, 1200 UTC through Sunday 1159 UTC) preliminary LSRs are already tickets. Kansas carried the hardest wind: Chanute Martin Johnson Airport logged 84 mph at 0545 UTC Sunday; Chanute dispatch reported power outages and tree branches; utility poles went down near Galesburg in Neosho County. Clark County, Kansas, mesonet gusts reached 75 mph near Acres. Cherokee County, Kansas, saw a hangar roof collapse near Hallowell and 70 mph estimated at West Mineral. Perryton, Texas, had 6–8 power poles snapped south of town and an uprooted tree. Kingfisher County, Oklahoma, reported snapped wooden poles and 60–70 mph gusts near Cashion.

Hail: golf-ball (1.75 inch) at Beatrice, Nebraska, and Randall, Kansas; 2.00 inch near Coldwater and Wilmore in south-central Kansas; walnut-size at Holdrege, Nebraska. Pennsylvania already had tree-and-wire work Saturday afternoon across Washington, Allegheny, Jefferson, Westmoreland, Indiana, and Greene counties — including a tree on a house near Spraggs. A landspout was reported near Palm Coast, Florida, and an EF-0 survey was completed east of Spring Grove, Virginia. Those are closed survey items, not today’s Slight Risk.

Pulse table

Region	Main threats	SPC / NWS level	Status this afternoon
Upper OH Valley / SW PA / central NY	Damaging wind, lightning, isolated hail	SPC Slight (2000 UTC)	Live outlook — no watch
Columbus–Cincinnati–Buffalo ring	Isolated strong wind	SPC Marginal	Conditional
Long Island / coastal CT–RI–SE MA	Flash flood, urban ponding	WPC Slight ERO	Winding down late afternoon
Eastern KS / western MO	Training heavy rain overnight	WPC Slight ERO	Tonight into Monday morning
High Plains / western SD	Isolated hail and gusts	SPC isolated / Marginal	Afternoon–overnight scatter
Four Corners / S Rockies	Heavy rain on wet soils	WPC Marginal	Monsoon-style cells
Saturday KS–OK–TX / PA trees	Wind, hail, trees, poles	LSRs logged	Aftermath / tickets
Atlantic / Gulf vs. U.S. mainland	No landfalling tropical cyclone	NHC quiet Atlantic	Quiet

What this means for restoration teams

A Slight Risk without a watch is still a staffing problem. The corridor from northeast Ohio through southwest Pennsylvania into Rochester and Syracuse can produce a few 58–65 mph gust swaths, trees on service drops, and isolated hail even if coverage stays widely scattered. Saturday’s 84 mph Chanute gust and snapped poles in Neosho, Cherokee, Kingfisher, and Ochiltree counties are already claims. Southern New England and Appalachian runoff is extraction and drying, not a new wind line.

For teams in the Slight: stage before the first warning, not after. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside. Turn around on flooded Appalachian and Delmarva roads — Saturday and early-Sunday warnings already documented closed pavement.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. The National Hurricane Center afternoon page showed no tropical cyclones in the Atlantic. Tropical Storm Norbert was moving west over the open eastern Pacific near 18.2°N, 132.7°W with 50 mph winds — not a U.S. land threat. Do not invent a watch that SPC has not issued. The work today, if it verifies, will be scattered: a wind swath through an Ohio, Pennsylvania, or New York county, leftover flood tickets from Saturday, and a possible overnight rain pulse toward Kansas City.

Looking ahead

SPC Day 2 Convective Outlook issued 12:29 p.m. CDT Sunday (valid 12 UTC Monday through 12 UTC Tuesday) places a Slight Risk from southeast Nebraska into western Iowa. Summary language: scattered strong to severe thunderstorms late Monday afternoon into early evening near Omaha, Lincoln, Des Moines, Council Bluffs, and Ames, with a Marginal ring toward Sioux City, Waterloo, and Grand Island. That is Monday’s desk. Tonight’s Ohio Valley–New York band should weaken after dark.

Sources and how to verify

Primary sources dated Sunday, September 13, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook; SPC current watches page (none valid); SPC current mesoscale discussions page (none in effect); SPC today’s storm reports (none received in the 13/1200–14/1159 UTC window at afternoon check) and September 12 LSR list; Weather Prediction Center Day 1 Excessive Rainfall Outlook updated 0748 UTC; National Hurricane Center public page (no Atlantic tropical cyclones; TS Norbert over the eastern Pacific); National Weather Service watches/warnings text feed.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay. Morning desk for this calendar day: Storm Updates: Ohio Valley–Northeast Marginal Risk, Kansas Wind Aftermath — Sunday, September 13, 2026 (Morning).

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 13, 2026

Storm Updates: Ohio Valley–Northeast Marginal Risk, Kansas Wind Aftermath — Sunday, September 13, 2026 (Morning)

This is a live Sunday morning snapshot of local storm-type events across the United States as of the early hours of Sunday, September 13, 2026. Overnight into this morning the south-central Plains watch expired. Severe Thunderstorm Watch 667 is no longer valid. The Storm Prediction Center 1300 UTC Day 1 outlook holds a Marginal Risk of severe thunderstorms across parts of the Ohio Valley into the Northeast, and a second Marginal Risk across the central and northern High Plains, valid 131300Z–141200Z.

These remain county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Restoration exposure this morning is leftover Kansas wind and hail from last night, plus an afternoon wind corridor from Ohio into western New York and the Northeast if the front organizes. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this morning

No convective watches are currently valid. The most recently issued watch was Watch 667, covering portions of southwest Kansas, Oklahoma, and the Texas Panhandle through 10:00 p.m. CDT Saturday. That watch is expired. SPC’s 0744 AM CDT Sunday discussion (Gleason/Lyons) expects isolated to scattered thunderstorms along and ahead of a cold front by mid-afternoon (around 19–22Z) from parts of Ohio into western New York, then spreading quickly east across the upper Ohio Valley into the Northeast.

Deep-layer shear of 35–45 kt is enough for supercells at first and a marginal, isolated hail threat despite poor lapse rates aloft. Clusters and bowing segments with isolated damaging wind are the more likely mode once linear forcing of the front takes over. Confidence is too low for higher wind probabilities. Convection should weaken this evening as it moves into a less unstable airmass.

A separate Marginal Risk sits from northeast Colorado into southeast Wyoming and the Nebraska Panhandle late afternoon, with elevated storms possible later tonight across western and central South Dakota toward the mid-Missouri Valley. Isolated hail and wind are the language there, not a watch.

Hotspot 1 — Upper Ohio Valley into the Northeast

This is today’s live outlook corridor, not a live watch. A surface cold front tracks east under a strengthening west-southwesterly mid-level jet. Seasonably moist low-level air is in place, but poor mid-level lapse rates and cloud cover should keep instability marginal. That is why this is a Marginal Risk and not a Slight.

Cities and counties to watch this afternoon and evening: Columbus, Cleveland, Cincinnati, Dayton, and neighboring Ohio counties; Pittsburgh and the western Pennsylvania ridge; Buffalo and western New York; the northern West Virginia panhandle. SPC lists a Day 1 Marginal footprint of about 163,000 square miles and roughly 22.7 million people, with Columbus, Cleveland, Pittsburgh, Cincinnati, and Buffalo named in the risk-area list.

Bands of precipitation with embedded thunderstorms were already ongoing this morning across New Jersey into southern New York and New England. Most guidance keeps that activity elevated over land. Trends still get monitored for any surface-based instability over Long Island and southern New England.

Restoration read: wind first if cells organize after 3 p.m. local. Stage tarps and tree crews in the Ohio–Pennsylvania–western New York strip before late afternoon, not after the first warning. Water is secondary unless a cell trains on ground already wet from Saturday’s Ohio Valley–Mid-Atlantic rain.

Hotspot 2 — Kansas, Oklahoma, and Texas Panhandle just-hit

Watch 667 is the overnight ticket, not today’s new watch. Preliminary SPC local storm reports from the 12 UTC Saturday–12 UTC Sunday window include 2.00-inch hail north of Coldwater in Comanche County, Kansas, and northwest of Wilmore in Kiowa County around 0010–0015 UTC; golf-ball hail earlier near Beatrice, Nebraska, and Randall, Kansas; and measured wind of 84 mph at Chanute Martin Johnson Airport (KCNU) at 0545 UTC, with power outages and tree branches down in Chanute and utility poles near Galesburg in Neosho County. Additional measured gusts of 75 mph on the Kansas mesonet east-southeast of Acres in Clark County, 64 mph near Darrouzett in Lipscomb County, Texas, and snapped poles and a grain auger south of Perryton, Texas, sit in the same family.

Those are already claims. Photograph in daylight if it is safe. The new work today, if it verifies after 13 UTC Sunday, is isolated damaging wind on the Ohio Valley–Northeast Marginal Risk plus isolated High Plains hail and wind.

Hotspot 3 — High Plains and leftover water

A closed mid- and upper-level low over the Pacific Northwest this morning moves toward the northern Rockies and High Plains. Destabilization is limited. A narrow upslope corridor from northeast Colorado into southeast Wyoming and the Nebraska Panhandle is the afternoon cell area. Elevated storms may increase later tonight over western and central South Dakota toward the mid-Missouri Valley, with isolated hail on the first development.

Saturday’s Weather Prediction Center Day 1 excessive-rainfall outlook carried a Slight Risk over portions of the Ohio Valley, Mid-Atlantic, and southern Arizona, with the northern New Jersey–New York City–Long Island piece weighted toward late Saturday night into Sunday. That water is already in streets, small streams, and some interiors. Treat leftover flood statements as aftermath, not a new national headline, and check the current WPC Day 1 map and local NWS flood products before you assign a crew.

Just hit

Saturday’s Kansas–Oklahoma Slight Risk and Watch 667 produced the hail and wind listed above. Pennsylvania tree and wire reports from Saturday afternoon in Washington, Allegheny, Westmoreland, Indiana, Jefferson, and Greene counties are already on the books from the previous flood-and-wind pulse. A Flagler County, Florida, landspout near Palm Coast and an EF-0 survey east of Spring Grove in Surry County, Virginia, are local Saturday reports, not today’s organized corridor.

The National Hurricane Center discussion this morning shows no named tropical cyclone threatening U.S. land. The Atlantic remains quiet for a named-storm landfall. A central Atlantic wave is being monitored at low odds and is not a U.S. mainland desk item this morning.

Pulse table

Region	Main threats	SPC / NWS level	Status this morning
Upper OH Valley / Northeast	Isolated damaging wind, brief hail	SPC Marginal (Day 1 1300 UTC)	Outlook live; no watch
Central / northern High Plains	Isolated hail and wind	SPC Marginal	Late afternoon into tonight
SW Kansas / Oklahoma / TX Panhandle	Wind to 84 mph, 2-inch hail overnight	Watch 667 expired	Just-hit / claims
OH Valley–Mid-Atlantic water	Flash flood leftover from Saturday Slight ERO	Local flood products	Aftermath; verify county
Atlantic / Gulf vs. U.S. mainland	No landfalling named storm	NHC quiet on the coast	Quiet

What this means for restoration teams

An 84 mph airport gust and snapped poles are roof, siding, tree-on-structure, and service-drop work in Neosho, Comanche, Kiowa, Clark, and neighboring Kansas counties plus the Perryton, Texas, corridor. Two-inch hail is vehicle and roof claims on a narrow path. Today’s Ohio Valley–Northeast Marginal Risk is a thinner wind desk: isolated gusts, not a regional derecho. Staff it as county warnings, not a multi-state surge.

Water from Saturday night into Sunday morning along the I-95 and upper Ohio Valley axis is a 24–48 hour mold clock if it is already inside. Do not send the same crew to Chanute wind and a Pittsburgh or northern New Jersey water job without checking which county still has a warning.

What this is not

This is not a live severe thunderstorm watch and not a U.S. mainland hurricane landfall. The work this morning is leftover Kansas and Texas Panhandle wind and hail. The work this afternoon, if it comes, will be scattered wind along the front from Ohio into the Northeast and isolated High Plains cells. That is the local-storm pattern this desk should staff.

Looking ahead

Monday (Day 2) the SPC has a Slight Risk of severe thunderstorms late afternoon into evening across parts of eastern Nebraska into western and central Iowa — an isolated severe storm or two, and perhaps a small organizing cluster, near Omaha, Lincoln, Council Bluffs, and Ames. Destabilization along a northward-retreating front remains the uncertainty. Watch the next Storm Tracker update rather than assuming Sunday’s Marginal Risk is the last line of the week.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center Sep 13, 2026 1300 UTC Day 1 Convective Outlook; SPC current watches page (no watches valid as of 0814 UTC Sunday; most recently issued watch 667); SPC today’s storm reports for the 20260912 1200 UTC–20260913 1159 UTC window; Weather Prediction Center Day 1 Excessive Rainfall Outlook language covering Saturday into early Sunday; National Hurricane Center Atlantic tropical weather discussion 1215 UTC Sunday; National Weather Service warning text for Wichita, Dodge City, Amarillo, Cleveland, Pittsburgh, Buffalo, and neighboring offices.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay. Prior desk: Saturday afternoon, September 12 storm updates (Watch 667).

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 13, 2026

Muse to Cursor: I Gave My AI Its Own Engineering Team
TL;DR: My personal AI runs on Muse. It can’t write code into my repos by itself — so I built it a bridge to Cursor’s cloud agents. One repo, two transports, nine tools. Now when I say “add CI to that repo,” it dispatches an agent, checks the PR, and merges. Here’s how the Muse-to-Cursor loop actually works.

The direction nobody talks about

Everyone’s building the same arrow: human → AI writes code faster. I built the other arrow: AI → AI. My assistant (Muse) holds all my context — my repos, my work orders, my rules. Cursor’s cloud agents hold the hands — they can open PRs, run CI, touch repos. The bridge between them is an MCP server I open-sourced: cursor-cloud-agents-mcp.

The interesting part isn’t the tools. It’s the shape: one orchestrator that holds all the context, and disposable agents that each know one task. The orchestrator doesn’t write the code — it briefs, checks, and merges. The agents don’t set direction — they execute the brief. That separation is the whole trick.

Two transports, one repo

I almost built two projects. Then I realized the only real difference between audiences is where the credential lives. So it’s one repo, two transports:
- REST — your Cursor API key, direct to api.cursor.com. For general users.
- Sandbox — for assistants running inside sandboxed environments (like Muse/Meta’s), where there is no API key to hand out. It shells out to a brokered cursor-agent CLI on PATH instead.
Same nine tools either way: launch, status, result, follow-up, cancel, list, models, whoami, usage.

The lessons are in the timeouts

The v1 API splits agents and runs, and launches can take minutes — sometimes timing out after succeeding. So the bridge mints the agent ID client-side before the call: a retry after a timeout can never create a duplicate. A timeout is reported as unknown, never as failure, then reconciled. Run status is the source of truth, because agent “ACTIVE” doesn’t mean “still working.” These are the details that separate a demo from something you can actually operate.

It earned its keep on day one

The first thing I pointed it at was its own repo: add CI to cursor-cloud-agents-mcp. The agent opened a PR with a GitHub Actions workflow. The first CI run failed — and caught a real bug: the package’s floating dependency had resolved to MCP 2.x, which renamed FastMCP out from under the import. The repo was shipping broken against current dependencies and nobody knew. Pin, re-run, green, merge. I didn’t touch a terminal.

I didn’t trust my own first draft

Before any of that, four AI models reviewed the spec against Cursor’s live docs — and independently caught the same flaw: my original design was shaped around the retired v0 API. Then two more reviewed the actual code and found real bugs: a broken idempotency path, a transport auto-detect that would have grabbed the wrong binary, a polling loop that blocked the server. All fixed before it shipped. The irony I like: the final review round ran through the bridge itself. The launcher timed out on all four agents — and the bridge’s own timeout-reconciliation showed they were all actually running.

Where this goes

v1.1 brings MCP 2.x support. Around it, I’m building the rest of the pattern: work orders as GitHub issues, a daily SLA check, a weekly digest — the scaffolding that turns “AI that can open PRs” into something closer to staff. Most people use agents as a faster keyboard. I’m interested in what happens when they’re the hands and something with memory is the head.

MIT licensed. Issues and PRs welcome — help make it better.

github.com/tygart-media/cursor-cloud-agents-mcp
September 12, 2026

Storm Updates: Kansas–Oklahoma Watch 667, Ohio Valley Flood Pulse — Saturday, September 12, 2026

This is a live Saturday afternoon snapshot of local storm-type events across the United States as of Saturday, September 12, 2026. The organized pulse is on the south-central Plains. The Storm Prediction Center holds a Slight Risk of severe thunderstorms across parts of the south-central Plains into the Ozarks, and Severe Thunderstorm Watch 667 is in effect from 3:45 p.m. until 10:00 p.m. CDT for portions of southwest Kansas, Oklahoma, and the Texas Panhandle. Farther east, the Weather Prediction Center keeps a Slight Risk of excessive rainfall over the Ohio Valley and Mid-Atlantic. Tropical Storm Norbert is over the open eastern Pacific and is not a U.S. land threat.

These are county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Restoration exposure this afternoon and evening is wind-driven roof and siding work, isolated large hail, trees on service drops, and interior water where cells train over already-wet ground in the Ohio Valley and Mid-Atlantic. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What is live this afternoon

Watch 667 covers southwest Kansas, Oklahoma, and the Texas Panhandle through 10:00 p.m. CDT. Primary threat language from SPC: scattered damaging winds and isolated significant gusts to 80 mph, plus isolated very large hail to 2 inches. Tornado probability in the watch is low. The 2000 UTC Day 1 outlook, issued 3:00 p.m. CDT Saturday, expanded the Slight Risk southwest across parts of western Oklahoma after satellite showed agitated cumulus and isolated initiation along a remnant outflow. Temperatures of 102–104°F south of the wind shift support severe-caliber downdrafts if clusters organize.

Mesoscale Discussion 2286, issued 2:52 p.m. CDT, flagged southern Kansas into northwest Oklahoma as watch-likely before the watch went up. Most probable peak gusts in that discussion were 65–80 mph; most probable peak hail 1.50–2.50 inches. MD 2287 followed on a severe-potential, watch-possible track as storms tried to fill in.

WPC’s Day 1 Excessive Rainfall Outlook, valid 12 UTC Saturday through 12 UTC Sunday, keeps a Slight Risk over the Ohio Valley and Mid-Atlantic. That language is flood first, wind second: 2.0–2.25 inch precipitable water along I-95 from Richmond toward Philadelphia, with a higher-end Slight pocket in the upper Ohio Valley where flash-flood guidance is under 2 inches in northern West Virginia and western Pennsylvania. Central Plains stay Marginal for excessive rain. Florida remains in a localized urban-flood environment on 2.0–2.25 inch precipitable water.

The official SPC Local Storm Report list for the 12 UTC Saturday through 12 UTC Sunday window was still empty as of mid-afternoon, which is expected this early in the convective day. SPC’s same-day report-trend plot on the homepage was already counting preliminary tornado, wind, and hail ticks as storms started to fire. Treat those as unofficial until they land on the LSR page.

Hotspot 1 — Southwest Kansas, Oklahoma, Texas Panhandle

This is the live watch. Storms are expected to increase and intensify near an outflow boundary across Oklahoma and near a front across Kansas and the eastern Texas and Oklahoma Panhandles. SPC notes a narrow corridor of 2,000–3,500 J/kg MLCAPE, 30–40 kt of deep-layer shear, and steep mid-level lapse rates that support isolated 2-inch hail before storms cluster. Higher-based convection in the hot mixed layer favors wind over tornadoes.

Cities and counties to watch: Wichita, Hutchinson, and Emporia in Kansas; Enid, Ponca City, and the Oklahoma City metro fringe; Alva to Chandler along the watch axis; Amarillo and the eastern Texas Panhandle. Neighboring offices: Dodge City, Wichita, Norman, Tulsa, Amarillo.

Restoration read: wind and hail first. Stage tarps, generators, and glass/roof crews before dark. A 75–80 mph gust on a well-mixed 104°F afternoon is a tree-and-roof ticket, not a regional catastrophe. Photograph roofs in remaining daylight only if it is safe.

Hotspot 2 — Ohio Valley and Mid-Atlantic flood pulse

This is the water desk, not the watch desk. WPC holds a Slight Risk of excessive rainfall from the upper Ohio Valley through the Mid-Atlantic. HREF signals in the morning discussion showed moderate-to-high chances of 3-hour and 6-hour flash-flood guidance exceedance in the upper Ohio Valley, and 20–40 percent chances of 3-hour totals over 2 inches from the Richmond area late Saturday into the Delaware Valley and southern New Jersey Saturday night. The Slight Risk was extended north through eastern Pennsylvania, northern New Jersey, and into the New York City metro and lower Long Island for late Saturday night into Sunday.

SPC keeps a Marginal Risk of isolated damaging wind with loosely organized clusters in the upper Ohio Valley this afternoon. That is secondary to the flood overlay.

Cities and counties to watch: Pittsburgh and western Pennsylvania; northern West Virginia; Columbus–Dayton corridor on the wind-marginal fringe; Richmond, Baltimore, Philadelphia, and the I-95 urban core Saturday night.

Restoration read: extraction and drying if cells train. Urban streets, underpasses, and small streams fail first. Do not treat this as the same story as Watch 667. Different hazard, different crew mix.

Hotspot 3 — North Georgia leftover water and Plains scatter

National Weather Service Peachtree City issued multiple Flash Flood Warnings this morning for Cobb, DeKalb, Douglas, Fulton, Carroll, and Paulding counties, including Atlanta, Marietta, Sandy Springs, Douglasville, and Villa Rica. Radar-indicated totals of 1–4 inches were already on the ground in those products, with additional 1–3 inches possible in the warned windows. Some of those warnings expired by mid-afternoon; the water is still in the street and in the buildings. That is already a ticket, not a new watch.

Elsewhere, isolated strong-to-severe cells remain possible on the edges of the Slight Risk into the Ozarks and on the hot High Plains. Florida stays a local urban-flood and lightning desk on deep tropical moisture. A Flash Flood Watch remains up over the Paradise and Hagen burn scar in northeast Oregon and southeast Washington from Saturday afternoon through Sunday evening — debris-flow country, not a CAT event.

Just hit

Friday’s official LSR window (12 UTC September 11 through 12 UTC September 12) is the last closed book. Preliminary reports included a tornado touchdown 7 miles northeast of Artichoke, Minnesota, plus golf-ball hail near Artichoke and Alberta in Stevens County, Minnesota. Wind and hail also hit Tarrant County, Texas (Arlington–Mansfield trees, poles, and up to 1.75-inch hail), Bexar County, Texas (golf-ball hail near Converse and Kirby), and a long tree-down swath through South Carolina, Virginia, and North Carolina. Those are already claims. Today’s new work, if it verifies after 12 UTC Saturday, is Watch 667 wind and hail plus Ohio Valley–Mid-Atlantic water.

Pulse table

Region	Main threats	SPC / NWS level	Status this afternoon
SW Kansas / Oklahoma / TX Panhandle	Damaging wind to 80 mph, isolated 2-inch hail	Slight + Watch 667 to 10 p.m. CDT	Live watch
Ohio Valley / Mid-Atlantic	Flash flood, training heavy rain, isolated wind	WPC Slight excessive rainfall; SPC Marginal wind	Tonight into Sunday morning
North Georgia metro	Urban flash flood leftover from morning warnings	FFW earlier today	Aftermath / still in street
Ozarks / central Plains fringe	Isolated hail and wind	SPC Marginal	Scattered
NE Oregon / SE Washington burn scar	Flash flood / debris flow	Flash Flood Watch through Sunday evening	Local hydrologic
Atlantic / Gulf vs. U.S. mainland	No landfalling tropical cyclone	Quiet on the mainland coast	Quiet (Norbert open EPAC)

What this means for restoration teams

Wind at 65–80 mph is roof, siding, gutter, and tree-on-structure work. Isolated 2-inch hail is broken glass and pitted panels in a narrow swath, not a statewide event. Heavy rain on the Ohio Valley–Mid-Atlantic Slight Risk is wet drywall and a 24–48 hour mold clock. Atlanta-metro water from this morning is already inside some buildings.

For teams in or near Watch 667: stage before 5 p.m. CDT, not after the first warning. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside. Do not send the same crew to Oklahoma wind and Pittsburgh water without checking which county actually has a warning now.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. Tropical Storm Norbert is expected to dissipate east-southeast of Hawaii by midweek and is not a CONUS or Hawaii landfall problem on this desk. The work tonight, if it comes, will be scattered: a wind or hail swath through a Kansas or Oklahoma county, a flooded intersection where Ohio Valley or Mid-Atlantic cells train, leftover urban water in metro Atlanta. That is the local-storm pattern this desk should staff.

Looking ahead

Sunday, SPC Day 2 is a Marginal Risk of strong storms with small to marginally severe hail and locally damaging wind from the Ohio Valley to the Northeast. Coverage is uncertain. Monday, Day 3 adds a small Slight Risk across eastern Nebraska into western Iowa. Watch the next Storm Tracker update rather than assuming Watch 667 is the last line of the weekend.

Sources and how to verify

Primary sources, all date-stamped Saturday, September 12, 2026: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook; Severe Thunderstorm Watch 667; Mesoscale Discussions 2286 and 2287; SPC today and September 11 Local Storm Reports; Weather Prediction Center Day 1 Excessive Rainfall Outlook issued 3:39 a.m. EDT; National Weather Service warning text including Peachtree City flash-flood products; National Hurricane Center public advisory on Tropical Storm Norbert (open eastern Pacific, no U.S. land threat).

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay. Morning desk for this calendar day: Saturday morning Storm Updates. Related desk: Friday afternoon Storm Updates.

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 12, 2026

Storm Updates: Kansas–Oklahoma Slight Risk, Ohio Valley–Mid-Atlantic Flood Pulse — Saturday, September 12, 2026 (Morning)

This is a live Saturday morning snapshot of local storm-type events across the United States as of the early hours of Saturday, September 12, 2026. Overnight into this morning the organized severe pulse that ran eastern South Dakota into Minnesota has expired. Severe Thunderstorm Watch 666 is down. No convective watches are valid as of mid-morning UTC. The Storm Prediction Center 1300 UTC Day 1 outlook has upgraded the afternoon and evening corridor to a Slight Risk of severe thunderstorms across parts of the central and southern Plains into the Ozarks. The Weather Prediction Center Day 1 Excessive Rainfall Outlook holds a Slight Risk for portions of the Ohio Valley and Mid-Atlantic.

These are county- and ZIP-scale thunderstorms, not a mainland hurricane landfall. Restoration exposure today is large hail and damaging wind on the Plains, plus interior water where Ohio Valley and Mid-Atlantic cells train. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

What expired overnight vs what is live this morning

Watch 666 covered southwestern into north-central Minnesota and eastern South Dakota from 6:40 p.m. to 10:00 p.m. CDT Friday. Primary language was scattered large hail, isolated very large hail to two inches, damaging gusts to 70 mph, and a tornado or two if a supercell held together early in the watch. That watch is expired. SPC current watches page as of 12:03 UTC Saturday: no watches valid. Last issued watch remains 666.

What is live this morning is the outlook, not a watch. The 0748 AM CDT Saturday Day 1 convective outlook is valid 1300 UTC Saturday through 1200 UTC Sunday. Headline: there is a Slight Risk of severe thunderstorms across parts of the central and southern Plains. Summary language: isolated to scattered severe thunderstorms capable of large to very large hail and severe or damaging winds may occur across parts of the central and southern Plains into the Ozarks this afternoon and evening. A separate Marginal Risk corridor remains over the upper Ohio Valley for isolated damaging gusts this afternoon.

WPC’s current Day 1 excessive-rainfall outlook, issued 339 AM EDT Saturday and valid 12Z Saturday to 12Z Sunday, keeps a Slight Risk of rainfall exceeding flash-flood guidance for portions of the Ohio Valley and Mid-Atlantic. Precipitable water of 2.0 to 2.25 inches is forecast to stream north along the I-95 corridor from Richmond and Washington toward Baltimore and Philadelphia by Saturday evening, then into the New York metro and lower Long Island late Saturday night. That late-night northern end of the slight risk is expected to linger into Sunday (Day 2).

Hotspot 1 — Southern Kansas, northern Oklahoma, eastern Oklahoma and Texas Panhandles into the Ozarks

This is today’s severe ticket. Elevated storms persisted overnight into early morning across southern Nebraska into eastern Kansas and western Missouri on a modest low-level jet. SPC expects that activity to weaken through the remainder of the morning, with some guidance still showing additional development along outflow across southern Kansas and northern Oklahoma. A fairly strong cold front is draped from eastern Colorado into Kansas and northwest Missouri. That boundary is the afternoon focus.

Along and south of the front, a narrow zone of moderate to strong instability (MLCAPE 2000–3500 J/kg) is forecast this afternoon from the eastern Oklahoma and Texas Panhandles into southern Kansas and northern Oklahoma. Deep-layer shear of about 30–40 kt is enough for organized updrafts. Isolated robust development along the front is favored around 21–23Z once convective temperatures are reached. Sustained supercells would pose a threat for large to very large hail, including isolated two-inch-plus stones. Higher-based convection from the eastern Panhandles into southwest and south-central Kansas and northern Oklahoma favors scattered severe downdrafts. Some gusts could exceed 75 mph. Clustering later this afternoon and evening remains uncertain, but isolated damaging wind may persist into much of Oklahoma and the Ozarks if upstream storms in Kansas and western Missouri stay organized.

Cities and counties to watch: Wichita, Hutchinson, Emporia, Liberal, and Derby in the Slight Risk core; Oklahoma City, Tulsa, and Kansas City sit in the surrounding Marginal Risk. Restoration read: hail first in the Slight Risk, then wind. Stage tarps and roof kits before mid-afternoon local. If a cell trains on the same ZIP, treat it as a water job by morning.

Hotspot 2 — Ohio Valley through the Mid-Atlantic I-95 corridor

This is today’s flood ticket, not the hail ticket. SPC keeps only a Marginal Risk of isolated damaging wind across parts of the upper Ohio Valley this afternoon in a narrow corridor of filtered heating between denser clouds over Ohio and a stationary boundary to the east. Mid-level lapse rates stay poor. The bigger operational signal is WPC. HREF signals include moderate-to-high chances of three- and six-hour flash-flood-guidance exceedance in the upper Ohio Valley, and a 20–40 percent chance of three-hour QPF over two inches from the Richmond area late Saturday afternoon, then from northeast Maryland into the Delaware Valley and southern New Jersey Saturday night. The Slight Risk was extended north through eastern Pennsylvania, northern New Jersey, and into the New York metro and lower Long Island, with that northern end weighted late Saturday night into Sunday.

Cities and counties to watch: Pittsburgh and western Pennsylvania, northern West Virginia, the upper Ohio Valley; Richmond, Washington, Baltimore, Philadelphia, northern New Jersey, New York City, and lower Long Island on the late-day and overnight rain axis. Restoration read: urban street flooding, low crossings, and wet drywall where cells train. The 24–48 hour mold clock starts when water is inside, not when the outlook expires.

Hotspot 3 — Just-hit Upper Midwest and leftover Arizona water

Friday evening’s Slight Risk over far eastern South Dakota into Minnesota verified locally. Preliminary Storm Prediction Center local storm reports for the 1200 UTC Friday to 1159 UTC Saturday window include a tornado touchdown reported seven miles northeast of Artichoke in Stevens County, Minnesota, around 0051 UTC, plus downed power poles eight miles south of Alberta on County Highway 9. Golf-ball hail (1.75 inches) was reported east and south of Artichoke and south of Alberta. Half-dollar hail fell near Dumont, Herman, Norcross, and Toronto, South Dakota. Wind damage and trees on lines were reported around Chokio, Embarrass and Britt in St. Louis County, Whipholt and Longville in Cass County, and Blue Grass in Wadena County, with one report noting possible tornado damage and large trees blocking County Road 23.

Separate Friday hail and wind clusters hit Tarrant County, Texas (Arlington and Mansfield, golf-ball hail and trees and poles down), Bexar County, Texas after 0310 UTC (golf-ball hail near Converse), and a long tree-down corridor through South Carolina, North Carolina, and Virginia. Arizona flash-flood warnings fired Friday evening over Gila, Coconino, Navajo, Cochise, and Graham Counties, including fire-scar drainages. Those Arizona warnings were evening products; treat them as just-hit water, not today’s new Slight Risk.

Just hit

Minnesota and eastern South Dakota are yesterday’s tickets: hail, trees, poles, and at least one reported tornado touchdown that still needs a damage survey, not a new watch. North Texas and San Antonio-area hail are Friday afternoon and overnight work already on the books. The Carolinas and southern Virginia tree-down scatter is the same. Today’s new work, if it verifies, is the Kansas–Oklahoma hail and wind corridor plus localized flash flooding from the Ohio Valley onto the Mid-Atlantic I-95 axis tonight.

Pulse table

Region	Main threats	SPC / NWS / WPC level	Status this morning
Southern KS / northern OK / Panhandles / Ozarks	Large to very large hail, damaging wind, isolated 75+ mph gusts	SPC Slight (core) + Marginal surround	Outlook live; no watch yet
Upper Ohio Valley	Isolated damaging wind; heavy rain / flash flood	SPC Marginal + WPC Slight ERO	Afternoon increase
Mid-Atlantic I-95 (RIC–DC–BAL–PHL–NYC)	Training heavy rain, urban flash flood	WPC Slight ERO	Late afternoon through Saturday night
Eastern SD / west-central and northern MN	Hail, trees, poles, reported tornado	Watch 666 expired 10 p.m. CDT Fri	Aftermath / just-hit
North Texas / San Antonio metro	Friday hail and wind	Local LSRs	Aftermath
Southeast AZ fire scars / washes	Flash flood from Friday cells	Expired FFWs	Aftermath
Atlantic / Gulf vs. U.S. mainland	No landfalling tropical cyclone	NHC: formation not expected next 7 days in Atlantic	Quiet on the mainland coast

What this means for restoration teams

Two-inch hail is roof and auto glass work in the Slight Risk counties. Gusts of 60–75 mph are siding, gutter, and tree-on-structure work. A reported tornado near Artichoke, Minnesota, is a narrow swath — staff it as a local damage survey, not a regional event. Ohio Valley and Mid-Atlantic heavy rain is wet drywall and a same-night extraction clock if water is inside. Do not send the same crew to Wichita hail and Pittsburgh flooding without checking which county actually has a warning now.

For teams in or near the Kansas–Oklahoma Slight Risk: stage before mid-afternoon local, not after the first warning. Property owners should photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside.

What this is not

This is not a regional derecho and not a U.S. mainland hurricane landfall. National Hurricane Center Atlantic outlook at 800 AM EDT Saturday: tropical cyclone formation is not expected during the next seven days. Eastern Pacific Tropical Storm Norbert is well west-southwest of the southern tip of Baja California and is not a U.S. land threat. The work today, if it comes, will be scattered: a hail swath through a Kansas or Oklahoma county, a wind-thrown tree in the upper Ohio Valley, a flooded underpass where Mid-Atlantic cells train. That is the local-storm pattern this desk should staff.

Looking ahead

SPC Day 2 is a Marginal Risk Sunday afternoon and evening from western New England through the upper Ohio Valley for small to marginally severe hail and locally damaging gusts. Day 3 is also Marginal. Fire-weather outlooks are Elevated today and Sunday. The next Day 1 convective outlook is scheduled by 1630 UTC. Watch the afternoon Storm Tracker update rather than assuming this morning’s Slight Risk is the last line of the weekend.

Sources and how to verify

Primary sources: NOAA Storm Prediction Center Sep 12, 2026 1300 UTC Day 1 Convective Outlook (issued 0748 AM CDT); SPC current watches page (no watches valid; most recently issued Watch 666); SPC preliminary local storm reports for 20260911 1200 UTC–20260912 1159 UTC; Weather Prediction Center Day 1 Excessive Rainfall Outlook issued 339 AM EDT Sat Sep 12, 2026; National Hurricane Center Atlantic Tropical Weather Outlook 800 AM EDT Sat Sep 12, 2026; National Weather Service watch/warning text feed.

Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay. Prior desk: Friday, September 11 storm updates (afternoon).

Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

September 12, 2026

Author: William Tygart

What is live this afternoon

Hotspot 1 — Eastern Nebraska into western and central Iowa

Hotspot 2 — Watch 668: western and northern Kansas, south-central Nebraska

Hotspot 3 — Central and southwestern Iowa flood Moderate, plus Southwest rain

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

The rule is not a rumor

The volume is not a vibe

Stop treating these as separate products

The wedge is a free checker. Not a platform.

Why this is buildable now

How the company actually compounds

What not to build

A build order that will survive contact

Why this is worth writing, and building

What does a 3,222 request-per-hour spike actually mean?

Why are six wp-login POSTs the number that matters?

How do you tell bot noise from a hostile login event?

What is the one-paragraph verdict from this morning’s numbers alone?

Why does this belong on an AEO and GEO desk?

What we would not claim

What we would do again

FAQ

Is a WordPress request spike the same thing as a brute-force attack?

How many wp-login POSTs should trigger a change?

Can AI crawlers cause a 3,000-request hour?

Should you publish the source IP addresses from a spike?

What is live this morning

Hotspot 1 — Eastern Nebraska into western and central Iowa

Hotspot 2 — Central and southwestern Iowa flood overlay

Hotspot 3 — Sunday just-hit and Southwest scatter

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

The Warning: Rio Blanco County, CO

Colorado Search Demand & Trend Signal

What This Means for Restoration Teams

Sources and Verification

What is live this afternoon

Hotspot 1 — Upper Ohio Valley into central New York

Hotspot 2 — Southern New England flood leftover plus Mid-Atlantic runoff

Hotspot 3 — High Plains scatter and Central Plains flood overnight

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

What is live this morning

Hotspot 1 — Upper Ohio Valley into the Northeast

Hotspot 2 — Kansas, Oklahoma, and Texas Panhandle just-hit

Hotspot 3 — High Plains and leftover water

Just hit

Pulse table

What this means for restoration teams

What this is not

Looking ahead

Sources and how to verify

The direction nobody talks about

Two transports, one repo

The lessons are in the timeouts

It earned its keep on day one

I didn’t trust my own first draft

Where this goes

What is live this afternoon

Hotspot 1 — Southwest Kansas, Oklahoma, Texas Panhandle

Hotspot 2 — Ohio Valley and Mid-Atlantic flood pulse

Hotspot 3 — North Georgia leftover water and Plains scatter

Just hit

Pulse table

What this means for restoration teams

What this is not