INDUSTRY FIELD GUIDE
Airport baggage transfer data for AI trace review
A baggage transfer scan confirms one event.
NAICS 488119 · Other Airport Operations
A baggage transfer scan confirms one event. It may not confirm that the bag reached an onward flight. IATA explains baggage tracking and the operational points at which bags can be tracked. An airport and its partners can use a simulation to test how a model explains an incomplete custody sequence. IATA baggage tracking
Make up three bag IDs, two flights, and a transfer record. Give one bag a matching onward load event and a second only the transfer event. Give the third a reused training tag on a different date. Ask which bag histories can be closed and which need a further event. Keep bag identity, source system, and the time of the observed action in separate fields.
Clear the rights to event records with the airport, carrier, and handling contractor. Omit passenger identities, actual tags, restricted area plans, operational camera footage, and security process details. A mock bag and offline sample log can show the workflow.
Describe a baggage event dataset
Original Fiund exercise
A transfer scan does not establish loading onto the onward flight
An original baggage-log simulation uses invalid bag tags, fictional flights and abstract dates. It includes no passenger, real itinerary, restricted area or operational footage.
| Record | Source | What it records |
|---|---|---|
| BG1 | Bag A history | Service day D1: transfer event A-T followed by confirmed onward load A-L for flight F2, both exact bag A references. |
| BG2 | Bag B history | D1 transfer B-T names flight F2 as intended onward flight. No onward load event supplied. |
| BG3 | Reused tag case | Training bag C has a D2 load event. A D1 question references the same short tag, but no D1 load or date-equivalence record. |
Question for the model
Which bag has a matched D1 onward-load history, and what gaps remain for B and C?
Show the reference answer and checks
BG1 explicitly links A's D1 transfer and onward F2 load. BG2 supports B's transfer and intended flight but no confirmed load. BG3's C event occurs on D2 and cannot establish D1 loading from a reused short tag. Preserve service day, full identity and event type rather than close all histories from a transfer scan or a tag match across dates. The fixture makes no real baggage-delivery guarantee.
- Treating transfer custody as proof of onward loading.
- Using a reused training tag's event from another service day.
Fields to preserve
- Bag, service day and flight alias
- Defines the journey.
- Transfer versus load event
- Separates stages.
- Source system and missing confirmation
- Supports the evidence gap.
Test another case
Add a B load event for a different onward flight. Require loading to be reported with the itinerary mismatch preserved.
Use offline prop logs. Exclude actual tags, passengers and security details; airport, carrier and handler ownership must be reviewed for real event data.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.