Free tool

Type B baggage messages, explained

Paste a BSM, BPM, BTM or BUM and see what every line says. Or build a test BSM for your integration.

Everything runs in your browser. The message is never sent to a server.

Examples
BSM

Baggage Source Message

Sent by the airline (or its handler) from its check-in system to the airport's baggage system. Says which bag goes on which flight.

Type B header

Priority
QU
To
LIMBRZZLIM · function BR (baggage reconciliation system) · airline ZZ
From
HDQKMZZHDQ · function KM (airline host) · airline ZZ
Sent
day 23, 18:45

Summary

Tag
0999311902, 0999311903
Passenger
PAREDES/LUZ
Arrives on
ZZ1180 · 23NOV · CUZ
Departs on
ZZ2047 · 23NOV · MIA
Continues on
ZZ0412 · 24NOV · JFK
Baggage
2 pieces · 41 kg
Station
LIM
Special handling
SCON (short connection)
Authority to load
yes, may be loaded

Notes

No format issues found.

Line by line

  1. .V/1TLIMVersion and supplementary data
    Dictionary version
    1
    Bag source
    Ttransfer: arrives from another flight
    Station
    LIM
  2. .F/ZZ2047/23NOV/MIA/YOutbound flight
    Flight
    ZZ2047Airline ZZ · number 2047
    Date
    23NOVNovember 23
    Destination or transfer
    MIA
    Class
    Y
  3. .I/ZZ1180/23NOV/CUZ/YInbound flight
    Flight
    ZZ1180Airline ZZ · number 1180
    Date
    23NOVNovember 23
    Origin
    CUZ
    Class
    Y
  4. .O/ZZ0412/24NOV/JFK/YOnward flight (connection)
    Flight
    ZZ0412Airline ZZ · number 0412
    Date
    24NOVNovember 24
    Destination or transfer
    JFK
    Class
    Y
  5. .N/0999311902002Bag tag
    Tag
    0999311902Issuing airline numeric code 999 · serial 311902 · 2 consecutive tags
    Also covers: 0999311903
  6. .S/Y/31A/CReconciliation data
    Authority to load
    Yyes, may be loaded
    Seat
    31A
    Passenger status
    Cchecked in
  7. .W/K/2/41Pieces, weight and dimensions
    Data type
    Kkilograms
    Pieces
    2
    Checked weight
    41kilograms
  8. .P/PAREDES/LUZPassenger
    Surname
    PAREDES
    Given name / initial / title
    LUZ
  9. .E/SCONException / special handling
    Code
    SCONshort connection
  10. ENDBSMEnd of message

About this tool

It follows IATA Recommended Practice 1745, the baggage messaging standard between airlines, airports and ground handlers. Some systems use variants; the decoder accepts them and tells you when something isn't standard.

Sample data is fictional: airline ZZ doesn't exist.

Concord receives these messages in real time and turns them into what each ramp agent sees on their scanner.

Try the Concord demo