By ShipCalculators.com · Published 9 May 2026

Voyage Data Recorder (VDR + S-VDR): SOLAS V/20 marine black box

The Voyage Data Recorder (VDR) and its Simplified Voyage Data Recorder (S-VDR) sibling are the maritime equivalent of the aircraft “black box”: tamper-resistant casualty-investigation recorders mandated by Regulation 20 of Chapter V of the SOLAS Convention to capture navigational, operational, audio, radar and alarm data continuously while the ship is at sea. The current performance standard is IMO Resolution MSC.333(90), adopted in 2012 and superseding the earlier A.861(20) of 1997 and MSC.214(81) of 2006; the testing standards are IEC 61996-1 for full VDR and IEC 61996-2 for S-VDR; both sit on top of IMO Resolution A.694(17) general requirements for shipborne radio equipment and electronic navigational aids. Carriage is mandatory on passenger ships built on or after 1 July 2002, on cargo ships of 3,000 GT and above built on or after 1 July 2002, and as S-VDR retrofit on cargo ships of 150 to 3,000 GT built before 1 July 2002 (compliance phased through 2008-2010). The captured dataset spans 15 mandatory items including UTC date and time, GNSS position, speed over ground and through water, gyro and magnetic heading, full bridge audio, VHF radio audio, radar image with acquired targets, ECDIS chart and alarms, echo sounder, main alarms, rudder and engine order plus response, hull-opening status, acceleration and hull stresses where fitted, and wind speed and direction; the recording duration is a minimum 12-hour rolling cycle in the protected capsule plus 30-day extended dataset since MSC.333(90). Storage uses a dual architecture: an orange aircraft-style Float-Free Capsule (FFC) with 6-month battery, 37.5 kHz pinger, 6,000 m depth survival and 1,100 degrees C fire one-hour survival, plus a fixed protected capsule for diver-free recovery and a long-term internal hard drive. The casualty record where VDR data was decisive includes Costa Concordia 2012, Sewol 2014 and the contrast of MV Stellar Daisy 2017 where capsule recovery failed. This article maps the SOLAS regime to the SOLAS Chapter I general provisions, interfaces with AIS and ECDIS, GMDSS, SOLAS Chapter IV radio communications, the ISM Code, the MARPOL Convention, the ISPS Code, the Polar Code and STCW Chapter II master and deck officer competence; ShipCalculators.com hosts the calculator catalogue supporting carriage-threshold determination, recording-duration arithmetic, FFC battery and pinger sizing, and APT scheduling.

Contents

Background: post-Estonia 1994 + Herald of Free Enterprise 1987 push

The case for a maritime equivalent of the aircraft cockpit voice recorder and flight data recorder grew through the 1980s and 1990s out of a series of catastrophic ferry losses where investigators were left without an objective record of what happened on the bridge in the minutes before the casualty. The Herald of Free Enterprise capsizing on 6 March 1987 in the approaches to Zeebrugge killed 193 people and produced the Sheen Inquiry, which had to reconstruct the sequence of bow-door non-closure, list, downflooding and capsize from witness testimony alone, with no objective record of bridge orders, engine state, or ship-trim trace. The Estonia loss on 28 September 1994 in the Baltic killed 852 people and again left an investigative team (the Joint Accident Investigation Commission of Estonia, Finland and Sweden) reliant on survivor testimony and limited wreck examination because no recording device captured the bridge audio or the bow-visor failure sequence.

The MV Scandinavian Star ferry fire of 7 April 1990, the MV Jan Heweliusz capsize of 14 January 1993 and the Princess of the Stars capsize of 21 June 2008 added to the casualty record where the absence of a black-box-style recorder hampered investigation. The aviation parallel was already well established: the ICAO Annex 6 Operation of Aircraft mandated cockpit voice recorders and flight data recorders progressively from 1957 onward, and by the 1980s these devices had become routine forensic tools enabling causal reconstruction of complex pilot-error, mechanical and weather-related accidents. The maritime industry recognised that comparable instrumentation could provide equivalent forensic value at sea.

The IMO Maritime Safety Committee placed the question on its agenda in the early 1990s, working through the NAV Sub-Committee (Navigation) and the COMSAR Sub-Committee (Radiocommunications and Search and Rescue) to develop a performance standard. The IMO Assembly adopted Resolution A.861(20) at its 20th session in November 1997, establishing the first VDR performance standard. SOLAS amendments mandating VDR carriage were adopted by MSC at its 73rd session in December 2000 and entered force on 1 July 2002, with phased implementation across ship categories.

SOLAS V/20 application: VDR + S-VDR thresholds

Regulation 20 of SOLAS Chapter V defines the carriage requirement. The text of Regulation 20.1 states that ships, when engaged on international voyages, shall be fitted with a Voyage Data Recorder, and Regulation 20.2 lists the specific categories. The current Regulation 20 framework, after the 2002 amendments and the 2004 amendments introducing S-VDR, distinguishes three carriage categories:

Passenger ships of any size, irrespective of date of build, where SOLAS applies (this includes ro-ro passenger ships and cruise ships).
Cargo ships of 3,000 GT and above built on or after 1 July 2002, fitted with a full VDR meeting the current MSC.333(90) performance standard.
Cargo ships of 150 GT and above but less than 3,000 GT built before 1 July 2002, fitted with a Simplified VDR (S-VDR) meeting the IEC 61996-2 standard, on a phased schedule running from 1 July 2008 to 1 July 2010 depending on tonnage band.

The Regulation 20.4 exemptions cover ships solely engaged on domestic voyages within the territorial sea of the flag State (subject to flag-State discretion), and a flag State may exempt a ship from VDR carriage when its trade pattern, age or technical configuration would make installation impracticable, but exemptions are reported to IMO and are subject to PSC scrutiny. Ships covered by the regulation must keep the VDR or S-VDR fully operational, with the continuous power supply maintained from a battery back-up sufficient for at least two hours of recording after main and emergency power loss (MSC.333(90) paragraph 4.5).

VDR mandatory: passenger + cargo ≥3,000 GT post-2002

The full VDR carriage applies to ships built on or after 1 July 2002 in two categories. All passenger ships, irrespective of size and irrespective of voyage type, when SOLAS applies, must carry a full VDR. This sweeping requirement reflects the high consequence of passenger-ship casualties and the lessons from Herald of Free Enterprise and Estonia. Cargo ships of 3,000 GT and above built on or after 1 July 2002 must also carry a full VDR. The 3,000 GT threshold was chosen because it covers the deep-sea cargo fleet (most general-cargo vessels, bulk carriers, oil tankers, chemical tankers, container ships, and gas carriers exceed this size) while excluding the small coastal and short-sea tonnage where the cost-benefit balance favoured the simpler S-VDR alternative.

The performance standard applicable to the full VDR has evolved through three IMO instruments. Ships built between 1 July 2002 and 30 June 2008 were originally fitted to Resolution A.861(20) of 1997. Ships built between 1 July 2008 and 30 June 2014 were fitted to Resolution MSC.214(81) of 2006, which raised the audio-channel count, expanded the radar-data capture and clarified the FFC environmental-survival specifications. Ships built on or after 1 July 2014 are fitted to Resolution MSC.333(90) of 2012, the current standard, which added the 30-day extended-dataset requirement, increased the FFC environmental specifications, refined the data-extraction protocol, and added explicit cyber-resilience guidance. Existing ships are not required to retrofit to the latest standard unless the operator chooses to upgrade or the equipment is replaced after major repair.

S-VDR retrofit: cargo 150-3,000 GT pre-2002, since 2008

The Simplified VDR category was added by SOLAS amendments adopted at MSC 79 in December 2004 and entered force on 1 July 2006. The S-VDR addresses the gap between the full-VDR mandate and the long tail of older, smaller cargo tonnage: ships of 150 GT to 3,000 GT built before 1 July 2002 must carry an S-VDR meeting the IEC 61996-2 testing standard. The retrofit timeline ran on a phased schedule:

