Airline Operations
Basics

The IOCC is the most integration-dense department. Its systems receive data from PSS, DCS, crew management, MRO, weather feeds, and ATC simultaneously. Understanding these data flows is essential for any airline IT project.

• Flight Dispatch: Legally co-responsible for each flight alongside the captain. Issues the flight release, reviews weather, NOTAMs, ATC restrictions, and fuel planning. No flight departs without a dispatcher's signature
• Crew Scheduling: Manages open-time flying, last-minute crew swaps, and real-time duty-hour tracking. Every crew change cascades through FAR Part 117 recalculation
• Maintenance Control: Monitors all active MEL deferred defects and AOG events live. Coordinates part sourcing, tech dispatch, and aircraft swap with other IOCC teams
• Airport Operations Control (AOC): Manages gate assignments, ground delay program compliance, and airport slot adherence across the network
• Load Planning: Finalises weight-and-balance for each departure — approves or rejects cargo/baggage loads in real-time

• Triggered by: Severe weather, FAA Ground Delay Programs (GDP), aircraft AOG, security events, medical diversions, or crew duty-hour exhaustion
• IOCC simultaneously manages: Aircraft swaps, passenger re-protection (rebooking on next available flights), crew rerouting within legal limits, gate changes, and fuel diversion planning
• Systems involved: PSS, DCS, Crew Management System, MRO, GDS (for rebooking), hotel/voucher systems, and customer notification platforms — all must be synchronised
• Airlines publish IROPS policies (e.g., "re-protect within 2 hours or offer full refund") — these are directly testable business rules

• Divides cabin into fare classes/buckets (Y=full fare business, B M H Q V W=progressively discounted economy). Each bucket has an inventory count that opens/closes dynamically based on demand
• Algorithms set bid prices — the minimum price per seat RM will accept at each booking horizon (how far in advance the booking is made)
• Overbooking: Deliberate and legal — RM models historical no-show rates to sell more seats than physically available (typically 5–15% over capacity). When all passengers show, it triggers denied boarding procedures
• Ancillary revenue streams (seat upgrades, bags, meals, lounge access) now tracked as separate RM categories — increasingly important to profitability

• Operates on 12–36 month horizons; seasonal schedules submitted to IATA and published to GDS 330 days in advance
• Fleet assignment: matching aircraft types (B737, B787, A320, A321XLR) to routes based on range, seat count, fuel economics, and fleet availability
• Slot coordination: At slot-controlled airports (JFK, LGA, DCA, ORD), schedules must be coordinated with the FAA and IATA slot body — violations result in slot loss
• Schedule changes distributed via SSIM files to GDS, codeshare partners, and internal systems — testing schedule change propagation and PNR notifications is a critical regression area

Most airline production defects originate at system boundaries. Understanding the message formats and integration points between systems is the highest-value knowledge for integration and regression testing.

• GDS → PSS: Booking requests flow from travel agencies via GDS. PSS creates PNR, confirms seat inventory, issues e-ticket, and returns confirmation. Protocol: legacy EDIFACT or modern NDC/XML. Latency SLA: <2 seconds for seat confirmation
• PSS → DCS: Check-in system pulls passenger manifest via PNL message ~24 hrs pre-departure. DCS returns real-time check-in updates (ADL messages) back to PSS. Gate boarding scans update PNR coupon status
• DCS → BRS: Checked-in passenger list and bag tag data sent to BRS for reconciliation. BRS notifies DCS when bags are flagged for offload (no-show passenger detection)
• RM → PSS → GDS: Fare class inventory updates (AVS messages) flow RM → PSS → GDS in near-real-time. Closing a fare class must propagate to all GDS channels within <30 seconds
• MRO → IOCC: Aircraft airworthiness status (airworthy / MEL deferred / AOG) feeds continuously to IOCC ops system. Any AOG status change triggers an immediate IOCC response workflow
• PSS → Crew Mgmt: Flight schedule updates feed crew management. Crew assignments confirmed back to IOCC ops system. Schedule changes trigger re-pairing checks

