|
|
Post by tornado on Mar 3, 2014 18:06:37 GMT -5
The 7900.5C never says that it does. While ideally it would, it seems to be possible that the locations of the 2 phenomena would be different. Thoughts?
|
|
|
|
Post by toofarnorth on Mar 4, 2014 14:36:36 GMT -5
7900.5c, 10.29 references LTG as defining a TS. You can't have LTG without a TS, therefore if you have 2 locations (LTG at station and, say, DSNT N) you would report TS in present wx and remark for LTG in both locations and TS in both locations. I see no occasion when LTG could be reported w/o a TS. Anybody have such a scenario?
|
|
|
|
Post by toofarnorth on Mar 4, 2014 14:49:24 GMT -5
One possibility - LTGCA - you could have the parent CB in one sector and the LTGCA stretching to another sector - ie. LTGCA VC N-NE and TS VC N MOV___
|
|
|
|
Post by tornado on Mar 5, 2014 15:40:58 GMT -5
How would you code the follwing thunderstorm situation? Let's say a CB produced one audible thunderclap, from a LTGCG to the west, at 0000Z. LTGCG W TS W MOV E is coded in the TSB SPECI. After the initial SPECI, the CB moves overhead, producing heavy rain and gusty winds, but no more LTG. A SPECI is needed for VIS 2SM, and it is 0007Z. What are the remarks you would carry? The first picture on the left illustrates this.  What then would happen, if the CB quickly moves away to the east? Let's say it is now 0014Z. LTGCG has not been observed since 0000Z, and that was the 1 bolt to the west. But now, the CB that produced the LTG is to the east. A SPECI is needed at 0014Z, since the VIS improved to 7SM. The 2nd picture on the right illustatres this. How would you encode the LTG and TS remarks? |
|
|
|
Post by hlsto2 on Mar 5, 2014 16:28:10 GMT -5
since both examples are within 15 min of the TS start. TS OHD MOV E (0007Z) TS E MOV E (0014Z) since no ltg observed since 0000 and assuming you heard no thunder...a speci at 0015 or later to end the TS. remarks possibly...TS MOV E...TS DSIPTD E...or no remarks...since no remarks are required to show what happened to the TS that ended.
|
|
|
|
Post by tornado on Mar 5, 2014 16:32:55 GMT -5
since both examples are within 15 min of the TS start. TS OHD MOV E (0007Z) TS E MOV E (0014Z) What about a lightning remark? Would you omit it, because it was old data? |
|
|
|
Post by hlsto2 on Mar 5, 2014 17:01:41 GMT -5
if I saw no additional ltg...and the only strike was CG west of the station, it would no longer be valid. now, if I heard thunder while the TS was overhead or east...and didn't see the ltg I might say: OCNL LTGIC OHD TS OHD MOV E. lots of different possibilities.
|
|
|
|
Post by hlsto2 on Apr 2, 2014 13:22:02 GMT -5
would like to find out what other sites are doing in reference to ALDARS. Last night there was a super cell about 100 miles west of our location...moving east toward our area. The only cell on radar. I turned ALDARS on and it added the remark: LTG DSNT W when the storm was about 60 miles out. I could not see the storm or any ltg from my location, so I allowed ALDARS to xmit LTG DSNT W on the hourly. Then about 25 min later, ALDARS changed the remark to LGT DSNT W AND NW. I was then able to observe in cloud ltg. Since ALDARS does not code frequency, and only detects CG and CC ltg...it was not representative and not coding per service level A requirements. I turned ALDARS off and added the manual remarks: OCNL LTGIC DSNT W-NW CB DSNT W-NW MOV E. I left ALDARS off the rest of the event and the storm eventually dissipated about 20 miles west of the airport...whew. there were reports of hail 2.5" in diameter with this storm.
|
|
cirrus
Junior Member
Posts: 86
|
Post by cirrus on Apr 2, 2014 16:10:37 GMT -5
As soon as I get a hit on ALDARS I turn off the sensor and go manual, to avoid unwanted ASOS speci's
|
|
|
|
Post by hlsto2 on Apr 3, 2014 12:04:33 GMT -5
That's what I did. As soon as "I" saw the ltg I turned ALDARS off...so instead of LTG DSNT W...I manually input OCNL LTGIC DSNT W CB DSNT W MOV E
|
|
|
|
Post by consltg on Apr 6, 2014 18:47:54 GMT -5
I thought we weren't supposed to include movement in regards to DSNT CB.
|
|
sky
New Member
Posts: 45
|
Post by sky on Apr 8, 2014 9:59:51 GMT -5
Our station does follow both the lighting location and TS location have to match. Also we DO NOT put movement on Lighting or movement on DSNT CB's as well.
|
|
|
|
Post by toofarnorth on Apr 8, 2014 13:41:12 GMT -5
CBs should be accounted for - they either get reported "MOVD" if they drift out of sight or "DSPTD" if they collapse in our sight - we report movement even for DSNT CBs.
|
|
|
|
Post by consltg on Apr 8, 2014 15:07:08 GMT -5
Always amazed how the rules of weather observations can vary from one station to another. At our station if we were to put a Movement on a DSNT CB or LTG, it would be marked as an error.
|
|
|
|
Post by hlsto2 on Apr 8, 2014 21:54:49 GMT -5
Who would give you an error for DSNT CB movement...and why? If it is your SWO, you need a new SWO. If you have internet access, obviously you can access radar loops and easily determine movement of distant CB. If a line of distant CB is 50NW of the airport and moving southeast you can give heads up of possible tstm activity in a few hours, depending on the speed the line is moving. Otherwise, if you are not allowed to give the movement until the line is within 10 miles, you don't give much notice that significant weather is about to impact the airport.
|
|