Cargo ships of 20,000 GT and above built before 1 July 2002: fit an S-VDR not later than the first scheduled dry-docking after 1 July 2006, but not later than 1 July 2009.
Cargo ships of 3,000 GT and above but less than 20,000 GT built before 1 July 2002: fit an S-VDR not later than the first scheduled dry-docking after 1 July 2007, but not later than 1 July 2010.
Cargo ships of 150 GT and above but less than 3,000 GT: fit an S-VDR following equivalent phased schedule, with effective full-fleet compliance by 1 July 2010.

The simplified label refers to a reduced data-channel set: the S-VDR captures the date and time, ship’s position, speed, heading, bridge audio, VHF audio, radar data and the principal navigational alarms, but is exempted from the more demanding capture of engine and rudder order plus response feedback, hull-opening status, accelerometer data, and the full main-alarm set. The reduced capture envelope reflects the sensor-availability reality on smaller, older vessels where many of the full-VDR data sources (NMEA-instrumented engine telegraph response, hull-stress monitors, accelerometer arrays) are not fitted in the original ship design and would require disproportionate retrofit cost. The S-VDR still uses the same FFC capsule architecture and the same 12-hour rolling-recording duration as the full VDR.

IMO performance standards: A.861(20) 1997 → MSC.214(81) 2006 → MSC.333(90) 2012

The performance-standard lineage spans three IMO resolutions, each tightening the technical envelope:

Resolution A.861(20) (Assembly, November 1997) was the original VDR performance standard. It defined the 15-item data capture, the minimum 12-hour rolling-recording duration, the FFC orange-coloured capsule with 30-day pinger battery and 6,000 m depth survival, and the annual performance test (APT) by approved service personnel. A.861(20) was the standard applicable to the first generation of full VDRs fitted under the 2002 mandate, and most ships of that vintage are still operating to that standard today.

Resolution MSC.214(81) (December 2006) was a substantive revision. It increased the bridge-audio channel count to capture more of the bridge environment (multiple ceiling microphones, port-bridge-wing and starboard-bridge-wing microphones, and provision for capturing radio-room audio when the radio room is separate from the bridge), raised the FFC pinger battery life from 30 days to 6 months (responding to deep-water-recovery time-frames after major casualties), tightened the fire-survival specification to the current 1,100 degrees C for one hour plus 260 degrees C for 10 hours envelope, and added explicit requirements for the capture of the radar image with all radar-acquired targets visible.

Resolution MSC.333(90) (May 2012) is the current performance standard. It introduced the 30-day extended-dataset requirement (an internal hard drive holding a longer-duration record at lower bit-rate, supplementing the 12-hour high-resolution rolling capsule), refined the data-extraction interface so that flag-State and IACS investigators can extract the data using a standardised playback toolchain, added explicit guidance on cyber-security and tamper-resistance of the recorder, expanded the captured-data envelope to include additional NMEA inputs from modern integrated bridge systems, and clarified the APT acceptance criteria. MSC.333(90) is mandatory for VDRs fitted on or after 1 July 2014.

A.694(17) general radio equipment requirements

Resolution A.694(17) of November 1991, “General Requirements for Shipborne Radio Equipment forming part of the Global Maritime Distress and Safety System (GMDSS) and for Electronic Navigational Aids,” is the horizontal performance standard that sits beneath every IMO carriage requirement for shipborne electronic equipment. It defines the baseline mechanical, electrical and environmental performance that all approved equipment must meet, including the VDR. The principal A.694(17) requirements applicable to VDRs are the environmental categories (temperature range, humidity, vibration, salt-mist exposure), the electromagnetic compatibility envelope (immunity to conducted and radiated interference, limits on emissions), the power-supply tolerance (operation across mains and emergency-source variation), the mechanical-shock survival (the VDR continues operating across the ship-motion regime expected at sea), and the type-approval marking identifying the model, manufacturer, performance standard met, and the recognised organisation that issued the type-approval certificate. A.694(17) is referenced in the introductory clauses of MSC.333(90) and in IEC 61996-1 and 61996-2 as the foundation on which the VDR-specific requirements are layered.

IEC 61996-1 (full VDR) + IEC 61996-2 (S-VDR) testing

IEC 61996-1 is the international testing and conformance standard for the full VDR, published by the International Electrotechnical Commission and adopted by IMO and IACS as the operational benchmark for VDR type-approval. The current edition is IEC 61996-1:2013, which aligns with the MSC.333(90) performance standard and supersedes the earlier 2007 edition that aligned with MSC.214(81). The standard specifies the test methods for each of the 15 data channels, the environmental-test envelope for the FFC and fixed capsule (including the depth-pressure test, the fire-survival test, the static-load and penetration tests, and the saltwater-immersion test), the playback-software conformance requirements, the annual-performance-test acceptance criteria, the electromagnetic-compatibility test sequence, and the identification and marking requirements. Type-approval certificates issued under IEC 61996-1 by recognised classification societies (DNV, LR, ABS, BV, NK, RINA, KR, CCS, RS, IRS) are accepted by IMO Member States as evidence that the equipment meets the performance standard.

IEC 61996-2 is the parallel testing and conformance standard for the Simplified VDR. It uses the same FFC and fixed-capsule architecture as IEC 61996-1, with the same depth and fire survival envelope, but a reduced data-channel set reflecting the simplified capture envelope of the S-VDR. The current edition is IEC 61996-2:2018. Both IEC standards are referenced explicitly in MSC.333(90) and in the IACS Unified Requirement UR M51, which mandates that all VDR and S-VDR installations comply with the corresponding IEC standard at type-approval and through the in-service annual-performance-test cycle.

Captured data 1: date + time UTC

The date and time stamp underpins every other recorded channel and must be referenced to Coordinated Universal Time (UTC) with sub-second resolution. The MSC.333(90) standard requires the date and time to be derived from a primary GNSS source (typically the same GPS receiver feeding the AIS and ECDIS chains) with secondary fallback to the ship’s master clock. Time-stamp accuracy is required to be better than 1 second when the GNSS source is healthy, and the recorder must flag a degraded time stamp when the GNSS lock is lost so that investigators reading the data later can identify the period during which time-stamp accuracy is reduced.

Captured data 2: ship’s position (GNSS)

The ship’s position is captured from the primary GNSS receiver as latitude and longitude in WGS-84 reference frame, with the resolution of the originating receiver (typically 1/10,000 minute, approximately 1.8 m at the equator). The recorder logs the fix quality flag (autonomous, differential GPS, RTK, no-fix), the HDOP (horizontal dilution of precision), and the age of the fix. Where the ship is fitted with a secondary GNSS receiver (often required by SOLAS V/19 for the integrated bridge configuration), both feeds may be logged so that comparison between primary and secondary can identify a single-receiver fault. The position track is sampled at intervals defined by the equipment performance standard, typically every 1 to 5 seconds in the high-resolution rolling capture and at lower resolution in the 30-day extended dataset.

Captured data 3: ship’s speed (SOG + STW)

The ship’s speed is captured both as speed over ground (SOG) from GNSS and as speed through water (STW) from a Doppler speed log or electromagnetic speed log. The SOG and STW values diverge in current-affected waters and the differential is itself a forensically valuable indicator of set and drift; for casualty investigation, comparison of SOG and STW with course over ground and heading reveals current-induced drift and is essential to the reconstruction of grounding casualties. The speed sources feed via NMEA 0183 sentences (VTG for SOG, VBW for both SOG and STW, VHW for STW) over the IEC 61162 serial interface to the VDR.

Captured data 4: heading (gyro + magnetic)

The heading is captured from both the gyrocompass (typically a north-seeking gyro on commercial vessels above 500 GT, fed via NMEA HDT or HDG sentence) and the magnetic compass (where fitted, with deviation correction applied). The gyro is the primary heading source for navigation and autopilot control; the magnetic is the back-up reference and the source against which gyro accuracy is verified daily. The VDR records both feeds independently. Heading-source comparison is a standard forensic check in casualty investigation: a divergence between gyro and magnetic that grew progressively before a grounding may indicate gyro drift not noticed by the bridge team.

Captured data 5: bridge audio (all conversations)