• EDIFACT: Legacy UN electronic data interchange format — still dominant in GDS messaging (PNRGOV, BSGA, BSGT messages). 30+ year old standard, still mandatory to support
• NDC XML (IATA 21.3): Modern REST/XML API standard — enables richer personalised offers, ancillary upsell, and direct connections bypassing GDS fees
• AIDX: IATA Airport Data Exchange — XML standard for flight status sharing between airlines, airports, and handlers. Powers FIDS displays and ground handler alerts
• ACARS: Aircraft Communications Addressing and Reporting System — two-way digital data link. Ground sends: load sheets, weather. Aircraft sends: OOOI events, position reports, engine health data

The PSS is the airline's mission-critical backbone. 15 minutes of downtime can cost $500k+. Every booking, change, and refund flows through PSS — understanding it is foundational for any airline IT project.

• Created (HK): PNR created on booking — 6-character alphanumeric locator (e.g., ABC123). Contains: segments, passengers, contact, fare basis code, SSRs, OSIs, payment reference. Status HK = Holding Confirmed
• Ticketed (TK): E-ticket (13-digit: 3-char IATA airline code + 10-digit serial) issued on payment. Coupon status: O = Open for use. Waits in this state until check-in
• Modified: Voluntary changes (date, name correction, upgrade) — each triggers fare recalculation and potential change fee. Change fee waived if schedule change waiver (SCW) applies
• Checked In: DCS pulls PNR, assigns seat, records baggage count. PSS coupon status remains O. PNR updated with seat number and bag count
• Boarded (F): Gate scan records boarding. Coupon status updated O → F (Flown). No-shows flagged NS → triggers BRS bag offload
• Refunded (R) / Void (V): Post-travel or cancellation. Coupon marked R or V — prevents double-processing. Revenue accounting and loyalty systems triggered

• HK = Holding Confirmed  |  HL = Holding Waitlist  |  KL = Confirmed from waitlist
• SC = Schedule Change (flight time changed)  |  UN = Unable — airline cannot accommodate
• RQ = Request pending  |  TK = Ticketed  |  NS = No Show — triggers BRS bag offload

The GDS is the global marketplace connecting airline seat inventory to hundreds of thousands of travel agents, OTAs, and corporate booking tools worldwide. Understanding GDS architecture is essential for testing distribution, booking, and availability synchronisation workflows.

• Global Distribution System (GDS): A third-party network that aggregates inventory from multiple airlines and distributes it to travel agents and Online Travel Agencies (OTAs). The three major GDS platforms are Amadeus (headquartered in Europe), Sabre (US-based, used natively by American Airlines), and Travelport (Galileo + Worldspan brands)
• Who accesses GDS: Traditional travel agencies (brick-and-mortar and online), corporate travel management companies (TMCs), OTAs like Expedia and Booking.com, and airline reservation agents who use GDS terminals directly
• What airlines pay: Airlines pay a per-segment booking fee to the GDS for each reservation made through the platform. This fee has driven airlines to develop NDC as a direct distribution alternative

• Inventory feeds: Airlines publish seat availability to GDS in real time via AVS (Availability Status) messages. When RM closes a fare class, the update must reach all GDS platforms within SLA (typically under 30 seconds)
• Booking flow: Agent searches availability in GDS → GDS queries airline PSS → PSS confirms seat → GDS creates PNR in its own system → simultaneously triggers PNR creation in airline PSS. Both the GDS PNR and the airline PNR must stay synchronised
• Fare filing: Airlines file fares into ATPCO (Airline Tariff Publishing Company) — a central fare database that GDS platforms read to calculate prices and rules. Fare rule changes in ATPCO propagate to all GDS systems on a scheduled basis
• Schedule distribution: Airlines submit schedule data in SSIM format. GDS platforms ingest this to build their timetable databases — schedule changes must propagate and trigger notifications to all affected existing PNRs
• Ticketing: Once a booking is confirmed, the agent issues an e-ticket through the GDS. The ticket is transmitted to the airline PSS and settled financially through BSP or ARC

