Resolution 743 – Found and Unclaimed Checked Baggage
Introduction
Resolution 743 is an IATA Passenger Services Conference (PSC) binding standard governing found or unclaimed checked baggage. It is codified in the IATA Passenger Services Conference Resolutions Manual (PSCRM), which “contains all the Resolutions and Recommended Practices … for baggage handling processes”[1]. In the PSCRM, Res. 743 is listed as “Found and Unclaimed Checked Baggage”[2]. By IATA convention, resolutions like 743 are Type B (mandatory) provisions adopted by PSC votes and uniformly enforced by member airlines. These standards are developed by IATA’s Passenger Standards Conference and are binding on all member carriers[3][2]. In practical terms, Res. 743 “outlines the responsibility and procedures” for baggage that arrives at an airport but goes unclaimed or cannot be delivered because the owner is unknown[4]. Under Res. 743, airlines and airports must agree (typically via a local baggage committee) on standardized steps to catalogue, secure and repatriate found bags, ensuring no bag is left indefinitely in limbo[4][5].
Origin and Publication
Resolution 743 was first adopted by IATA’s Passenger Services Conference at its 31st meeting (noted as “PSC (31) 743” in IATA references[5]). (Exact dates are given only in the PSC minutes and PSCRM itself; accessible archives are limited.) Since original adoption, Res. 743 has been updated only through formal PSC amendment ballots (via circulars to member airlines). For example, companion resolutions 743a, 743b, and 743c were later added to handle related issues (743a – Forwarding Mishandled Baggage; 743b – Baggage Identification Chart; 743c – On-hand Baggage Summary Tag). These appeared at subsequent PSC meetings (e.g. PSC (36) for 743a[6]). Each amendment was published in the PSCRM edition following the vote. In practice, IATA members track the full changelog in the “Amendment History” annex of each new manual edition (not publicly posted). Key changes are announced by PSC circulars to members rather than press releases.
Procedure Step
1. Identification of Found Baggage
Action
Any airline/handler that discovers an unattended bag on arrival (e.g. at baggage hall) must tag it as found and record its details.
Timeline
Immediately on discovery.
2. Enter Tracing Message
Action
The airline must enter a standard “Found Bag” message in the global baggage tracing system (per IATA message format in Res. 743’s Attachment A)[7].
Timeline
Within hours of discovery.
3. Local Baggage Committee Notification
Action
The find is reported to the airport’s local baggage committee (often required by Res. 744) so a holding policy applies.
Within 24h (per local rules).
4. Search for Owner
Action
The airline uses passenger records, PNR data or other clues to trace the bag’s owner.
Timeline
Ongoing (typically 0–5 days).
5. On-hand (OHD) Reporting
Action
If no claim within 120 hours (5 days), the airline must either forward the physical bag to its central office or send an “On Hand Baggage” (OHD) message to its own central tracing office[8]. The OHD message alerts others that this unclaimed bag is in custody.
Timeline
By 120h after discovery.
6. Extended Disposal or Auction
Action
If the bag remains unclaimed beyond the local legal holding period (typically weeks), airlines follow local rules for disposal or sale (per local baggage committee policy).
Timeline
Varies by country/airport.
Purpose
The main purpose of Res. 743 is to prevent found bags from “languishing” indefinitely by ensuring a consistent process. It requires airlines to catalogue and report found baggage immediately (improving chances of reuniting it with its owner) and to store it securely until claimed. IATA explains that these procedures reduce cost and inconvenience: by working “seamlessly” through industry-wide standards, airlines and airports minimize delays and lost-baggage claims[9][4]. For passengers, Res. 743 offers the assurance that a found bag will be tracked (via the industry messaging system) and not simply discarded. The resolution also facilitates legal compliance: for example, if a bag can’t be delivered, the carrier remains responsible under the Montreal/Warsaw Conventions for lost luggage, so following Res. 743 helps meet those international obligations.[10][4]. In effect, the rule makes each airline accountable for found baggage and ensures information (bag tag number, flight, airport code) is recorded in the baggage tracing system.
Technical Structure
Resolution 743 is formatted as a PSC (Type B) resolution. It contains definitions and a series of sections and attachments detailing procedures. (The full text is in the PSCRM, but briefly: it defines terms like late bag, found bag, OHD message, etc.) Key provisions include:
- Immediate messaging: “Member airlines are required to enter a standard message in the applicable baggage tracing system using the prescribed format in Attachment A of Resolution 743”[7]. In other words, as soon as a bag is found, the airline must generate an official IATA message (analogous to the “Baggage Source Message” used for mishandled bags) so that all interline partners see the bag’s status.
- Time-based triggers: If no claim is made “within 120 hours after the baggage being found,” then an On-hand message is sent[8]. This section provides a clear 5-day rule, after which the bag is treated as on-hand (i.e. officially unclaimed but stored).
- Attachments and codes: Resolution 743’s attachments specify the message formats and code values to use for found/unclaimed bags. (For example, there is likely an attachment that indicates which message type and code to send in the industry Type-B baggage system.) These attachments ensure technical interoperability across airlines’ computer systems.
Because Res. 743 deals with local practice, it defers some details to local baggage committees (governed by Res. 744). For instance, how long to store a bag before disposal is handled by local regulation or airport policy (often decided by the local baggage committee). However, the core requirements (immediate logging, notification, 120-hour rule) are uniform worldwide.
Implementation Guidelines
Airlines implement Res. 743 via their Ground Operations manuals and by working with airports. In practice this means: whenever a bag is found, staff tag it as Found Bag, log it in the station’s lost-and-found system, and immediately send the industry baggage message. Many airlines train handlers to recognize this situation and to store found bags in a dedicated area or vault (often the airport police or security office). Local baggage committees (Res. 744) typically establish detailed local procedures – for example, agreeing on default hold periods or auction rules. Though not published by IATA, such local rules often require the airline to physically apply a “found bag tag” and to inventory the bag’s contents if needed. The IATA-recommended practice is that airlines should contact the passenger via email/phone once a match is suspected and arrange delivery of the bag. If the owner cannot be reached, the bag stays secured until the 120-hour trigger.
Benefits for Airlines
Adhering to Res. 743 brings several benefits. First, it reduces the labor and claim costs of truly lost bags: by quickly identifying and reuniting found baggage, airlines cut the number of paid-out loss claims. A standardized system also means less confusion and fewer disputes between interline carriers when a bag is traced across networks. For example, SITA’s baggage-tracking system WorldTracer is designed around IATA standards like Res. 743; it “ensures the airline community meets IATA … Resolution 743 for found and unclaimed checked baggage”[10]. In practice, this means airlines avoid unnecessary delays and audits: they can prove they followed industry procedure. Also, standardized logging of found baggage provides an audit trail for regulators: each bag’s status and messages are recorded electronically.
Auditability
Because Res. 743 mandates the use of IATA’s baggage messaging and defined procedures, all actions are logged in interline systems. Auditors can check an airline’s baggage trace database to confirm that found bags were handled per Res. 743. Key audit points include: whether a message was sent within the required timeframe, and whether local policies (e.g. storage requirements) were followed. The PSCRM includes an “Amendment History” table for each resolution, so airlines can verify they are using the latest version. Moreover, IATA encourages carriers to maintain records (invoices, warehouse logs, disposal receipts) for unclaimed baggage, which can be reviewed to ensure compliance. In essence, the combination of mandatory messaging, standard forms, and local committee oversight makes Res. 743 highly auditable.
Real-World Use Cases
In practice, Res. 743 is exercised at every airport worldwide. For example, if a bag arrives at CDG airport with no passenger to claim it (perhaps due to a tight connection), the handling airline will mark it “found,” alert the local baggage committee, and send the IATA message. Similarly, when a passenger finally reports a missing bag days later, the OHD message triggered by Res. 743 enables the airline to locate the bag at its secure holding area. Airlines often reference Res. 743 in training: one IATA advisory notes that 743 “outlines the responsibility and procedures” when baggage is found[4]. Industry solutions have built workflows around it: e.g., WorldTracer Lost & Found (a SITA product) automates the trace messaging for Res. 743 events. Some airlines also use the resolution to guide luggage auctions – for instance, after the mandated holding period, they may sell unclaimed bags at airport auctions in line with local law (as agreed by the local baggage committee).
Summary
Resolution 743 (adopted at PSC 31) establishes a global, standardized process for found/unclaimed baggage. It was first published in the IATA PSCRM in the early 2000s (at PSC meeting 31[5]) and has since been supplemented by related amendments (743a–743c). Its core purpose is to ensure that any bag found at an airport is immediately tagged, logged and traced, with a clear 120-hour rule for handling unclaimed cases. By doing so, it streamlines lost-baggage operations, ensures regulatory compliance, and provides auditability. As one IATA summary puts it, Res. 743 “outlines the responsibility and procedures” for such baggage[4] – a fitting description of a rule that turns random found luggage into a managed process.
Sources
IATA materials and industry documents (PSCRM, Baggage Reference Manual, IATA guidance) and related regulatory summaries[1][4][11][10] were consulted to compile this overview. These sources explain the scope and requirements of Res. 743, its adoption context, and practical applications in airline baggage handling.
- IATA - Baggage Standards
https://www.iata.org/en/programs/ops-infra/baggage/standards/ - IATA - Passenger Standards Conference
https://www.iata.org/en/about/corporate-structure/passenger-standards-conference/ - infrastructure.gov.au — (IATA advisory referenced)
https://www.infrastructure.gov.au/sites/default/files/documents/acrc2025-submission-c42-international-air-transport-association.pdf - escholarship.mcgill.ca — (related analysis / extracts)
https://escholarship.mcgill.ca/downloads/sj139429r.pdf - SITA | WorldTracer celebrates 30 years of repatriating mishandled baggage
https://www.sita.aero/pressroom/news-releases/worldtracer-celebrates-30-years-of-repatriating-mishandled-baggage/
Author: John Karume
John Is a Baggage Operations and Systems expert with 15+ years of airline experience who leverages People, Process, Technology to deliver measurable improvements. He builds innovative tech solutions, from Baggage Systems, LMS and educational sites to business process automation and full-stack software integrations—and is a Power BI, Excel, and Tableau guru as well as a full-stack web and software developer. A Certified Lean Black Belt, Business Analyst, Aviation Auditor and Quality Control specialist, John combines operational insight with technical delivery to keep systems efficient and baggage moving on time.
Contact: john.karume@baggagelogistics.com | https://www.fiverr.com/s/o8G3q2x
Comments (0)