Bridge audio is the most distinctive VDR data channel and the source of greatest forensic value in many casualties. The MSC.333(90) standard requires the capture of all bridge audio from microphones positioned to record conversations between bridge personnel, between bridge personnel and pilots, between bridge personnel and external visitors (engineers reporting from below, mooring teams reporting from forward and aft stations), and the ambient bridge environment including alarm tones, telegraph order acknowledgements, and external sounds heard through open bridge wings. The audio coverage requires multiple microphones: typically two ceiling-mounted microphones in the wheelhouse plus port-bridge-wing and starboard-bridge-wing microphones, with provision for additional microphones in the chart room or radio room when these are separate from the wheelhouse. Audio is recorded at sufficient quality for clear speech recognition, with the MSC.333(90) standard specifying a minimum sampling rate suitable for intelligible speech and the storage encoded in a format playable by standard VDR playback software. The bridge-audio recording is continuous and unattended; the master and officers cannot pause, edit, or selectively delete the recording without triggering tamper indicators.

Captured data 6: VHF audio (all channels in use)

VHF radio audio is captured from all VHF channels in use on the bridge, including the principal Channel 16 distress and calling channel, the bridge-to-bridge Channel 13 in regions where it is in use, the VTS working channel in port-approach areas, the port-operations channels, and any inter-ship working channels assigned by VTS or by mutual agreement during close-quarters manoeuvring. The VDR captures both the received audio and the transmitted audio, time-stamped against the bridge-audio and navigational data so that a reviewer can correlate VHF traffic with bridge actions. VHF capture is essential in collision investigation, where the timing and content of bridge-to-bridge negotiation about meeting agreements is often pivotal to the causal reconstruction.

Captured data 7: radar data with acquired targets

Radar data is captured as a periodic screen-image snapshot from the principal navigation radar (typically the X-band 9 GHz radar, with the secondary S-band 3 GHz radar also captured where fitted). The image is sampled at intervals defined by the equipment standard, typically every 15 to 30 seconds, and includes the radar picture as the operator sees it: the radar echoes, the acquired targets with their ARPA-derived course-and-speed vectors, the trial-manoeuvre overlay when the operator has activated trial-manoeuvre, the chart overlay when the radar is interfaced with the ECDIS, and the range scale and centre offset in use. The radar capture allows investigators to reconstruct what radar information the bridge team had at any moment and whether the radar picture supported the bridge decisions taken.

Captured data 8: ECDIS chart, position, alarms

The ECDIS data captures the chart in use on the principal ECDIS (or on the back-up ECDIS where dual-ECDIS configuration is fitted), the vessel position and track as displayed on the chart, the route plan loaded on the ECDIS, and the ECDIS alarm state at each sample interval. ECDIS alarms include the anti-grounding alarm triggered by safety-contour crossing, off-track alarms when the ship deviates beyond the cross-track distance threshold, chart-update overdue alarms, next-waypoint approach alarms, and specialist alarms for areas of caution (traffic-separation schemes, area-to-be-avoided polygons, marine protected areas). The capture is interface-driven via the IEC 61162 serial link from the ECDIS to the VDR; the integration is standardised by the IEC 61174 ECDIS performance standard and the IEC 62288 navigation display alert standard.

Captured data 9: echo sounder

The echo sounder captures the under-keel depth at each sample interval, fed from the primary echo-sounder transducer through NMEA DPT or DBT sentence. Depth-trace capture is forensically essential in grounding casualty reconstruction, allowing the investigator to trace the under-keel clearance from the moment the ship entered the casualty area through to the actual grounding. The depth trace is also useful in deep-water casualty reconstruction (heavy-weather rolling and pitching can reveal swell and sea-state via depth-modulation patterns).

Captured data 10: main alarms

The main alarms capture aggregates the fire-detection alarms, the machinery alarms from the engine-room control system, the navigation alarms from the integrated bridge system, the bilge alarms, the steering-failure alarms, the emergency generator alarms, the CO2 release alarms, the fire-door open alarms, the watertight-door alarms, and the propulsion alarms. The MSC.333(90) standard requires the capture of all alarms presented on the bridge alarm panel, time-stamped to within one second so that the alarm cascade in the moments before a casualty can be reconstructed in sequence. Alarm-cascade reconstruction is a routine forensic technique: the order in which alarms triggered, and the time delay between each alarm and the bridge acknowledgement, indicates whether the bridge team identified the problem correctly and responded promptly.

Captured data 11: rudder order + response

The rudder order and response capture is split into rudder order (the helm command issued by the helmsman or autopilot) and rudder response (the actual rudder angle achieved, fed from the rudder-angle indicator). The differential between order and response identifies steering-gear lag, hydraulic-pressure problems, or steering-gear failure. NMEA RSA sentence (rudder sensor angle) supplies the response feed; the order feed is taken from the autopilot or helm console. The rudder-order versus response trace is essential in collision investigation where the ship’s response to last-minute helm orders is in question.

Captured data 12: engine order + response

The engine order and response capture is the propulsion equivalent of the rudder capture: engine telegraph orders issued from the bridge (full ahead, half ahead, slow ahead, dead slow ahead, stop, dead slow astern, slow astern, half astern, full astern, on shafts with controllable-pitch propellers the requested pitch in percentage) plus the engine response (actual shaft RPM or actual propeller pitch achieved). The propulsion telegraph is captured via the IEC 61162 serial interface from the engine-control console, with both the requested order and the achieved response time-stamped. Propulsion-order reconstruction is essential in casualty investigation involving emergency-stop manoeuvres, crash-stop tests after main-engine failure, and any situation where the bridge team’s intent versus the actual machinery behaviour is in question.

Captured data 13: hull opening + watertight + fire door status

The hull-opening status captures the open or closed state of the bow visor, stern ramps, side doors, shell doors for ro-ro and ro-pax vessels, plus the watertight doors between subdivision compartments and the fire-door state on the principal subdivision boundaries. The capture is on a per-door basis with each door’s state (open, closed, locked) time-stamped at each change-of-state. This data is decisive in ro-ro flooding casualties where bow-door or stern-door non-closure is the precursor to capsize: the Herald of Free Enterprise loss, in which bow doors were left open for the channel passage from Zeebrugge, demonstrated the value of an objective record of door state. The post-Estonia 1996 Stockholm Agreement and the subsequent 2003 SOLAS amendments tightened bow-visor and ro-ro door integrity requirements, and the VDR’s hull-opening capture allows investigators to confirm objectively whether door state was correct at the moment of casualty.

Captured data 14: acceleration + hull stresses

The acceleration and hull stresses channel is captured where fitted: it is mandatory only on vessels fitted with a hull-stress monitoring system or accelerometer array, which is increasingly common on container ships (where stack-acceleration limits drive the lashing design and parametric-rolling alarms have entered the bridge alarm panel since the 2008 IMO Guidance on parametric rolling), on bulk carriers (where hull-stress monitors track the vertical wave-bending moment and alert the master to dangerous stress concentrations), on gas carriers (where cargo-tank stress monitoring is integrated with the IGC Code safety case), and on large passenger ships (where motion data informs passenger-comfort management). The data captured includes triaxial acceleration at the bridge or at the centre-of-gravity, longitudinal hull-bending moment, vertical wave-bending moment where measured, and the alarm thresholds set by the master or by the class-approved loading manual.

Captured data 15: wind speed + direction

The wind speed and direction capture is from the ship’s anemometer, fed via NMEA MWV (wind speed and angle) sentence. Both the apparent wind (relative to the ship) and the true wind (corrected for the ship’s velocity) are recorded. Wind data is forensically valuable in mooring-failure casualties (where wind force during port stay or during pilotage exceeded the bollard-pull capacity of the deployed lines), in heavy-weather management casualties (where heavy weather and wind force exceeded the operational envelope chosen by the master), and in manoeuvring casualties in confined waters where wind-induced drift contributed to a near-miss or contact.

Recording duration: 12 hours rolling + 30 days extended

The recording duration combines two storage tiers introduced by MSC.333(90):

\text{Recording duration: 12 hours rolling capsule + 30 days extended dataset}

