National Weather Service Logs 69 MPH Gust at Greensboro Airport as Storms Cut Power to More Than 20,000 in Guilford County

A 70 MPH Warning, a 69 MPH Reading, and 20,000 Dark Homes

Just after 2:30 p.m. on Friday, September 18, an instrument at Greensboro's airport clocked a wind gust of 69 mph^[1]. Eleven minutes later, the National Weather Service issued a warning citing that reading and forecasting gusts up to 70 mph across the storm's path^[1]. That one-mile-per-hour gap matters more than it looks. The 70 mph figure is a forecast of the worst gust the storm could produce; the 69 mph figure is the one number an instrument actually measured^[1].

The storms that followed knocked out power across the Piedmont Triad. Duke Energy reported more than 20,000 customers without electricity in Guilford County by Friday evening^[3]. By Saturday morning, over 13,000 customers were still dark across Guilford, Forsyth and Rockingham counties, with about 10,000 of those in Greensboro alone^[4]. Crews found downed trees, downed lines, and damage to roofs and outbuildings^[1][4].

What nobody has yet is a dollar figure. No agency has published a damage estimate, an injury count, or a verified tally of wrecked buildings for this storm. That gap is where this story gets complicated — because two weeks earlier, a different storm hit some of the same towns, and its numbers are much easier to find.

Two Storms, One Set of Numbers

Central North Carolina had already been hit once this month. A storm on September 4 and 5 tore through Greensboro, and the city's own response update counted roughly 77 downed trees, about 31,000 Duke Energy customers out at peak, a destroyed playground on Pear Street, and a damaged footbridge in Bluford Park^[5]. WFDD, the public radio station covering the cleanup, dated that story September 5 — pinning those numbers to the earlier storm, not the one on September 18^[6].

Asheboro's state of emergency belongs to that same earlier event. Mayor Joey Trogdon declared it at 8:45 a.m. on Sunday, September 6, after a storm the day before^[7][8]. The city was still under that declaration on September 16, having hauled out more than 160 tons of debris^[9] — two days before the storms this article covers even arrived.

The risk is obvious: those two sets of facts are easy to merge. Asheboro shows up in this week's Weather Service warning text as a town in the storm's path, which is accurate, but it doesn't mean Asheboro took new damage on September 18^[1]. Borrowing the September 4-5 numbers to describe this storm would overstate what actually happened this time.

Why a Warning Counts as Success Even If Nobody Gets Hurt

A severe thunderstorm warning goes out when a storm is producing, or is expected to produce, winds of at least 58 mph or hail at least one inch across. The Weather Service issued a string of these from around 11:40 a.m. to 4:24 p.m. on September 18, naming Greensboro, High Point, Asheboro, Randleman, Siler City and several smaller towns directly^[1][2][17].

Here's the mechanism worth understanding: the agency is graded on lead time and specificity, not on whether the storm actually caused damage everywhere it warned about. A warning naming a town in the storm's path is a projection of where the danger is heading, not proof that town got hit. That's also why the same 69 mph gust at one airport can justify a 70 mph hazard line for an entire warning area — forecasters are estimating the worst plausible gust across the whole storm, not claiming every town felt it^[1].

That distinction sits underneath a much bigger national argument. Critics of recent staffing cuts at the National Weather Service's parent agency, NOAA, say the real danger isn't the storm that got warned correctly — it's the one that doesn't, because nobody was on shift to catch it. The Center for American Progress, a Democratic-aligned think tank, says NOAA has lost close to 600 staff, with about 40% of forecast offices carrying significant vacancies, and at least eight no longer staffed overnight^[14].

A Fight That Isn't Actually About This Storm

Supporters of the staffing changes make a different argument: judge the agency by outputs, not inputs. On September 18, warnings went out hours before the worst winds arrived, and they named specific towns^[1][2][17]. To supporters, that's evidence the system still works even with a leaner staff, helped by modernized radar and automated tools.

Both camps are arguing past this particular storm. Neither has pointed to anything about September 18 specifically — no missed warning, no documented staffing gap in the Raleigh office that day. NBC News reported NOAA has been actively trying to rehire forecasters^[12], which critics read as evidence the cuts went too far and supporters read as normal churn.

One fact-check keeps both sides honest. PolitiFact examined the claim that the administration "defunded" the Weather Service and rated it false — the agency was cut, but not defunded, with a smaller NWS budget increase actually still proposed^[15]. That finding undercuts the more extreme version of the critics' argument without settling the underlying question of whether current staffing is enough.

Trees, Power Lines, and Who Pays to Keep the Lights On

On the ground in Greensboro, the fight is less abstract. Duke Energy's argument is that thunderstorm damage in the Piedmont mostly comes from wind-driven trees falling on power lines, not equipment failing on its own^[3][4]. Fixing a 20,000-customer outage means finding and repairing hundreds of separate breaks scattered across the grid, which is slower than the headline number suggests.

Customers have a recurring counterargument: if tree-trimming and line-hardening programs are supposed to prevent this, they want to see outages actually declining, not repeating in the same counties every few weeks^[4][10]. That tension resurfaces every time Duke asks state regulators to approve rate increases tied to storm recovery and grid-hardening costs^[20].

City governments sit in the middle of this, and their main tool is a legal one. A state of emergency isn't a statement about how severe a storm looked — it's a switch that lets a city skip normal purchasing rules, call in outside crews, and start the paperwork trail needed for state or federal reimbursement^[7][9]. That's why Asheboro kept its declaration active for ten days after a storm that, by most accounts, wasn't catastrophic.

What's Still Missing

Even the yardstick for measuring storm costs has gotten less reliable. NOAA's billion-dollar disaster database, long the standard public reference for storm damage nationally, hasn't been updated since the tracking program was halted^[11][16]. WRAL has also reported on a long-run rise in atmospheric instability across the eastern U.S. since 1979, using data from Climate Central, a climate-communications nonprofit — a regional trend, but not one any scientist has tied to this specific storm^[11].

So for now, the honest tally is a short one: a 69 mph measured gust, a 70 mph forecast hazard, more than 20,000 outages at the peak, and no damage estimate at all^[1][3][4]. Local stations have filled that gap with outage counts and words like "violent" because there isn't yet a dollar figure to report^[4]. Whether a firmer number — or a fuller picture of what this storm did versus what the last one did — arrives in the coming days is still an open question.