• GDS limitation: Traditional GDS uses EDIFACT messaging — a 1980s standard with fixed data fields. It cannot carry rich content like branded fare descriptions, seat photos, bundled ancillary offers, or personalised pricing
• NDC (New Distribution Capability): IATA XML standard enabling airlines to communicate directly with agents via modern REST/XML APIs. Supports dynamic pricing, ancillary bundling, personalisation, and richer content that GDS cannot carry
• Current reality: Most major airlines are mid-migration — running GDS (EDIFACT) and NDC simultaneously. Test environments must validate both channels independently and verify inventory consistency between them
• ATPCO vs dynamic pricing: GDS fares are typically filed in ATPCO in advance. NDC enables dynamic offers computed in real-time — a significant architectural difference requiring different test approaches

• PNR (Passenger Name Record): GDS creates its own PNR (e.g., in Sabre: XKABCD) alongside the airline PSS PNR. Both must remain synchronised — changes in one must reflect in the other
• Segment: Each flight leg in the itinerary. GDS tracks availability, status codes, and fare basis per segment
• Fare Basis Code: Alphanumeric code (e.g., YLOWUS) identifying the exact fare rules applying to a ticket — determines refundability, change fees, baggage allowance, and upgrade eligibility
• Queue: GDS-side message queues used to route PNRs to specific agency desks or airline back-office teams for manual handling (e.g., visa check queue, special services queue)

The DCS is the airport-facing system used by check-in agents, gate agents, and load planners. It bridges the PSS (reservation world) and the physical airport world — from the moment a passenger arrives at check-in to the moment the aircraft door closes. Understanding DCS is critical for testing check-in flows, boarding logic, and weight-and-balance compliance.

• Passenger Check-In: Agent pulls PNR from PSS via PNL message. Verifies passenger identity. Assigns or confirms seat. Collects bag count and weight. Issues boarding pass (printed or mobile). DCS records check-in status and feeds updates back to PSS in real time
• Seat Assignment & Management: DCS maintains the real-time seat map — showing PSS reservations, DCS check-in assignments, blocked seats (crew rest, safety seats), and seats available for upgrade. Must reconcile with PSS seat map without conflicts
• Baggage Processing: Generates 10-digit IATA baggage tags. Records bag count and weight per passenger. Calculates excess baggage fees and triggers EMD creation in PSS. Sends checked-in bag data to BRS for tracking
• Weight & Balance (W&B): DCS integrates with the Load Planning system to calculate real-time W&B as passengers check in. Tracks total aircraft weight (passengers + bags + cargo + fuel) and centre of gravity (CG). Produces the load sheet sent to the captain via ACARS
• Boarding Gate Control: Gate agent uses DCS to scan boarding passes, validate entitlement, manage pre-board groups, process upgrades and standbys, close the gate, and send the final boarding count to load planning and the captain
• Departure Release: Before the OUT event can be recorded, DCS must confirm: minimum FA count met, load sheet accepted by captain, no outstanding security holds, and APIS submission confirmed (international flights)

• PSS → DCS (PNL/ADL): PSS sends the passenger manifest (PNL) to DCS approximately 24 hours before departure. Real-time updates (ADL — Additions and Deletions List) continue until gate closure. DCS must process ADL messages immediately to reflect last-minute changes
• DCS → BRS: As each passenger checks in, DCS sends bag tag data and passenger status to BRS. When a passenger is marked as a no-show (NS), DCS triggers BRS to flag their bags for offload before departure
• DCS → IOCC: DCS sends real-time boarding progress updates to the IOCC operations system — allowing the IOCC to monitor if a flight is tracking to an on-time departure or if intervention is needed
• DCS → ACARS: The final load sheet (weight-and-balance document) is transmitted from the Load Planning module integrated with DCS to the aircraft via ACARS. Captain must digitally accept it before pushback
• DCS → Loyalty System: Check-in event confirms the flight segment for the passenger — triggers pre-flight loyalty checks and post-flight miles posting queues