The 12-hour rolling capsule is the high-resolution recording that fills the FFC and fixed capsule. As the recording reaches the 12-hour limit, the oldest data is overwritten in a continuous loop, ensuring that the most recent 12 hours is always available for casualty extraction. This duration was set to cover the typical pre-casualty window where the relevant decisions and events occur (a grounding investigation typically requires the last 4 to 8 hours of bridge audio and navigation data; a collision investigation typically requires the last 1 to 4 hours).

The 30-day extended dataset is held on an internal hard drive within the VDR head unit (not in the FFC or fixed capsule). This longer-duration record stores the data at a lower bit-rate and lower sample resolution but covers the full preceding 30 days, supporting investigations where the casualty has roots beyond the 12-hour rolling window (for example, a fatigue-related casualty where the master’s rest-hour pattern over the preceding weeks is relevant, or a mechanical failure where the alarm history over several days indicates a developing problem). The 30-day requirement was introduced by MSC.333(90) and is mandatory on VDRs fitted on or after 1 July 2014.

Dual storage: Float-Free Capsule + Fixed + long-term drive

The MSC.333(90) standard requires a dual-storage architecture combining three storage elements:

Float-Free Capsule (FFC): an orange aircraft-style capsule mounted on a hydrostatic-release frame on the upper deck. On submersion below the activation depth (typically 1 to 4 m), the hydrostatic release frees the capsule, which floats to the surface and activates an EPIRB-like locator beacon and the 37.5 kHz acoustic pinger. The FFC is the primary recovery target after a sinking casualty.
Fixed (or sealed) capsule: a protected capsule mounted in a position that allows recovery without diving, typically on the wheelhouse roof or on a deck-edge bracket. The fixed capsule survives fire, flooding, mechanical impact and the casualty environment, but is recovered manually (not floated free); it is the primary recovery target in casualties where the ship remains afloat or aground (allowing salvors or investigators to access the wheelhouse area).
Long-term storage drive: typically an internal hard drive or solid-state drive within the VDR head unit, holding the 30-day extended dataset at lower resolution. The long-term drive is not protected to the same survival envelope as the capsules and is recovered from the wreck by salvors when the wreck is accessible.

Investigators target whichever storage element is recoverable. In the Costa Concordia casualty of 13 January 2012, the ship grounded and partially capsized but remained accessible, so the fixed capsule and long-term drive were recovered immediately. In the Sewol casualty of 16 April 2014, the ship sank in 36 m of water, and salvors recovered the fixed capsule from the wreck during the underwater investigation. In the MV Stellar Daisy casualty of 31 March 2017, the ship sank in 3,461 m of water in the South Atlantic, and the FFC was located via the 37.5 kHz pinger but the recovery operation was complex; the FFC was retrieved and the data extracted.

FFC requirements: 6-month battery + 37.5 kHz pinger

The Float-Free Capsule technical requirements under MSC.333(90), aligned with IEC 61996-1, are:

T_{\text{battery}} \geq 6 \text{ months}

f_{\text{pinger}} = 37.5 \text{ kHz}

The 6-month battery life powers the EPIRB-style locator beacon (transmitting on the 406 MHz Cospas-Sarsat distress frequency for satellite location) and the 37.5 kHz acoustic pinger for sonar-based location by surface salvage vessels. The pinger frequency of 37.5 kHz aligns with the ICAO aircraft-cockpit-recorder pinger frequency, allowing the same sonar-search equipment to locate both maritime VDR FFCs and aircraft black boxes after a casualty, and supporting common training for sonar-search operators across the maritime and aviation casualty-investigation communities.

The battery chemistry is typically lithium-thionyl-chloride or lithium-manganese-dioxide, chosen for the long shelf life and low self-discharge required to maintain the 6-month operational envelope after a sudden casualty. The battery is non-replaceable in service: at the 5-year overhaul the entire FFC is returned to the manufacturer for battery replacement, capsule recertification and pinger transducer test.

FFC environmental: 6,000m depth + 1,100 degrees C fire 1 hour

The FFC environmental survival envelope under MSC.333(90) and IEC 61996-1 is:

d_{\text{depth survival}} = 6{,}000 \text{ m}

T_{\text{fire survival}} = 1100°C \text{ for 1 hour}

The 6,000 m depth survival specification covers the deep-ocean abyssal-plain environment where most large-merchant-vessel sinkings occur. The MV Stellar Daisy casualty at 3,461 m and the MV Cemfjord casualty (capsize and sinking 2 January 2015 in the Pentland Firth) both occurred well within the FFC depth envelope. The pressure hull of the FFC is hydrostatically tested to the 6,000 m equivalent (60 MPa or approximately 600 bar) during type-approval testing; in-service capsules are not pressure-tested but are subject to visual inspection at each annual performance test for damage to the hull, the locator-beacon antenna, and the pinger transducer.

The 1,100 degrees C fire-survival specification covers a one-hour exposure to flame at this temperature, simulating the engine-room or accommodation fire environment that may precede a sinking casualty. A secondary specification covers a longer-duration low-temperature exposure (typically 260 degrees C for 10 hours) representing the smouldering post-fire wreck environment. Together these specifications ensure the data inside the FFC remains readable after both the high-intensity active fire and the long-duration smouldering aftermath. The FFC also meets cold-temperature survival to minus 55 degrees C for use in polar trades under the Polar Code, and it survives mechanical impact to a specified energy level simulating debris impact during a sinking casualty.

Major manufacturers: Furuno, Kongsberg, JRC, Danelec, Rutter, Hi-Sea, Headway

The VDR manufacturer market is dominated by a small group of established marine-electronics companies, each with a portfolio of type-approved VDR and S-VDR products:

Furuno Electric Co. Ltd. (Japan): a global leader in commercial-marine electronics, with VDR products in the VR-3000 / VR-7000 series, type-approved by JG (Japan Class), DNV, LR, ABS, BV, NK, RINA, KR and others.
Kongsberg Maritime (Norway): the K-Bridge VDR product is integrated with the K-Bridge integrated bridge system and is widely fitted on Norwegian-flagged tonnage and on offshore vessels.
Japan Radio Co. Ltd. (JRC, Japan): the JCY-1900 and JCY-1850 product families, with broad type-approval coverage.
Danelec Marine (Denmark): the DM100 / DM200 product range, marketed strongly in northern European and Mediterranean fleets, with focus on remote-data-extraction and cyber-resilient architectures.
Rutter Technologies (Canada): VDR and integrated radar-VDR products, with strength in the offshore and ice-class market.
Hi-Sea (Korea): serving the Korean shipbuilding cluster (Hyundai Heavy Industries, Daewoo Shipbuilding and Marine Engineering, Samsung Heavy Industries) and Korean-flagged tonnage.
Headway Technology (China): serving Chinese shipbuilding (CSIC, CSSC) and Chinese-flagged tonnage, with type-approval through CCS and progressively expanding into other classification societies.

Other manufacturers serving regional markets include L3Harris Maritime, Consilium, Sperry Marine (Northrop Grumman), and AMI Marine. The competitive market means typical lead time for a new VDR installation is 8 to 16 weeks from order to commissioning, with most manufacturers offering global service-network coverage for the annual performance test.

Typical models: Furuno VR-7000, Kongsberg K-Bridge VDR, JRC JCY-1900, Danelec DM100

The typical contemporary models representing the current VDR generation include:

Furuno VR-7000: type-approved to MSC.333(90) and IEC 61996-1, with FFC, fixed capsule, and 30-day long-term drive. The VR-7000 supports up to 8 audio channels, dual-radar capture, ECDIS data interface, 64 alarm-channel inputs, and IP-network data export for remote diagnostics.
Kongsberg K-Bridge VDR: integrated with the K-Bridge integrated bridge system, MSC.333(90)-compliant, with 12 audio channels, dual-radar capture, and integration with the K-Bridge alarm-management system. Strong fit on Norwegian-flagged offshore vessels and OSVs.
JRC JCY-1900: MSC.333(90)-compliant, 8 audio channels, dual-radar capture, NMEA 0183 and IEC 61162-2 (Ethernet) interfaces. Widely fitted on Japanese-built tanker, bulker and container tonnage.
Danelec DM100: MSC.333(90)-compliant, with strong remote-data-extraction architecture and cyber-resilient design, including signed data archives and authenticated playback. The DM100 is increasingly specified by operators with strong cyber-security posture (cruise lines, large tanker operators, LNG carriers).

