Speed is an input, not one universal fact
A ship can have speed through water, speed over ground, longitudinal speed, transverse speed and values filtered over different intervals. Each supports different decisions. Treating them as interchangeable can corrupt collision assessment, track control and under-keel calculations.
IMO distinguishes measurement capability
Resolution MSC.96(72) sets performance standards for devices measuring and indicating speed and distance. The applicable arrangement, axes, reference and operating limitations must be understood on the actual vessel.
Ground speed serves track monitoring
GNSS-derived speed over ground supports ETA and achieved-track assessment. It may be false or unavailable during jamming, spoofing or receiver failure.
Agreement can be accidental
Through-water and ground speed may match in weak current while both contain similar calibration error. Agreement at one moment is not a complete test.
Current is the difference with direction
Subtracting scalar speeds is insufficient where vectors differ. Use course, heading and velocity components to understand set and drift.
Doppler modes can change reference
Some equipment can operate in water-track or bottom-track modes under different depth and seabed conditions. The bridge should know which mode is active and how the change is indicated.
Aeration can degrade the sensor
Bubbles, heavy weather, shallow water and hull flow can interrupt acoustic measurement. A stable retained value may look healthier than a visibly fluctuating one.
Fouling alters performance
Marine growth, coating damage or transducer condition can introduce error. Include speed sensors in hull, dry-docking and performance investigations.
Calibration is condition-dependent
Loading, trim, draught, sea state and water properties can affect readings. Record the conditions and method used when checking or adjusting calibration.
A zero test is useful but limited
A stationary indication in port can reveal offset, but it does not test scale error at sea. Use approved trials and cross-checks across operational speeds.
Transverse speed matters in pilotage
Large vessels can build sideways motion that a longitudinal figure hides. Pilots, bridge teams and tug operators need a shared understanding of reference point and direction.
Reference point changes lateral prediction
Bow, stern, center and sensor locations can have different transverse velocities during rotation. Portable pilot units and ship displays must use compatible geometry.
Radar stabilization depends on the input
True-motion and true-vector calculations require reliable own-ship motion. A wrong log can alter target vectors and closest-point predictions without changing the raw echo.
Relative motion remains valuable
When own-speed quality is doubtful, correctly used relative plots and observed bearing trends can preserve collision assessment. Officers must know presentation settings and limitations.
AIS may tell a different story
AIS commonly reports speed over ground from a positioning source, while radar can use log inputs. Divergence may reflect current, latency, sensor failure or target data quality rather than hostile manipulation.
ECDIS dead reckoning can inherit error
If position input is lost, heading and speed can propagate an estimated position. A small speed bias becomes a growing along-track error.
Autopilot performance can be affected
Track and steering systems may use speed to shape control or prediction. Know which source is selected and how failure or substitution is shown.
Squat estimates are speed-sensitive
Squat can rise strongly with speed. Using the wrong reference or an understated value can consume under-keel margin that appears available in a static calculation.
Propulsion monitoring uses different evidence
Shaft power, rpm, fuel and through-water speed help assess hull and propeller performance. Ground speed alone can make favorable current look like improved efficiency.
Weather routing needs source clarity
Routing platforms may compare predicted and achieved speed using noon reports or live feeds. Label ground and water references to avoid false performance conclusions.
ETA pressure can distort reporting
Commercial teams may focus on ground speed because it determines arrival. The bridge must not suppress current, safety or sensor uncertainty to preserve a promised ETA.
Alarm thresholds need context
Low-speed or sensor alarms should reflect manoeuvring, traffic and system design. A silenced alarm during expected slow steaming can conceal later sensor failure.
Source selection must be visible
Integrated systems should show which sensor feeds radar, ECDIS, AIS, autopilot and voyage recording. A label reading speed without provenance is operationally incomplete.
Automatic substitution can surprise
After a failure, a system may change from log speed to GNSS speed or a manually entered value. The bridge needs an unambiguous indication and must reassess every dependent function.
Manual entry ages immediately
A manually inserted value can support temporary operation, but it becomes stale with engine, current or weather change. Mark the source and review interval.
GNSS spoofing creates a distinctive conflict
Ground speed may jump while engine, log, radar and visual evidence remain stable. Preserve the disagreement and fix independently before accepting the new track.
Common power can defeat redundancy
Two speed displays may share a transducer, processor, network switch or supply. Map the chain rather than counting screens.
Cyber compromise is one possible cause
Bad configuration, failed updates, wiring, fouling and hardware defects are often plausible. Isolate safely, preserve evidence and avoid attribution until analysis supports it.
Pre-transit tests need realistic movement
Static checks cannot expose every dynamic error. Review recent sea comparisons, alarms, source selection and dependent displays before entering constrained waters.
Define expected relationships
The passage plan can state expected ground and through-water speed ranges, current effects and triggers for disagreement. This makes anomaly detection deliberate.
Slow down when the model is doubtful
Where traffic and steerage allow, reduced speed lowers closure rate, buys assessment time and may reduce squat. The master should balance these effects against threat exposure.
Add people with assigned tasks
One officer can compare sensors, another maintain radar plotting and another con the vessel. Structured reinforcement is more useful than a crowd watching conflicting numbers.
Record raw and displayed values
Capture time, mode, source, settings, heading, course, both speeds, radar presentation, GNSS status and actions. A later spreadsheet cannot recreate an unrecorded selection change.
Owners need sensor-lineage diagrams
Document transducers, processing, networks, power and consumers. Update the diagram after retrofits and verify it onboard.
Charterers need qualified performance data
Claims about speed and consumption should account for contractual definitions, weather and current. A navigation-sensor anomaly is not automatically proof of underperformance.
Insurers need dependency evidence
After collision or grounding, preserve log calibration, maintenance, source selection, radar, ECDIS, AIS, VDR and bridge communications. Similar displayed values may share one failed input.
Hypothetical: the optimistic squat
The UKC model receives understated through-water speed while the ship accelerates in a shallow channel. A cross-check with rpm and ground motion triggers slowdown before the minimum margin is breached.
Hypothetical: the false turn
Radar true vectors change sharply after automatic substitution to a spoofed GNSS speed. Relative plotting shows the targets did not manoeuvre, preventing an unnecessary alteration.
Hypothetical: the stale manual value
A temporary speed entry remains after engine reduction. ECDIS dead reckoning runs ahead until the watch identifies the source label and rebuilds the fix.
Forecast
Future integrated bridges will expose speed-source confidence and lineage more clearly. Safety will still depend on officers understanding the physical reference, vector meaning and downstream consumers.
ZeaClub view
Never ask only whether speed is available. Ask speed relative to what, measured where, updated when and consumed by which systems. In Hormuz, a wrong log can distort radar, route monitoring, squat and commercial expectations at once. Raw observations and independent geometry must remain available to challenge the polished prediction.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- IMO, Performance standards for devices to measure and indicate speed and distance, MSC.96(72)Accessed 2026-11-19
- IMO, Revised performance standards for radar equipment, MSC.192(79)Accessed 2026-11-19
- IMO, ECDIS performance standards, MSC.530(106)Accessed 2026-11-19
- IMO, Revised guidelines for onboard operational use of shipborne AIS, A.1106(29)Accessed 2026-11-19
- IMO, Convention on the International Regulations for Preventing Collisions at SeaAccessed 2026-11-19