• Airport Counter Check-In: Agent-assisted. Full service — handles name corrections, special needs, oversized bags, upgrade requests. Agent accesses DCS via dedicated terminal
• Self-Service Kiosk: Passenger-initiated check-in at airport kiosk. Limited to standard transactions — seat changes, boarding pass reprint. Kiosk connects to DCS directly; exceptions routed to agent
• Web/Mobile Check-In: Passenger checks in via app or website 24–1 hours before departure. Boarding pass issued digitally. DCS processes the check-in and updates PSS. Bag drop lane required if checking bags
• Automated Bag Drop (ABD): Passenger uses self-service bag drop unit — scans boarding pass, places bag on belt, system weighs and tags automatically. ABD interfaces directly with DCS and BRS
• Gate Check-In (Go-Show): Passengers who haven't checked in online can be processed at the gate. Last resort — DCS allows gate agents to perform basic check-in and print boarding pass at the gate

• What W&B calculates: Total aircraft weight (Zero Fuel Weight + fuel) must be below Maximum Take-Off Weight (MTOW). Centre of Gravity (CG) must stay within the forward and aft limits certified by the aircraft manufacturer
• Real-time calculation: DCS/Load Planning recalculates W&B dynamically as bags and passengers check in. Last-minute passenger no-shows or cargo changes require W&B recalculation and resubmission
• Load sheet sign-off: The final load sheet is a legally required document. It must be transmitted to the captain and digitally accepted via ACARS before pushback. An unaccepted load sheet = aircraft cannot depart
• Consequence of error: An incorrect W&B can place the aircraft outside its certified CG envelope — creating dangerous handling characteristics on takeoff and landing. This is a safety-critical system where defects have direct aircraft safety implications

• ASM (Available Seat Miles): Seats × Miles Flown. Total capacity offered regardless of how many seats are actually sold. The fundamental supply-side denominator used in all per-unit airline metrics
• RPM (Revenue Passenger Miles): Paying Passengers × Miles Flown. Measures actual demand — the capacity consumed by revenue-generating passengers. Always ≤ ASM
• Load Factor: RPM ÷ ASM × 100. The percentage of available seat capacity filled by paying passengers. When Load Factor = 100%, every seat is occupied by a paying passenger
• RASM (Revenue per ASM): Total Revenue ÷ ASM. Measures how much revenue the airline generates for every unit of capacity it offers. Expressed in cents per seat mile
• CASM (Cost per ASM): Total Operating Cost ÷ ASM. Measures cost efficiency per unit of capacity. When RASM > CASM, the airline is profitable on that flight or network. When CASM exceeds RASM, the operation is loss-making
• Yield: Revenue per RPM. Measures the average fare paid per mile flown by a paying passenger. High yield on thin routes can offset lower load factors. Low yield requires high load factor to cover costs

• D0 (Gate Departure On-Time): Aircraft pushes back at exactly the scheduled minute — ZERO tolerance. 1 minute late = D0 failure. Most demanding OTP metric, used internally by airlines to manage schedule integrity
• A14 (Arrival On-Time): Aircraft arrives within 14 minutes of scheduled arrival. This is the DOT-reported public metric. Airlines publish monthly A14 statistics — consumer-facing and tied to DOT rankings
• IATA Delay Codes: 93 standard delay cause codes (e.g., 93=weather, 41=aircraft damage, 61=late arriving crew). Airlines must record delay codes for all delays — used for root cause analysis, ground handler SLAs, and DOT reporting

• OOOI Events: Out (pushback), Off (takeoff), On (landing), In (gate arrival) — four ACARS-transmitted timestamps that power every downstream OTP, duty-hour, and status system
• MTT (Minimum Turn Time): The minimum allowable window for a full aircraft turnaround — varies by aircraft type and airline. Missing MTT cascades to every subsequent rotation on that aircraft tail — a morning delay compounds throughout the day
• AOG (Aircraft on Ground): Aircraft has a defect preventing airworthiness. All flying stops until a certified technician clears it. AOG events are operationally and financially severe — costs accumulate rapidly from recovery, rerouts, hotels, and passenger compensation
• Block Time: Total time from gate pushback (OUT) to aircraft stop at destination (IN). Used for crew duty-hour calculation and schedule construction. Must be stored and calculated in UTC