Each manufacturer issues type-approval certificates from the relevant classification society and lists conformance with the IMO performance standards (MSC.333(90), MSC.214(81) or A.861(20) depending on the build year of the equipment). The VDR is one of the most heavily standardised pieces of marine electronics, and the inter-operability of playback-data exchange across manufacturers is supported by the VDR Replay standard format defined in IEC 61996-1 Annex F.

Typical cost: USD 30,000-80,000 installed

The typical installed cost of a new full VDR is in the range USD 30,000 to 80,000, with the spread reflecting the choice of manufacturer, the audio-channel count, the inclusion of advanced cyber-resilient or remote-data-extraction features, the radar-data-capture configuration (single or dual radar), the alarm-channel count, the labour cost of installation in the building yard or in retrofit at a repair yard, and the type-approval certificate package required by the flag State or operator. The S-VDR is typically 30 to 50 per cent less than the equivalent full VDR, reflecting the reduced data-channel count and the simpler installation envelope.

The operating cost consists of the annual performance test by an approved service technician (typically USD 1,500 to 3,000 per visit, including travel and consumables), the 5-year overhaul with FFC battery replacement and capsule recertification (typically USD 5,000 to 12,000), and the consumables (no significant consumables in normal operation; the FFC battery is non-replaceable in service and is replaced at the 5-year overhaul). Over a 25-year ship life the total VDR lifecycle cost is therefore typically USD 70,000 to USD 150,000, dominated by the initial installation cost and the 5-year overhauls.

5-year overhaul + Annual Performance Test (APT)

The VDR maintenance regime under MSC.333(90), IACS UR M51 and the various flag-State implementing regulations rests on two recurring intervals:

T_{\text{APT cycle}} = 12 \text{ months}

T_{\text{overhaul cycle}} = 5 \text{ years}

The Annual Performance Test (APT) is conducted at intervals not exceeding 12 months by an approved service technician working for a manufacturer-authorised service centre. The APT verifies that each of the 15 data channels is recording correctly, that the audio capture is intelligible on each microphone, that the FFC hydrostatic release activates correctly, that the 37.5 kHz pinger is transmitting at the specified output level, that the locator beacon is functioning, that the long-term storage drive is healthy, and that the playback toolchain can extract the data. The APT generates a performance certificate which must be present on board and is checked at PSC inspection.

The 5-year overhaul is more invasive: the FFC is removed and returned to the manufacturer for battery replacement (the lithium battery is non-replaceable in service and reaches end of useful life at approximately the 5-year mark), pinger transducer test and recertification, hydrostatic release frame test, and capsule recertification. The 5-year overhaul also typically includes a software update where the manufacturer has issued firmware patches addressing identified issues or cyber-resilience improvements. The 5-year cycle is aligned with the typical SOLAS Cargo Ship Safety Equipment Certificate renewal interval, allowing the overhaul to be scheduled alongside the renewal survey.

Playback systems: VDR-Replay, JRC Voyage Replay

The playback toolchain is the software environment in which casualty investigators replay the recorded data. Each manufacturer provides a proprietary playback application: VDR-Replay (Danelec, Furuno-compatible), JRC Voyage Replay, Kongsberg K-Bridge Replay, and others. The IEC 61996-1 Annex F specification defines a standardised data-export format that allows cross-manufacturer playback for casualty investigation, so that an investigator with one manufacturer’s playback tool can read data from a different manufacturer’s VDR.

The playback environment provides synchronised display of the bridge audio, VHF audio, radar image, ECDIS image, and the navigational data (position, speed, heading, depth, alarms) on a single timeline. The investigator can scrub through the timeline, slow down or speed up the playback, focus on a particular audio channel, and extract still frames or audio segments for use in the investigation report. The playback also supports alarm-cascade analysis and target-track reconstruction for collision investigation.

Data extraction within 24 hours of incident

The data-extraction protocol under the IMO Guidelines on Voyage Data Recorder Ownership and Recovery (MSC.1/Circ.1024 and successor circulars) requires the operator to extract a forensic copy of the VDR data within 24 hours of the incident and preserve the original data unchanged. The operator’s responsibility is to:

Stop the ship’s normal operating cycle to prevent the incident-window data from being overwritten by the rolling-recording loop. In practice this means powering down the VDR or invoking the VDR’s “incident-save” function within the first 4 to 8 hours of the casualty.
Within 24 hours, contract an approved data-extraction service (manufacturer service centre or approved third-party investigator) to extract a forensic copy with chain-of-custody documentation.
Preserve the FFC, the fixed capsule and the long-term storage drive in their as-recovered state pending the flag-State or coastal-State investigation.
Provide the data to the flag-State investigation team, the coastal-State investigation team if the casualty occurred in coastal waters, the classification society if classification certificates are at issue, and, where applicable, the insurance interests.

The 24-hour window is critical because the rolling 12-hour recording cycle would overwrite the incident data within half a day if the VDR continued running. The MSC.333(90) standard requires the VDR to provide a prominent incident-save button on the bridge that, when pressed, locks the most recent recording window in non-volatile storage and prevents overwrite.

IMO Casualty Investigation Code MSC.255(84) primary evidence

IMO Resolution MSC.255(84), the Code of the International Standards and Recommended Practices for a Safety Investigation into a Marine Casualty or Marine Incident (the Casualty Investigation Code), entered force on 1 January 2010 and is mandatory under SOLAS Regulation XI-1/6. The Code establishes the obligation on flag States to investigate “very serious marine casualties” (loss of ship, loss of life, severe pollution) and provides a recommended framework for less serious casualties. The Code identifies the VDR data as the primary technical evidence in a marine casualty investigation, alongside witness testimony, radar-track records from VTS authorities, AIS-track records from terrestrial and satellite AIS, and physical examination of the wreck or damaged vessel.

Flag States that are party to SOLAS are required to give the Casualty Investigation Code effect through national legislation. The investigation team is empowered to demand production of the VDR data, to interview crew members, to inspect the vessel and its equipment, and to publish a final investigation report subject to confidentiality protections for individual contributors. The flag State’s investigation report is uploaded to the IMO GISIS Marine Casualties and Incidents module, where it joins the global casualty database used for trend analysis and for guiding future regulatory amendments through MSC.

Costa Concordia 2012, Sewol 2014, Stellar Daisy 2017 case impact

Three casualties illustrate the varying outcomes of VDR data recovery and use:

Costa Concordia (13 January 2012): the cruise ship grounded on rocks off Isola del Giglio in Tuscany after an unauthorised “salute” manoeuvre by the master, killing 32 people. The VDR was recovered intact within 24 hours of the casualty by Italian salvors accessing the partially capsized but accessible wreck. The bridge audio captured the master’s discussion with subordinates and his telephone call after the grounding; the radar data captured the ship’s track close to shore; the ECDIS data captured the route plan modification that led the ship away from the safe deepwater track. The Italian Ministry of Infrastructure and Transport investigation report relied substantially on the VDR data, and the master, Francesco Schettino, was convicted of multiple charges including manslaughter in 2015 with a 16-year sentence; the VDR audio was a central piece of evidence at trial.

Sewol (16 April 2014): the South Korean ferry sank in the Yellow Sea, killing 304 people, the majority of them schoolchildren on a class trip. The VDR was recovered from the sunken wreck during the salvage operation. The bridge audio captured the third officer’s helm orders during the manoeuvre that initiated the capsize, the master’s delayed decision to issue evacuation orders, and the cargo-shift sequence as the ship lost stability. The Korean Maritime Safety Tribunal investigation and the subsequent criminal trial of the master and crew used the VDR data extensively; the master was convicted of murder by gross negligence and sentenced to life imprisonment in 2015.

