Home » Featured »Missouri »Politics/Policy »Sunday Poll »Transportation » Currently Reading:

Sunday Poll: Can A STL-KC Hyperloop Get Built Without The Use Of Eminent Domain?

February 9, 2020 Featured, Missouri, Politics/Policy, Sunday Poll, Transportation No Comments
Please vote below

The idea of a high speed tube transportation system connecting St. Louis to Kansas City (Missouri, not Kansas) was back in the news recently after getting initial approval the Missouri House:

Although the long-term goal is to connect St. Louis and Kansas City with a pneumatic tube people mover that could transport passengers across the state in 30 minutes, a recent study commissioned by House Speaker Elijah Haahr recommends the state should first build a 15-mile track to test the feasibility of the concept.

The report put the price tag on the test track at $300 million to $500 million. The cost to build a track linking St. Louis, Columbia and Kansas City is estimated at $10.4 billion.

Before lawmakers gave their approval, however, Fitzwater proposed an amendment that would ban eminent domain for tube transport systems. (Post-Dispatch)

For those unfamiliar with the term eminent domain

Eminent domain refers to the power of the government to take private property and convert it into public use. The Fifth Amendment provides that the government may only exercise this power if they provide just compensation to the property owners. (Wex legal dictionary)

My one and only Hyperloop poll was in October 2018, and readers were split on Missouri being able to afford such a massive project.

Today’s poll is about the amendment banning the use of eminent domain added to the Hyperloop bill.

As always, today’s poll will close at 8pm. On Wednesday I’ll share my thoughts on Hyperloop and eminent domain.

— Steve Patterson

 

Comment on this Article:

Advertisement



FACEBOOK POSTS

This message is only visible to admins.

Problem displaying Facebook posts.
Click to show error

Error: An access token is required to request this resource.
Type: OAuthException
Solution: See here for how to solve this error

Archives

Categories

Advertisement


Subscribe