Deployment Notes: Stamford Coastal Zone, September 2023
We hit the water just before 0400 hours, timed specifically to catch the peak flood tide coming in from the Long Island Sound. The air was damp, smelling of salt and urban runoff, and the surface of the harbor looked deceptively calm. But beneath that glassy skin, the water was fighting itself. I've spent decades tracking acoustics in some of the world's most erratic estuaries, yet the junction where the Mianus River dumps into the Sound remains a textbook example of hydrodynamic chaos.
The conditions were typical for a late summer transition. We had a moderate south-westerly breeze pushing surface water toward the shoreline, creating a surface drift that fought the incoming tide. The water state was messy. Between the tidal prism of the Sound and the freshwater discharge from the Mianus, we were sitting right in a pycnocline—a sharp density gradient that acts like a ceiling for nutrients and a trap for pollutants. Visibility was poor, likely due to recent rains washing silt from the urban corridor into the basin.
What We Found
The data came back with a shock: the vertical velocity gradient was an absolute mess. We recorded flood velocities that were significantly more aggressive than the ebb, a classic tidal asymmetry that makes this stretch of the Sound a nightmare for sediment transport modeling. The most striking part? The 'tug-of-war' effect. In the upper water column, the wind-driven current was pushing west, while just ten meters down, the tidal flow was hauling water east. If you're relying on surface-level measurements for dredging or navigation, you're essentially guessing. You're missing 70% of the actual physics occurring at the seabed.
I noticed a massive spike in acoustic attenuation during the mid-tide transition. It wasn't a sensor failure; it was a turbidity plume. The Mianus River had pushed a wall of suspended solids into our deployment zone, creating a 'cloud' that swallowed the signal. We saw significant bin contamination in the lower cells, where the signal bounced off the muck rather than the water column. It's the kind of environment where a 'standard' setup fails because the water isn't standard. It's a cocktail of salt, fresh water, and urban debris.
Equipment Performance
I opted for a 600kHz ADCP for this run, and frankly, it was the only right choice. A 300kHz unit would have given us more range, but in these shallow depths (varying wildly from a few meters to 30 meters across the shelf), range is irrelevant. We needed spatial resolution. The 600kHz unit handled the erratic turbidity better than I expected, though we still fought some noisy data during the peak runoff events. Bottom-mounting was mandatory. Any attempt to use a moored float in this area is an invitation for disaster, given the localized eddies and vortices created by the uneven bottom topography. The unit stayed seated, the data stayed clean enough for a sanity check, and the vertical profiling proved that the seabed was moving in the opposite direction of the surface flow.
Recommendations for Future Deployments
Don't get lazy with the site survey. The bathymetry here shifts too fast for generic charts to be useful. If you want a clean signal, you have to ground-truth your placement to avoid the worst of the river's turbidity plumes.
- Stick with 600kHz transducers to maintain resolution in the upper water column where the mixing is most violent.
- Use heavy-duty bottom mounts to prevent sensor tilt caused by high-velocity shear layers.
- Schedule deployments to avoid peak storm-runoff windows if you need high-precision velocity data without acoustic attenuation.
- Always correlate ADCP data with a CTD profile to identify the exact depth of the pycnocline.
Field report by Capt. Marcus Thorne. Capt. Thorne is a specialist in underwater acoustics and maritime instrumentation with 20+ years of experience in port hydrography.
Field Deployment Report: Velocity Profiling at the Mianus River and Long Island Sound Interface