IATA RP 1743e: Baggage Irregularity Report (BIR) – The Industry’s Common Language for Mishandled Bags

Introduction

Every day airlines and airports handle millions of pieces of checked baggage. When a bag is delayed, damaged, left behind or otherwise mishandled, the incident must be recorded accurately so that the bag can be traced, the passenger compensated and the root cause identified. Without a common format and vocabulary, each carrier would invent its own report, rendering interline messages ambiguous and industry statistics meaningless.

IATA Recommended Practice 1743e solves this problem. It defines the content, format and irregularity-code scheme of the Baggage Irregularity Report (BIR)—the uniform document used whenever checked luggage is lost, delayed or damaged. By requiring every participating airline to record the same fields and to apply the same primary and secondary codes, RP 1743e creates a shared data language that travels with the bag through messaging systems, claims processes and performance analyses. The result is faster passenger service, cleaner audit trails and the ability to benchmark mishandling rates across the global network.

Origin and Adoption

RP 1743e first became effective on 1 June 2008. It appears in the 30th Edition of the IATA Passenger Services Conference Resolutions Manual (effective 1 June 2010), confirming that the practice was adopted by the relevant Passenger Services Conference meeting shortly before the 2008 effective date.

Like all IATA Resolutions and Recommended Practices, RP 1743e is member-controlled intellectual property. Airlines propose, debate and vote on its content through formal PSC ballots; amendments are distributed via official circulars rather than public announcements. The resolution’s amendment-history table in the PSC manual records any subsequent changes to wording or coding. As of the latest available editions, the practice remains current and is listed among IATA’s official baggage standards under the title “Baggage Irregularity Report.”

Purpose and Function

The Baggage Irregularity Report serves two interlocking purposes.

First, it standardizes mishandling data. Every report captures the same core information—location and time of the irregularity, handling carrier, bag-tag number, flight details and a set of predefined irregularity codes that classify both the type and the probable cause of the mishandling. Because every airline uses identical fields and identical code definitions, the industry can aggregate, compare and analyse performance across carriers, airports and process stages.

Second, it accelerates claims and customer-service recovery. When a passenger reports a missing or damaged bag, ground staff complete a BIR (increasingly in electronic form). The completed report, complete with its codes, is transmitted through baggage-messaging systems such as SITA WorldTracer or IATA standard messages. Receiving carriers immediately understand the nature of the problem, can prioritise tracing or delivery, and can process the passenger’s claim against a consistent record. The same codes also support interline prorating of liability under related resolutions, ensuring that costs are allocated fairly among the carriers involved.

In short, RP 1743e is the rulebook that tells every airline what to record, which codes to apply, and how to file the report so that the data remain usable by every subsequent party in the baggage chain.

Technical Structure

