My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP09166
CWCB
>
Water Supply Protection
>
Backfile
>
9001-10000
>
WSP09166
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:51:40 PM
Creation date
10/12/2006 3:30:00 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
5960
Description
Flood Protection Section - Miscellaneous Publications
State
CO
Basin
Statewide
Date
9/1/1981
Author
FEMA
Title
Multi-Government Management of Floodplains in Small Watersheds - Federal Emergency Management Agency
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
65
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).
Show annotations
View images
View plain text
<br />001188 <br /> <br />What will happen if this urbanization is <br />allowed to go unchecked, with no <br />thought to flooding? And who is going <br />to do something about it? <br /> <br />Public Jurisdictions: A Jumble of <br />Conflicts <br /> <br />Like its flood water, the distribution <br />of public authority in the Haikey basin <br />is chaotic. Basically, the watershed is <br />divided among four jurisdictions (Fig. <br />17): the City of Tulsa, at the northwest <br />corner of the watershed; the City of <br />Broken Arrow, scattered in a jumble of <br />annexations across much of the upper <br />and middle parts of the watershed; the <br />lowland Town of Bixby, straddling the <br />Arkansas River; and Tulsa County, <br />which has primary responsibility for <br />the unincorporated balance. <br /> <br />Tulsa, incorporated in 1898 on a high <br />bluff of the Arkansas River, already had <br />urban problems by 1960, with a popula- <br />tion of 182,000. But by 1970, its popu- <br />lation had nearly doubled, and its prob- <br />lems were proportionately bigger. An es- <br />pecially ominous one was the threat of <br />flooding-a threat which was borne out <br />with the 1974 and 1976 floods, the lat- <br />ter being the most costly disaster in the <br />city's history. The 1976 flood gave im- <br />petus to the city's previously half- <br />hearted floodplain management policies, <br />concocted at least partly in compliance <br />with the National Flood Insurance Pro- <br />gram, which Tulsa joined in 1970. As the <br />1976 floodwaters subsided, Tulsa de- <br />clared a moratorium on all construction <br />exposed to flash floods. This mora- <br />torium lasted until the city commission <br />adopted new floodplain ordinances in <br />late 1977 whose general goal was to al- <br />low only development that would not be <br />flooded or aggravate flooding for others. <br />Flooding concern also inspired related <br />planning efforts: a growth guidance pro- <br />gram for the city, of which floodplain <br />management was an important part; and, <br />as described further on, the Army Corps <br />of Engineers' Tulsa Urban Study. <br />Meanwhile, in other parts of the water- <br />shed, Broken Arrow was rushing to other <br />remedies in the face of the 1976 flood. <br />Their solution was structural: a flood. <br />plain policy committee of developers, <br />engineers, and citizens recommended <br />channelizing all streams in new develop- <br />ments throughout Broken Arrow, to <br /> <br />carry stormwater efficiently out of its <br />jurisdiction. Fine, perhaps, for Broken <br />Arrow (although rather costly rnot so <br />fine for downstream Bixby (Fig. 18). <br />Bixby, on getting word of Broken <br />Arrow's intention, threatened a court <br />suit to compel that city to control its <br />runoff, which Bixby maintained would <br />substantially increase-to the down- <br />stream town's detriment-if Broken Ar- <br />row went ahead with its proposed chan- <br />nelization. Bixby's charges were borne <br />out by preliminary findings in the Corps <br />of Engineers' Tulsa Urban Study, which <br />further found that channelization would <br />be far more expensive than a suggested <br />alternative: preserving the floodplains <br />as open space rather than developing <br />them at all. This finding, com bined with <br />maintenance costs to be passed on to <br />water users, persuaded Broken Arrow's <br />voters to reject channelization. <br />Broken Arrow then abandoned the <br />scheme and switched to a more benign <br />approach: it adopted ordinances pro- <br />hibiting new construction on the 100- <br />year floodplain and also prohibiting <br />major stream channel alteration where <br />the contributing drainage area exceeded <br />one square mile. It also started looking <br />for ways to finance storm water deten- <br />tion and construction and floodplain <br />open space compensation. Concurrently, <br />Bixby-trying to put its own house in <br />order-was considering putting them on <br />stilts or higher ground: after a brief <br />floodplain development moratorium, the <br />town adopted requirements that new <br />house floor levels be at least one foot <br />above the l00-year flood level. It alao <br />required that large construction allow <br />flood waters to p888 underneath, and that <br />development on higher ground have <br />stormwater detention measures. <br />All this took place in the two years <br />following the 1976 inundation. Mean- <br />while, what was the fourth actor, Tulsa <br />County, doing? Very little. Although un- <br />incorporated areas remain under its juris- <br />diction, Oklahoma law does not give it <br />the prerequisites of home rule, and it <br />would have to formally seek zoning au- <br />thority. It has not done so yet, although <br />to qualify for federal flood insurance, it <br />did, in 1975, adopt a building code. <br /> <br />FonlDlS for Coordination <br /> <br />t <br />, <br /> <br />I <br /> <br />And who has been there to reconcile <br /> <br />34 <br />
The URL can be used to link to this page
Your browser does not support the video tag.