Home/Aviation & Travel/Missed Connection Preparation
Aviation & Travel
Connecting flight records

Missed Connection Preparation: Organize Your Journey Records

Build a private record of the booking, delayed segment, missed connection, rerouting, final arrival, expenses, airline response, and source-backed route context before deciding what to do next.

Preparation workspace, not a calculator

This page helps you structure facts and sources. It does not predict a result, contact an airline, submit an official complaint, or provide legal advice.

Booking context
Single booking, separate tickets, interline, or self-transfer notes
Timeline focus
Delayed segment, missed gate time, rerouting, and final arrival
Evidence focus
Booking, boarding passes, alerts, receipts, and airline messages
Private first
Saved notes go to your workspace for review

Prepare a Missed Connection Record

Capture the facts that usually matter before you choose an airline, regulator, card issuer, insurer, or private review route.

Missed Connection Record Preparation

Add the journey facts you already have. You can complete missing details later.

Your notes are saved into a private workspace so you can organize source-backed next steps.

The workspace stores your notes for preparation. It does not produce remedy amounts, score eligibility, submit a complaint, or contact any airline or authority.

Source-Backed Missed Connection Context

Missed-connection routes are fact-specific. Keep source context separate from your own records so a reviewer can see what happened and which route may apply.

Single booking or self-transfer

The booking structure often changes which passenger-rights route is relevant. Preserve the original ticketing and itinerary evidence.

  • Save the booking confirmation, ticket receipt, passenger names, and every booking reference.
  • Mark whether all segments were sold as one itinerary or purchased separately.
  • Keep travel-agent or online-agency messages that describe transfer responsibilities.

Final arrival timeline

A missed connection record should show the full journey timeline, not only the delay at the connection airport.

  • Record scheduled and actual times for the first segment, connection, rerouting, and final arrival.
  • Save gate-change, delay, cancellation, and rebooking alerts with timestamps.
  • Separate confirmed facts from estimates or memory-based notes.

Care, rerouting, and expenses

If the disruption created waiting time or extra costs, keep the airline response and out-of-pocket records together.

  • Save meal, hotel, local transport, replacement-ticket, and call receipts.
  • Record whether the airline offered care, rerouting, refund, voucher, or no support.
  • Keep copies of anything you submit yourself, including timestamps and confirmation numbers.

Records to Gather Before Taking Action

A useful preparation packet separates itinerary facts, timeline proof, airline messages, expenses, and route notes. That keeps the next step user-controlled and reviewable.

Booking and itinerary

Documents that identify the journey, booking structure, and passengers.

  • Booking confirmation, ticket receipt, passenger names, and booking references.
  • Original route, segment numbers, airports, dates, and scheduled times.
  • Boarding passes, check-in confirmation, bag tags, and app itinerary screenshots.
  • Agency, codeshare, interline, alliance, or self-transfer details.

Timeline and rerouting

Records showing what happened at each stage of the journey.

  • Delay or cancellation alerts for the segment that affected the connection.
  • Gate screenshots, departure-board photos, app notifications, and airport announcements.
  • Missed-connection point, new flight details, standby records, and final arrival time.
  • Airline explanation, denial, or extraordinary-circumstances statement.

Care and expenses

Proof of support offered, support refused, or extra costs paid.

  • Meal, hotel, local transport, replacement travel, phone, or baggage receipts.
  • Care vouchers, hotel letters, taxi vouchers, or written refusal of support.
  • Card statements or payment confirmations for extra costs.
  • Notes showing whether the airline desk, app, or call center handled rerouting.

Route notes

Source-backed context to review before choosing a path.

  • Jurisdiction context: EU261, UK261, Montreal Convention, US DOT, airline policy, insurer, or card issuer.
  • Relevant time limits and escalation steps from official or reliable sources.
  • Questions that still need source checking before any complaint or request is sent.
  • Your preferred next step and any routes you want to avoid.

Possible Routes to Review

The workspace can prepare facts for different routes. It does not decide, submit, or contact anyone for you.

Passenger-rights route

For journeys connected to EU, UK, or other passenger-rights systems, preserve the booking, delay, rerouting, and final-arrival facts needed to compare route rules.

Baggage, expense, or insurer route

If the missed connection caused baggage problems, replacement travel, care costs, or travel-insurance issues, keep those records next to the airline communications.

Review before escalation

Before sending anything externally, review sources, redactions, claim wording, attachments, deadlines, and whether professional advice is needed.

Missed Connection Preparation FAQ

Does this page produce remedy amounts?

Can I use it if I booked separate tickets?

What should I upload first?

Will Compens.ai contact the airline for me?

Is this legal advice?