STARS site 127

[n4jri]

I can't seem to find the thread where we originally discussed this, but I've confirmed Site 127 (or more specifically, CC 152.5175) to be at VDOT's Edgehill Area Headquarters on State Road in King George County. Didn't get much reception on it through most of Caroline, but it's strong in King George on my handheld and gets out to about Westmoreland State Park. Just east of the park, my handheld switches over to Burgess. Not much heard on 127, but VSP RICH2 although a King George forest fire got me a little action on DOF OPS-2.

73/Allen (N4JRI)

 

[n4jri]

I can't seem to find the thread where we originally discussed this, but I've confirmed Site 127 (or more specifically, CC 152.5175) to be at VDOT's Edgehill Area Headquarters on State Road in King George County. Didn't get much reception on it through most of Caroline, but it's strong in King George on my handheld and gets out to about Westmoreland State Park. Just east of the park, my handheld switches over to Burgess. Not much heard on 127, but VSP RICH2 although a King George forest fire got me a little action on DOF OPS-2.

73/Allen (N4JRI)

Oops, my bad. Whatever I said about my radio switching over to the Burgess site, I really meant Warsaw.

My Fri/Sat journey took me along the C&O river line almost to Buchanan, and then home along the mountain line (now the Buckingham Branch RR) from Millboro to Keswick. Not a lot to report.

In Staunton, the folks using 464.55 [d051] at Western State Hospital appear to be using 467.900 [d051] as their Ch-2. The repeater on 154.04 [151.4] is there, but very low audio. (I wonder if they've narrowbanded) Nothing else new, except for the fact that the Buckingham Branch RR appears to have 160.455 working along the old C&O mountain line all the way to Clifton Forge.

73/Allen (N4JRI)

 

[MOTORHEAD3902]

I submitted this tower's established name to the DB. "Site 127" just sounded so cold and impersonal...think Area 51, LOL.

 

[n4jri]

I submitted this tower's established name to the DB. "Site 127" just sounded so cold and impersonal...think Area 51, LOL.

Okay! Of course, we're still waiting for sites 117 and 123, I think--not to mention Div.2 & 7. Are we in a slowdown?

I have to say that SEVA coverage was a lot better this time on my PSR-500. It seemed to glide effortlessly from Petersburg to Williamsburg to Franklin to Emporia to South Hill on this trip. Makes me wonder if they still think they need Waverly.

Any news on Div 2? I was hoping to do some tower-hunting after Easter.

73/Allen (N4JRI)

 

[MOTORHEAD3902]

From the events of last night, it seems 7th may be next up. Here's why I say this: someone (or something-read:computer switching) keeps patching Fairfax into Div 1, where the patch just keys up and talks over ongoing conversations. I thought I recognized the dispatcher that was talking over our traffic, then she ID-ed her station with the infamous quickly slurred KNAA586...

NoVA listeners, keep a-listening for those control channels!

 

[tglendye]

...Any news on Div 2? I was hoping to do some tower-hunting after Easter.

73/Allen (N4JRI)

Allen,

I was going to ask the same question today. From outside of Harrisonburg, I do a search b/n 150-160 mhz a couple of times a week, and have not found anything new in reference to STARS. I also have a TYS set up in my 500 with frequencies that APPEAR to be associated w/ the Harrisonburg site, but they have been quite as well.

I wonder if the budget situation has caused a slow down. I figure (ASSume) the budget has little or nothing to do w/ it since it is a contracted project, though.

Todd

 

[fmon]

I have to say that SEVA coverage was a lot better this time on my PSR-500. It seemed to glide effortlessly from Petersburg to Williamsburg to Franklin to Emporia to South Hill on this trip. Makes me wonder if they still think they need Waverly.73/Allen (N4JRI)

Off topic a little. Allen, what ROAM settings are you using on the 500?

Back on topic. Nice report, wish I'd had the freq programmed day before Thanksgiving as we drove up 301 across the Potomac, though Burgess was active well into Charles County MD.

 

[n4jri]

Off topic a little. Allen, what ROAM settings are you using on the 500?

Back on topic. Nice report, wish I'd had the freq programmed day before Thanksgiving as we drove up 301 across the Potomac, though Burgess was active well into Charles County MD.

Hi Frank,

I'm using 80 & 95 as my STARS thresholds and am pretty happy with it. It shops around more often and helps me deal with border areas like Surry, McKenney and Ashland. I need to give it more of a workout in southern New Kent.

When going up 301 were you using a moble or or portable? I had no luck at all with STARS in that area before Edgehill went online, and (contrary to what I reported in error) I never switched over to Burgess. I did go to Warsaw as I passed Westmoreland State Park and approached Montross. (got my CC freqs mixed up--that's where I miss the PRO96)

73/Allen (N4JRI)

 

[fmon]

Hi Frank,

I'm using 80 & 95 as my STARS thresholds and am pretty happy with it. It shops around more often and helps me deal with border areas like Surry, McKenney and Ashland. I need to give it more of a workout in southern New Kent.

When going up 301 were you using a moble or or portable? I had no luck at all with STARS in that area before Edgehill went online, and (contrary to what I reported in error) I never switched over to Burgess. I did go to Warsaw as I passed Westmoreland State Park and approached Montross. (got my CC freqs mixed up--that's where I miss the PRO96)

73/Allen (N4JRI)

Using 600 on STARS & JCNR/ NSWC Dahlgren, but had 500 scanning JCNR/AP Hill/Indian Head MD & Charles County MD

Edit:ROAM settings were default