Close menu
September 04, 2020

5G “Small Cell” Proliferation Takes a Hit in Cambridge MA

In an important win for those who are concerned about 5G and small cell wireless proliferation, on August 26, 2020 the U.S. District Court for the District of Massachusetts dismissed a lawsuit by “neutral host” provider ExteNet Systems, Inc. against the City of Cambridge, MA.

The case could have far-reaching impacts when “neutral host providers” like American Tower, Crown Castle and ExteNet try to secure approval to occupy municipal rights-of-way. Neutral host providers build wireless infrastructure and then lease space to the wireless companies (like AT&T, T-Mobile and Verizon) that provide the wireless service.

ExteNet filed several applications in Cambridge to replace utility light poles with new ones that housed equipment to be leased to AT&T. AT&T, not ExteNet, would supply the fiber connections and electric power. Cambridge’s Pole and Conduit Siting Policy requires applicants working on a proposed project with other companies to designate a lead company for the application.

In practical terms this means the local authority can identify deficiencies at any time and/or deny the application because of a deficiency at the very end.

The lead company has responsibility for coordinating the applications, permitting, constructions, wiring, and operation and acts as the point of contact. As such, the lead company must obtain all the necessary information and provide it to the planning commission as part of the application. In this case, ExteNet did not obtain or provide any information about how the facilities would obtain power or fiber connections, even though the policy expressly required that information. Nor was ExteNet able to provide sufficient information to demonstrate actual need for the wireless coverage that would be supported by the facility, which was another substantive Cambridge requirement.

The City denied ExteNet’s permit applications because of the missing information. ExteNet contended the City’s procedure was unlawful because it unreasonably waited until the end of the allowed period for the review of the application (shot clock)  before it advised ExteNet of the deficiencies. ExteNet also challenged the substantive requirement that ExteNet provide information that only its customer (AT&T) could provide.

The district court rejected ExteNet’s procedural and substantive claims.

First, the court ruled that the FCC’s procedural shot clock rules do not require a local permitting authority to provide notice of any deficiencies to the applicant within 10 days. It interpreted the rules to say that notice of deficiency within 10 days is only required if the local authority wants to stop or reset the shot clock. In practical terms this means the local authority can identify deficiencies at any time and/or deny the application because of a deficiency at the very end.

. . . Will require that the wireless companies who will be leasing from the neutral host provider be named participants and provide the necessary information, whereas until now they have been able to avoid the need to do so while also keeping important information away from cities and concerned citizens.

The district court approved Cambridge’s substantive requirement for all relevant information. The Cambridge policy required that the “applications include evidence that the proposed installation is needed to prevent a material inhibition of wireless services.” ExteNet did not (and claimed it could not) make this showing since AT&T was the customer and the one with the information necessary to prove the facilities were needed to fill a significant gap in coverage, would in fact be used to fill any gap that did exist, and there were no viable alternative locations. The court held, however, that ExteNet had a burden of proof and failed to meet it. “Where ExteNet’s complaint and its original applications fail to show the existence of a coverage gap, it is impossible to infer that the denial of ExteNet’s applications has the effect of prohibiting the provision of wireless services”.  The court ruled that ExteNet did not allege sufficient facts to show that Cambridge’s application information requirements did or could materially inhibit the provision of service.

The court readily accepted Cambridge’s argument that the information it required was relevant to and necessary for any intelligent and reasonable assessment of the application’s merits. The court stated: “Because a wireless facility could not function without power and data, requiring information concerning that power and data is not an effective prohibition of the provision of wireless services. … Further, ExteNet has not alleged that forcing joint applications would, in all circumstances, “materially inhibit or limit the ability of any competitor . . . to compete in a fair and balanced legal and regulatory environment.”

This decision has major implications for applications by neutral host providers. The now-affirmed information requirements will – as a practical matter – require that the wireless companies who will be leasing from the neutral host provider be named participants and provide the necessary information, whereas until now they have been able to avoid the need to do so while also keeping important information away from cities and concerned citizens. It may also, in the long term, eliminate some of the business case justifications for the neutral host business. This is important since a very large portion of the small cell deployments are planned, permitted and constructed by the neutral host providers. Cities can now justifiably demand to know who will be using the wireless infrastructure and in position to obtain more information and commitments from them. Finally, it will allow cities to better determine whether and where wireless facilities are actually needed, and the services they will support.

Documentation:

Sign up for free news and updates from Children’s Health Defense. CHD focuses on legal strategies to defend the health of our children and obtain justice for those injured. We can't do it without your support.

Republishing Guidelines