• 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.

1/17/11 REPORTS: FL

Joined
Jan 7, 2008
Messages
537
Location
Bryan, TX
Mediocre results here but since the tornado-warned storm was within range for what I thought would be a possible intercept, and there was some rotation on GR3 before I set out, I gave it a shot. Ended up getting the following picture when I stopped at Jetty Park in the Cape Canaveral area at 12:42 PM of what might be the diminished wall cloud (or a scud cluster that was the next closest thing) that produced the tornado report to the West in Orange Countyat 12:13 (16:13 UTC)
--
1613 6 W PORT SAINT JOHN ORANGE FL 2848 8089 OBSERVER REPORTED ROTATING FUNNEL WITH DEBRIS CLOUD NEAR THE INTERSECTION OF FAY BLVD AND I-95.

approximate radar image showing my vehicle position also attached, though rotation had already diminished, and I didn't discern any visually.

update: just added a somewhat later radar pic that shows meso-marker returned as storm moves further out over ocean.Picture 7.jpg


possiblewallcloudNorthofJettyPark1-17-11.jpgradarofJettyParklocation1-17-11tornadowarning.jpg

This was a day with almost no CAPE at all but as you can see, there was ample helicity:
http://www.srh.noaa.gov/images/rtimages/mlb/adas/helicity31.gif

Update: here's a wider view of possible wall cloud (with scud)
widerviewpossiblewallcloud.jpg

update: SPC corrected the tornado report from Orange to read "Brevard":

1613 4 W PORT SAINT JOHN BREVARD FL 2848 8085 OBSERVER REPORTED ROTATING FUNNEL WITH DEBRIS CLOUD WEST OF THE INTERSECTION OF FAY BLVD AND I-95. THIS IS A CORRECTION TO THE LOCATION OF THE PREVIOUS STORM REPORT.
 
Last edited by a moderator:
Back
Top