This is the third post in the CanalClear Kiel Canal cluster. The first post — Kiel Canal Filing Requirements 2026 — covers the full ELWIS pre-notification stack, WSV traffic-group tables, and the dangerous-cargo declarations required for a NOK transit at the filing-layer level. The second post — Kiel Canal Transit Tolls and NOKBefAbgV Canal Dues 2026 — covers the LOA-based fee bands, the June 2026 §7 compulsory-pilot discount, and the WSV Webshop payment flow operators hit on transit settlement. Together they cover the filing stack and the cost stack; this third post closes the cluster with the operational layer that surfaces for any vessel carrying IMDG-class cargo on the NOK: §11 SeeSchStrO, the ELWIS pre-arrival DG submission, the WSV Verkehrsgruppen DG-class sequencing at the lock approach, and IMDG-class-specific stowage requirements specific to the 99 km canal stretch.
Where the first post worked through the umbrella filing stack that mentions dangerous cargo at the form level and the second post worked through the fee math that ignores cargo content entirely, this post works through what actually happens on the bridge when the vessel is laden with a regulated DG manifest — what the §11 provision requires, what the ELWIS DG submission field set must contain, how the WSV Verkehrsgruppen assignment moves the lock sequence at Brunsbüttel and Kiel-Holtenau, how IMDG-class segments (1, 3, 7 in particular) lay out differently against the lock chamber and the bridge-wing geometry than on an open-water transit, and how the WSV Hamburg VTS and the lock masters coordinate the day-of-transit on a laden-DG vessel. Operators running mixed cargo programmes on the NOK — including ballast-with-DG-residue and laden-without-DG cases around cargo operations at Brunsbüttel or Kiel — see this layer activate and deactivate between transits in ways that the standard pre-notification filing layer does not surface.
Get the Kiel Canal Compliance Reference — Free
ELWIS pre-notification validation, IMDG manifest cross-checks, WSV Verkehrsgruppen sequencing logic, and canal dues estimation. Enter your work email and we'll send the Kiel Canal Compliance Primer straight to your inbox.
What §11 SeeSchStrO Defines as Dangerous Cargo on the NOK
The Seeschifffahrtsstraßen-Ordnung (SeeSchStrO) is the German federal ordinance governing vessel traffic on the federal sea waterways — the NOK among them — and §11 is the provision that defines what counts as dangerous cargo for canal-transit purposes. The §11 framework cross-references the IMDG Code rather than restating a parallel classification system, which means a cargo entry that is IMDG-regulated is automatically §11-regulated for the purposes of the NOK transit. The Kanalbenutzungsordnung (the canal-use ordinance) layers on top of §11 with the operational rules a vessel has to follow at the lock approach, the IMDG-class-specific segregation distances, and the WSV's discretionary authority to delay entry or reroute the manifest queue.
The IMDG Code classes that fall under §11 SeeSchStrO for the purposes of a NOK transit:
- Class 1 — Explosives. Divisions 1.1 through 1.6 covering mass-explosion, projection, fire, and very-insensitive substances. Class 1 carries the highest lock-approach scrutiny of any IMDG class on the NOK — the WSV requires a Class 1 vessel to satisfy the IMDG segregation distance from the bridge wing and the accommodation block at both Brunsbüttel and Kiel-Holtenau, and the lock master has discretionary authority to decline simultaneous chamber entry with any non-compatible Division 1.1 through 1.3 vessel.
- Class 2 — Gases. Compressed, liquefied, refrigerated, or dissolved gases, including flammable and non-flammable aerosol propellants. Class 2 is subdivided into Division 2.1 (flammable), Division 2.2 (non-flammable, non-toxic), and Division 2.3 (toxic). Each division has its own IMDG segregation geometry on the NOK and its own ELWIS DG field set.
- Class 3 — Flammable liquids. Flash-point-defined liquids including most packaged bunker-fuel intermediates and the substantial bulk-petroleum segment. Class 3 is the IMDG class most frequently carried in commercial cargo on the NOK and is the most consistent source of IMDG deck-stow geometry discussions at the lock approach.
- Class 4 — Flammable solids, substances liable to spontaneous combustion, substances which on contact with water emit flammable gases. Divisions 4.1, 4.2, and 4.3 — each with its own IMDG segregation profile against the lock chamber. Class 4 is uncommon in NOK commercial transit but appears in chemical-tanker and bagged-cargo programmes.
- Class 5 — Oxidizers and organic peroxides. Divisions 5.1 (oxidizers) and 5.2 (organic peroxides). Class 5 segregation against Class 1, Class 3, and Class 4 is enforced at the IMDG Code level and surfaces visibly in the lock-chamber pairing rules on the NOK.
- Class 6 — Toxic and infectious substances. Divisions 6.1 (toxic) and 6.2 (infectious). Class 6 is rare in commercial NOK transit but appears in chemical-tanker programmes and refrigerated pharma cargo under regulated-temperature conditions.
- Class 7 — Radioactive material. The IMDG class with its own dedicated WSV oversight layer. A Class 7 vessel is typically routed through the NOK with a radiation-monitoring handoff to the WSV radiation officer at the lock approach; the IMDG segregation geometry is layered on top of the standard Class 7 monitoring programme.
- Class 8 — Corrosives. Bulk and packaged corrosive cargoes; segregation against Class 1 and Class 5 is enforced at the IMDG Code level and surfaces in the lock-chamber pairing rules.
- Class 9 — Miscellaneous dangerous substances. The catch-all IMDG class for substances and articles not covered by Classes 1 through 8 but presenting a recognised hazard during transport. Class 9 includes lithium batteries, asbestos, and certain elevated-temperature cargoes.
Why IMDG equivalence matters operationally on the NOK: §11 SeeSchStrO does not maintain a parallel classification system — it cross-references the IMDG Code directly. A cargo entry that is IMDG-regulated is automatically §11-regulated for the canal transit, and an ELWIS pre-arrival DG declaration that does not reconcile against the IMDG manifest field set has the same rejection surface under §11 as it does in any other regulated waterway. The implication: an IMDG manifest populated correctly for an open-sea voyage ports directly to the Kiel filing, but the segregation geometry has to be re-keyed at the canal-layer level because the lock chamber and the bridge-wing distance are NOK-specific.
ELWIS DG Pre-Arrival Submission: Field Set and IMDG Manifest Cross-Check
The ELWIS pre-arrival DG declaration is a separate field set filed on top of the standard ELWIS pre-notification that every NOK transit requires. The standard ELWIS pre-notification carries vessel particulars, traffic-group classification (Verkehrsgruppen assignment by beam/length/draft), and the planned transit window — those are the fields the Kiel Canal Filing Requirements 2026 post works through in detail. The ELWIS DG declaration adds the IMDG manifest field set on top: UN number, proper shipping name, IMDG class or division, packing group, quantity, stowage position on board, and segregation notes per cargo entry. The two field sets are reviewed by different WSV staff — the standard pre-notification by the traffic-group officer, the DG declaration by the WSV dangerous-cargo desk — but they have to reconcile against the same vessel particulars and the same transit window. A vessel that has IMDG-class cargo on board and files only the standard ELWIS pre-notification without the DG field set is held at the lock approach and re-sequenced to the next manifest slot after the DG declaration lands.
The ELWIS DG submission field set, mapped against the IMDG manifest fields operators maintain on board:
| ELWIS DG field | IMDG manifest field | Operational consequence |
|---|---|---|
| UN number | UN-No. column on the IMDG manifest | Wrong UN number is the single most common ELWIS DG rejection — typically a transposed digit on the IMDG manifest carried over to ELWIS without re-keying |
| Proper shipping name (PSN) | PSN column on the IMDG manifest | PSN must match the technical name on the IMDG Code for the cited UN number; trade-name-only entries are rejected |
| IMDG class or division | Class / Division column on the IMDG manifest | Determines the Verkehrsgruppen DG-class assignment at the lock approach |
| Packing group | PG column on the IMDG manifest (I, II, III) | Required for Class 3, Class 4, Class 5, Class 6.1, Class 8 — surfaces in IMDG segregation geometry |
| Quantity | Total quantity per UN number per cargo entry | Aggregate quantity at the IMDG Code chapter level determines whether the §11 limit thresholds are tripped |
| Stowage position on board | Stowage location / on-deck or in-hold coordinates | Bridge-wing distance, accommodation distance, deck-stow vs. in-hold — the IMDG segregation geometry applied at the lock chamber |
| Segregation notes | Segregation code matrix per IMDG Code chapter 7.2 | Cross-class compatibility at the lock chamber pairing — surface in the lock-master's discretionary authority to delay entry |
Critical intersection point: the ELWIS DG field set is the WSV's view of the vessel's cargo posture, and the IMDG manifest on board is the operator's view of the same cargo at the moment of each lock approach. The two have to reconcile at both Brunsbüttel and Kiel-Holtenau individually. A vessel that files the ELWIS DG declaration cleanly but carries an undeclared IMDG-class cargo on board at the lock approach (or vice versa) is held at the relevant outer lock approach until the gap is closed — typically a several-hour wait for the relevant lock to free.
WSV Verkehrsgruppen Classification: How DG-Class Vessels Get Sequenced at the Lock
The WSV assigns every Kiel-bound vessel to one of six Verkehrsgruppen (traffic groups) based on beam, length, and draft — Verkehrsgruppen 1 through 6, with the higher numbers carrying tighter transit constraints. The standard assignment works without reference to the cargo posture and is what the Kiel Canal Filing Requirements 2026 post works through in detail. A vessel carrying IMDG-class cargo above the §11 thresholds is reassigned to a dedicated Verkehrsgruppen DG traffic-group classification (operationally cited as VG 5 under the WSV's DG-class sequencing rules) that overrides the standard traffic-group logic — even if the vessel's dimensional profile would otherwise put it in a lower-numbered Verkehrsgruppe.
The Verkehrsgruppen DG assignment has four operational consequences at the lock approach that are not present on a non-DG transit:
- Dedicated lock sequence. A DG-class vessel behind a non-DG vessel in the manifest queue does not get bundled into the same lock chamber cycle. The lock master sequences DG vessels into the chamber when no other DG-class vessel whose IMDG compatibility is non-compatible is present — typically on a longer chamber-rotation cycle than the standard non-DG rotation.
- Bridge-wing distance geometry. IMDG segregation geometry is enforced against the bridge-wing distance and the accommodation block on board. A Class 1 vessel entering the chamber has to satisfy the IMDG Code chapter 7.2 segregation distance from the bridge structure during the lock approach, which constrains the chamber approach geometry versus a non-DG vessel of the same dimensions.
- WSV Hamburg VTS handoff. DG-class traffic on the NOK is co-ordinated at the traffic-group level through the WSV Hamburg VTS. The VTS desk manages the bridge geometry and the timing between Brunsbüttel and Kiel-Holtenau for DG-class vessels rather than treating the transit as a routine non-DG transit.
- Discretionary lock-master delay. The lock master at Brunsbüttel and at Kiel-Holtenau has discretionary authority to delay entry of a DG-class vessel if the IMDG segregation would be compromised by bridge weather, by traffic-group chamber interaction, or by a coincident non-compatible DG-class vessel already in the chamber queue. Operators should plan the manifest window with a buffer for a discretionary delay at the relevant lock.
Practical rule of thumb: A laden DG transit and a ballast non-DG transit on the same vessel will see different Verkehrsgruppen assignments at the lock approach even though the vessel particulars and the dimensional profile are unchanged. The IMDG manifest field set drives the Verkehrsgruppen assignment, not the LOA/beam/draft. Operators running mixed cargo programmes should treat the Verkehrsgruppen assignment as a per-transit variable, not a per-vessel constant.
For the broader Verkehrsgruppen traffic-group framework — including the dimensional thresholds, the speed-restriction rules per group, and the conditions under which a canal helmsman is dispensable — the Kiel Canal Filing Requirements 2026 post is the natural companion. The Verkehrsgruppen DG-class sequencing overlay covered here is a sub-layer on top of that framework, activated by the IMDG manifest field set and not by the dimensional profile.
IMDG-Class-Specific Stowage Rules at the Lock Chamber
The IMDG Code specifies stowage and segregation geometry for each of its nine classes — and the Kiel Canal lock chamber geometry activates specific segments of that geometry that are not present in an open-water or sheltered-waterway transit. Most of the IMDG framework was written for container shipping on open seas, where the segregation distances are measured against other cargo on the same vessel or against containers in the same hold. On the NOK, the relevant geometry is the lock chamber width at Kiel-Holtenau and at Brunsbüttel, the bridge-wing distance on the transiting vessel, the accommodation block on the transiting vessel, and the chamber approach rotunda for vessels waiting for the entry sequence. Three IMDG classes surface most consistently on the NOK because the geometry-relevant segments are unique to a canal transit:
- Class 1 — Explosives. The bridge-wing distance geometry at the lock approach is the most consequential IMDG-coded constraint on the NOK. A Class 1 vessel has to satisfy the IMDG Code chapter 7.2 segregation distance from the bridge structure and the accommodation block during the lock entry sequence. At Kiel-Holtenau's largest operational chamber the segregation geometry against the bridge wing is tighter than the open-water IMDG default because the chamber width constrains the lateral distance.
- Class 7 — Radioactive material. A dedicated WSV radiation-monitoring handoff is layered on top of the standard IMDG Class 7 segregation geometry. The lock approach at Brunsbüttel or Kiel-Holtenau for a Class 7 vessel includes a WSV radiation-monitoring officer whose authority is independent of the standard IMDG segregation review. The Class 7 vessel's stowage geometry on board has to satisfy both the IMDG Code constraints and the WSV radiation-monitoring geometry at the chamber approach.
- Class 3 — Flammable liquids. Flash-point deck-stow requirements on Class 3 cargoes activate at the lock approach against the in-hold vs. on-deck geometry, and against the IMDG segregation distance from the bridge wing. Bulk-Class-3 vessels (most of the commercial oil-transit segment) typically satisfy the geometry at the lock approach through consistent in-hold stow; packaged-Class-3 vessels (chemical tankers, containerised Class 3 cargoes) have to satisfy the geometry through a per-bay deck-stow or in-hold placement review against the IMDG Code chapter 7.2.
The NOK-specific geometry segments above are the IMDG rules that surface most consistently on commercial Kiel transits. Other IMDG classes — Class 4, Class 5, Class 6, Class 8, Class 9 — have their own IMDG Code geometry that applies on the NOK but rarely activates as a specific lock-approach constraint in the way Class 1, Class 7, and Class 3 do. The three classes above are the operational reference points for fleet managers who are planning a laden-DG transit on the NOK for the first time.
Day-of-Transit Coordination: WSV Hamburg VTS and Lock-Master VHF Sequence
On the day of transit, the master coordinates the laden-DG posture against the WSV Hamburg VTS and against the relevant lock master — Brunsbüttel for eastbound boarding from the North Sea side, Kiel-Holtenau for westbound boarding from the Baltic side. The VHF call sequence is materially different from the non-DG transit sequence, with more mandatory call windows and tighter timing at the chamber approach. The IMDG-specific lock-approach sequence anomaly handling — the lock master's discretionary authority to delay entry on a DG-class vessel — is the most frequent operational surprise for first-time laden-DG Kiel transits.
Four VHF call windows apply to a laden-DG transit on the NOK, in the order they surface on the day of transit:
- Pre-arrival call — Hamburg VTS. First VHF call is to the WSV Hamburg VTS for canal-stretch coordination. The call confirms the IMDG manifest posture, the Verkehrsgruppen DG-class assignment, and the planned transit window, and the VTS desk registers the vessel's IMDG posture for the bridge-wing geometry handoff to the lock masters at both ends.
- Lock approach call — first lock. Second VHF call is to the lock master at the boarding-side lock — Brunsbüttel for eastbound, Kiel-Holtenau for westbound. The call confirms the IMDG stowage geometry on board, the segregation notes, the proposed chamber sequence, and any IMDG-class-specific factor (Class 1 segregation distance, Class 7 radiation-monitoring handoff window, Class 3 deck-stow review).
- Bridge transit call — Hamburg VTS mid-canal. Third VHF call is to the WSV Hamburg VTS at the mid-canal check-in. The call confirms the IMDG posture has not changed since the boarding-side lock entry, the crew list and master are unchanged, and the bridge team is at the relevant IMDG posture for the next lock approach.
- Lock approach call — exit-side lock. Fourth VHF call is to the lock master at the exit-side lock — Kiel-Holtenau for eastbound, Brunsbüttel for westbound. The call repeats the IMDG stowage geometry review against the next chamber and confirms any IMDG-class-specific factor that applies at the exit-side lock approach.
Each of these calls is mandatory on a laden-DG transit. A vessel that misses a call window — most commonly the mid-canal check-in — is logged as a procedural anomaly by the WSV Hamburg VTS and surfaces as a layer of scrutiny at the next lock approach. Operators should plan the manifest window with a buffer for the four mandatory call windows and for any discretionary lock-master delay at the relevant lock.
The lock-master's discretionary authority on a DG-class transit: The lock master at Brunsbüttel and at Kiel-Holtenau can delay entry of a DG-class vessel if the IMDG segregation geometry would be compromised by bridge weather, by traffic-group chamber interaction, or by a coincident non-compatible DG-class vessel in the chamber queue. The delay is at the master's discretion and is not subject to a defined maximum — on a typical NOK transit in adverse weather, the delay can run from a few minutes to several hours. Operators should plan the manifest window with a buffer for this discretionary delay.
How Kiel DG Handling Compares With the Suez DG Stack
The Kiel Canal and the Suez Canal both reference the IMDG Code at the regulatory layer, but they apply the IMDG framework against materially different operational baselines. The comparison matters for fleet managers running mixed Kiel and Suez programmes on the same vessel class — the IMDG manifest field set is shared, but the segregation geometry and the procedural anchor points diverge in specific ways. For the Suez-side IMDG paperwork stack, the Suez Canal dangerous goods compliance post is the relevant companion and is worth reading alongside this piece.
Three operational differences between the Kiel IMDG stowage rule and the Suez IMDG stack recur across fleet programmes:
- Lock chamber vs. convoy sequence. Kiel applies IMDG segregation geometry against the Brunsbüttel and Kiel-Holtenau lock chambers and against the bridge-wing distance at the chamber approach. Suez applies IMDG geometry against the convoy sequence (northbound and southbound) and against the Great Bitter Lake anchorage spacing. Kiel's IMDG stowage is more constrained on the lock approach (the lock chamber geometry); Suez's IMDG stowage is more constrained on the convoy leg (the canal-and-lake sequence).
- WSV lone-authority vs. SCA stack. DG-class Kiel transits are managed by a single authority — the WSV through the Hamburg VTS desk and the lock masters at both ends. DG-class Suez transits are managed through the SCA portal layer, the SCNT pre-arrival paperwork stream, and the boarding officer layer at the Port Said and Suez Bay outer anchorages. The Kiel DG layer is a single-authority paperwork stream; the Suez DG layer is a multi-authority paperwork stream.
- Verkehrsgruppen DG vs. boarding-node DG posture. Kiel assigns a Verkehrsgruppen DG traffic-group sequencing at the manifest level that drives the lock chamber approach. Suez assigns the DG posture against the boarding-node documentation at Port Said (northbound) and Suez Bay (southbound) individually. Kiel DG posture is a manifest-layer variable; Suez DG posture is a per-boarding-node variable on a single SCNT record.
For fleet managers running the same vessel across both waterways, the practical lesson is that the IMDG manifest field set ports across cleanly (because both reference the IMDG Code), but the segregation geometry and the procedural anchor points have to be re-keyed into the waterway-specific paperwork stream rather than carried over verbatim.
Practical Pre-Transit Checklist for a Laden-DG Kiel Transit
Before every laden-DG Kiel filing, the bridge team and the WSV-side filing agent should run through the same checklist. Every item on it is a yes/no — if the answer to any item is "no," the vessel should not depart for the lock approach until the gap is closed. The checklist maps directly to the broader ELWIS pre-notification checklist from the Kiel Canal Filing Requirements 2026 post and adds DG-class-specific items around the Verkehrsgruppen DG assignment, the IMDG stowage geometry at the lock chamber, and the mid-canal VHF check-in.
- ELWIS DG declaration filed within the pre-arrival window. DG declaration lodged ≥48 hours before the lock approach at either Brunsbüttel or Kiel-Holtenau, with UN number, proper shipping name, IMDG class or division, packing group, quantity, and stowage position populated correctly per cargo entry.
- IMDG manifest on board matches the ELWIS DG submission field for field. The IMDG manifest carried on board has to reconcile to the ELWIS DG declaration at each cargo entry — UN number, PSN, IMDG class, packing group, quantity, and stowage position have to match. A gap between the manifest on board and the ELWIS submission at any entry is a DG-layer rejection at the lock approach.
- Verkehrsgruppen DG assignment confirmed at the WSV desk. The vessel's Verkehrsgruppen DG sequencing is on file at the WSV desk and matches the IMDG-class posture on board at the moment of each lock approach. A non-DG assignment on a laden-DG vessel, or vice versa, reorders the lock sequence and triggers a discretionary delay at the relevant lock.
- IMDG-class-specific stowage geometry verified at the lock chamber. For Class 1: bridge-wing segregation distance verified at the lock approach. For Class 7: radiation-monitoring handoff window confirmed with the WSV radiation officer. For Class 3: deck-stow vs. in-hold positioning verified against the IMDG Code chapter 7.2.
- WSV Hamburg VTS pre-arrival call scheduled and logged. First VHF call to the WSV Hamburg VTS placed inside the published pre-arrival window, with the IMDG manifest posture and the Verkehrsgruppen DG assignment on file. The call window is mandatory on a laden-DG transit and missed calls surface as procedural anomalies at the next lock approach.
- Lock-master call at the boarding-side lock scheduled and logged. Second VHF call to the lock master at the boarding-side lock — Brunsbüttel for eastbound, Kiel-Holtenau for westbound — placed inside the published approach window. The call confirms IMDG stowage geometry, segregation notes, and IMDG-class-specific factors for the chamber sequence.
- Original ELWIS DG declaration and IMDG manifest accessible on board at both locks. The IMDG manifest, the ELWIS DG receipt, and the §11 SeeSchStrO paperwork are in the bridge folder, accessible at Brunsbüttel boarding and at Kiel-Holtenau boarding. A missing DG-launder document at either lock approach is a documentation discrepancy that the lock master will log.
Stop NOK Paperwork Errors Before Your Vessel Reaches Brunsbüttel
CanalClear automates Kiel Canal pre-notification validation — catching IMDG manifest mismatches, draft exceedances, and incomplete ELWIS DG declarations before your filing is rejected at the lock approach. We're solving compliance for Panama Canal first. Kiel Canal automation coming soon.
View Kiel Canal Compliance PlansFrequently Asked Questions
What counts as dangerous cargo on the Kiel Canal under §11 SeeSchStrO?
Dangerous cargo on the Kiel Canal under §11 of the Seeschifffahrtsstraßen-Ordnung is defined as any cargo falling within the IMDG Code classification system — Class 1 explosives, Class 2 gases, Class 3 flammable liquids, Class 4 flammable solids, Class 5 oxidizers and organic peroxides, Class 6 toxic and infectious substances, Class 7 radioactive material, Class 8 corrosives, and Class 9 miscellaneous dangerous substances — above the per-class threshold prescribed by the Kanalbenutzungsordnung. A vessel carrying any quantity of IMDG-class material above the §11 threshold has to lodge an ELWIS pre-arrival DG declaration before the lock approach and is sequenced into the canal under Verkehrsgruppen DG-class rules rather than the standard traffic group.
Does Kiel accept IMDG Class 1 explosive cargo during transit?
Yes — the Kiel Canal accepts IMDG Class 1 explosive cargo under heightened handling conditions including IMDG-mandated segregation distance from the bridge wing and accommodation block at the lock approach, dedicated Verkehrsgruppen DG-class sequencing at both Brunsbüttel and Kiel-Holtenau, and discretionary lock-master authority to delay entry on bridge weather, chamber interaction, or coincident non-compatible Division 1 cargo. A Class 1 vessel cannot share a chamber cycle with any non-compatible Division 1.1 through 1.3 vessel; the WSV requires advance ELWIS DG submission with the UN number, division, compatibility group, and quantity populated correctly.
Is an ELWIS pre-arrival DG declaration mandatory for every DG transit?
Yes — every laden-DG Kiel Canal transit requires an ELWIS pre-arrival DG declaration as a separate field set on top of the standard ELWIS pre-notification. The standard ELWIS pre-notification carries vessel particulars, traffic-group classification (Verkehrsgruppen), and the planned transit window; the ELWIS DG declaration carries the IMDG manifest field set — UN number, proper shipping name, class or division, packing group, quantity, stowage position, segregation notes — reviewed by the WSV before the vessel reaches the lock approach. A vessel that files only the standard ELWIS pre-notification without the DG field set is held at the lock approach and re-sequenced to the next manifest slot — typically a several-hour wait for the relevant lock to free.
How does WSV Verkehrsgruppen classification affect a Kiel Canal DG vessel's lock sequence?
The WSV assigns a laden-DG vessel to a dedicated Verkehrsgruppen DG traffic-group sequencing (operationally cited as VG 5 under WSV practice) that overrides the standard traffic-group logic normally assigned by beam, length, and draft. The Verkehrsgruppen DG assignment moves the lock chamber cycle for the laden-DG vessel: the lock master does not bundle the DG vessel into the same chamber cycle as the non-DG vessel behind it, sequences the DG vessel into the chamber only when no non-compatible DG-class vessel is already in the queue, and consults with the WSV Hamburg VTS for traffic-group level coordination rather than treating the transit as a routine non-DG transit. Operators running mixed cargo programmes see the Verkehrsgruppen assignment flip between laden-DG and ballast-non-DG transits on the same vessel.
How does the Kiel Canal IMDG stowage rule compare with the Suez Canal IMDG stack?
Both waterways reference the IMDG Code, but they apply IMDG against different operational baselines. Kiel applies IMDG geometry against the Brunsbüttel and Kiel-Holtenau lock chambers and against the bridge-wing distance at the chamber approach; Suez applies IMDG geometry against the convoy sequence and against the Great Bitter Lake anchorage spacing. Kiel DG handling is a single-authority paperwork stream through the WSV Hamburg VTS and the lock masters; Suez DG handling is a multi-authority SCNT stream against the boarding-node documentation at Port Said and Suez Bay. Kiel IMDG posture is a manifest-layer variable (Verkehrsgruppen DG); Suez IMDG posture is a per-boarding-node variable on a single SCNT record.
Where should operators cross-check ELWIS DG fields against the Suez pre-arrival SCNT paperwork set?
Operators running mixed Kiel and Suez programmes should cross-check the ELWIS DG field set against the Suez SCNT paperwork in three places: the IMDG manifest field set itself (UN number, PSN, class, packing group, quantity — these port over cleanly because both waterways reference the IMDG Code), the vessel particulars on the two filings (which should be a single canonical record so crew and master drift does not surface as a DG-layer discrepancy on either waterway), and the segregation notes (which diverge by canal geometry — bridge-wing distance on Kiel, convoy-position distance on Suez — and have to be re-keyed into the waterway-specific paperwork stream rather than carried over verbatim).