Voyage Data Recorders in 2026: Requirements and When to Replace
February 10, 2026
Voyage Data Recorders (VDRs) are the ship equivalent of an aircraft “black box”, but for maritime incidents. They continuously capture a time-stamped stream of navigation, bridge audio, and key sensor inputs so investigators (and operators) can reconstruct what happened, what the bridge team saw and heard, and what the ship was doing before an event.
VDR Carriage Requirements
Use this as a practical reference for SOLAS Chapter V VDR and S-VDR carriage. It is intentionally written so a ship manager can sanity-check compliance quickly before talking to class and flag.
Disclaimer
Always verify against your Flag, Class, and your ship’s trading pattern
- Rules below reflect SOLAS carriage triggers and IMO-level guidance, but flag State instructions, class interpretations, and trading limits can add requirements.
- “Constructed” dates matter. For borderline cases, confirm the ship’s construction date as recorded for SOLAS purposes.
- Some administrations can allow exemptions in limited scenarios where interfacing is unreasonable and impracticable, or where the ship will be taken permanently out of service within a defined period.
VDR full voyage data recorder
S-VDR simplified VDR allowed in specific cases
Intl voyages carriage phase-in applies to cargo ships engaged on international voyages
Scroll sideways on mobile
| Ship segment | Carriage trigger | Required recorder | Compliance deadline | ShipUniverse notes for operators |
|---|---|---|---|---|
| Passenger ships | ||||
| Passenger ships Constructed on or after 1 July 2002 | Constructed date threshold | VDR | At delivery (carried from newbuild) | Core passenger trigger for full VDR carriage. Plan integration early if doing bridge refits so you do not create interface surprises late in the yard period. |
| Ro-ro passenger ships Constructed before 1 July 2002 | Legacy passenger ro-ro trigger | VDR | Not later than the first survey on or after 1 July 2002 | This is an early compliance trigger compared with other passenger segments. If you operate older ro-ro pax tonnage, confirm survey timing and any class memo requirements for recording media location and float-free arrangements. |
| Passenger ships (non ro-ro) Constructed before 1 July 2002 | Legacy passenger non ro-ro trigger | VDR | Not later than 1 January 2004 | Widely phased in across legacy passenger fleet. In practice, a lot of the risk is in audio and interface quality: confirm bridge audio sources, channel mapping, and playback access in drills. |
| Non-passenger ships constructed on or after 1 July 2002 | ||||
| Cargo and other non-passenger ships 3,000 GT and up, constructed on or after 1 July 2002 | GT and constructed date threshold | VDR | At delivery (carried from newbuild) | This is the cleanest category: the ship is expected to be designed around a VDR from the start. If you replace the VDR later, verify the new installation meets the applicable IMO performance standards for the installation date. |
| Existing cargo ships constructed before 1 July 2002 (phased-in carriage) | ||||
| Cargo ships 20,000 GT and up, constructed before 1 July 2002 | Phased-in cargo carriage | VDR or S-VDR | First scheduled dry-docking after 1 July 2006, but not later than 1 July 2009 | The rule allows S-VDR (simplified) as an option for this legacy segment. For operators, the “dry-docking” trigger is the practical planning anchor for budgeting and yard scope. |
| Cargo ships 3,000 GT and up but less than 20,000 GT, constructed before 1 July 2002 | Phased-in cargo carriage | VDR or S-VDR | First scheduled dry-docking after 1 July 2007, but not later than 1 July 2010 | Same simplified allowance, later phase-in window. If the ship is nearing end-of-life, check if your Administration allows the limited out-of-service exemption tied to the implementation dates. |
| Ongoing operational requirement (applies once you carry a VDR system) | ||||
| Ships carrying a VDR system VDR system including sensors | Annual performance testing | Test and certificate | At least annually (retain certificate on board) | Annual performance test is the recurring compliance item operators miss most often. A practical checklist: recorded duration, data recoverability, protective capsule condition, and any location-aid device serviceability. |
| Performance standards (matters most when replacing or installing a new unit) | ||||
| New VDR installations Installed on or after 1 July 2014 | Installation date threshold | Meet revised standards | Applies at installation or replacement | For replacements, confirm the new unit conforms to the IMO performance standards applicable to the installation date. This is a key reason “swap only the box” projects sometimes turn into broader interface and sensor scope. |
| Older VDR installations Installed before 1 July 2014 | Installation date threshold | Meet earlier standards | Applies to the existing installed system | Older VDRs can remain compliant if they meet the earlier referenced standards and pass annual performance tests. Replacement decisions usually come from supportability, failed annual tests, interface changes, or upgrades to other bridge systems. |
Operator takeaway
Two quick checks before you assume you are “fine”
- Carriage trigger: passenger category, GT, and construction date decide whether you must carry a VDR and whether S-VDR was permitted for older cargo tonnage.
- Keep it compliant: annual performance testing and certificate retention are the recurring compliance items that show up in audits and investigations.
Scope note: This table focuses on SOLAS Chapter V carriage triggers and IMO-level requirements. If you want, I can follow this section with a “Replacement Timing” block that ties replacement decisions to annual test failures, end-of-support risk, bridge retrofits (ECDIS, radar, conning), and planned dry-docking windows.
When to Replace
Most shipowners do not replace a VDR because a regulation says “at X years.” They replace it because the unit becomes harder to support, starts failing annual performance tests, or a bridge upgrade breaks interfaces. This section gives you a practical replacement decision map.
When to Replace a VDR
There is no universal “replace at 10 years” rule. Replacement is usually driven by supportability, annual performance test results, and interface risk when other bridge systems change.
Disclaimer
Use this as a decision guide, then confirm scope with your Flag and Class
- Keeping an older VDR can be acceptable if it remains serviceable and passes annual performance testing.
- When you install or replace a VDR, the new installation should conform to the performance standards applicable at the time of installation.
- Local requirements can add items such as specific capsule servicing rules, recording channel expectations, or audit documentation.
Replace now hard risk or non-compliance
Plan in dry-dock predictable risk you can schedule
Keep and monitor acceptable if APT stays clean
Scroll sideways on mobile
| Trigger category | What you see on board | Why it matters | What to do next | Replacement timing call |
|---|---|---|---|---|
| Annual performance test failure | APT fails on accuracy, duration, data recoverability, audio channels, or sensors. The unit may be “recording” but output is incomplete or unreadable. | A failed APT is the clearest signal that the recorder is not meeting the baseline operational requirement. Repeat failures also expose you during incidents and PSC scrutiny. | Fix root cause first (sensor feed, audio mapping, storage module, capsule, firmware). If failure is not repairable within reasonable time and cost, scope a replacement. | Replace now |
| End of manufacturer support | Vendor cannot provide spares, certified service, or software updates. Authorized service network has limited capability for your model. | Supportability becomes an operational risk: a minor defect can become a long off-hire event. It also increases the chance you fail the next APT. | Treat as a planning trigger. Ask for written support status, lead times for key spares, and service coverage in your trading regions. | Plan in dry-dock |
| Bridge refit interface risk | New ECDIS, radar, conning display, GNSS, gyro, speed log, AIS, or alarm systems planned. Existing VDR uses legacy serial interfaces or custom wiring. | Most “simple swaps” fail because the VDR is the hub for many feeds. Changes to other equipment can break inputs and audio routing. | During the refit design, map every input and output and confirm the recorder can ingest the new protocol set. If not, bundle a VDR replacement into the refit. | Plan in dry-dock |
| Recurring minor faults | Intermittent alarms, missing channels after power cycling, storage media errors, inconsistent time sync, or bridge audio that drops out randomly. | These are early warning signs that often turn into a failed APT, or unusable data after an incident. | Track defects as a reliability trend. If you have multiple service calls in a year, price the full replacement versus ongoing repairs. | Plan in dry-dock |
| Capsule or locating device serviceability | Protective capsule damage, corrosion, mounting issues, or the locating aid device is out of service. | Even if data is recorded, recovery and survivability are part of the end purpose of the system. | Resolve through certified servicing where possible. If the capsule module is obsolete or repeatedly fails, replacement becomes the efficient path. | Plan in dry-dock |
| Cyber and remote access policy changes | You need controlled download, remote diagnostics, or stricter access control. Older units have limited user management or weak controls by modern standards. | This is a governance trigger, not a SOLAS trigger, but it matters for fleet-wide cyber posture and incident handling. | If your SMS or cyber policy requires capabilities the current unit cannot support, scope an upgrade during a planned stop. | Keep and monitor |
| Standards step-up at replacement | Your installed VDR is older and still serviceable. You are considering a replacement for business reasons. | Replacement installs generally need to meet the performance standards applicable on the installation date, which can expand scope beyond the box itself. | Before ordering, confirm the required standard for the new install date and list any additional sensors, channels, or survivability features. | Plan in dry-dock |
Replacement Readiness Score
This is a quick planning tool. It helps you decide if the VDR should be treated as an urgent replacement item, a dry-dock bundle, or something to keep while monitoring.
Score: 0 / 41
Keep and monitor
If APT is clean and support is healthy, keep the system serviceable and focus on next APT readiness.
Planning notes
How owners typically schedule the work
- Best window: next scheduled dry-dock or a bridge refit window, because interface testing is easier when multiple vendors are already mobilized.
- Scope control: require a channel list and interface map in the quote so you do not discover missing inputs during commissioning.
- Practical KPI: if you have recurring defects or support risk, avoid waiting until the next APT forces an emergency purchase.
ShipUniverse angle: In the next section of your guide, you can follow this with a tight “Replacement scope checklist” for procurement:
sensor list, audio sources, interface protocols, capsule and locating aid servicing, commissioning tests, crew playback access, and APT planning.
We welcome your feedback, suggestions, corrections, and ideas for enhancements. Please click here to get in touch.