Doesn't work. Busted by a factor of 2.
Not to belittle your analysis, which is
quite good in my opinion, but the safety factors inherent to the retention pond design process usually more than account for being off by a factor of two or more with the infiltration rate.
A stormwater retention pond is not a watch. The "design storm" will never fall on your watershed. The "first flush" is an extremely arbitrary runoff volume that in truth should vary widely by location, but regulations usually don't acknowledge the variance. The whole field of stormwater hydrology is built on one conservative assumption after another.
So lets say your regulation requires that the retention volume in your pond recovers in 72 hours after a storm. I think that's typical in Florida, but I'm pulling that from memory and haven't done a Florida job in over a year, so please look it up before trusting me on that. You design it by the simplified methods presented to you in your regulatory guideline, which basically use darcy law, (incorrectly) assume a constant head instead of the falling head you'd actually see in a pond leaking out, use your infiltration rate over the pond bottom, divide, show the regulator some math that says 72 hours or less. Well that's not how it's actually going to happen when it rains. For one, you're not allowed to take credit for any infiltration through the banks, just along the flat bottom, so that's conservative. Another thing, as the head in the pond drains down, you've got less head driving the flow. Third, if you're down near the water table as in much of Florida, the water table itself changes during the course of the infiltration.
Lets continue to monkey with the discussion. In SFWMD, your pervious SCS runoff curve numbers vary by depth to the water table instead of pulling them out of the book. Well if the groundwater is varying, then your runoff number is varying too, which changes how much water should come in to your retention pond, but we pretty much ignore that during design. Add in seasonal fluctuations in depth to the water table, just for fun, or the idea that your neighbor might have a retention pond that's crowding out the volume you'd like to infiltrate into. Then lets say the contractor sods the thing instead of seeding it, and sod is grown on muck from a sod farm that's got less infiltration capacity than your soil, whoops. Or the owner dumps his grass clippings into it, because why not, it's just a hole out back. Etc.
By the time you're done with it all, even if you did have a 100% correct and accurate infiltration rate, you'd need to do some sort of flownet model combined with a stormwater hydrology model just to figure out exactly what's going on. And by the time you'd done all that, then answer would be this:
"Hrmm, yeah, that hole seems about right."
So instead of diving down that rabbit hole, we pick a infiltration test and stick with a simple design method to go with it. And if those two methods doesn't give us good results, we don't go searching for the perfect infiltration test in combination with the perfect computer model, we just change the regulation to say "48 hour recovery time" instead of 72, and call it a day. It's not like anyone's sitting around these things with a stopwatch.
Sorry for the rant. I don't do a lot of wellpoint design, and only very cursory work designing temporary dewatering operations, so I don't encounter many applications where accurate infiltration rates are crucial. For stormwater hydrology, if you can get it within a factor of 2 you're doing pretty good. As long as it's not 10 times off, it'll probably work in the end.
Hydrology, Drainage Analysis, Flood Studies, and Complex Stormwater Litigation for Atlanta and the South East -