My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 09/16/2010 - Special Meeting
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2010
>
Agenda - Planning Commission - 09/16/2010 - Special Meeting
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:04:09 AM
Creation date
9/10/2010 1:53:11 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Title
Special Meeting
Document Date
09/16/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
152
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
July 10, 2010I Volume 4I No. 13 Zoning Bulletin <br />More specifically, TMGS contended that its state -conferred eminent do- <br />main power trumped/was immune from the setback requirement. TMGS <br />also maintained that the setback requirement conflicted with, and was <br />therefore preempted by, the PSA's express preemption of state "safety <br />standards for pipeline facilities ...." <br />The district court disagreed with TMGS. It held that Section 10's <br />setback requirement was lawful. <br />TMGS appealed. <br />The Court's Decision: Judgment of district court affirmed. <br />The United States Court of Appeals, Fifth Circuit, rejected TMGS's <br />argument that its eminent domain power trumped the setback require- <br />ment. As a matter for first impression (i.e., the first time the court con- <br />sidered the issue), the court also held that the PSA did not preempt a <br />setback requirement for a compressor station. <br />In rejecting TMGS's eminent domain immunity argument, the court <br />said that "an eminent domain entity like TMGS must comply with <br />generally applicable zoning requirements." TMGS's argument found <br />"no support in law." TMGS had failed to show that: state law in- <br />tended to exempt it from zoning or setback requirements; or that state <br />regulations preempted the City's police powers in this area. Moreover, <br />TMGS failed to show that the City's setback requirement was "unrea- <br />sonable or arbitrary" (i.e., that it "fail[ed] to promote public health, <br />safety, or welfare"). Although it might be "costly or inconvenient for <br />TMGS to acquire enough land to ensure that its compressor station <br />conforms to [the City's] [setback] requirements .... these are normal <br />consequences of complying with local zoning laws," said the court. <br />As to the PSA preemption argument, the court explained that fed- <br />eral law may exempt state (and local) law in three ways: (1) clearly <br />and expressly; (2) implicitly by "directly conflicting with it" (conflict <br />preemption); or (3) implicitly by "occupying a field so pervasively as to <br />naturally exclude it" (field preemption). <br />The court acknowledged that the PSA expressly preempted "safety <br />standards" for pipeline facilities. Since the PSA provided this express <br />preemption, the court determined it need not look to see if there were <br />other implicit preemptions. The court said that the question then <br />here was: whether the City's setback requirement was a "safety stan- <br />dard," which was preempted by the PSA. The court found the setback <br />requirement was not a safety standard; rather it concluded it was an <br />aesthetic standard. Moreover, the court said that even if the setback <br />requirement had an incidental affect on fire safety (as TMGS had ar- <br />gued), it still was not preempted by the PSA. (Section 192.163 of the <br />PSA mandated that compressor stations be "situated to minimize fire <br />risks.") This was because: (1) the setback requirement did not reduce <br />safety and hinder Congress's intent of the PSA safety standards; and <br />6 © 2010 Thomson Reuters <br />92 <br />
The URL can be used to link to this page
Your browser does not support the video tag.