Go ahead and issue the PCN for the 11 that is clear now. If they aren't paying 
attention you are golden. If they are then submit the license request anyway. 
It will be rubber stamped and issued. Their protest, if they bother, is going 
to have to include documentation of their squatting and that is not going to 
help their case. Someone needs to stand up to these guys. Might as well be you 
Mark.


PC
Blaze Broadband

On December 15, 2014 8:16:04 PM EST, Mark Radabaugh via Af <af@afmug.com> wrote:
>The squatting by the HFT guys is really ticking me off at the moment.  
>I need an additional link on a path and can’t find any working channels
>in 11Ghz.   I’m going to have to replace the existing 11Ghz link with 2
>18Ghz links instead of adding a polarization to the existing 11Ghz.  
>It doubles the cost for a path that the HFT guys have been sitting on
>for at least 2 years.
>
>Mark
>
>
>> On Dec 15, 2014, at 8:09 PM, Ken Hohhof via Af <af@afmug.com> wrote:
>> 
>> Maybe he’s assuming in a few years quantum entanglement or
>faster-then-light neutrinos will make them obsolete?
>>  
>> I see more PCNs than physical links.  Abusing the system to call dibs
>on towers and frequencies.  Most of the PCNs I see are actually
>renewals, that way they can tie up the coordinated path without
>starting the construction deadline clock ticking.
>>  
>>  
>>  
>> From: Jon Langeler via Af <mailto:af@afmug.com>
>> Sent: Monday, December 15, 2014 6:53 PM
>> To: af@afmug.com <mailto:af@afmug.com>
>> Subject: Re: [AFMUG] licensed prior coordination notifications
>>  
>> What happens in a few years?
>>  
>> -Jon
>> 
>> Sent from my iPhone
>> 
>> On Dec 15, 2014, at 7:11 PM, CARL PETERSON via Af <af@afmug.com
><mailto:af@afmug.com>> wrote:
>> 
>>> I use them to make a KML of all the HFT links that are going to be
>sitting there on the towers doing nothing in a few years.  
>>>  
>>> 
>>> 
>>> On Dec 15, 2014, at 6:01 PM, Bill Prince via Af <af@afmug.com
><mailto:af@afmug.com>> wrote:
>>> 
>>>> We get them all the time too.  I just scan them to see if they are
>in the same county as our stuff (and they usually are not).  But I
>filter them all to a PCN folder so they aren't clogging up my inbox.
>>>> 
>>>> You get it if (I think) you are within 150 miles on the same
>frequency with one of your licenses.
>>>> 
>>>> --
>>>> bp
>>>> <part {dash} 15 {at} SkylineBroadbandService {dot} com>
>>>> 
>>>> On 12/15/2014 9:57 AM, Chuck McCown via Af wrote:
>>>>> Sorry Tim...Liz  and all the other frequency coordinators here.  I
>know it is not your fault.
>>>>>  
>>>>> You get a few licensed links up and pretty soon you are inundated
>with notices. 
>>>>> The one time I complained about a link, nothing happened at all. 
>>>>>  
>>>>> So, as far as I am concerned, they are a welfare plan designed by
>the federal government to employ postal workers. 
>>>>>  
>>>>> From: Chuck McCown via Af <mailto:af@afmug.com>
>>>>> Sent: Monday, December 15, 2014 10:55 AM
>>>>> To: af@afmug.com <mailto:af@afmug.com>
>>>>> Subject: Re: [AFMUG] licensed prior coordination notifications
>>>>>  
>>>>> They go directly to the trash.
>>>>>  
>>>>> From: That One Guy via Af <mailto:af@afmug.com>
>>>>> Sent: Monday, December 15, 2014 10:51 AM
>>>>> To: af@afmug.com <mailto:af@afmug.com>
>>>>> Subject: [AFMUG] licensed prior coordination notifications
>>>>>  
>>>>> Since we got our license a few weeks ago we have gotten a ton of
>these things, some of which are a state away.
>>>>> What is the criteria for sending these things out?
>>>>> What are we supposed to do with them, are we supposed to run a pth
>calc to see if it looks like it will cause issues?
>>>>> whos responsible for prior notice if it looks like it might? Is it
>us or the applicant frequency coordinator?
>>>>>  
>>>>> -- 
>>>>> All parts should go together without forcing. You must remember
>that the parts you are reassembling were disassembled by you.
>Therefore, if you can't get them together again, there must be a
>reason. By all means, do not use a hammer. -- IBM maintenance manual,
>1925
>>>> 
>>> 
>>>  

Reply via email to