Skip to content

x565 XML, explained

x565 is the XML form of IATA AHM 565: one file that holds an airline's weight and balance data for its aircraft types, which a departure control or load control system can read without anyone retyping it. The current schema is version 1.010. This page shows how a file is built, what the schema checks and what it misses, and how files are made today.

Written by Jón Rúnar Baldvinsson · Reviewed by Kristján Óttar Rögnvaldsson · Updated

What an x565 file is

An x565 file is one message, named IATA_LoadControl_SemiPermanentDataNotifRQ: a notice from the airline that owns the aircraft to the airlines that operate them, their handling agents and their DCS providers. It carries the same data as the AHM 565 datasheets, and IATA's implementation guidelines map each datasheet to its place in the file.

IATA publishes the schema (an XSD), implementation guidelines written for software vendors, and an x565 editor in its GOXML toolkit, which comes with the digital Airport Handling Manual.

AHM 565 explained

How a file is built

A file holds one or more carriers. A carrier holds its own standards (units, standard passenger and crew weights, ULD types) and one or more aircraft groups. A group is one aircraft type: its registrations, its units and its balance formula.

A group's tables sit in configurations. One configuration holds what all the group's aircraft share; others hold what differs for some of them, and each lists the registrations it applies to. Inside every element the children are in alphabetical order, and the order means nothing.

IATA_LoadControl_SemiPermanentDataNotifRQ
  Carrier
    AircraftGroup
      Aircraft
        AircraftRegistrationID
      AircraftGroupConfiguration
        AircraftRegistrationID
        CenterOfGravityLimitTable
        Deck
        DryOperatingAircraft
        FlightDeckCrewLocation
        FuelingProcedure
        MaximumWeightsTable
      AircraftName
      IATA_AircraftTypeCode
      IndexConversionConstantValue
      MAC_Measure
      WeightUnitCode
    AirlineDesigCode
    Name
    WeightUnitCode
  Remark
    EffectiveDate

A group's other tables, such as cargo positions, seats and fuel distribution, sit beside these in the configurations.

The start of a complete file, from Example Air, a fleet of three A220-300s we use for demonstrations:

<IATA_LoadControl_SemiPermanentDataNotifRQ xmlns="http://www.iata.org/IATA/2015/00/2026.1/IATA_LoadControl_SemiPermanentDataNotifRQ">
    <Carrier>
        <AircraftGroup>
            <Aircraft>
                <AircraftRegistrationID>ZZ-ABC</AircraftRegistrationID>
                <MSN_ID>99001</MSN_ID>
            </Aircraft>
            <Aircraft>
                <AircraftRegistrationID>ZZ-ABD</AircraftRegistrationID>
                <MSN_ID>99002</MSN_ID>
            </Aircraft>
            <Aircraft>
                <AircraftRegistrationID>ZZ-ABE</AircraftRegistrationID>
                <MSN_ID>99003</MSN_ID>
            </Aircraft>
            <AircraftGroupConfiguration>
                <AircraftRegistrationID>ZZ-ABC</AircraftRegistrationID>
                <AircraftRegistrationID>ZZ-ABD</AircraftRegistrationID>
                <CenterOfGravityLimitTable>
                    <CenterOfGravityLimit>
                        <AftIndexValue>75.6</AftIndexValue>
                        <AftMAC_Percent>34</AftMAC_Percent>
                        <ForwardIndexValue>44.7</ForwardIndexValue>
                        <ForwardMAC_Percent>14</ForwardMAC_Percent>
                        <WeightMeasure UnitCode="KGM">36000</WeightMeasure>
                        <WeightTypeCode>TO</WeightTypeCode>
                    </CenterOfGravityLimit>
…

The whole file (x565 1.010, 68 KB)Example Air is not a real airline. Its figures are for demonstration only and must never be used to load an aircraft.

Versions

The current schema is version 1.010. A file names its namespace on its root element, and without it the file cannot be validated at all:

http://www.iata.org/IATA/2015/00/2026.1/IATA_LoadControl_SemiPermanentDataNotifRQ

Since version 1.008, the fuel formula changed shape, a few elements were removed or renamed, many required elements became optional, remarks became repeatable in most places, a hold has at most one door, and a dry operating configuration can carry its own water and weight adjustments. A file written for an older version does not validate against 1.010, and moving it takes more than a new namespace.

IATA's guides were written before 1.010 and still show a few elements where 1.010 no longer has them. A file is validated against the schema.

What the schema checks, and what it does not

An XSD checks a file's shape: which elements exist, in what order, how many of each, and that a number is a number. The x565 schema checks little more: it declares no keys, no references between elements and no either-or rules, and a measure is any decimal with an optional unit. IATA's own guidelines say the schema alone cannot show that a file is logical or unambiguous.

So a file can pass the schema and still be wrong:

  • It names a hold position, crew location, tank or code that the file does not define.
  • A configuration lists a registration that is not one of the group's aircraft.
  • The same table appears in two configurations that one aircraft reads, with different values.
  • A CG limit states neither an index nor a %MAC, or a fuel effect neither a volume nor a weight.
  • An extent is stated backwards, or a centroid sits outside its extent.
  • The taxi fuel's burn ratios do not add up to one.
  • A fuel formula uses a character it does not declare.
  • A value is in a unit other than its aircraft group's.

Tekna Vault checks the data against these rules as well as the schema before any change is published, and reads every file it writes back through its own importer before serving it.

IATA's x565 editor

IATA's x565 editor is a Microsoft Excel workbook that comes with the toolkit. It opens an x565 file as datasheets, lets you edit them, and writes a new file. Its user guide is plain about its scope:

  • It holds one aircraft group at a time, and recommends one group per file.
  • It keeps no history of the data: the guide suggests a version number in the file name and a revision note in the file's remark, and re-issuing the whole file after any change.
  • It has no review or approval: checking the data against the manufacturer's certified data is the airline's job.
  • It checks three things: references to something not defined, text where a number belongs, and units against the group's own. It does not judge whether the data is right.
  • Changing the structure of its sheets can break the file it writes.

For one engineer preparing one aircraft type, that may be all that is needed. For an airline whose data several people change, review and send to several systems, it leaves the versions, the review and most of the checking to people.

Sources

  • IATA, the IATA_LoadControl_SemiPermanentDataNotifRQ schema, version 1.010.
  • IATA, x565 implementation guidelines, version 3.1 (June 2024).
  • IATA, the user guide to its x565 spreadsheet editor, version 1.3.
  • IATA, GOXML toolkit

Tekna is independent of IATA. AHM 565 and x565 are IATA's.

The weight and balance glossary

Safety-critical data deserves a proper system of record

A 30-minute call on Google Meet: 15 minutes to show you the platform, 15 for your questions.