|
|
Post by wethurgeek on Aug 3, 2015 6:54:11 GMT -5
Thoughts on putting movement on distant CBs? I've always been instructed not to do it, wondering why? |
|
|
|
Post by TCU 2U2 on Aug 3, 2015 8:10:13 GMT -5
Thoughts on putting movement on distant CBs? I've always been instructed not to do it, wondering why? We leave it as optional ... will not write up either way CB DSNT W CB DSNT W MOV E |
|
|
|
Post by coldairfunnel on Aug 3, 2015 9:47:39 GMT -5
You are the observer. If you feel it is operationally significant then put anything you want to in remarks. It's your call.
|
|
|
|
Post by weatheri on Aug 3, 2015 9:55:04 GMT -5
The examples in 7900.5 (both B and C) are horrible.
The format for reporting a CB is:
14.38.Significant Cloud Type [PLAIN LANGUAGE]. Cumulonimbus or Cumulonimbus
Mammatus (CB or CBMAM_LOC_ (MOV_DIR). Cumulonimbus (CB) or cumulonimbus mammatus
(CBMAM), as appropriate, (for which no thunderstorm is being reported) is coded in the above format,
where CB or CBMAM is the cloud type, LOC is the direction from the station, and MOV_DIR is the
movement with direction (if known). The cloud type, location, movement, and direction entries must
be separated from each other with a space.
Nowhere in that paragraph does it state unless it is beyond 10SM. However the example states:
EXAMPLES
CB up to 10 SM west of the point of observation, moving toward the east: CB W MOV E
Cloud is more than 10 SM away: CB DSNT W
We always go by the definition, not the examples.
So, yes we include the movement.
|
|
|
|
Post by alstein on Aug 3, 2015 10:32:56 GMT -5
I always felt that order went this way
1) 7900
2) Contractor rules, provided they don't contradict 7900
3) Whatever you determine is important. Whatever isn't forbidden is permitted.
I won't write up for someone violating 2 if it's legal in 1- I might say something, that's it.
|
|
|
|
Post by hlsto2 on Aug 3, 2015 11:15:39 GMT -5
We give distant CB movement. everybody has the internet, so everybody should be able to tell movement from the radar loop. those of you that don't give movement...what if you have a line of CB 30 miles north of the stn moving south at 30 mph. giving movement gives the ap an hours warning that TS may strike within the hour. no movement given...like gomer says...surprise...surprise...surprise! 7900, page 111, gives an incorrect LTG remark...FRQ LTGCG VC. VC is a distance...not a location. frequent lightning SOMEWHERE between 5 and 10 miles out. FRQ LTGCG VC W. frequent lightning 5-10 miles WEST of the AP.
I still see a few stns with the remark...OCNL LTGCG VC S TS S MOV N. to me, and according to 7900, you are a saying the lightning is 5-10 miles south but the TS is 0-5 miles south.
|
|
|
|
Post by kukblue1 on Aug 3, 2015 18:33:11 GMT -5
I'll give movement most of the time but if they are drifting or moving real slow then I'll leave it out
|
|
|
|
Post by Prplra on Aug 4, 2015 11:02:17 GMT -5
Movement of distant CB's is optional for us. If I can reasonably determine movement (from radar for example) then I will include it in the obs.
|
|
|
|
Post by wx74012 on Jan 7, 2016 19:59:29 GMT -5
If you have a low cloud ceiling and are not able to see a distant CB but there is a distant thunderstorm, is it ok to put in the remarks something like this? DSNT LTGICCCCG NE TS NE MOV E or does it have to be DSNT LTGICCCCG NE CB NE MOV E? It seemed to me from the 7900 that it was ok to use either or and is not really clear.
|
|
|
|
Post by hlsto2 on Jan 7, 2016 23:21:20 GMT -5
of course if you CAN hear the thunder from a storm 15 miles away...OCNL LTGCG DSNT E TS DSNT E MOV E. if you CAN'T hear thunder...OCNL LTGCG DSNT E CB DSNT E MOV E. 7900 hints that a TS 15 miles away would only be in remarks...not in present weather.
|
|