At the heart of RP 1743e is a hierarchical coding system. Each report carries one primary code (P10–P90) that identifies the general category or location of the mishandling, together with one or more secondary codes (S##) that supply finer causal detail. The primary categories and representative secondary codes are:

• P10 – Origin Station – Check-In
  Errors at departure check-in. Secondary examples include S11 (incorrect or no entries on tag), S12 (not checked to final destination), S15 (wrong bag labelled / tag switched).
• P20 – Origin Station – Failed to Load
  Bags left behind at origin or gate. Examples: S21 (bag left at station of origin, correctly labelled), S23 (standby bag left behind), S26 (off-loading due to weight or space).
• P30 – Any Station – Loading/Offloading
  Handling errors en route. Examples: S31 (wrong aircraft), S32 (off-loaded by error), S33 (not off-loaded when passenger transfers).
• P40 – Arrival Station
  Mishandling at destination. Examples: S41–S43 (bag sent to wrong carousel or delayed delivery to claim area).
• P50 – Transfer Station
  Problems during interline connections. Examples: S51 (passenger rerouted, bag not rerouted), S52–S56 (MCT or interchange issues), S57 (codeshare-partner bag), S59 (bag not authorised to load).
• P60 – Airport General
  External or systemic factors. Examples: S61 (strike / industrial action), S62 (weather delay), S63 (airport security hold), S64 (equipment down).
• P70 – Miscellaneous
  Residual causes. Examples: S72 (passenger off-loaded, bag not off-loaded), S73 (bag not claimed by passenger).
• P80 – Damage
  Physical damage to the bag. Examples: S83 (damage to security-inspected baggage), S91 (damage resulting from pilferage).
• P90 – Pilferage/Theft
  Loss under suspicious circumstances. Examples: S91 (pilferage including bag damage), S93 (pilferage from security-inspected baggage), S95 (pilferage from crew baggage), S96 (pilferage including damage from crew bag), S98 (law-enforcement intervention – bag untraceable).

The RP text further instructs that when a handling agent files a report on behalf of a carrier, that carrier’s three-letter code is used; if no responsible station can be identified, the code “XXX” is inserted. In practice the BIR form (paper or electronic) provides fields or checkboxes for the primary code and space for the relevant secondary codes, together with the usual passenger, bag-tag and flight data.

Implementation Guidelines

Airlines and airports embed RP 1743e into both operational procedures and electronic systems. Whenever a bag is declared lost, delayed or damaged, staff complete a BIR—today usually on a terminal linked to the baggage-tracing platform. The report captures passenger details, bag-tag number, flight information and the appropriate P/S codes.

These codes are not confined to the local form. They travel with the bag through IATA baggage messages. An optional SI (Special Information) line may be added to messages such as AHL (Advice of Originated Handled Baggage) or FWD (Forwarding), carrying the RP 1743e irregularity code so that every downstream carrier immediately sees the nature of the problem.

Ground-operations manuals, training curricula and quality-assurance programmes explicitly require that every mishandled-bag incident generate a correctly coded BIR. Because the code set is standardised, automated systems can validate consistency (for example, ensuring that a P50 code is accompanied by a transfer-station location). Auditors can therefore verify compliance by sampling reports against the official code definitions.

Operational Workflow

1. A passenger reports a missing, delayed or damaged bag, or staff discover an irregularity during handling.
2. The agent identifies the most accurate primary code (P10–P90) and any applicable secondary codes.
3. A BIR is completed—electronically or on paper—containing passenger data, bag-tag number, flight details, location/time of the irregularity and the chosen codes.
4. The report is entered into the baggage-tracing system (WorldTracer or equivalent).
5. Where interline delivery or further handling is required, the irregularity code is transmitted in the SI line of the relevant baggage message.
6. The receiving carrier uses the coded information to prioritise tracing, expedite delivery or process the claim.
7. The completed BIR remains on file as the permanent audit record of the incident.

Benefits for Airlines

Uniform application of RP 1743e yields several concrete advantages.

• Comparable performance data. Carriers and IATA can aggregate reports by primary and secondary code, revealing the most frequent failure points (for example, a high incidence of P10/S12 tagging errors) and enabling targeted process improvements.
• Faster, fairer claims handling. A completed BIR with precise codes allows claims staff to assess liability quickly, detect anomalous patterns that may indicate fraud, and support accurate interline prorating under related resolutions.
• Clear audit trail. Every mishandled bag generates a standardised record that demonstrates procedural compliance and supplies evidence in the event of dispute or regulatory enquiry.
• Interline clarity. When a bag moves between carriers, the shared code vocabulary eliminates ambiguity about why the bag was delayed or damaged, allowing the delivering carrier to take the correct next action.
• Regulatory readiness. Jurisdictions that require mishandling statistics can receive data already structured according to an internationally recognised scheme.

Auditability and Compliance

Because RP 1743e is an official IATA standard, airlines incorporate it into their internal manuals and quality systems. Auditors examine samples of BIRs to confirm that a report exists for every mishandled bag, that the codes used are valid, and that the primary category is consistent with the recorded location. The amendment-status tables in the PSC manual show the practice as permanent, giving users a single authoritative reference for the current code set. Any future change (for example, the addition of a new secondary code) requires a formal PSC vote and is published by amendment circular, so systems built around the existing codes remain stable for long periods.

Relationship to Other IATA Standards

RP 1743e is the documentary and coding backbone of the entire 1743 series. RP 1743a (missing checked baggage), RP 1743b (unchecked baggage and damage), RP 1743c (interline tagging errors) and RP 1743d (theft/pilferage prevention) all rely on the BIR form and its codes to record the outcome of the procedures they prescribe. The codes travel inside standard baggage messages whose formats are defined elsewhere in the IATA messaging suite. Liability allocation and interline settlement draw on related resolutions (including Resolution 780). Local Baggage Committees operating under Resolution 744 frequently review aggregated BIR statistics when diagnosing airport-level performance problems.

Real-World Use Cases

• A bag misses its connection because the minimum connecting time proved insufficient. The transfer agent completes a BIR with primary code P50 and secondary code S52, enters it into the tracing system, and the SI line of the forwarding message carries the same codes so the destination station knows the bag is late due to a transfer-timing issue.
• A suitcase arrives with a tear that occurred after security screening. The agent records P80 and S83; the coded BIR accompanies the passenger’s damage claim and supplies objective evidence for the claims assessment.
• Industry analysts examine months of aggregated BIR data and observe a spike in P10/S12 incidents on a particular domestic sector. The finding triggers a focused review of tagging procedures at the origin stations, leading to revised training and a measurable drop in that category of error.
• An interline bag is delivered late. The delivering carrier’s agent sees the RP 1743e code in the incoming message, understands the original cause, and can both expedite final delivery and correctly attribute responsibility for any compensation.

Industry Challenges

Accurate coding depends on front-line staff correctly interpreting the definitions. Under time pressure an agent may select a generic secondary code rather than the most precise one, diluting the analytical value of the data. Electronic systems must be kept synchronised with the official code list; any lag after an amendment creates temporary inconsistency. Smaller stations or third-party handlers may have less frequent training, increasing the risk of incomplete or miscoded reports. Continuous reinforcement through training, system validation and audit sampling remains necessary to preserve data quality.

Future Outlook

The source material indicates that substantive changes to RP 1743e have been infrequent; the core primary and secondary code structure has remained stable since its introduction. As baggage-tracking platforms become more automated, the same codes can be populated or suggested by system logic, further reducing manual error while preserving the human-readable, standardised vocabulary that the industry relies upon. Any future expansion of the code set will continue to follow the formal PSC amendment process.

Amendment Status

RP 1743e became effective on 1 June 2008 and has been maintained in successive editions of the Passenger Services Conference Resolutions Manual. It is recorded as a permanent recommended practice. Amendments, when required, are adopted by PSC ballot and published through official circulars; the amendment-history table in the manual provides the definitive record of changes.

Key Takeaways

• RP 1743e defines the uniform Baggage Irregularity Report and its hierarchical irregularity-code scheme.
• It became effective on 1 June 2008 and remains a permanent standard in the PSC Resolutions Manual.
• Primary codes (P10–P90) classify the location or type of mishandling; secondary codes supply precise causal detail.
• The same codes travel in the SI line of baggage messages, giving every downstream carrier immediate visibility of the problem.
• Standardised data enable industry-wide analysis, faster claims processing, accurate interline settlement and robust audit trails.
• Every mishandled bag must generate a correctly coded BIR; compliance is verified through internal and external audits.
• The practice underpins the entire 1743 series and integrates with baggage messaging, liability and local-committee frameworks.
• Real-world use ranges from daily transfer delays to damage claims and strategic performance reviews.
• Data quality depends on accurate front-line coding and continuous training.
• The core code structure has remained stable, providing a reliable foundation for both operational and analytical systems.

Conclusion

RP 1743e is the quiet infrastructure that makes global baggage performance measurable and manageable. By prescribing a single form and a shared vocabulary of irregularity codes, it converts thousands of individual mishandling events into coherent, comparable data. Airlines gain clearer insight into failure points, passengers receive faster and more consistent service, and the industry as a whole can track progress toward lower mishandling rates. In an operation that moves bags across dozens of carriers and hundreds of airports every day, that common language remains indispensable.