{
  "title": "Passenger airline gate-event data for AI review",
  "source_page": "https://fiund.com/industries/passenger-airline-gate-event-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A gate return makes the first departure different from the later final departure",
    "context": "An invented flight-event sequence uses invalid service aliases and reference-clock timestamps. It contains no passenger, airport plan, active flight or operational instruction.",
    "records": [
      [
        "AGT1",
        "D1 service A",
        "Observed gate departure 08:00, observed gate return 08:10. Same fictional service instance A/D1."
      ],
      [
        "AGT2",
        "Later A/D1 events",
        "Observed second gate departure 08:30, verified takeoff 08:45, same reference clock. No further gate-return event in the supplied packet."
      ],
      [
        "AGT3",
        "Other records",
        "Estimated departure 07:55 is labeled forecast. Similar service A/D2 has a 07:50 departure; no D1 relationship."
      ]
    ],
    "question": "Which events support A/D1's supplied departure-and-return timeline, and which gate event precedes the verified takeoff?",
    "answer": "AGT1 documents an 08:00 departure followed by an 08:10 return. AGT2 supplies the later 08:30 gate departure and 08:45 verified takeoff, so 08:30 is the last gate departure preceding takeoff in this packet. AGT3's estimate is not observed, and D2 is another service day. Preserve both D1 departures and the return rather than report the earliest timestamp as the final gate departure or confuse gate movement with takeoff.",
    "failureModes": [
      "Using the first gate departure after a documented return as the final departure.",
      "Mixing estimates, takeoff and gate events or matching another day's service."
    ],
    "fields": [
      [
        "Service instance and date",
        "Defines the flight fixture."
      ],
      [
        "Gate departure, return and takeoff type",
        "Separates milestones."
      ],
      [
        "Observed versus estimated time basis",
        "Supports chronology."
      ]
    ],
    "holdout": "Give the second departure an unknown clock offset. Require its order and identity to be reported while precise intervals need authoritative time reconciliation.",
    "boundary": "Use fictional offline logs. Exclude live data and restricted records; this retrospective task directs no aircraft operation."
  }
}