How Sonar Actually Works

Here's the entire trick. The transducer makes a sharp click of sound — the ping. Sound travels through freshwater at roughly 4,800 feet per second (about four times faster than through air). The ping hits something, part of it bounces back, and the transducer hears the echo. The head unit measures the time between click and echo, does one multiplication, and knows the distance.

The numbers are almost silly. In 20 feet of water, the round trip — down 20 feet, back up 20 feet — takes about eight thousandths of a second. Your unit can comfortably fire many pings per second and never confuse one echo with the next. Every depth number you'll ever read is just this stopwatch running.

Echo STRENGTH carries the second piece of information. A hard thing — rock, gravel, a tree trunk, a hard clay bottom — bounces most of the sound back, and the unit draws it bright and thick. A soft thing — silt, muck, weeds — absorbs sound, and the unit draws it dim and thin. So one ping tells you both how far away something is and roughly what it's made of. Keep those two ideas — TIME means distance, STRENGTH means hardness — and every screen in this course will make sense.

A fish is mostly water, and sound passes through water-like things without bouncing. So why do fish light up a sonar screen? The swim bladder — the gas-filled sac fish use to control their buoyancy. The boundary between water and gas is violent to a sound wave; it reflects it almost like a mirror. Your sonar isn't really seeing the fish. It's seeing the air inside the fish.

This one fact explains screen behavior that otherwise seems random. Species with big swim bladders (crappie, stripers, trout) mark strong for their size. Bottom-hugging species with small bladders can be nearly invisible. A big fish sideways to the beam marks stronger than the same fish nose-on. When you hear an angler say 'the fish were there, they just weren't showing well' — this is usually the physics behind it.

The ping doesn't travel down as a laser line — it spreads as it goes, like a flashlight beam, forming a CONE. A typical 200 kHz beam is about 20 degrees wide, which works out to a simple rule of thumb: the circle of bottom you can see is about one-third of the depth. In 20 feet of water you're looking at a patch of bottom about 7 feet across. In 10 feet of water, about 3 feet across.

Sit with that for a second, because it's the most common beginner miscalibration: in shallow water you are looking through a drinking straw. A fish 10 feet to the side of your kayak in 8 feet of water simply does not exist to your sonar. When your screen is blank, it doesn't mean the area is empty — it means the skinny cone under your hull is empty. This is exactly the problem side imaging and live sonar were invented to fix, and it's why they get their own lessons.

The cone also explains the depth number's fine print: the unit reads depth from the strongest bottom echo inside the cone, mostly the center. On a steep drop-off, the cone touches shallow bottom on one edge and deep bottom on the other — so the number wobbles and the bottom line thickens. That's not a glitch. That's the machine honestly telling you the bottom isn't flat.

One more foundation and you're ready to read screens. Each ping paints ONE vertical stripe of pixels at the right edge of the display — everything at echo-distance for that instant, top to bottom. Then the whole picture shifts left and the next ping paints a new stripe. The screen you look at is a strip-chart of history: the right edge is right now, and everything left of it is the past.

Two consequences, and they trip up every single beginner. First: the screen scrolls even when you're parked, because the unit keeps pinging — a scrolling screen does not mean you're covering water. Second: horizontal distance on screen is TIME, not distance. A hump that looks 50 feet wide might be a small hump you drifted across slowly. Fix those two ideas now and the next lesson — actually reading the screen — gets dramatically easier.