MV Stellar Daisy (31 March 2017): the very large ore carrier sank in the South Atlantic en route from Brazil to China, with 22 of 24 crew lost and only two survivors. The wreck site is in 3,461 m of water. A search by the underwater-recovery vessel Seabed Constructor in 2019 located the wreck and recovered the VDR FFC. Data extraction was achieved despite the long subsea immersion. The Marshall Islands flag-State investigation, supplemented by the South Korean Maritime Safety Tribunal, used the recovered data in the casualty reconstruction, identifying structural failure in the cargo hold area as the proximate cause and connecting the failure to the conversion history of the vessel from VLCC tanker to ore carrier.

These three cases illustrate the spectrum: in Costa Concordia the FFC was easily recovered because the wreck remained accessible; in Sewol the FFC was recovered after a complex but ultimately successful salvage operation; in Stellar Daisy the FFC required deep-ocean ROV recovery but the data was eventually retrieved and used. The lesson is that the FFC depth and battery specifications, while demanding, do enable casualty data recovery in scenarios that would have been opaque to investigators in the pre-VDR era.

2024 VDR cyber-resilience submissions

The 2024 IMO submissions addressing VDR cyber-resilience were prompted by a series of ransomware attacks against shipping operators in the early 2020s, including the 2017 NotPetya attack on Maersk (which while not directly targeting VDRs raised industry concern about shipboard-electronics cyber-vulnerability), the 2020 ransomware attack on the United Nations International Maritime Organization itself, and the 2023 ransomware attack on DNV’s ShipManager fleet-management platform. The submissions to the IMO MSC and the IMO PPR Sub-Committee in 2024 included:

Proposals to mandate signed data archives in the long-term storage drive and in the playback export format, so that any tampering with the data after recording would be cryptographically detectable.
Proposals to mandate network segregation between the VDR head unit and the broader shipboard IT network, so that a ransomware attack on the IT network cannot reach the VDR or compromise its data integrity.
Proposals to mandate firmware-update authentication so that the firmware-update mechanism cannot be exploited by an attacker to install malicious firmware that would falsify or destroy the recorded data.
Proposals to extend the APT scope to include verification of the cyber-resilience features (firmware-signature verification, network-segregation tests, data-integrity verification).

These submissions are progressing through MSC and HTW Sub-Committee work programmes, with adoption expected through 2025-2026 and entry into force in the latter half of the 2020s. The cyber-resilience workstream complements the broader IMO Maritime Cyber Risk Management framework set out in Resolution MSC.428(98) and the ISM Code compliance obligations placed on operators since 1 January 2021.

Relationship to ECDIS + radar + AIS integration

The VDR sits at the convergence of the integrated bridge system electronics, capturing data from each of the principal navigation electronics streams. Its interface relationships are:

AIS and ECDIS: the VDR captures the ECDIS chart, route plan, and alarm state via the IEC 61162 serial link from the ECDIS, and captures the AIS-derived target picture either directly from the AIS transponder or indirectly via the ECDIS overlay. The VDR also captures the AIS message stream itself in some configurations, including the static and voyage data of nearby vessels at the time of casualty.
Radar: the VDR captures the radar image as a time-stamped screen image, including the ARPA-acquired targets with their course-and-speed vectors and any trial-manoeuvre overlays.
GNSS: the VDR captures the position, speed-over-ground, fix-quality flag, and HDOP from the primary GNSS receiver, with secondary GNSS recording where dual-receiver configuration is fitted.
Gyrocompass and magnetic compass: heading from both sources, allowing comparison and identification of gyro drift.
Speed log: speed through water, complementing the speed-over-ground from GNSS.
Echo sounder: under-keel depth.
Anemometer: wind speed and direction.
Engine telegraph and rudder feedback: order and response from the propulsion and steering chains.
Alarm panel: the consolidated alarm state from the integrated alarm-management system.
VHF radio: audio capture from all VHF channels in use.
Bridge audio: the multi-microphone capture of the wheelhouse, bridge wings, and chart room.

The IEC 61996-1 standard specifies the interface formats for each input, with the IEC 61162-1 (NMEA 0183), IEC 61162-2 (high-speed NMEA), and IEC 61162-450 (lightweight Ethernet networks) supporting the data interchange. Modern VDRs increasingly use the IEC 61162-450 Ethernet interface for the high-bandwidth radar and ECDIS image capture, with the IEC 61162-1 serial interface retained for the lower-rate sensor data.

IACS UR M51 + PR16 + class society type-approval

The IACS Unified Requirement M51 (Voyage Data Recorders) and the IACS Procedural Requirement PR16 (Type Approval of Equipment) define the classification society implementation of the VDR regime. UR M51 prescribes the survey, installation and in-service maintenance requirements for VDRs on classed vessels, including:

Acceptance of the type-approval certificate issued by the manufacturer’s selected classification society as the basis for approval on a given installation.
Verification at initial survey that the installation matches the type-approved configuration and that the FFC and fixed capsule are mounted in the specified locations with the specified hydrostatic release.
Verification at annual survey that the APT certificate is current and that the VDR is recording the 15 mandatory channels.
Verification at renewal survey (typically every 5 years) that the 5-year overhaul has been completed and that the FFC battery and pinger have been recertified.
Investigation of any defect identified during operation: a VDR fault that prevents recording on one or more channels triggers a class condition requiring rectification within a specified time window.

PR16 sets out the type-approval procedure: a manufacturer submits the VDR design to a classification society, which reviews documentation, witnesses the type tests in a recognised laboratory (covering the 15 data channels, the FFC environmental tests, the EMC tests, and the APT-procedure verification), and issues a type-approval certificate listing the approved model, the performance standards met, and any conditions of approval.

DNV, LR, ABS, BV, NK, RINA, KR, CCS, RS, IRS approval

The principal classification societies issuing VDR type-approval certificates are the IACS member societies:

DNV (Norway): the largest issuer of VDR type-approvals, covering all major manufacturers and many smaller regional players.
Lloyd’s Register (LR, UK): strong in the UK-flagged fleet and in the Hellenic-flag market.
American Bureau of Shipping (ABS, USA): covering US-flagged tonnage and a significant share of the international tanker fleet.
Bureau Veritas (BV, France): covering French-flagged tonnage and a significant share of the cruise and chemical-tanker market.
ClassNK (NK, Japan): covering Japanese-flagged tonnage and Japan-built export tonnage.
RINA (Italy): covering Italian-flagged tonnage and a significant Mediterranean cruise-ship share.
Korean Register (KR, Korea): covering Korean-flagged tonnage and Korean-built export tonnage.
China Classification Society (CCS, China): covering Chinese-flagged tonnage and Chinese-built export tonnage.
Russian Maritime Register of Shipping (RS, Russia): covering Russian-flagged tonnage.
Indian Register of Shipping (IRS, India): covering Indian-flagged tonnage and Indian-built export tonnage.

The IACS harmonisation through UR M51 and PR16 ensures that a type-approval issued by one IACS member is recognised by the other members, supporting cross-flag installation of any approved VDR. Non-IACS classification societies issue their own type-approvals, which are accepted by the flag States that recognise those societies but not necessarily by IACS-member-led flag administrations.

PSC inspection: functionality + 12-month APT certificate

Port State Control inspectors include the VDR in their list of items checked during routine and detailed inspections. The standard PSC checks are:

Carriage: confirm that a VDR or S-VDR is fitted in accordance with the SOLAS V/20 carriage threshold for the ship’s type, size and date of build.
Type-approval: confirm that the equipment is type-approved by an IACS member society (or an other classification society recognised by the flag State) and that the type-approval certificate is on board.
APT certificate: confirm that the 12-month Annual Performance Test certificate is current and on board, and that no APT deficiencies remain unresolved.
5-year overhaul: confirm that the 5-year overhaul has been completed within the required interval.
Functionality test: in detailed inspections the PSC inspector may witness a basic functionality demonstration, including verification that the VDR is recording, that the bridge-audio capture is intelligible, and that the incident-save button on the bridge is functional.
Documentation: confirm that the playback toolchain is available on board for use in extraction after a casualty.