Flight tracking combines ATC radar, ADS-B transponder data, ACARS data link, and airline operations systems. Understanding these feeds is essential for building or testing real-time flight status systems, passenger notification platforms, and OTP reporting engines.

Refund processing is one of the most compliance-heavy workflows in airline IT. It involves fare rules, waiver codes, BSP settlement, payment gateway reversal, and DOT-mandated timelines. Defects in refund logic are high-visibility and financially material.

• Void: Ticket cancelled on the same day of issue — before midnight BSP/ARC settlement runs. Full face value returned, no penalty. Simplest path — reverses the ticketing transaction entirely. Coupon → V (Void)
• Involuntary Refund (INVOL): Airline-initiated — cancelled flight, DOT-defined significant delay (>3 hrs domestic), denied boarding, or schedule change beyond passenger tolerance. Full refund mandatory by DOT. Fare rules do NOT apply. Must process within 7 business days (credit card) or 20 business days (cash). Coupon → R (Refunded)
• Voluntary Refund (VOL): Passenger-initiated — subject to fare rules. Non-refundable fares: $0 cash refund, retain as future travel credit (FTC) minus change fee. Refundable fares: full face value minus any applicable cancellation fee
• EMD Refund: Ancillary services (seat fees, bags, upgrades) have separate rules — typically non-refundable unless the associated flight is cancelled (INVOL). Must test EMD refund independent of base ticket

Airline payment processing is a complex, multi-party flow involving payment gateways, card schemes, acquiring banks, BSP/ARC clearing, and fraud prevention systems. Every step has compliance implications and potential failure points that must be tested.

• Credit & Debit Cards: Visa, Mastercard, Amex, and local card schemes (e.g., UnionPay, RuPay). Most common for direct bookings. Card data handled by a PCI-DSS compliant payment gateway — airlines never store raw card numbers
• UATP (Universal Air Travel Plan): Aviation-specific charge card used by corporates and frequent travellers. Issued by airlines directly. Widely accepted in GDS transactions without card scheme fees
• BSP / ARC Cash: Travel agents settle ticket sales through BSP (international) or ARC (US domestic) — weekly financial clearing with the airline. The agent effectively extends credit to the passenger and settles net with the airline
• Airline Travel Bank / Credit Wallet: Stored value in the passenger's loyalty account (future travel credits, vouchers, compensation credits). Applied at booking as a full or partial payment. Must track expiry, fare restrictions, and currency
• Buy Now Pay Later (BNPL): Instalment payment options (Affirm, Klarna, Afterpay) increasingly offered on airline direct channels. The BNPL provider pays the airline upfront; the passenger repays in instalments
• PayPal / Digital Wallets: Apple Pay, Google Pay, PayPal accepted on direct airline websites and apps. Token-based — no card number transmitted to airline systems
• Cash at Airport: Some regions still accept cash at airport ticket offices or check-in. Increasingly rare for international carriers but important for regional and low-cost carriers in cash-heavy markets

• EMD (Electronic Miscellaneous Document): Ancillary services — seat selection, excess baggage, lounge access, upgrades — are charged and tracked via EMD. The EMD has its own document number, coupon status, and refund rules independent of the base ticket. A single booking may have multiple EMDs attached
• Split Payment: Passenger pays part with travel credit and part by card. PSS must handle multi-tender transactions — deducting travel bank balance first, then charging the remaining amount to card. Each tender has its own refund path if the flight is cancelled
• Currency and FX: International bookings may involve multiple currencies. Fare is quoted in the ticketing currency (usually the country of departure). Card is charged in the airline's billing currency or the card's home currency (DCC — Dynamic Currency Conversion). Exchange rate used must be locked at time of ticketing and recorded in the PNR
• Corporate / Invoice Billing: Some corporate accounts are billed via invoice rather than card — monthly or per-trip billing. Airline's AR (Accounts Receivable) system manages credit limits, invoice generation, and payment reconciliation for corporate accounts

