This morning's Asian propagation wasn't bad overall, although what sounded like 
a promising band around 1300 failed to get much of a sunrise enhancement boost. 
Energetic audio was once again limited to the NHK big guns, 972-HLCA and 
1566-HLAZ. 
  
An initial band check at 1300 showed a serious carrier from 1206-Yanbian, which 
soon fizzled before the FSL-enhanced PL-380's could be set up in the back yard. 
At my 1305 start time it was once again 594, 693, 747, 774, 972 and 1566 as the 
only TP's with fair to good audio, although the CRI stations on 1017, 1044 and 
1206 were at threshold levels in and out for much of the session. Like 
yesterday the 1053-Jammer was on a roll, reaching one of its best signals on 
these hot-rodded PL-380's at 1317. And also like yesterday a presumed 738-BEL2 
was in and out with weak Chinese speech and music, to be joined at 1320 with 
603-HLSA, having similar weak signals. Weak audio from 657-Pyongyang around 
1310 fizzled quickly, and increasing daylight didn't help bring up anything 
new, although the Japanese big guns on 594, 693 and 774 sounded a little more 
vibrant. Overall it was a fairly typical April session, which might have been 
pretty exciting on the ocean coast but pretty routine here. 
  
1053  Korean Jammer   One of its best jams of the season at 1317 (very good) 
https://app.box.com/s/pj7827coqbrt3imwh9ksvlm8hxexzrrn   
  
73 and Good DX, 
Gary DeBock (in Puyallup, WA, USA) 
Stand-alone 3" FSL Tecsun PL-380 Ultralight 
  
  
_______________________________________________
IRCA mailing list
[email protected]
http://montreal.kotalampi.com/mailman/listinfo/irca

Be sure to register now for the Joint DX Convention
Kansas City, September 9 to 11.  Hotel space is filling up.
Registration info:
http://www.nrcdxas.org


Opinions expressed in messages on this mailing list are those of the original 
contributors and do not necessarily reflect the opinion of the IRCA, its 
editors, publishing staff, or officers

For more information: http://www.ircaonline.org

To Post a message: [email protected]

Reply via email to