How I Track Tides in Juneau and What It Actually Tells You
I spend most of my time on the water around Southeast Alaska, and the tide isn't just a number on a chart. It's the main thing that decides whether you launch your skiff, get stuck on a sandbar, or lose gear to a sudden current shift. Juneau sits on a complex stretch of coastline where the tidal behavior is different from what you'd see further north or south, and getting good data matters more than most people realize. The way I approach this starts with pulling data from NOAA's tidal prediction tables, but raw predictions alone aren't enough. Juneau's waterfront has a range that typically hits around 18 to 20 feet at spring tides, but the actual timing can drift depending on weather systems moving in from the Gulf of Alaska. Barometric pressure changes of just a few millibars can hold the water level back or push it higher than the predicted numbers by a foot or more. I track that gap between prediction and reality because that gap is where problems show up. My main tool is a combination of the NOAA CO-OPS database and a local logger I keep mounted near the Auke Bay area. The government stations give you the baseline, but they're fixed points. What happens at low tide in one cove doesn't always match what's happening three miles down the shore. I've noticed that the ebb current around the Lemon Creek channel runs significantly faster than the prediction models account for, especially during the early morning hours when wind patterns shift. This matters when you're working around boat ramps or tidal inlets where the current can sweep things out past the mooring lines if you don't factor in that extra speed.
Here's the thing most people miss when they start tracking Alaskan tides: the lunar day isn't the only driver. Wind setup and freshwater discharge from glacial melt change the whole picture in late spring and summer. During June and July, the runoff from the Mendenhall Glacier and surrounding watersheds pushes into the harbor and actually slows the outgoing tide in certain areas. I've seen the ebb drag out by 45 to 60 minutes compared to the predicted schedule. If you're timing a launch or a dive around a narrow channel, that delay can put you in trouble. I keep a simple spreadsheet that logs the predicted high and low times against what I'm actually seeing on the water. Over a few months you start to spot the patterns. Some days the tide behaves exactly like the charts say. Other days, particularly after a storm passes through, the whole schedule shifts. The lag between a pressure drop and the water responding isn't consistent, which means you can't just apply a fixed adjustment factor. I've found that checking the wind speed and direction from the nearby weather station a few hours ahead of the predicted low tide gives me a decent read on whether the water will come in earlier or hold back longer than expected. There's a workaround I use when the data gets messy. Instead of relying solely on the published predictions, I time-stamp my observations and compare them against the nearest NOAA station readings from the same day. When the discrepancy is more than 30 minutes off, I adjust my personal schedule and note the reason in the log. This isn't foolproof, and it doesn't replace the official tables, but it keeps me from getting caught out when the coast isn't behaving normally.
Where This Method Breaks Down
I should be straight about the limitations. Tidal tracking in this region is complicated by seiches, which are standing wave oscillations that can raise or lower water levels unpredictably for several hours. I've had days where the water level bounced up and down in a way that made the tide charts look useless. Seiches are caused by wind events or atmospheric pressure shifts hitting the bay at just the right frequency, and there's no reliable way to predict them from the surface. They just happen, usually without much warning. Another issue is the gap in real-time data coverage. The NOAA stations are accurate, but there are stretches along the coast where the nearest monitoring point is dozens of miles away. If you're working in a remote inlet between stations, you're essentially guessing based on the closest available data. That guess works fine for general planning, but it falls apart when conditions are already unusual. For those situations, carrying a portable water level sensor or at least a manual staff gauge helps a lot. I keep a marked stick at my launch point and check it twice daily when I'm in the area regularly. It takes about five minutes and gives you ground truth that satellite-based or distant station data can't provide. The deeper problem is that climate variability is changing some of the baselines these predictions rely on. Glacial retreat and shifting precipitation patterns are subtly altering the freshwater input that affects tidal behavior in places like Juneau. The adjustments aren't massive yet, but over time the old reference levels may not fit as well. NOAA is aware of this and updates their datums periodically, but there's always a lag between environmental change and the charts reflecting it. Until the reference frames catch up, local observers like me fill in the gap, which is why keeping your own records matters.
Get the Full Details
If you're serious about tracking this stuff, the NOAA Tides & Currents website at tidesandcurrents.noaa.gov is the starting point. You can pull hourly predictions for the Juneau stations and export the data for your own spreadsheets. It's free and it's the most reliable source available. After that, it's mostly about showing up on the water, watching what happens, and writing it down so you can see the pattern over time. The better you know your local stretch of coast, the less you have to rely on the charts alone.
