AJet delayed flight: the three-hour arrival test

For an AJet delay, begin with the clock rather than the compensation band. Preserve the scheduled endpoint, the first usable door time and any later arrival after a protected connection. A VF departure from Britain or the EU can enter UK261 or EU261 even though the airline is Turkish; a Turkey-origin flight does not gain those regimes merely by landing there. Keeping timing and territorial scope in separate rows prevents a three-hour result from being mistaken for automatic European eligibility.

Measure arrival, not the most visible airport timestamp

For the arrival delay, scheduled and actual landing are not the complete comparison. The legal arrival point is normally when at least one door opens and passengers can leave at the protected destination. Keep the airline's message, airport record and a contemporaneous note rather than relying on a later app estimate. On an EU departure sold under a partner code but shown as operated by AJet, crossing time zones also invites error: place each local time beside a UTC control column and do not subtract two clock faces without conversion.

A connection can move the decisive clock to the last destination

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 arrival delay for AJet. If the itinerary is one contract, the final ticketed arrival can control even where the first aircraft was fewer than three hours late. The passenger should show one PNR or linked ticket coupons, checked-through baggage where available, and the carrier's duty to reroute after the missed connection. Separate self-transfer tickets generally create separate assessments, so a long wait for flight two does not automatically enlarge the legal delay on flight one.

Delay duration and the carrier's defence are separate findings

A result of 7 hours and 27 minutes in file 357 answers only the timing limb. It does not prove who operated, territorial scope or responsibility for the cause. Ask AJet to identify any weather, ATC, security or technical event and its effect on this rotation. Then examine whether spare capacity, a crew solution or reasonable rerouting could have limited the delay. Care during the wait remains a separate issue from the fixed award.

Arrival-time worksheet for an AJet return beginning in Turkey and ending in Britain

• Save the original scheduled arrival before the booking is refreshed.
• Note touchdown, stand arrival and door opening as separate moments.
• Name the source beside every actual time in the chronology.
• Mark the contract's final destination and each ticket number.
• Explain how the first delay caused a missed protected connection.
• Separate a self-transfer with another PNR from the through journey.
• Record meals, hotel and transport offered during the wait.
• Ask for the causal event instead of accepting the word delay as an explanation.

Send a focused request and choose escalation

The useful clock ends at the protected final destination, normally when an aircraft door opens and passengers can leave (AJet; matter 357). Touchdown, parking and the time shown by a tracking app may each be earlier (AJet; record 357).

A short first delay can therefore become a qualifying long arrival delay after a missed protected connection, while a late departure followed by recovery in the air may remain below the threshold (AJet; record 357).

AJet itineraries via Sabiha Gokcen need two clocks: the physical movement of the delayed aircraft and completion of the ticketed journey. For an AJet return beginning in Turkey and ending in Britain, keep the VF sector, the connection offered after disruption and the door-opening time at the last point on the same contract. Then state separately whether the direction receives EU261, UK261 or SHY protection. File 357 is persuasive when the time calculation can be repeated from archived records without relying on a changing app display.

Arrival time is assessed under the law operating on 10 September 2026 (AJet; record 357). Deferred reform provisions must not replace the current delay test or be quoted as though already binding (AJet; case chronology 357).

Close the AJet chronology with three totals: departure lateness for context, door-to-door endpoint lateness for the legal test, and time spent waiting for which care was required. They may differ. File 357 should cite a source for every endpoint and leave an uncertainty visible rather than converting an estimate into a fact.

When station data disagree in an AJet delay case, do not choose the latest-looking screen automatically. Preserve each source, its capture time and what event it purports to show. Airport movement data may establish landing or stand arrival, while a passenger note, crew announcement or carrier record may be needed for disembarkation. Explain any remaining range and calculate whether both ends of that range cross the relevant threshold. A transparent uncertainty is stronger than an exact minute with no provenance.

Audit the time evidence as though the airline disputed the result by five minutes (AJet; record 357). Name the source for scheduled arrival, touchdown, stand arrival, first usable door and final completion after any protected connection (AJet; case chronology 357). Keep local dates beside every timestamp before adding a separate UTC check (AJet; file 357). If a diversion ended at another airport, record the onward transport offered to the agreed destination and the time it actually finished (AJet; matter 357). Where sources conflict, state an interval and request the operational door record rather than selecting the most favourable value (AJet; record 357). The finished chronology should let a reviewer repeat the calculation, identify the single-contract endpoint and separate elapsed time from the carrier's explanation for why the delay occurred (AJet; case chronology 357).

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

Related AJet guides

• AJet cancelled flight: refund or rerouting
• AJet missed connection on one booking
• AJet codeshare: identify the operating carrier
• AJet delayed, lost or damaged baggage claim

FAQ: Questions passengers ask about the arrival delay

Does the three-hour test use take-off delay?

AJet: No. A flight may depart late and recover time, or depart less than three hours late and miss a protected connection. The relevant final arrival must be measured.

Is landing time the legal arrival time?

AJet: Usually not. Door opening that permits passengers to leave is the standard reference, so landing and gate data should remain separate.

What if the first sector lost only ninety minutes?

AJet: A single booking can still qualify when that delay causes a missed connection and arrival at the final ticketed destination is sufficiently late.

Do separate tickets combine their delays?

AJet: Normally they do not. Each contract is assessed on its own unless the documents establish a different legal relationship.

Are meal receipts part of the fixed sum?

AJet: No. Reasonable care expenses are itemised separately and may remain recoverable even if extraordinary circumstances defeat compensation.

Official sources

Sources checked for AJet delayed flight: the three-hour arrival test:

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