{"id":51611,"date":"2026-04-17T21:26:17","date_gmt":"2026-04-17T20:26:17","guid":{"rendered":"https:\/\/maritimehub.co.uk\/?p=51611"},"modified":"2026-04-17T21:26:17","modified_gmt":"2026-04-17T20:26:17","slug":"dangerous-goods-deck-stowage-basics","status":"publish","type":"post","link":"https:\/\/maritimehub.co.uk\/dangerous-goods-deck-stowage-basics\/","title":{"rendered":"Dangerous goods \u2013 deck stowage basics"},"content":{"rendered":"
\n

BRIDGE \u2192 Stability & Cargo<\/strong><\/p>\n

Position on the Bridge<\/strong><\/p>\n

System Group:<\/strong> Cargo Management \/ Dangerous Goods<\/p>\n

Primary Role:<\/strong> Safe acceptance, segregation, and stowage of IMDG-classified cargo aboard ship<\/p>\n

Interfaces:<\/strong> Cargo planner, chief officer, shore terminal, CSO, DG documentation chain, GMDSS emergency response library<\/p>\n

Operational Criticality:<\/strong> Absolute \u2013 a single stowage error with incompatible classes can produce a casualty that no amount of firefighting can reverse<\/p>\n

Failure Consequence:<\/strong> Undetected incompatibility leads to chemical reaction or fire; deck stowage errors deny access for suppression; misdeclared cargo means EmS guidance is wrong from the first minute<\/p>\n<\/div>\n

 <\/p>\n

<\/p>\n

The IMDG Code does not make dangerous cargo safe.<\/p>\n

It defines the minimum distance between what can kill you and everything else.<\/p>\n

<\/em><\/p>\n

Introduction<\/h2>\n

Every port in the world ships dangerous goods. Flammables, oxidisers, toxics, corrosives, radioactives \u2013 they move in containers and packaged form on virtually every general cargo and container vessel in service. The IMDG Code exists because without a common framework, the combination of cargo types, stowage positions, and documentation practices would be entirely arbitrary. That framework is now well-established. The problem is not its absence. The problem is the gap between formal compliance and operational reality.<\/p>\n

Deck stowage is where that gap shows most clearly. A container with a correct placard, a signed DGD, and a position on the stowage plan can still be in entirely the wrong place relative to what surrounds it. The officer who accepts the plan at face value, without understanding the segregation logic behind it, is operating blind. The IMO’s casualty record is not short of examples where the paperwork was correct and the ship still burned.<\/p>\n

This article addresses what the IMDG Code actually requires for deck stowage, why the structure of the code matters operationally rather than bureaucratically, and where the common errors concentrate. It is written for officers who already know what a UN number is and want to understand the reasoning, not the definitions.<\/p>\n

Contents<\/h2>\n
    \n
  • 1. The IMDG Code \u2013 structural logic<\/li>\n
  • 2. Classes and the problem of incompatibility<\/li>\n
  • 3. Stowage categories \u2013 what they actually mean at sea<\/li>\n
  • 4. Deck stowage versus under-deck stowage<\/li>\n
  • 5. Segregation in practice<\/li>\n
  • 6. The documentation chain<\/li>\n
  • 7. Emergency response \u2013 MFAG and EmS<\/li>\n
  • 8. Common stowage errors<\/li>\n
  • 9. Closing Reality<\/li>\n<\/ul>\n

    1. The IMDG Code \u2013 structural logic<\/h2>\n

    The IMDG Code is structured around four elements that have to work together: classification, packing, marking and labelling, and stowage and segregation. Most shore-side failures occur in the first two. Most shipboard failures occur in the last one. The Code’s two-volume structure divides between general provisions and the individual substance schedules, with the segregation tables and EmS guide sitting as distinct operational references within the package.<\/p>\n

    Amendment cycles matter. The Code is updated every two years. An amendment comes into force and ships operate with guidance that pre-dates it for years afterwards. The obligation falls on the ship’s operator to ensure the edition in use is current. Where a flag administration has enacted a specific amendment into domestic law, that version is mandatory \u2013 not the latest edition if the latest has not yet been given force.<\/p>\n

    The Dangerous Goods List in Volume 2 is not a catalogue. It is an operational document. Each entry gives the UN number, proper shipping name, class, subsidiary risk, packing group, stowage category, segregation group, and special provisions. Reading an entry correctly means understanding what each column demands of the stowage plan before the ship sails.<\/p>\n

    2. Classes and the problem of incompatibility<\/h2>\n

    The nine IMDG classes are well-known to any officer who has held a watchkeeping certificate. What is less well understood at the operational level is that the class label describes primary hazard only. A substance with a Class 3 label may carry a subsidiary risk of Class 6.1 toxicity or Class 8 corrosivity. The segregation obligation applies to both the primary class and the subsidiary risk. Treating only the primary label is one of the most common errors in stowage planning.<\/p>\n

    Subsidiary risks appear in the DGL entry and must appear on the DGD. If they do not appear on the DGD, the shipper’s declaration is deficient, and the deficiency is the carrier’s problem once the container is aboard.<\/p>\n

    Class 1 explosives and Class 5.1 oxidisers next to Class 3 flammable liquids is an obvious problem. Less obvious is Class 4.3 dangerous when wet materials that have been sheeted and appear dry, or Class 2.3 toxic gases in cylinders stowed on the weather deck in positions that concentrate any release towards accommodation ventilation intakes. These are not theoretical scenarios. They are recurring patterns in incident reports.<\/p>\n

    The class system describes hazard categories. It does not automatically resolve stowage decisions. That requires reading the segregation table.<\/em><\/p>\n

    3. Stowage categories \u2013 what they actually mean at sea<\/h2>\n

    The IMDG Code assigns each substance or article a stowage category from A through E. The categories define where the goods may be carried relative to the ship’s structure, not relative to other cargo.<\/p>\n

    Category A permits stowage anywhere \u2013 on or under deck. Category B is on deck or under deck with specific ventilation conditions. Category C is on deck only. Category D is on deck only, away from heat sources. Category E is on deck only in a closed freight container.<\/p>\n

    The practical consequence of Category C or E assignments is significant. These goods must be on deck. That is not a preference \u2013 it is a requirement driven by the nature of the hazard, typically flammability, reactivity with water, or the need for immediate jettison access. When a port planner moves a Category C unit below deck to solve a space problem, the entire basis for the stowage category has been undermined. This happens. It has consequences.<\/p>\n

    Stowage category compliance is not cargo planning convenience. It is the Code’s first line of defence against an uncontrollable casualty.<\/em><\/p>\n

    4. Deck stowage versus under-deck stowage<\/h2>\n

    The preference for deck stowage of many DG classes is not arbitrary. It reflects three operational realities: ventilation, access, and emergency response.<\/p>\n

    Ventilation under deck is mechanically dependent. If the source of ignition or reaction is the cargo itself, the same space contains both the hazard and the air supply. On deck, natural ventilation dilutes vapour release, reduces concentration, and buys time. For gases and flammable liquids with low flash points, that difference between deck and below-deck stowage can determine whether a crew has minutes or seconds before a space becomes untenable.<\/p>\n

    Access matters for two reasons. The first is monitoring. DG cargo on deck can be visually inspected during a watch. Leaking containers, deformation, fire, or unusual odours are detectable. Below deck, the same indicators may not be noticed until compartment temperatures have already elevated to dangerous levels. The second reason is firefighting. Deck stowage positions are reachable with boundary cooling and direct application. Under-deck DG fires frequently require fixed suppression systems whose effectiveness depends entirely on the accuracy of the cargo declaration \u2013 if the cargo is not what the DGD says it is, the suppression agent may be wrong.<\/p>\n

    There is a common misconception that deck stowage exposes DG cargo to weather damage and therefore increases risk. That is a shipper’s concern, not a safety concern. The Code’s stowage categories reflect hazard management, not cargo condition management. Both matter, but they are not the same calculation.<\/p>\n

    5. Segregation in practice<\/h2>\n

    The IMDG Code’s segregation table expresses the required separation between classes in four terms: away from, separated from, separated by a complete compartment or hold from, and separated longitudinally by an intervening complete compartment or hold from. Each term has specific physical meaning on a ship.<\/p>\n

    On deck, these terms translate to minimum distances and intervening structure. Away from means at least 3 metres horizontal separation on the same deck. Separated from means in different cargo spaces, or on deck with at least 6 metres horizontal separation in the fore-and-aft direction, or with a full deck between them. The more demanding categories require longitudinal separation that in practice can mean opposite ends of the ship.<\/p>\n

    Segregation from the ship’s structure matters independently of cargo segregation. Class 1 articles have specific requirements for separation from the vessel’s sides, funnel, heat sources, and accommodation. These are not replicated by simply separating from other DG classes. Both sets of requirements apply simultaneously.<\/p>\n

    In container ship operations, segregation is frequently managed by the terminal’s automated cargo planning system. The risk is that officers accept the terminal output without verifying it against the IMDG requirements independently. Automated systems have constraint sets. Those constraint sets have been incorrectly configured. The officer who signs the dangerous goods declaration accepting the stowage plan has accepted personal responsibility for what that plan contains.<\/p>\n

    The terminal planner’s system is not the authority. The IMDG Code is the authority.<\/em><\/p>\n

    6. The documentation chain<\/h2>\n

    Three documents form the core of the DG documentation chain: the shipper’s dangerous goods declaration, the container packing certificate where applicable, and the ship’s dangerous goods manifest or stowage plan. Each document has a defined responsibility. When the chain breaks, accountability becomes ambiguous and the operational information needed to respond to an emergency degrades.<\/p>\n

    The shipper’s declaration is the origin of all hazard information. It must include the correct UN number, proper shipping name, class, packing group, total quantity, and emergency contact. It must be signed. Where a subsidiary risk applies, it must appear. The carrier is not in a position to verify the chemistry of a misdeclared shipment at the berth. What the carrier can do is reject declarations that are incomplete, unsigned, or where the placard on the container does not correspond to the class declared. Incomplete declarations accepted under commercial pressure are a direct line to emergency situations where the crew is working with wrong information.<\/p>\n

    The dangerous goods manifest consolidates all DG units aboard into a single operational document. It must be held in a position accessible to the master and, critically, to shore-side responders. SOLAS requires a copy to be held ashore, typically with the ship’s agent. In an emergency, the manifest is what port fire services use to understand what they are dealing with. A manifest that does not reflect the actual cargo \u2013 because a last-minute amendment was not captured, because a container was substituted at the berth, or because stowage was changed without updating the plan \u2013 is an emergency response document that will cause harm.<\/p>\n

    The stowage plan must show DG positions accurately. Bay, row, tier. Class, UN number, stowage category. This is not administrative tidiness. It is the reference document by which an officer on watch who notices a problem locates the affected unit and identifies what they are dealing with.<\/p>\n

    7. Emergency response \u2013 MFAG and EmS<\/h2>\n

    The Emergency Response Procedures for Ships Carrying Dangerous Goods \u2013 the EmS Guide \u2013 and the Medical First Aid Guide for Use in Accidents Involving Dangerous Goods \u2013 MFAG \u2013 are not supplementary references. They are the primary operational response documents for DG casualties at sea. Both are held as part of the IMDG Code package and must be accessible to the officer of the watch, not archived in the master’s office.<\/p>\n

    The EmS guide contains two schedules for each substance: a fire schedule (F-designation) and a spillage schedule (S-designation). These are referenced from the DGL entry against each UN number. The fire schedule gives recommended firefighting media and specific warnings \u2013 for example, substances where water application accelerates reaction, or where toxic combustion products require full BA before any approach. The spillage schedule addresses containment, personnel protection, and initial action for a non-fire release.<\/p>\n

    The operational discipline required is straightforward: when a DG incident occurs, the first action after crew safety is to locate the manifest, identify the UN number, find the EmS entry, and follow it. The sequence breaks down when the manifest is inaccessible, when the EmS guide is a superseded edition, or when the substance on deck is not the substance declared. All three of these situations appear in incident investigations with regularity.<\/p>\n

    The MFAG links to the EmS through schedule numbers and gives medical treatment guidance for exposure casualties. Where a ship carries a Class 6.1 or Class 2.3 cargo and the medical officer is not a physician, the MFAG is the only clinical reference available. Its guidance is dependent on correct substance identification. A cargo misdeclared as a Class 3 material when it is actually toxic will produce entirely wrong first-aid treatment from the MFAG entry.<\/p>\n

    Emergency response at sea begins with documentation accuracy. If the paperwork is wrong, everything that follows is built on that error.<\/em><\/p>\n

    8. Common stowage errors<\/h2>\n

    The errors that recur across incident reports and port state control deficiency lists fall into recognisable patterns. None of them require unusual circumstances. They happen on ordinary voyages with experienced officers.<\/p>\n

    Failure to account for subsidiary risks is the single most frequent segregation error. The primary class is checked against the segregation table. The subsidiary risk is not. Two units that appear compatible by primary class are incompatible when the subsidiary risks are applied.<\/p>\n

    Stowage category violations under commercial pressure are common in short-sea trades where terminal throughput drives decisions. A Category C unit placed below deck to complete a load is not a minor paperwork irregularity. It has removed the unit from the position the Code requires.<\/p>\n

    Outdated documentation \u2013 specifically, using an IMDG amendment edition that has been superseded \u2013 produces stowage plans that comply with requirements that no longer apply. This is a flag state and operator responsibility, but it lands on the officer who signs the plan.<\/p>\n

    Proximity to heat sources is underappreciated. Engine room casing, exhaust uptakes, and areas of the deck that accumulate solar heat in tropical trades are relevant to the stowage of Class 4.1 and 4.3 materials. The Code’s separation requirements from heat sources are not always carried through into terminal planning systems with the same fidelity as class-to-class segregation.<\/p>\n

    Blocking access for emergency response is a stowage error that does not appear in the segregation tables but produces the same consequences as a segregation failure. A DG unit buried behind general cargo, or stowed in a position where fire hose access requires removing other containers first, has been placed in a position where its stowage category requirement \u2013 visible, accessible, capable of being jettisoned \u2013 has been satisfied on paper and defeated in practice.<\/p>\n

    Accepting a stowage plan without independent verification is arguably the most consequential error of all. It is not the terminal’s liability. It is the ship’s.<\/p>\n

    9. Closing Reality<\/h2>\n

    Deck stowage of dangerous goods is a system with two purposes that cannot be separated: keeping incompatible materials apart, and keeping hazardous materials accessible when something goes wrong. Segregation without access is incomplete. Access without correct documentation produces emergency response that works from wrong assumptions.<\/p>\n

    The IMDG Code provides the framework. The officer who understands the logic of that framework \u2013 not just the rule, but why the rule takes the form it does \u2013 is the one who catches the error the terminal system missed, who reads the subsidiary risk column, who checks the manifest against the actual stowage before signing. The officer who treats the Code as a compliance exercise is the one who discovers the gap between paperwork and reality at the worst possible moment.<\/p>\n

    Cargo that is correctly declared, correctly segregated, and correctly stowed on deck is cargo that can be responded to. Everything else is a liability waiting for a trigger.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

    Deck stowage of dangerous goods is not a checkbox exercise. Segregation, access, and documentation failures kill ships and crews.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"fifu_image_url":"","fifu_image_alt":"","c2c-post-author-ip":"2a02:c7c:2ef8:2400:931:afb1:9971:4a62","footnotes":""},"categories":[10,1],"tags":[9156,9160,9153,9159,9155,9157,9154,9158],"class_list":["post-51611","post","type-post","status-publish","format-standard","hentry","category-bridge","category-latest","tag-cargo-segregation","tag-container-stowage","tag-dangerous-goods","tag-dangerous-goods-documentation","tag-deck-stowage","tag-ems","tag-imdg-code","tag-mfag"],"acf":[],"_links":{"self":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fcomments&post=51611"}],"version-history":[{"count":1,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51611\/revisions"}],"predecessor-version":[{"id":51616,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51611\/revisions\/51616"}],"wp:attachment":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fmedia&parent=51611"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fcategories&post=51611"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Ftags&post=51611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}