• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

6/4/08 REPORTS: VA/MD/DC

Bill Hark

EF5
Joined
Jan 13, 2004
Messages
1,354
Location
Richmond Virginia
This was an unexpected chase opportunity in Virginia. I couldn't resist a moderate risk for central and northern Virginia. With high instability and decent upper level support, severe storms were likely. I didn't like the veered surface winds though there was a small area of backed winds to the north of Richmond. The SPC issued a moderate risk for northern Va, MD and DC. I got off work at 1PM and drove north. A bow echo had already formed west of northern VA/DC and was moving east at 50 mph. The south side would pass south of DC and I hoped for some tornadic potential in that area. I drove north on -95, then east at Fredricksburg on 218. The bow echo rapidly by causing widespread wind damage, power outages and a couple of tornadoes. The tornadoes were mainly on the northside of the bow echo.
I meandered back west hoping for some isolated development south of where the bow echo passed. As expected, an isolated cell formed just north of Charlotteville, Va. I blasted west. The cell quickly became supercellular. Unfortunately, I got on the wrong side of the Rappahannock river. I expected the storm to come to me but it slowed and right-turned. I had to back track east, then south before turning back west toward the storm. It was now tornado-warned. Now I was stuck in heavy rush hour traffic slowing my progress. I followed the storm east. I think the meso passed over me while on I-95 judging by wind shift. Traffic was also slowed by these idiots taking cover under an overpass and blocking traffic. I followed the isolated supercell east, my progress slowed by the roadless Fort AP Hill. Just south on 17 from the intersection of 17 and 301, I filmed a weakly rotating funnel cloud to the northeast at about 7:08PM. I was looking into King George County.The storm weakened and I was caught on the otherside of the Rappahannock river. I ended the chase. I sent in a copy of the footage to the Sterling NWS. Hopefully, they will compare my location to their radar archives and any damage reports. So far, none for that area.

funnel cloud
http://www.harkphoto.com/060408funnelcloudKIngGeorgeCountyVA.jpg

Bill Hark
 
Back
Top