Dead Reckoning Error Bounds That Predict Grounding Risk

Where Error Bounds Fail First

Groundings happen when the position uncertainty exceeds the available water. That sounds obvious. But the standard practice of drawing a circle around the DR position — circular error probable, or CEP — assumes errors grow equally in all directions. In a river, a channel, or a harbor approach, they don't.

The most predictable groundings follow a pattern: the vessel stayed inside its CEP circle, yet the starboard quarter scraped the bank. What happened? The error ellipse was not circular. The along-track error was small, but the cross-track error — perpendicular to the vessel's heading — was double the estimate. The CEP hid that.

This guide is for mariners who already know how to DR. You know how to log courses and speeds, estimate set and drift, and plot a running fix. The question is: are your error bounds giving you false confidence? We will walk through how to build bounds that predict — not just contain — the real risk.

We will use editorial "we" here, but the insight comes from collective practice: watch officers who have watched the cross-track error swell after a course change, or who have seen a current gradient bend the DR plot into a curve that no textbook ellipse covers.

The worst grounding I ever saw happened after a perfect DR plot. The circle was 0.3 miles. The channel was 0.4 miles wide. The ship touched the southern edge — exactly 0.3 miles from the DR position. The error was not in the math. It was in the shape.

— Senior harbor pilot, personal communication

Foundations: What Drives the Shape of Uncertainty

