On 1/12/2017 9:53 AM, Henry N. Chappell II wrote:
> Josh,
>
> No, the NEPA & SHPO is required in all states for all new structures
> with licensed and unlicensed equipment.

Henry, we have been told by the FCC that it's not required if the 
structure will hold only unlicensed equipment. I have a query into them 
regarding the lightly-licensed (3.65) radios, but it takes a while to 
hear back from them. I posted here hoping to expedite my question 
somewhat. :)


> -------- Original message --------
> From: Josh Reynolds <[email protected]>
> Date: 1/12/17 9:42 AM (GMT-06:00)
> To: WISPA General List <[email protected]>
> Subject: Re: [WISPA] NEPA/SHPA Requirement
>
> This seems to be only required in certain areas, correct? Mainly on or
> near areas of historical or religious significance?
>
> On Jan 12, 2017 9:35 AM, "Sam Morris" <[email protected]
> <mailto:[email protected]>> wrote:
>
>     (Sorry... SHPO, not SHPA)
>
>     National Environmental Policy Act, and State Historical Preservation
>     Office. I'm not a lawyer, and I didn't sleep in a Holiday Inn Express
>     last night, but the way I understand it, they are legal requirements
>     pertaining to new structures that are going to hold radio equipment that
>     uses licensed (or lightly-licensed?) frequencies, and makes a
>     requirements to go through a certification process from these two
>     offices. NEPA
>     (https://www.epa.gov/nepa/national-environmental-policy-act-review-process
>     
> <https://www.epa.gov/nepa/national-environmental-policy-act-review-process>)
>     is an EPA requirement, and SHPO,
>     (https://www.nps.gov/Nr/shpolist.htm
>     <https://www.nps.gov/Nr/shpolist.htm>)
>     as it has pertained to us, is primarily native-Americans inspecting the
>     site and certifying that you're not desecrating sacred ground.
>
>     I know it's a requirements if the structure holds 11 Ghz, 220 Mhz, 6
>     Ghz, etc. I don't know if it is also a requirements if it's the 3.65
>     type of license, hence my question. :)
>
>     Thanks
>     Sam
>
>     On 1/12/2017 8:40 AM, Josh Reynolds wrote:
>      > NEPA/SHPA? Educate me pls
>      >
>      > On Jan 12, 2017 7:05 AM, "Sam Morris" <[email protected]
>     <mailto:[email protected]>
>      > <mailto:[email protected] <mailto:[email protected]>>> wrote:
>      >
>      >     Good Morning,
>      >
>      >     It's my understanding that if a new structure that will hold only
>      >     non-licensed equipment is built, that NEPA/SHPA certification
>     isn't
>      >     required. What about 3.65 equipment? Since it's "lightly
>     licensed",
>      >     where would a new structure (where 3.65 equipment will
>     reside) fall with
>      >     regards to the NEPA/SHPA requirement?
>      >
>      >     Thanks!
>      >     Sam
>      >     _______________________________________________
>      >     Wireless mailing list
>      > [email protected] <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>
>      > http://lists.wispa.org/mailman/listinfo/wireless
>     <http://lists.wispa.org/mailman/listinfo/wireless>
>      >     <http://lists.wispa.org/mailman/listinfo/wireless
>     <http://lists.wispa.org/mailman/listinfo/wireless>>
>      >
>      >
>      >
>      > _______________________________________________
>      > Wireless mailing list
>      > [email protected] <mailto:[email protected]>
>      > http://lists.wispa.org/mailman/listinfo/wireless
>     <http://lists.wispa.org/mailman/listinfo/wireless>
>      >
>
>     _______________________________________________
>     Wireless mailing list
>     [email protected] <mailto:[email protected]>
>     http://lists.wispa.org/mailman/listinfo/wireless
>     <http://lists.wispa.org/mailman/listinfo/wireless>
>
>
>
> _______________________________________________
> Wireless mailing list
> [email protected]
> http://lists.wispa.org/mailman/listinfo/wireless
>

_______________________________________________
Wireless mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/wireless

Reply via email to