My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 12/03/2009
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2009
>
Agenda - Planning Commission - 12/03/2009
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:01:23 AM
Creation date
11/30/2009 9:32:33 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
12/03/2009
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
138
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />u <br /> <br />Zoning Bulletin <br /> <br />August 25,20091 Volume 31 No. 16 <br /> <br />(~ <br /> <br />In September 2006, T-Mobile sought to close a "service gap" and to <br />expand its coverage ill the city. Pursuant to'the city's municipal code (the <br />"Code"},T-Mobile applied to the city for a "special use permit" {"SUP"} <br />to construct an additional wireless telecommunications facility ("WCF") <br />at a particular site {the "Site"} in the city. The permit 'application "ana- <br />lyzed eighteen site. alternatives and proposed the construction of a 116- <br />foot monopole with three antennas at the top." <br />Eventually, the city Planning Commission denied T-Mobile's applica- <br />tion. T-Mobile appealed, and the City Council also denied the applica- <br />tion. The City Council based its decision on the conClusions that the pro- <br />posed WCF would: have a "commercial appearance 'and would detract <br />from the residential character and appearance of the surrounding neigh- <br />borhood," which was "predominately single-family residences;" and <br />"negatively impact the views from single-family residences in the vicin- <br />ity." The City Council also concluded that T-Mobile's Site was the "least <br />intrusive," since "[a]t least four alternative sites were potentially accept- <br />able to provide [the required coverage]." <br />T-Mobile filed an action in federal district court against the city. <br />Among other claims, I t alleged that the city's denial of the SUP violat- <br />ed S. 332{~} of the federal Telecommunications Act of 1996 {the "Tele- <br />communications Act" or the "Act"} {47 U.S.C. S 332{c}{7}{B}}. Section <br />332(c}{7}{B} of the Act provided that local regulations "shall not pro~ <br />hibit or have the effect of prohibiting the provision of personal wireless <br />services." Section 332{c} further required that a 10cal zonj.ng decision be <br />, "supported by substantial evidence." <br />The district court ruled in T-Mobile's favor. It found that T-Mobife's <br />proposed Site "was the least intrusive 'means to close a significant gap <br />inits wireless service in the [c]ity." It also found that "the [c]ity's denial <br />was not supported by substantial evidence." It concluded that" [b ]ecause <br />the [c]ity prevented T-Mobile from closing a significant gap through the <br />'least intrusive' means available, the [c]ity's decision ha[d] the effect of <br />'prohibiting wireless services in violation of [S] 332(c}{7}." <br />The city appealed. <br /> <br />() <br /> <br />DECISION: Affirmed. <br /> <br />The United States Court of Appeals, Ninth Circuit, found that the <br />,city's denial of the special use permit was supported by substantialevi- <br />dence. Nevertheless, the court concluded that the' denial violated the <br />Telecommunications Act because the city had failed to rebut T-Mobile's <br />. showing that its proposal constituted the least intrusive means of rem- <br />edying. the service gap. <br />The court 'explained that in reaching its conclusion, it applied a two- <br />part test: {1} consideration of whether the city's denial under the city <br /> <br />@ 2009 Thomson Reuters <br /> <br />9 <br /> <br />55 <br />
The URL can be used to link to this page
Your browser does not support the video tag.