<% Response.CharSet="utf-8" %> UN/EDIFACT D97B Message TANSTA - Tank status report message Return to Stylus Studio EDIFACT D97B Messages page.

Tank status report message

Contr. Agency:UN
SOURCE:Joint Rapporteurs Message Design Group JM4

Tank status report message
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
    1. Standard terms and definitions
    1. Data segment clarification
    2. Data segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction

This message also occurs in the following versions of this standard:
D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B


This specification provides the definition of the Tank status report message (TANSTA) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1.1. Functional Definition

A message from a vessel to the shipplanning department of a shipping line and vice versa (e.g. via satellite), giving details about the contents of ballast tanks, fuel tanks, water tanks and other figures necessary for the calculation of the stability of the vessel.

1.2. Field of Application

The Tank status report message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.

1.3. Principles

This message serves to transmit information about all non-cargo deadweight items on board a vessel. This includes all ballast and service tanks, stores, crew and effects and other miscellaneous items including deadweight constants.

The message can be used for transmission of either current or forecast status of tank and deadweight items. For example, the message may be used to transmit information relating to an actual departure condition from one port but can also be used to transmit data relating to a forecast arrival condition at another port.

In general, the message will be generated on board by the ship's operator and transmitted to other parties interested in the vessel's stability and safety. This is normally the operations or tonnage centre but may also be a third party such as a terminal operator.

In certain circumstances the message can also be transmitted to the vessel. In this case the contents of the message may be used to advise the ship's master of a desirable arrival condition.


See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.


4.1. Data Segment Clarification

This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Tank status report message is TANSTA.

Note: Tank status report messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065TANSTA

0020 BGM, Beginning of message

A segment to indicate the beginning of a message and to transmit identifying number.

0030 DTM, Date/time/period

A segment to indicate a date and time applying to the whole message, such as: - document or message date and or time

0040 NAD, Name and address

A segment to identify a party's name, address, and function, such as: - message recipient - message sender

0050 Segment Group 1: RFF-DTM

A group of segments to specify a reference (and its related date and or time) which applies to the whole message.

0060 RFF, Reference

A segment to specify a reference, such as: - reference to previous message

0070 DTM, Date/time/period

A segment to indicate a date and or time related to the reference.

0080 Segment Group 2: TDT-LOC-DTM-RFF-FTX

A group of segments to provide details of the main carriage transport, including related locations and date and times.

0090 TDT, Details of transport

A segment to specify transport details for the main carriage, such as: - discharge voyage number - radio call sign of the vessel - nationality of the vessel

0100 LOC, Place/location identification

A segment to specify either the place of departure or the place of arrival for the main carriage.

0110 DTM, Date/time/period

A segment to specify a date and or time related to the main carriage transport, such as: - estimated date/time of departure - estimated date/time of arrival

0120 RFF, Reference

A segment to specify a reference related to the transport details, such as: - loading voyage number (if different from the voyage number assigned by the carrier or his agent in the TDT-segment).

0130 FTX, Free text

A segment to specify supplementary information related to the main carriage transport.

0140 Segment Group 3: LOC-MEA-DIM-FTX

A group of segments to identify a tank or deadweight item by its place on or in the means of transport.

0150 LOC, Place/location identification

A segment to specify the location of a tank or deadweight item on the means of transport, such as: - fore peak tank

0160 MEA, Measurements

A segment to provide a measurement related to the tank or deadweight item, such as: - gross weight of tank contents - volume of liquid in the tank - specific gravity - percentage full

0170 DIM, Dimensions

A segment to specify dimensions of the deadweight item, such as: - length expressed in 'longitudinal centre of gravity' - width expressed in 'transverse centre of gravity (from centerline)' - height expressed in 'vertical centre of gravity (from keel)'

0180 FTX, Free text

A segment to describe the actual contents of tanks, such as lubricating oil, marine fuel oil, fresh water.

0190 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.

4.2. Data segment index (Alphabetical sequence by tag)

BGM Beginning of message
DIM Dimensions
DTM Date/time/period
FTX Free text
LOC Place/location identification
MEA Measurements
NAD Name and address
RFF Reference
TDT Details of transport
UNH Message header
UNT Message trailer

4.3. Message structure

4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─DTM Date/time/period ×1 (M)
├─NAD Name and address ×9 (C)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×9 (M)
├─TDT Details of transport ×1 (M)
├─LOC Place/location identification ×1 (M)
├─DTM Date/time/period ×9 (M)
├─RFF Reference ×1 (C)
└─FTX Free text ×1 (C)
├─Segment Group 3 ×999 (C)
├─LOC Place/location identification ×1 (M)
├─MEA Measurements ×9 (M)
├─DIM Dimensions ×9 (C)
└─FTX Free text ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97B Messages page.