Common PSC deficiencies recorded under SOLAS V/20 include APT certificate overdue, FFC battery overdue for 5-year replacement, microphone(s) unserviceable preventing complete bridge-audio capture, GPS or speed-log feed missing from the VDR, ECDIS data feed not interfaced, and radar-image capture inoperative. Severe deficiencies (multiple-channel failure, FFC inoperative, APT certificate missing or out of date by more than 3 months) can lead to detention. The Paris MOU and Tokyo MOU annual reports document SOLAS V/20 deficiencies as a recurring inspection finding, with the deficiency rate trending downward over time as the regime matures and as APT and overhaul disciplines stabilise across the fleet.

Formula, assumptions, and limits

This section is mandatory for every wiki article and provides the regulatory and quantitative anchor for the topic.

Formula

The VDR regulatory and operational envelope is anchored by a small number of explicit numerical specifications under MSC.333(90) and IEC 61996-1:

\text{Recording duration: 12 hours rolling capsule + 30 days extended dataset}

T_{\text{battery}} \geq 6 \text{ months}

f_{\text{pinger}} = 37.5 \text{ kHz}

d_{\text{depth survival}} = 6{,}000 \text{ m}

T_{\text{fire survival}} = 1100°C \text{ for 1 hour}

T_{\text{APT cycle}} = 12 \text{ months}

T_{\text{overhaul cycle}} = 5 \text{ years}

The carriage thresholds are encoded as:

\text{Full VDR: Passenger ships of any size + Cargo} \geq 3{,}000 \text{ GT (built on or after 1 July 2002)}

\text{S-VDR: Cargo ships } 150 \leq \text{GT} < 3{,}000 \text{ (built before 1 July 2002, retrofit by 1 July 2010)}

The incident-save data window is the 12-hour rolling-recording duration that is locked at the moment the incident-save button is pressed; the operator must extract a forensic copy within 24 hours to prevent loss through the rolling-overwrite cycle, recognising that the rolling cycle would otherwise complete one overwrite per 12 hours of continued operation.

Derivation

The 12-hour rolling-recording duration was set by A.861(20) in 1997 and retained through MSC.214(81) and MSC.333(90) on the basis of the empirical observation that the relevant pre-casualty bridge events (the last meeting agreement before a collision, the last helm order before a grounding, the last alarm acknowledgement before a propulsion failure) occur within the last 4 to 8 hours of operation in the great majority of casualties; a 12-hour window provides a comfortable forensic margin without requiring excessive storage capacity in the protected capsule.

The 30-day extended dataset introduced by MSC.333(90) addresses the residual case where the casualty has roots beyond the 12-hour window (fatigue-related casualties, slowly-developing mechanical failures, accumulated alarm-suppression bad practice) and where the long-term record on the unprotected internal hard drive supplements the protected 12-hour recording.

The 6-month FFC battery life was raised from the original 30-day specification of A.861(20) to 6 months by MSC.214(81) in 2006 in response to the deep-water-recovery time-frames observed in casualties; the MV Derbyshire loss of 1980, the MV Munchen loss of 1978 and other deep-water losses had typically taken several months to locate even where the wreck was eventually found, and the 30-day battery was insufficient. The 6-month envelope covers the typical deep-water-recovery operational planning window.

The 37.5 kHz pinger frequency is the harmonised maritime and aviation casualty-recorder pinger frequency, allowing common sonar-search infrastructure to locate both maritime VDR FFCs and aircraft black boxes.

The 6,000 m depth-survival specification covers the deep-ocean abyssal-plain environment (the ocean basins typically lie between 3,000 and 6,000 m depth) where most large-merchant-vessel sinkings occur. The 1,100 degrees C fire-survival specification was set by reference to the fire-environment temperature measured in engine-room and accommodation fires on commercial vessels; the 1-hour duration covers the active-flame phase of the casualty before the wreck transitions to the smouldering phase covered by the secondary 260 degrees C 10-hour specification.

Assumptions

The VDR or S-VDR carried on board meets the performance standard applicable at its date of fitment (A.861(20), MSC.214(81), or MSC.333(90)) and the corresponding IEC 61996-1 or 61996-2 testing standard.
The type-approval certificate issued by an IACS member society (or by another society recognised by the flag State) is valid and on board, and the equipment installation matches the type-approved configuration.
The Annual Performance Test has been conducted within the preceding 12 months by an approved service technician, and the APT certificate is on board with no unresolved deficiencies.
The 5-year overhaul has been completed within the preceding 5 years, with FFC battery replacement and capsule recertification.
The VDR is continuously powered while the ship is at sea, with the back-up battery covering at least 2 hours of post-power-loss operation.
The bridge-audio microphones are positioned to capture all bridge conversations, and crew are trained not to obstruct or interfere with the capture.
The incident-save button on the bridge is identified and accessible, and the master and officers are trained to press it within the first hours of any significant incident.
The data-extraction protocol is in the operator’s emergency-response plan, with the contact details of the approved data-extraction service identified.

Worked example

A 5,000-DWT general cargo ship built in 2018 trades internationally and is therefore subject to the full VDR carriage requirement (cargo ships of 3,000 GT and above built on or after 1 July 2002). The owner specifies a Furuno VR-7000 at new-build, type-approved by NK and DNV, supplied with FFC, fixed capsule and 30-day long-term drive. Initial cost: USD 55,000 installed.

Year 1 to Year 5: APT in months 12, 24, 36, 48 (cost approximately USD 2,500 per APT). Total 5-year APT cost: USD 10,000.
Year 5: 5-year overhaul, FFC battery replacement, capsule recertification (cost approximately USD 8,000) plus the regular APT (usually combined with the overhaul service visit).
Year 6 to Year 10: APT annually (4 APT visits) plus 5-year overhaul at year 10.
Year 25 (typical demolition age): cumulative VDR cost approximately USD 55,000 (initial) + USD 60,000 (24 APTs) + USD 32,000 (4 overhauls) = USD 147,000.

The investment is justified by the SOLAS V/20 mandatory carriage requirement; the operational benefit, in the rare casualty scenario, is the availability of objective data supporting the operator’s defence against allegations of negligence and the regulatory investigation. In casualty-free operation the VDR is a continuous operating expense without direct revenue benefit, but the regulatory mandate, the insurance interest, and the casualty-rare-but-high-consequence calculus drive universal compliance.

Edge cases and limits

VDR fitted to A.861(20) on 2003 build, retrofit not mandatory: an older VDR fitted to the original 1997 performance standard remains compliant indefinitely; retrofit to MSC.333(90) is not required by SOLAS unless the operator elects to upgrade or the equipment is replaced after major repair.
S-VDR retrofit deferred for ships in coastal-only trade: a flag State may exempt a ship engaged solely on domestic voyages within the territorial sea from the SOLAS V/20 carriage requirement. The exemption is reported to IMO and is subject to flag-State discretion; the ship remains exposed to PSC scrutiny if it strays into international voyages.
FFC battery overdue but APT current: a VDR where the FFC battery is overdue for 5-year replacement but the APT is current is a recurring PSC finding; the deficiency is typically classified as “rectify before next port” rather than detention, but operator delay can escalate to detention if not resolved.
Bridge microphone obstructed or muted: any deliberate or negligent suppression of bridge-audio capture is a serious PSC finding and may also be a criminal offence under flag-State legislation if the suppression is found to have occurred during a casualty period, on the same theory that obstruction of casualty evidence is criminally punishable.
VDR inoperative at sea: SOLAS V/20 does not, in itself, require return to port if the VDR fails at sea. However, the ISM Code SMS will typically require the operator to record the failure, plan the repair, and proceed with caution; PSC at the next port will check that the failure was logged and that repair was scheduled.
Cyber-attack on VDR: a successful cyber-attack that compromises the data integrity of the VDR is a serious incident; the Resolution MSC.428(98) cyber-risk-management framework requires the operator’s SMS to include cyber-resilience measures, and the 2024 IMO submissions are progressing toward mandatory cyber-resilience features in the VDR itself.
Polar trading: a vessel entering the Polar Code area must operate the VDR through the cold-temperature envelope; the FFC environmental specification covers polar operation but the wider VDR head unit must also be specified for the cold-temperature operating range.
Capsule recovery beyond 6 months: a sinking casualty where the FFC is not located within 6 months may yield an FFC with depleted battery, no longer transmitting on the locator beacon or the 37.5 kHz pinger. The data within the FFC remains intact, but recovery requires bathymetric and side-scan-sonar mapping rather than acoustic homing.
S-VDR data limitations in collision investigation: the S-VDR does not capture engine and rudder order plus response feedback or the full main-alarm set. In collision investigation involving a vessel fitted with S-VDR rather than full VDR, the absence of these channels can complicate causal reconstruction.
Multi-VDR issues on vessel transfer: vessels changing flag mid-life may face issues where the existing VDR type-approval is not recognised by the new flag State or by the new classification society; in such cases a re-survey or replacement may be required.

