Deployment Notes: Kochi Port, Southwest Monsoon Window
I stepped off the tender into a thick, humid haze that only the Kerala coast can produce in July. The air felt like a wet blanket, and the water in the Kochi harbor was a murky, opaque brown. We were positioning the instruments near the International Container Transshipment Terminal (ICTT), and the current was already fighting us. It's a chaotic environment. You have the Arabian Sea pushing in, the massive freshwater discharge from the Periyar River flushing out, and Post-Panamax ships churning up the bottom sediment in the dredged channels.
Kochi is a nightmare for acoustic profiling if you aren't prepared. At 9.9°N, the seasonal swing is violent. During this Southwest Monsoon deployment, the Periyar plume creates a stratified mess. We aren't just dealing with salt and fresh water; we are dealing with a suspended solids load that can choke a sensor. The bathymetry here is deceptive. The main channels are kept at 14.5 meters, but the surrounding seabed is a shifting slurry of silt and clay that moves with every tide.
What We Found
The data came back with a vertical shear that would make any ship pilot nervous. We found current reversals happening mid-column that were completely invisible from the surface. In one specific bin, we saw the surface layer screaming outward toward the Arabian Sea while the bottom layer—driven by the dense salt wedge—was creeping inward. This kind of layering is common in tropical estuaries, but the magnitude here is aggressive. The asymmetry between the flood and ebb tides is where the real story is. The flood tide doesn't just reverse the flow; it changes the entire velocity profile, often pushing a slug of high-salinity water deep into the harbor.
The most frustrating part was the 'signal fence.' During the peak of the monsoon runoff, the suspended sediment from the Periyar becomes so dense that the acoustic backscatter goes off the charts. The signal attenuates before it even hits the bottom. We saw periods where the data became essentially noisy junk because the water was too 'thick' for the pings to penetrate. Conversely, during the dry season, I've seen the opposite happen—the water gets too clear, we lose our scatterers, and the signal-to-noise ratio drops. It's a constant balancing act.
Equipment Performance
We deployed both 300kHz and 600kHz units to see which would hold up better against the silt. Honestly, the 600kHz unit was the only thing that gave us a clean signal in the shallower, river-influenced zones. The 300kHz unit worked fine in the deeper ICTT approach, but it struggled with bin contamination near the halocline. That sharp density shift—the salt wedge—causes side-lobe interference. The ADCP starts picking up velocities from outside the primary beam, and if you don't manually scrub that data, your readings are fiction. I've seen port authorities use uncorrected data like this to plan dredging, which is a massive waste of fuel and money. We spent three days ground-truthing the data against a handheld current meter to make sure our vertical profiles weren't lying to us.
Recommendations for Future Deployments
If you're heading into Kochi, don't rely on a single frequency. The environmental variance is too high.
- Use 600kHz units for any deployment within 5km of the Periyar river mouth to combat signal attenuation from silt.
- Set a tighter blanking distance to avoid bottom-track errors caused by the shifting silt layers.
- Schedule deployments to avoid the peak monsoon surge if you need high-precision vertical profiles, or be prepared to throw out 20% of your data as noise.
- Always deploy a CTD (Conductivity, Temperature, Depth) sensor alongside the ADCP to map the halocline; without the salinity profile, you can't explain the velocity shears.
Field report by Elena Rodriguez. Elena is a specialist in underwater acoustics and oceanographic instrumentation with twenty years of experience mapping sediment transport in complex coastal environments.
Field Deployment Report: Bottom-Mounted ADCPs in the Kochi Port Approach