The Salt Wedge Sabotage
If you've never deployed an ADCP in the Mahakam River around Samarinda, you probably think you understand salinity gradients. You don't. Most of the industry treats the speed of sound as a fixed constant—usually 1,480 m/s—and calls it a day. In the Mahakam, that's a rookie mistake that will wreck your data before you've even cleared the dock.
The interaction between the Makassar Strait's saline intrusion and the river's freshwater discharge creates a refractive lens effect. We aren't dealing with a simple mix; we're dealing with a violent salt wedge that pushes deep inland during the Northwest Monsoon. I've seen salinity gradients shift so aggressively within a single tidal cycle that sound velocity fluctuates wildly over just a few vertical meters. When the pings bend, your bin depths are lies. Your velocity calculations? Pure guesswork.
I once watched a team's discharge estimates swing by 15% in a single afternoon. Why? Because they skipped the CTD (Conductivity, Temperature, Depth) cast. They assumed the water was homogeneous. In Samarinda, ignoring the Sound Velocity Profile (SVP) is essentially choosing to be wrong. If you aren't calibrating for the refractive index of that salt wedge, you're just playing with numbers.
The 'Chocolate Milk' Attenuation Problem
Then there is the turbidity. The Mahakam doesn't just look like chocolate milk; it behaves like a physical barrier to acoustic energy. High suspended sediment concentration (SSC) doesn't just block visibility—it eats your signal. We call it signal attenuation, and in this corridor, the attenuation coefficient is volatile.
You'll get a crisp return at the surface, but by the time that ping hits the benthos, the return signal is often buried in noise. This makes ground-truthing the bottom depth a constant fight. When the SSC spikes during heavy rain events in the upper catchment, your signal-to-noise ratio plummets. You start seeing 'phantom bottoms' or losing the bottom track entirely, which throws your entire moving-boat survey into chaos.
The Bathymetric Nightmare of the 0.5° S to 1.0° S Corridor
The stretch between 0.5° S and 1.0° S is where the river decides to be unpredictable. I've mapped sections where the riverbed drops from 5 meters to 22 meters over a distance of barely thirty meters. This isn't a stable channel; it's a shifting landscape of silt and scour holes. The thalweg—the deepest part of the channel—doesn't stay put. It migrates.
I remember a deployment where the main current axis shifted several meters laterally between two tidal cycles. If you're relying on old charts to position your transects, you're chasing a ghost. The bedforms here are dynamic. You can have a massive scour hole one month and a silt deposit the next. For anyone trying to calculate total discharge, this means your cross-sectional area is a moving target. If you don't have a high-resolution bathymetric map that is current to the week, your discharge totals are essentially a coin flip.
Tidal Asymmetry and the Samarinda Bottleneck
The tidal range in Samarinda creates a hydraulic squeeze that complicates everything. The incoming tide doesn't just raise the water level; it pushes a wall of saline water against the river's discharge. This creates an intense shear zone. I've seen vertical velocity profiles where the surface is screaming downstream at 1.2 m/s while the bottom layer is actually moving upstream.
This vertical shear is a nightmare for standard averaging. If your bin size is too large, you're smoothing out the most critical part of the hydrodynamic equation. You need tight binning and a very high sampling rate to capture the actual momentum flux. Most operators get lazy with their ensemble averaging, but in the Mahakam, laziness leads to massive underestimation of the total volume transport.
Field Realities: Gear and Grime
You can't just throw a sensor in the water and walk away. The debris load in the Mahakam is legendary. Between the floating logs and the urban runoff from Samarinda's sprawl, your transducers are under constant assault. I've had sensors fouled by organic slime within 48 hours, which kills your acoustic return. I always recommend a rigorous cleaning schedule and, if possible, protective shielding that doesn't interfere with the beam angle.
The real secret to surviving a campaign here is redundancy. Use multiple platforms. If your boat-mounted ADCP is giving you weird readings, check it against a stationary mooring if you have one. But remember, the mooring is subject to the same salt wedge refraction as the boat. If you aren't running a concurrent CTD, you're just guessing which sensor is lying to you.
Final Thoughts on Discharge Accuracy
Stop treating the Mahakam like a textbook river. It's a chaotic, stratified, sediment-heavy estuary that hates your equipment. To get a real number on discharge, you have to fight for it. Calibrate your sound velocity every few hours. Tighten your bins. Trust the CTD more than the ADCP's default settings. If you don't, you're not doing science—you're just collecting pretty pictures of noise.
Taming the Mahakam: Sound Velocity Chaos and Benthic Shifts in Samarinda