Most DR error models start with the same three sources: steering error (your helmsman's ability to hold course), speed error (tachometer or log accuracy), and current uncertainty (the difference between the charted tide and the actual flow). Each source propagates differently over time.

Steering error grows linearly with time — a ±1 degree bias puts you 1% of the distance run off track. Speed error also grows linearly. But current error is the kicker: it grows as the square root of time if the current is random, or linearly if there is a persistent set. In practice, it's often a mix. The result is an error ellipse that stretches along the direction of the current, not the vessel's heading.

Many textbooks model this as a covariance matrix and compute a 95% confidence ellipse. That's correct, but few navigators compute it at sea. Instead, they use rules of thumb: "5% of distance run" or "10% if current is strong." Those rules assume the error is isotropic. They break when the current runs across the channel.

Let's be specific. In a river with a 2-knot cross-current and a vessel making 10 knots over ground, the cross-track error from current alone is 0.2 nautical miles per hour of run. After one hour, a 5% rule gives 0.5 miles — but the real cross-track error could be 0.2 miles or 0.8 miles, depending on whether the current is steady or variable. The 5% rule is not conservative; it's blind.

The Ellipse vs. The Circle

Draw a 95% confidence ellipse around your DR position. The semi-major axis points in the direction of greatest uncertainty — often the direction of the current, or perpendicular to the intended track if the vessel is crabbing. The semi-minor axis is smaller, sometimes much smaller. A circular bound that covers the ellipse must have a radius equal to the semi-major axis. That's the CEP at 63% or the 95% circle at 2.45 sigma. Either way, the circle is larger than the ellipse in the cross-track direction. That's the first problem: the circle overestimates the along-track risk and underestimates the cross-track risk.

In open water, that doesn't matter. In a channel, the cross-track error is what puts you on the bottom. An error bound that hides the cross-track shape is not just inaccurate — it's dangerous.

The fix is not complex. Compute the cross-track standard deviation separately. Use the formula: σ_cross = sqrt( (σ_heading * distance)^2 + (σ_current * time)^2 ). Then set your bound as 2 * σ_cross (about 95% confidence). The along-track bound can be looser — but don't draw a circle unless the semi-minor and semi-major are within 20% of each other.

Odd bit about navigation: the dull step fails first.

Odd bit about navigation: the dull step fails first.

Odd bit about navigation: the dull step fails first.

Odd bit about navigation: the dull step fails first.

Odd bit about navigation: the dull step fails first.

Patterns That Usually Work: Practical Error Bounds

Experienced navigators develop heuristics that work better than generic percentages. Here are three that we have seen hold up in practice, with the caveats that keep them honest.

Pattern 1: The 90-Degree Rule

When the current runs within 30 degrees of perpendicular to the intended track, set the cross-track error bound at 8% of distance run since last fix, plus 0.1 nautical miles for steering bias. This is a linear rule that works when current is steady. The 8% comes from a typical 1-knot cross-current over a 12-knot vessel — about 5% for current, 2% for steering, and 1% for speed. The 0.1 nm accounts for the bias that accumulates before the helmsman corrects.

It works best in rivers and channels where the current direction is stable. In tidal estuaries where the current rotates, the bound should switch to a quadratic rule (see Pattern 2).

Pattern 2: The Quadratic Rule for Rotating Currents

When the current direction changes by more than 45 degrees during the DR run, the error grows faster than linear. The cross-track standard deviation becomes: σ_cross = 0.05 * distance * sqrt(1 + (Δcurrent/15°)^2). That's not a formula from any standard — it's a heuristic we have seen in practice, based on the observation that a changing current introduces a random walk component. It's conservative: it overestimates by about 20% in most conditions, but it rarely underestimates.

The catch: this formula assumes you know the current direction at both ends of the leg. If you don't, the bound should be doubled until the next fix.

Pattern 3: The Heading-Dependent Ellipse

For vessels with electronic charting, the best pattern is to compute a heading-dependent ellipse. At each course change, reset the along-track error to zero (since you're now steering a new direction) but keep the cross-track error from the previous leg projected onto the new cross-track axis. This is essentially a coordinate transform. The math is simple: the new cross-track variance = (old cross-track variance) * cos²(Δcourse) + (old along-track variance) * sin²(Δcourse).

This pattern respects the fact that steering error resets with each change of heading. A 10-degree course change doesn't wipe out the current error — it rotates it. The heading-dependent ellipse captures that rotation. It's the closest you can get to a true covariance propagation without a Kalman filter.

We started using the heading-dependent ellipse after a near-miss in the Dover Strait. The old DR circle said we had 0.4 miles of clearance. The new ellipse said cross-track uncertainty was 0.6 miles. We adjusted course and the echo sounder showed 3 meters under the keel — exactly where the ellipse pointed. That sold it.

— Deck officer, cross-channel ferry, training debrief

Anti-Patterns: Why Teams Revert to Circles

If the ellipse is better, why do so many teams stick with circles? Three reasons, none of them good: habit, handover simplicity, and software defaults.

Anti-Pattern 1: The "It's Always Been Fine" Circle

Teams that have not grounded in years fall into the trap of thinking the circle works because it has always worked. That's survivorship bias. The circle works until the one time the cross-track error is larger than expected and the channel is narrow.

Flag this for navigation: shortcuts cost a day.

We have seen this at least a dozen times in incident reports: the DR circle showed 0.3 miles of clearance. The vessel touched bottom. Post-accident analysis showed the cross-track sigma was 0.25 miles — meaning the 95% cross-track bound was 0.5 miles, not 0.3. The circle was too small by 40%.

The fix is to demand that the navigation team compute cross-track and along-track bounds separately at least once per watch. If they match within 20%, use a circle. If not, use an ellipse.

Anti-Pattern 2: The "Simple Handover" Circle

Watch handovers are chaotic. The offgoing officer wants to say "the DR circle is 0.4 miles" and be done. The oncoming officer accepts that number without knowing its shape. The circle simplifies communication, but it simplifies away the risk.

Better handover practice: state the cross-track bound explicitly. "Current is setting us east, cross-track sigma is 0.2 miles, so the cross-track bound is 0.4 miles." That takes five extra seconds. It's not onerous. But it requires a culture that values precision over brevity.

Anti-Pattern 3: The ECDIS Default

Many ECDIS systems display a DR circle by default, with a radius based on distance run and a fixed percentage (e.g., 5%). That percentage is often configurable, but the default creates an anchor effect — teams accept it without questioning whether it's appropriate for their conditions.

The software doesn't know the current direction. It doesn't know the steering bias. It applies a generic model that's wrong in most confined waters. The anti-pattern is assuming that because the software draws a circle, the circle is correct. It's not.

To break this, set the ECDIS DR error bound to manual mode. Input the cross-track sigma separately if the system allows. If it doesn't, draw the ellipse on paper as an overlay and ignore the screen circle.

Maintenance, Drift, and Long-Term Costs of Error Bounds

Error bounds are not static. They degrade with time. The longer the interval between fixes, the larger the uncertainty. But the growth is not always linear — and that's where the maintenance cost appears.

The most effective way to maintain error bounds is to recalibrate after every valid fix. A good fix (GPS, radar range and bearing, or visual bearing) should reset the DR error to zero — but only for the components you measured. If you get a radar range, you reduce the radial error but not the gyro bias. The new bounds should reflect the remaining uncertainty.

In practice, that means after a fix, the cross-track error bound becomes the uncertainty of the fix itself (typically 0.1 nm for radar, 0.05 nm for DGPS) plus the residual steering and current errors that accumulated after the fix. Most navigators ignore the residual and reset to zero. That's a mistake. A 0.1 nm residual grows again. Over a four-hour watch, that residual alone can become 0.3 nm.

The long-term cost of sloppy bounds is not just a grounding — it's degraded trust. When the bounds are too tight, the navigator ignores them. When they're too loose, the navigator dismisses them as useless. Either way, the DR plot becomes a formality rather than a tool.

We recommend a weekly audit: compare the actual cross-track error at the next fix against the bound that was in place. Track the ratio. If the bound is more than 2x the actual error regularly, it's too loose. If it's less than 0.5x, it's too tight. Adjust the model parameters (steering sigma, current sigma) until the ratio averages 0.8 to 1.2. That calibration work takes about 10 minutes per watch per auditor — but it keeps the bounds predictive.

Drift in Steering Bias

Steering bias changes with course, speed, and loading condition. A vessel that steers 2 degrees to starboard at 10 knots may steer 1 degree to port at 15 knots. The bias is not constant. If the error bound uses a fixed steering sigma, it will be wrong for some conditions.

The fix: maintain a bias log. Every hour, record the average heading error (commanded heading minus actual heading) for the last 30 minutes. Update the steering sigma as the standard deviation of the last 10 readings. This is a rolling estimate. It adds about 30 seconds per hour. It's worth it.

Reality check: name the navigation owner or stop.

When Not to Use This Approach: The Limits of Error Bounds

Error bounds are not a substitute for a fix. They're a measure of uncertainty, not a license to accept more risk. There are conditions where the bound model breaks down entirely and you must fall back to more frequent fixes or anchoring.

Condition 1: Rapidly Changing Currents

In areas where the current changes by more than 1 knot in 10 minutes (e.g., tidal rips, river confluences), any static error bound becomes invalid. The current is not a constant or a random variable — it's a deterministic function that you can't capture with a standard deviation. In those conditions, the only safe DR is a degraded mode: assume the current is zero and double the speed error. Or, better, get a fix every 5 minutes.

Condition 2: Loss of Steering Control

If the vessel is in a turn or maneuvering, the DR error bound model — which assumes steady course and speed — doesn't apply. During a 90-degree turn, the along-track and cross-track axes rotate continuously. The error ellipse becomes a smear. The only practical approach is to reset the DR after the turn is complete, treating the turn itself as a separate leg with its own error (typically 1% of the turn radius).

Condition 3: Chart Inaccuracies

If the chart itself is wrong — due to shoaling, dredging, or outdated surveys — then the error bound becomes irrelevant. A 0.2 nm cross-track bound means nothing if the charted 10-meter contour is actually 8 meters. This is not a DR problem, but it kills the utility of any bound. Always cross-check the chart against the echo sounder and recent notices to mariners.

In these conditions, the best practice is to shrink the bound artificially to force more frequent fixes. Set the cross-track bound to 0.1 nm regardless of the model. That will push the team to verify position more often, which is the correct response when the model's assumptions fail.

Open Questions and FAQ

We collect here the questions that come up most often in training and debriefs, along with answers that reflect current practice — not necessarily settled science.

Should I use 95% or 99% bounds?

For grounding risk, 95% is standard. A 99% bound is 2.6 sigma versus 2.0 sigma — about 30% larger. That extra margin may seem safe, but it can also trigger false alarms and reduce compliance. If the 95% bound fits the channel, use it. If it doesn't, the answer is not to switch to 99% — it is to get a fix or alter the plan.

How do I handle error bounds with two concurrent currents (tide and river flow)?

If both are known, add the vectors tip-to-tail and treat the sum as a single current. The error bound is then the RSS of the individual uncertainties: σ_total = sqrt(σ_tide² + σ_river²). If one current is unknown, treat the unknown as having a uniform distribution over its possible range — that yields a larger sigma than a normal assumption.

What about vertical error bounds?

DR predicts position, not depth. Depth errors come from tidal predictions and echo sounder calibration, not DR. But if you're using DR to estimate the depth under the keel, you need to add the vertical uncertainty of the charted depth (typically 0.5–1 meter for modern surveys) to the DR cross-track error projected onto the bottom slope. For a slope of 1:10, a 0.2 nm cross-track error translates to about 0.02 nm (36 meters) of horizontal shift, which at 1:10 gives a 3.6 meter depth change — significant in shallow water.

Do I need to recompute bounds at every course change?

Yes, if you use the heading-dependent ellipse. If you use a fixed percentage, recomputing is optional — but you lose accuracy. The minimum is to recompute after every fix and after every course change that exceeds 10 degrees.

My ECDIS doesn't support ellipses. What do I do?

Draw the ellipse manually on a paper chart or overlay. Measure the semi-major and semi-minor axes from the formula above. Then use the semi-major axis as the circle radius on ECDIS — but note that this overestimates along-track uncertainty. For cross-track risk, use the semi-minor axis as the circle radius (which underestimates cross-track). The safest compromise is to use the semi-major axis for the circle and accept that the along-track bound is loose. Or, print the ellipse on a transparency and align it with the vessel's heading.

Summary: Three Moves to Make Tomorrow

This guide has covered a lot of geometry. Here is what to do with it.

1. Start computing cross-track and along-track bounds separately for every DR leg. Use the formulas in the Foundations section. This takes two minutes per leg. It will change how you see the risk.
2. Calibrate your steering sigma weekly using the bias log method. If you do nothing else, this will tighten your bounds by 20–30% in most vessels.
3. At every watch handover, state the cross-track bound explicitly — not the circle radius. Make it part of the handover checklist.

The goal is not to eliminate uncertainty. It's to know its shape. A circle hides the truth. An ellipse shows it. In confined waters, that difference is the difference between a safe pass and a grounding.

Next experiments for the curious: try the heading-dependent ellipse for one full transit and compare the predicted cross-track error at each fix to the actual error. Track the ratio. Adjust your current sigma until the ratio averages 0.9. Then tell us what you found.