Cabin crew are primarily safety professionals — service is secondary to their regulatory safety function. Understanding their roles and legal requirements is critical for testing crew management, scheduling, and compliance systems.

• Captain (PIC — Pilot in Command): Legally responsible for safety of aircraft, crew, and passengers. Final authority on all operational decisions including diversion, fuel uplift, and passenger removal. Holds FAA Airline Transport Pilot (ATP) certificate — minimum 1,500 flight hours (250 for military). Highest seniority on the pairing
• First Officer (FO / Co-Pilot): Operates aircraft equally with captain — "Pilot Flying" and "Pilot Monitoring" roles alternate each leg. Post-Colgan Air regulations (2013): Restricted ATP required — minimum 1,000 hours at Part 121 carriers. Fully qualified to fly the aircraft at all times
• Relief Crew (Long-Haul >12 hrs): Additional pilots and flight attendants rotate in crew rest areas. FAR Part 117 governs maximum flight duty periods based on augmentation level (2-pilot, 3-pilot, 4-pilot operations)

• Purser / Inflight Service Director (ISD): Senior cabin crew member in charge. Responsible for crew safety briefing, cabin compliance, passenger service standards, and all communication with the flight deck. Typically requires 3–5 years as FA plus additional certification and annual recurrent training
• Flight Attendants (FAs): FAR Part 121 Subpart T: minimum 1 FA per 50 passenger seats — this is a hard FAA requirement. A B737-800 (162 seats) requires minimum 4 FAs. FAs hold FAA Flight Attendant Certificate with aircraft-specific qualification — recurrent training required annually
• Primary FA role is safety: Emergency evacuation command, safety demonstrations, hazmat identification, first aid, defibrillator (AED) operation, restraint of disruptive passengers. Service (meals, drinks) is secondary

• FAR Part 117: Maximum flight duty periods (8–14 hrs depending on augmentation and start time), minimum rest between duty periods (10 hrs), cumulative limits: 100 hrs in any 672-hour period, 1,000 hrs per calendar year
• Pre-flight Briefing: Legally required for every flight — covers emergency procedures, special passengers (UMNR, WCHR, MEDA), exit seating eligibility, and catering. Must be documented in the crew records system
• FAA Drug & Alcohol Testing: Random mandatory programme. Positive result = immediate removal from duty. Crew management system must flag grounded crew and trigger open-time coverage workflow
• Exit Row Seating: FAA requires cabin crew to assess exit row passengers for physical and language ability — handled via DCS seat assignment rules and SSR codes. Non-compliant assignment is a safety defect

A successful aircraft turnaround requires 8–10 teams working in parallel within a tight MTT window. Understanding this choreography is essential for testing turnaround management platforms, ground ops integration systems, and milestone tracking tools.

• Aircraft Marshallers / Wing Walkers: Guide aircraft into gate using hand signals or electronic VDGS (Visual Docking Guidance System). Prevent gate strikes. First team to engage on arrival. VDGS shows aircraft type, distance, and lateral alignment in real time
• Ramp Agents: Chock wheels, connect GPU (Ground Power Unit) and PCA (Pre-Conditioned Air), position jetbridge or air stairs. Operate all ramp equipment. GPU preferred over aircraft APU — saves ~120 kg fuel/hr
• Baggage Handlers (Belly Crew): Offload arriving bags in reverse load order, then load departing bags per load plan. Operate tugs, carts, belt loaders, and ULD handlers. Most physically demanding turnaround task
• Fuelling Team: Connects fuel truck — quantity specified by dispatcher/load planner in kg or lbs (never litres/gallons — fuel density varies with temperature). Captain must approve final fuel quantity before fuelling begins. Runs in parallel with boarding
• Catering Team: Catering trucks dock at galley doors. Remove used meal carts, uplift new meals, beverages, and duty-free. Uplift quantity per class matched to passenger load + crew allocation — managed by a catering system integrated with the PSS manifest
• Cabin Cleaning Crew: Rapid clean between flights — lavatories, seat pockets, tray tables, overhead bins checked. Cleaning completion is a critical gate for boarding start — cabin crew must certify cabin ready
• Aircraft Line Maintenance Tech: Walk-around inspection each departure. Clears any MEL items, checks fluid levels, tyre pressure, and visible structure. Signs off the Technical Log (Tech Log) — legally required before flight release. Cannot be skipped regardless of schedule pressure
• Load Planner / Ground Controller: Produces the load plan and W&B (weight-and-balance) calculation. Distributes bags, cargo, and fuel loads to keep aircraft CG within certified limits. Sends final load sheet to flight crew via ACARS — captain must formally accept before pushback is authorised
• Pushback Crew (Tug Operator): Connects tug to nose gear. Headset communication with captain throughout pushback. Releases aircraft to taxi under own power once clear of gate. Records the OUT event trigger — critical ACARS timestamp
• Gate Agent (DCS Departure Control): Manages boarding gate — scans boarding passes, processes upgrades/standbys, manages denied boarding, closes gate at T-10, sends final passenger count to load planner and captain

