Jump to content
  • Member Statistics

    18,663
    Total Members
    25,819
    Most Online
    tmcandrew
    Newest Member
    tmcandrew
    Joined

2026 Mid-Atlantic Severe Storm General Discussion


Kmlwx
 Share

Recommended Posts

Severe Thunderstorm Warning
National Weather Service Baltimore MD/Washington DC
745 PM EDT Thu Jun 11 2026

The National Weather Service in Sterling Virginia has issued a

* Severe Thunderstorm Warning for...
  South central Loudoun County in northern Virginia...
  The western City of Fairfax in northern Virginia...
  West central Fairfax County in northern Virginia...
  The northern City of Manassas Park in northern Virginia...
  Northwestern Prince William County in northern Virginia...
  The north central City of Manassas in northern Virginia...

* Until 800 PM EDT.

* At 745 PM EDT, a severe thunderstorm was located over Centreville,
  moving east at 50 mph.

  HAZARD...70 mph wind gusts.

  SOURCE...Radar indicated.

  IMPACT...Damaging winds will cause some trees and large branches
           to fall. This could injure those outdoors, as well as
           damage homes and vehicles. Roadways may become blocked by
           downed trees. Localized power outages are possible.
           Unsecured light objects may become projectiles.

* Locations impacted include...
  Centreville, South Riding, Fairfax, Vienna, Oakton, Chantilly, Bull
  Run, Haymarket, Manassas, Sudley, Manassas Park, Fairfax Station,
  Gainesville, Clifton, and Catharpin.

PRECAUTIONARY/PREPAREDNESS ACTIONS...

For your protection move to an interior room on the lowest floor of a
building.

&&

LAT...LON 3880 7763 3892 7763 3891 7727 3876 7737
TIME...MOT...LOC 2345Z 266DEG 43KT 3883 7742

THUNDERSTORM DAMAGE THREAT...CONSIDERABLE
HAIL THREAT...RADAR INDICATED
MAX HAIL SIZE...<.75 IN
WIND THREAT...RADAR INDICATED
MAX WIND GUST...70 MPH
 
Link to comment
Share on other sites

Had the craziest drive from Braddock to west ox via ffx county parkway. Left right as the shelf was coming overhead and made it home right before the rain wall. Gust front was legit, lots of airborne leaves and whatnot. Even managed to buffet my relatively small crv back and forth some. 

  • Like 2
Link to comment
Share on other sites

11 minutes ago, Eskimo Joe said:

Yes. I have the scanner up for Frederick County, MD and they have a somewhat steady stream of wires/trees calls coming out. 

It got windy here for sure especially before the downpour commenced.

Link to comment
Share on other sites

The shape of the velocity signature sort of makes me think there's a slight chance of a little kink or enhanced area that may be prone to spin briefly. But certainly not a strong tornado risk or anything - maybe more like a gustnado if that keeps up. 

Link to comment
Share on other sites

Just now, high risk said:

Two straight events in which the cams incorrectly weakened a line approaching our area.   Wondering if the lack of shear is causing the models to gust these lines out too quickly.  

It's interesting because anecdotally we have seen them bring through robust lines only for relative minimums to occur in swaths of our area. But yeah - this has been an interesting season of modeling. 

Link to comment
Share on other sites

37 minutes ago, Kmlwx said:

The LWX specialty warning size lol

97 mi long?  This kind of defeats the entire purpose of polygon *storm-based* warnings.

We can do better than one giant "carpet bomb" SVR.  There should be a limit to a size of a short-fused polygon warning.  

A large squall line is not necessarily "one-size fits all."

And all that has to happen is one wind damage report anywhere in the polygon and it verifies.  We should be fine-tuning and getting more detailed w/ warnings, not the other way around.  There is real impact (economic and social) from over-warning.

 

IMG_6710.PNG

  • Like 1
Link to comment
Share on other sites

1 minute ago, high risk said:

Two straight events in which the cams incorrectly weakened a line approaching our area.   Wondering if the lack of shear is causing the models to gust these lines out too quickly.  

Depth of the cold pool and surface inversions after the radiation flip over. I think the model cold pools are too shallow and/or the surface inversions are too deep.

  • Like 1
  • Thanks 2
Link to comment
Share on other sites

Just now, vortex95 said:

97 mi long?  This kind of defeats the entire purpose of polygon *storm-based* warming.  Back in the day,  entire counties were warned.

We can do better than one  giant "carpet bomb" SVR.  There should be a limit to a size of a short-fused polygon warning.  

And all that has to happen is one wind damage report anywhere in the polygon and it verifies.  We should be fine-tuning, and getting more details w/ warnings, not the other way around.  There is real impact (economic and social) from over-warning.
 

It seems like LWX will warn a huge swath and then if an area of considerable or destructive nature shows itself they will put a warning inside of the warning. I can see it from both sides...I think they do it because of the metro corridor honestly. 

  • Like 1
Link to comment
Share on other sites

Just now, high risk said:

Two straight events in which the cams incorrectly weakened a line approaching our area.   Wondering if the lack of shear is causing the models to gust these lines out too quickly.  

Two thoughts come to mind:

1.) These are machine learning/AI-influenced CAMS that don't yet have the "database" of events to properly articulate when these events die off.

2.) As we saw with April 2011 and the 2012 Derecho, mature MCS complexes persist longer than meso guidance if the downstream airmass is sufficiently unstable. However, the lack of an EML or good jet streak generally isn't enough to sustain the storms much past sunset. There is an eight part YouTube video from Rich Thompson (SPC met) speaking a Univ of Oklahoma and he talks about this extensively. I cannot find the YouTube series unfortunately.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

1 minute ago, wxmeddler said:

Depth of the cold pool and surface inversions after the radiation flip over. I think the model cold pools are too shallow and/or the surface inversions are too deep.

Any reason that it seems to be more prominent this season than prior ones? Or is that just recency bias? 

Link to comment
Share on other sites

2 minutes ago, vortex95 said:

97 mi long?  This kind of defeats the entire purpose of polygon *storm-based* warnings.

We can do better than one giant "carpet bomb" SVR.  There should be a limit to a size of a short-fused polygon warning.  

A large squall is not necessarily "one-size fits all."

And all that has to happen is one wind damage report anywhere in the polygon and it verifies.  We should be fine-tuning, and getting more details w/ warnings, not the other way around.  There is real impact (economic and social) from over-warning.

Agree 9/10 times. IMO, this is the 1 out of 10 times I'll differ given the numerous 250 Anniversary event from Baltimore to DC. In a situation like this, it's just easier to slap down a big polygon and say "it's coming everyone".

  • Like 1
Link to comment
Share on other sites

1 minute ago, Kmlwx said:

DCA is going to get rocked in a sec. Wind core almost heading right for the airport/Arlington. I see 70+mph pixels on LWX 

Actually even see a 75-76mph pixel on the LWX base reflectivity tilt. 

Link to comment
Share on other sites

Just now, yoda said:

Did LWX lose power?  Not getting any updates from them and getting internal server errors on their webpage

I can't imagine their page is hosted onsite - but I may be wrong. Probably just coincidental. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...