Regulatory basis

SOLAS Chapter V Regulation 20 (Voyage Data Recorders), as amended.
IMO Resolution A.861(20) (1997) Performance standards for shipborne voyage data recorders.
IMO Resolution MSC.214(81) (2006) Adoption of amendments to the performance standards for shipborne VDR.
IMO Resolution MSC.333(90) (2012) Adoption of revised performance standards for shipborne VDR (current).
IMO Resolution A.694(17) (1991) General requirements for shipborne radio equipment forming part of GMDSS and for electronic navigational aids.
IMO Resolution MSC.255(84) (2008) Code of the international standards and recommended practices for a safety investigation into a marine casualty or marine incident (the Casualty Investigation Code), mandatory under SOLAS XI-1/6 from 1 January 2010.
IMO Resolution MSC.428(98) (2017) Maritime cyber risk management in safety management systems.
IMO MSC.1/Circ.1024 Guidelines on voyage data recorder ownership and recovery (and successor circulars).
IEC 61996-1 Maritime navigation and radiocommunication equipment - Shipborne VDR Part 1 (full VDR).
IEC 61996-2 Maritime navigation and radiocommunication equipment - Shipborne S-VDR Part 2.
IEC 61162 series (data interface standards for marine electronics, NMEA 0183 and lightweight Ethernet networks).
IACS Unified Requirement UR M51 Voyage Data Recorders, defining survey and maintenance requirements.
IACS Procedural Requirement PR16 Type approval of equipment.

Common errors

Treating S-VDR as a full VDR substitute: the S-VDR is the carriage requirement only for cargo ships of 150 to 3,000 GT built before 1 July 2002. Ships built on or after 1 July 2002 above 3,000 GT and all passenger ships require the full VDR. Substituting S-VDR for full VDR is non-compliance.
Confusing the FFC capsule with the fixed capsule: the FFC is the orange free-floating capsule with the pinger and locator beacon; the fixed capsule is the protected wheelhouse-mounted capsule. Both are required under MSC.333(90); fitting only one is non-compliance.
Assuming the long-term drive is protected to the same specification as the FFC: the 30-day extended dataset is held on an internal hard drive that is not protected to the FFC fire and depth specifications. After a sinking casualty, the long-term drive is recovered only when the wreck is accessible to salvors.
Treating APT as optional or deferrable: the 12-month APT cycle is mandatory; an APT certificate that is overdue by more than 3 months exposes the operator to PSC detention risk.
Assuming the 5-year overhaul can be deferred: the FFC battery has a finite life and the 5-year overhaul is the only opportunity to replace it. Deferral risks an FFC with depleted battery at the moment of casualty, frustrating the casualty-investigation purpose of the VDR.
Misunderstanding the incident-save function: the incident-save button locks the most recent recording window; failure to press it after a casualty (whether through ignorance, training failure, or deliberate concealment) can lead to overwrite of the casualty-window data within 12 hours.
Assuming bridge audio is admissible without further authentication: in some legal jurisdictions the bridge audio recording must be authenticated by the manufacturer or by an expert witness before admission as evidence at trial. Operators should plan for this in their post-casualty response.
Treating VDR data as the operator’s confidential property: VDR data is the casualty-investigation evidence required to be produced to the flag State, the coastal State and (where applicable) the classification society and insurance interests. Operator attempts to withhold or restrict access can lead to enforcement action.
Fitting an unapproved VDR: only equipment with a current type-approval certificate from an IACS member or a recognised classification society is acceptable. Unapproved equipment will fail PSC inspection and may invalidate the SOLAS certificate.
Assuming cyber-resilience is optional: the IMO MSC.428(98) cyber-risk-management framework places obligations on operators since 1 January 2021; the 2024 IMO submissions are extending those obligations into the VDR equipment itself.

References

The principal source for SOLAS V/20 carriage of VDR and S-VDR is the IMO consolidated text of the International Convention for the Safety of Life at Sea, 1974, as amended, available from the IMO publishing service and the IMO Knowledge Centre, with Regulation 20 of Chapter V supplying the carriage threshold for full VDR (passenger ships of any size and cargo ships of 3,000 GT and above built on or after 1 July 2002) and S-VDR (cargo ships of 150 to 3,000 GT built before 1 July 2002, retrofit complete by 1 July 2010). The performance-standard lineage is set out in three IMO instruments: IMO Assembly Resolution A.861(20) of 1997 (the original VDR performance standard), IMO Resolution MSC.214(81) of 2006 (the substantive revision raising the FFC battery to 6 months and tightening fire and audio capture), and IMO Resolution MSC.333(90) of 2012 (the current standard, adding the 30-day extended dataset and the cyber-resilience guidance). The horizontal performance standard for shipborne radio equipment and electronic navigational aids is IMO Assembly Resolution A.694(17) of 1991, supplying the environmental, EMC and mechanical baseline beneath the VDR-specific requirements. The casualty-investigation framework is supplied by IMO Resolution MSC.255(84), the Code of the International Standards and Recommended Practices for a Safety Investigation into a Marine Casualty or Marine Incident (the Casualty Investigation Code), mandatory under SOLAS XI-1/6 from 1 January 2010, with VDR data identified as the primary technical evidence in marine casualty investigation. The cyber-risk-management framework is supplied by IMO Resolution MSC.428(98) of 2017, requiring cyber-risk management to be addressed in safety management systems by the first DoC verification after 1 January 2021. The data-extraction and ownership protocol is supplied by IMO MSC.1/Circ.1024 Guidelines on Voyage Data Recorder Ownership and Recovery and successor circulars. The international electrotechnical testing and conformance standards are IEC 61996-1 for the full VDR and IEC 61996-2 for the S-VDR, with the data-interface family IEC 61162-1 (NMEA 0183 serial), IEC 61162-2 (high-speed serial) and IEC 61162-450 (lightweight Ethernet networks) supplying the sensor-data interchange envelope. The classification-society implementation is set out in IACS Unified Requirement UR M51 Voyage Data Recorders (survey and maintenance requirements) and IACS Procedural Requirement PR16 Type Approval of Equipment, with type-approval certificates issued by IACS member societies (DNV, Lloyd’s Register, ABS, Bureau Veritas, ClassNK, RINA, Korean Register, China Classification Society, Russian Maritime Register of Shipping and Indian Register of Shipping) covering the principal manufacturers (Furuno, Kongsberg, JRC, Danelec, Rutter Technologies, Hi-Sea, Headway and others). Port-State-control enforcement of SOLAS V/20 is operated through the Paris Memorandum of Understanding and the Tokyo Memorandum of Understanding secretariats, with annual deficiency reports providing the principal evidence base on VDR compliance in practice. The casualty record where VDR data was decisive includes the Costa Concordia investigation report of the Italian Ministry of Infrastructure and Transport (2013), the Sewol investigation of the Korean Maritime Safety Tribunal (2014-2015), and the Stellar Daisy investigation of the Marshall Islands flag-State authority and the Korean Maritime Safety Tribunal (2017-2019), each available through the respective national authority and aggregated in the IMO Global Integrated Shipping Information System (GISIS) Marine Casualties and Incidents module. The UK Marine Accident Investigation Branch (MAIB) and the equivalent flag-State investigation bodies (the Australian Transport Safety Bureau, the United States National Transportation Safety Board for US-flagged casualties, and the Norwegian Safety Investigation Authority) publish individual casualty reports relying on VDR data as primary technical evidence.