AJet missed connection on one booking

A missed AJet connection needs a ticket map before it needs a delay calculation. Mark whether the sectors share one transport contract, where baggage was checked and who issued the replacement after the break at SAW or another airport. Only then identify the final protected endpoint and its door-opening time. Two separately purchased VF flights may sit in one travel-app view without becoming one journey, while a genuine through booking can carry the arrival test beyond the first delayed sector.

Prove one contract before using the final-destination rule

The visual itinerary in an agency app may place flights together without creating one contract. For the missed connection, compare the PNR, ticket numbers, coupon sequence, baggage destination and who assumed responsibility after the first delay. A through booking via SAW can make the final ticketed arrival relevant, whereas separately bought self-transfer flights are normally separate contracts with separate delay clocks; this finding on ticket continuity controls the analysis of the missed connection for AJet. If AJet or its partner rerouted the passenger to the last point without requiring a new purchase, that behaviour can support continuity, but the underlying ticket remains the strongest document.

Build one timeline from first gate to final door

For an AJet return beginning in Turkey and ending in Britain, record scheduled arrival of sector one, gate closure for the connection, actual door opening, transfer path, replacement offer and final door opening. The legal issue is usually the delay at the final protected destination on the single booking, not the number of minutes spent at the connecting airport. Case 829 should also show whether the original connection was reasonably bookable and whether the passenger presented on time rather than voluntarily abandoning it.

Self-transfer losses need a different recovery theory

Two separately bought flights normally mean the first operator did not promise transport to the second ticket's destination. The passenger can still assess compensation for the first contract, refund rights on any cancelled sector, insurance and proven contractual loss, but should not present the self-transfer endpoint as automatically protected. If a platform advertised a connection guarantee, preserve its terms and claim route. Keep meals or hotel during an airline-controlled wait distinct from the price of a replacement onward ticket.

Connection reconstruction for case 829

• Place PNR, e-ticket numbers and coupons beside one another.
• Check the final destination printed on the baggage tag.
• Record door opening, connection gate closure and transfer route.
• Show that the passenger reported to the carrier and accepted rerouting.
• Name the operator of the delayed sector and every replacement sector.
• Mark a new PNR or separately paid ticket as a possible contract break.
• Keep a platform connection guarantee with its original conditions.
• Calculate final arrival only after choosing the protected contract.

Send a focused request and choose escalation

A single booking can make the last ticketed destination the relevant arrival point (AJet; matter 829). Separate self-transfer bookings normally leave each carrier responsible only for its own contract and do not guarantee the onward sector (AJet; record 829).

Matching dates in an agency itinerary are not enough: compare PNRs, ticket numbers, checked-baggage destination and the carrier's rerouting duty after the first disruption (AJet; record 829).

Connections at SAW are not all legally alike. AJet may issue one VF contract to the last destination, while an online seller can place two independent tickets on one screen. For a VF-operated journey beginning at a London airport and connecting at SAW, file 829 must show ticket numbers, baggage arrangements, the original minimum connection and who provided rerouting. Only after that continuity decision should the final delay be measured. If the onward ticket is separate, preserve any seller guarantee and assess it without attributing a destination AJet never promised.

Contract continuity and journey's protected endpoint are examined under the framework applicable on 10 September 2026 (AJet; record 829). Later reform thresholds have no current role in this missed-connection calculation (AJet; case chronology 829).

If AJet rerouted only part of the journey in file 829, preserve the unused coupons and the sequence in which they were reissued. The record should reveal whether the carrier continued to recognise the original final point or ended its undertaking at SAW, leaving a genuinely independent ticket outside the protected contract.

AJet passengers should preserve how the carrier handled the missed sector at SAW. A new boarding document issued automatically, baggage retagging and hotel provision can corroborate that AJet treated the trip as continuous. They are evidence, not an irrebuttable label. Compare them with the original ticket coupons and payment record. If the onward leg was bought later, state whether the first carrier ever accepted responsibility for it and avoid calculating endpoint delay until that contractual question is answered.

Reconstruct the broken journey from transport documents rather than the itinerary picture in an agency app (AJet; record 829). Align individual ticket references, coupons, PNRs, baggage destination, scheduled minimum connection and every carrier-issued replacement (AJet; case chronology 829). Record arrival at the first gate, closure of the onward gate, instructions at the transfer desk and time a door permitted exit at the last contractual point (AJet; file 829). If the traveller bought the onward sector independently, preserve any platform guarantee and insurance terms but mark the contractual break (AJet; matter 829). If the airline took responsibility for rerouting to the final point, retain that conduct as supporting evidence without discarding the original ticket (AJet; record 829). This map decides which endpoint belongs in the delay calculation and which losses need a different legal route (AJet; case chronology 829).

Name the missing record, responsible company and next action in the closing sentence (AJet; record 829). Reconcile the balance with every payment already received, label any estimate and retain the dated calculation used (AJet; case chronology 829). The result remains actionable without turning an unresolved condition into certainty (AJet; file 829).

Related AJet guides

• AJet compensation claim form and evidence
• AJet hotel, meals and replacement transport costs
• AJet flight compensation for delay or cancellation
• AJet and EU261: which flights are covered?

FAQ: Questions passengers ask about the missed connection

Does one booking reference prove a through ticket?

AJet: It is strong evidence but should be read with ticket numbers, coupons and the airline's rerouting responsibility.

Can ninety minutes on the first flight lead to compensation?

AJet: Yes, where it causes a missed connection on one protected booking and the final arrival satisfies the legal threshold.

Are self-transfer tickets treated as one journey?

AJet: Usually not. A platform display or matching dates do not by themselves make the first carrier promise the onward destination.

Which airline receives the claim?

AJet: Start with the operating carrier of the sector that caused the protected disruption, then explain the final result on the single contract.

Can replacement-ticket costs be claimed?

AJet: Potentially, if useful rerouting was owed but not provided. Prove necessity, attempts to obtain help and a proportionate price.

Official sources

Sources checked for AJet missed connection on one booking:

• Regulation (EC) No 261/2004.
• UK CAA: delays and cancellations.
• AJet passenger-rights brochure.
• AJet feedback form.
• AJet conditions of carriage.
• Montreal Convention.