Every regulation below has been tested in production by real airline systems and has resulted in DOT enforcement actions, FAA certificate penalties, or safety incidents when not implemented correctly. These are your highest-priority test cases.

• Concurrency: Multiple agents modifying the same PNR simultaneously — race conditions can cause seat double-booking or data corruption. Test with 10+ concurrent modification scenarios
• Timezone & UTC handling: All OOOI timestamps, duty-hour calculations, and schedule times must be stored in UTC and displayed in correct local time. A 1-minute error in timezone conversion can cause a crew duty-hour calculation to incorrectly accept or reject an assignment
• Date Line crossings: LAX→SYD crosses the International Date Line — arrival date is +2 days from departure. Block time, duty hours, and OTP calculations must handle this correctly without overflow or negative duration
• DST Transitions: US clocks change at 2:00 AM in March and November. Flights during the crossover can have ambiguous or duplicate timestamps. Test the 2:00 AM hour specifically — clocks spring forward (missing hour) or fall back (duplicate hour)
• Overbooking edge cases: When all overbooked passengers show — denied boarding logic must run in strict priority order: VDB offers first (with correct escalating compensation amounts), then IDB only after VDB fails to fill the gap
• Multi-carrier refund proration: On a 3-segment codeshare itinerary (AA + BA + QF), when one segment is cancelled, the proration of the refund across three carriers' fare rules is extremely complex. Test with real multi-carrier test PNRs

• PNR test dataset covering all SSR types: WCHR, WCHC, WCHS, UMNR, MEDA, VGML, KSML, DEAF, BLND — each must have corresponding handling test
• Multi-carrier codeshare itineraries with partner airline PNR cross-references and interline bag through-check scenarios
• Crew pairings testing boundary conditions of FAR Part 117: exactly at limit (should accept), one minute/hour over limit (must reject), and post-rest re-assignment (must correctly reset counter)
• International flights requiring APIS data — use synthetic but format-valid passport data (correct checksum, valid country codes, correct date formats)
• Refund scenarios matrix: void, voluntary non-refundable, voluntary refundable, involuntary (airline cancel), involuntary (significant delay), waiver types (SCW, weather, bereavement, goodwill), partially-flown, multi-currency
• OOOI event test scenarios: normal sequence, out-of-order events (ON before OFF — should be rejected), missing events (aircraft lands without OFF recorded), and duplicate events

• Build a "golden flight" scenario library — canonical PNRs, crew pairings, and flight states covering all edge cases. Run after every release as a mandatory regression gate
• Include at least one of each: UMNR itinerary, IDB compensation calculation, INVOL refund with 7-day SLA validation, crew pairing at FAR 117 boundary, baggage no-show offload, and APIS submission with CBP response handling
• Performance regression: PSS PNR creation must complete in <2 seconds under 1,000 concurrent bookings. DCS check-in must complete in <1 second. AVS availability update must propagate to GDS in <30 seconds
• Compliance regression: any code change in refund, crew scheduling, or baggage reconciliation modules should trigger a full compliance regression run — these are the highest-cost defect areas post-production