OceanStWx
-
Posts
19,758 -
Joined
-
Last visited
Content Type
Profiles
Blogs
Forums
American Weather
Media Demo
Store
Gallery
Everything posted by OceanStWx
-
We'll get 'em next time.
-
Please report only your largest failstones
-
I love the shade SPC throws about wind. "Isolated 45-60 mph gusts"
-
I imagine some non-standard layer had 7+ lapse rates, but our 17z sounding had 6.5 from 700-500. Huge CAPE (2500) for around here, and 50 knots shear.
-
Half dollars at our old condo. Had my wife (then girlfriend) running around the deck to find the largest stone because I was at work.
-
Average temp at BOS on 12/23 is 33.3 degrees. You have to walk it back to 12/14 before you get an average temp warmer than that (33.7).
-
@Damage In Tolland got his tree topper and nothing more.
-
But sounds like the access road is a mess from all the rain/flash flooding. Also yes, if you head up from the Loop Trailhead it is quite steep, but the Brook Trail is more gradual. I wouldn't recommend looping it down the to the Loop Trailhead though, because you have to climb down through the ladders and rock cave. Going up is much easier in that stretch I think.
-
Head scratcher to me. Doesn't really match what the radar said, with a two scan TDS for Easton that's more than 400 yards. And Brockton definitely had a TDS too. Microburst don't throw debris into the air.
-
Yeah most of the time the tornado path looks like it's around 300 yard (but some of that could be RFD damage, hard to say when it's all sporadic trees), and at its widest around 450 yards. From the centerline to Ridgewood was nearly 3/4 of a mile. Far enough that could've been NBD. Given the environment, the RFD would've been the next windiest part of the storm, and a good deal south of Ridgewood. This wasn't the type of storm with a massive forward flank wind on it.
-
Based on the warning motion vector and the damage path, it was on the ground for around 8 or 9 minutes. Which matches the TDS, it was there for two scans which is at least 4 minutes but not quite 10. It's also clear that this wasn't continuously on the ground either. There are lots of roads it crossed without any damage indicated by BOX so far. So a weaker circulation that was "skipping" is likely.
-
It's definitely going to be a tornado. I'm following along as BOX uploads the damage points into our system, and it looks like mostly (all?) tree damage. High end EF0/low end EF1 type stuff. The still photo in the tweet above you can get the sense of what BOX is looking for beyond the damage itself. You can see the downed trees, while chaotic, are crossing paths showing convergent wind vs divergent straight line.
-
I'm listening to the scanner now and it's all hit and run chatter.
-
Unless you lived in those subdivisions it may not have been much to write home about.
-
That traffic stoppage is a telltale sign that some occurred.
-
BOX. Like around 0024z and 0030z. 0.9 degree slice is a little less noisy than 0.5.
-
There's going to be tornado damage just north of 495 near Easton/Raynham, and then the south side of Brockton.
-
That kind of sculpted updraft shows you just how fast it was spinning aloft.
-
Definitely two TDSs there in Bristol/Plymouth Counties.
-
Radar confirmed, so nobody has actually spotted one.
-
Really spinning like a top in the mid levels. There's enough juice below 10 kft that we could get a hose to the surface.
-
There's a little BWER on that UCONN cell. I would pull the trigger I think.
-
STP is near 1, so I could see pulling the trigger once rotational velocity is over 25 kt. Right now it's about 23.5 kt near Manchester. Pretty classic TOR problem of sidelobe contamination though.
-
Pics or it didn't happen. (You're not wrong though)
-
Skinny CAPE, no girth.
