How often are these flights late or cancelled?
LCY ↔ FLORENCE
In the twelve months from July 2025 to June 2026, 44.0% of 679 movements arriving into LCY were disrupted — that is, they landed more than fifteen minutes late or were cancelled at short notice.
Put the other way round, 56.0% of 679 movements arrived on time by the industry's fifteen-minute standard. Severe delays were rarer: about one arrival in every 85 crossed the three-hour mark. Lower is better on every figure on this page. These numbers describe what happened on the route; they are not a prediction for any individual flight.
Definitions, denominators and limits
- “Disrupted” means an arrival more than fifteen minutes late or a short-notice cancellation. The denominator is operated movements plus short-notice cancellations.
- Arrivals into the UK airport only; all published carriers.
- Crossing three hours is one condition for compensation, but monthly data cannot establish any individual passenger’s rights.
- Delay cause is not published in the open data.
- Source: CAA punctuality statistics · snapshot 17/08/2026 10:24 · method route-record-v2.1.
0 operations (0.00%) excluded because their published percentages could not be reconciled to whole numbers. Excluded operations enter neither the numerator nor the denominator. Outcome figures and comparisons are unavailable when the excluded share exceeds fifteen percent.
The four numbers at a glance
In the twelve months from July 2025 to June 2026, 44.0% of 679 movements were disrupted and 3.4% of 679 movements were cancelled at short notice.
When a flight was late, it was typically late by the range shown below. The delay is given as a range, not a single number, because the regulator rounds its published percentages and never says how many flights landed exactly on time.
| Disruption share | Short-notice cancellations | Average delay among delayed flights only — bounds | Operations |
|---|---|---|---|
| 44.0% of 679 movements | 3.4% of 679 movements | 30.8–57.2 min; N of delayed flights=276–491 | 679 |
Definitions, denominators and limits
The bounds account for CAA rounding and the unknown number of zero delays. A point average across all operated movements, including punctual ones, would answer a different question and is not used here.
When it is late, how late is it?
Most delays here are short. The ladder below shows how many arrivals crossed each threshold, from a quarter of an hour up to six hours; each rung can only be smaller than the one above it.
Cancellations are counted separately: 3.4% of 679 movements. “One in N” means how many arrivals you would typically see between events at that level.
Delay ladder table: share, movements and one-in-N
| Delay | Share and n | Movements | One delay in every N operations |
|---|---|---|---|
| >15 min | 40.6% of 679 movements | 276 | 2.5 |
| >30 min | 23.1% of 679 movements | 157 | 4.3 |
| >60 min | 9.3% of 679 movements | 63 | 10.8 |
| >120 min | 2.5% of 679 movements | 17 | 39.9 |
| >180 min | 1.2% of 679 movements | 8 | 84.9 |
| >360 min | 0.1% of 679 movements | 1 | 679.0 |
Definitions, denominators and limits
CAA counts delays strictly greater than each threshold, so exactly three hours is inseparable from the previous bucket. The ladder describes the archive, not a forecast.
Slightly late, or occasionally a disaster?
This route runs late less often than most, but when it does go wrong it tends to go badly wrong: its long delays are heavier than on the typical UK route.
The histogram below counts every recorded arrival, from more than fifteen minutes early through to more than six hours late. A tall bar near the middle and a thin right-hand tail is the healthy shape.
Definitions, denominators and limits
Ratio of the long tail to sixteen-to-sixty-minute delays: 0.0376; corpus median 0.0217; 2056 routes in the corpus. The shape is compared conditionally among delays; the class name does not measure absolute frequency. Histogram counts and shares cover all recorded operations including unmatched records; reconstructed uniquely.
Has this route got better or worse since 2018?
Best month: Sep 2020, 8.8% of 57 movements. Worst month: Sep 2024, 59.7% of 67 movements.
The line traces every month in the archive; lower is better. Gaps are months with no published data, never zeros. The 2020 and 2021 readings reflect the pandemic, not normal service.
Every month since 2018, including gaps and suppressed cells
| Month | Disruption on arrivals |
|---|---|
| Jan 2018 | 23.5% of 34 movements — small sample, not ranked |
| Feb 2018 | 36.4% of 33 movements — small sample, not ranked |
| Mar 2018 | 25.0% of 40 movements — small sample, not ranked |
| Apr 2018 | 27.6% of 58 movements |
| May 2018 | 45.3% of 64 movements |
| Jun 2018 | 43.8% of 64 movements |
| Jul 2018 | 37.7% of 77 movements |
| Aug 2018 | 29.5% of 78 movements |
| Sep 2018 | 31.8% of 66 movements |
| Oct 2018 | 46.9% of 32 movements — small sample, not ranked |
| Nov 2018 | suppressed: fewer than twenty movements |
| Dec 2018 | suppressed: fewer than twenty movements |
| Jan 2019 | 25.7% of 35 movements — small sample, not ranked |
| Feb 2019 | 30.6% of 36 movements — small sample, not ranked |
| Mar 2019 | 41.2% of 34 movements — small sample, not ranked |
| Apr 2019 | 26.7% of 30 movements — small sample, not ranked |
| May 2019 | suppressed: fewer than twenty movements |
| Jun 2019 | suppressed: fewer than twenty movements |
| Jul 2019 | suppressed: fewer than twenty movements |
| Aug 2019 | suppressed: fewer than twenty movements |
| Sep 2019 | suppressed: fewer than twenty movements |
| Oct 2019 | suppressed: fewer than twenty movements |
| Nov 2019 | suppressed: fewer than twenty movements |
| Dec 2019 | suppressed: fewer than twenty movements |
| Jan 2020 | 16.7% of 54 movements |
| Feb 2020 | 27.8% of 54 movements |
| Mar 2020 | 34.6% of 26 movements — small sample, not ranked |
| Apr 2020 | suppressed: fewer than twenty movements |
| May 2020 | suppressed: fewer than twenty movements |
| Jun 2020 | suppressed: fewer than twenty movements |
| Jul 2020 | suppressed: fewer than twenty movements |
| Aug 2020 | 6.5% of 31 movements — small sample, not ranked |
| Sep 2020 | 8.8% of 57 movements |
| Oct 2020 | no events in 38 movements — small sample, not ranked |
| Nov 2020 | suppressed: fewer than twenty movements |
| Dec 2020 | suppressed: fewer than twenty movements |
| Jan 2021 | suppressed: fewer than twenty movements |
| Feb 2021 | suppressed: fewer than twenty movements |
| Mar 2021 | suppressed: fewer than twenty movements |
| Apr 2021 | no data |
| May 2021 | no data |
| Jun 2021 | no data |
| Jul 2021 | suppressed: fewer than twenty movements |
| Aug 2021 | 4.8% of 21 movements — small sample, not ranked |
| Sep 2021 | 15.0% of 20 movements — small sample, not ranked |
| Oct 2021 | 20.0% of 25 movements — small sample, not ranked |
| Nov 2021 | 13.3% of 30 movements — small sample, not ranked |
| Dec 2021 | 16.7% of 30 movements — small sample, not ranked |
| Jan 2022 | 12.5% of 24 movements — small sample, not ranked |
| Feb 2022 | 22.2% of 27 movements — small sample, not ranked |
| Mar 2022 | 13.9% of 36 movements — small sample, not ranked |
| Apr 2022 | 14.5% of 55 movements |
| May 2022 | 35.0% of 60 movements |
| Jun 2022 | 58.6% of 58 movements |
| Jul 2022 | 58.9% of 56 movements |
| Aug 2022 | 44.1% of 59 movements |
| Sep 2022 | 44.8% of 58 movements |
| Oct 2022 | 19.3% of 57 movements |
| Nov 2022 | 18.0% of 50 movements |
| Dec 2022 | 32.0% of 50 movements |
| Jan 2023 | 11.5% of 52 movements |
| Feb 2023 | 20.4% of 49 movements — small sample, not ranked |
| Mar 2023 | 35.2% of 54 movements |
| Apr 2023 | 35.2% of 54 movements |
| May 2023 | 33.3% of 60 movements |
| Jun 2023 | 50.9% of 55 movements |
| Jul 2023 | 47.3% of 55 movements |
| Aug 2023 | 42.4% of 59 movements |
| Sep 2023 | 42.9% of 56 movements |
| Oct 2023 | 36.2% of 58 movements |
| Nov 2023 | 45.5% of 55 movements |
| Dec 2023 | 32.1% of 53 movements |
| Jan 2024 | 25.0% of 44 movements — small sample, not ranked |
| Feb 2024 | 19.6% of 51 movements |
| Mar 2024 | 16.1% of 56 movements |
| Apr 2024 | 23.0% of 61 movements |
| May 2024 | 29.4% of 68 movements |
| Jun 2024 | 53.7% of 67 movements |
| Jul 2024 | 55.9% of 68 movements |
| Aug 2024 | 32.4% of 71 movements |
| Sep 2024 | 59.7% of 67 movements |
| Oct 2024 | 48.5% of 66 movements |
| Nov 2024 | 33.9% of 56 movements |
| Dec 2024 | 56.1% of 57 movements |
| Jan 2025 | 38.3% of 47 movements — small sample, not ranked |
| Feb 2025 | 17.6% of 51 movements |
| Mar 2025 | 35.0% of 60 movements |
| Apr 2025 | 20.3% of 59 movements |
| May 2025 | 27.0% of 63 movements |
| Jun 2025 | 39.1% of 64 movements |
| Jul 2025 | 40.0% of 65 movements |
| Aug 2025 | 51.5% of 68 movements |
| Sep 2025 | 55.6% of 63 movements |
| Oct 2025 | 47.5% of 59 movements |
| Nov 2025 | 27.5% of 51 movements |
| Dec 2025 | 42.9% of 49 movements — small sample, not ranked |
| Jan 2026 | 31.0% of 42 movements — small sample, not ranked |
| Feb 2026 | 27.9% of 43 movements — small sample, not ranked |
| Mar 2026 | 53.8% of 52 movements |
| Apr 2026 | 37.3% of 59 movements |
| May 2026 | 51.5% of 66 movements |
| Jun 2026 | 50.0% of 62 movements |
What did the big disruptions actually do here?
Each named event below is shown against this route’s own baseline for the twelve months before it, and against how long the route took to get back to that baseline.
A month worse than baseline is not proof the named event caused it: the open data carry no delay-cause field at all. Some events sit near the edge of the archive, which limits how long a recovery can be traced.
| Event | Direction | Disruption that month | Baseline before | Return to baseline |
|---|---|---|---|---|
| Pandemic regime · Jun 2020 | Arrivals | suppressed: fewer than twenty movements | no complete baseline | not enough data: needs a complete baseline and a publishable event month |
| Pandemic regime · Jun 2020 | Departures | suppressed: fewer than twenty movements | no complete baseline | not enough data: needs a complete baseline and a publishable event month |
| Summer 2022 breakdown · Jul 2022 | Arrivals | 58.9% of 56 movements | no complete baseline | not enough data: needs a complete baseline and a publishable event month |
| Summer 2022 breakdown · Jul 2022 | Departures | 50.9% of 57 movements | no complete baseline | not enough data: needs a complete baseline and a publishable event month |
| NATS system failure · Aug 2023 | Arrivals | 42.4% of 59 movements | 32.7% across 653 flights | returned after 4 months |
| NATS system failure · Aug 2023 | Departures | 33.9% of 59 movements | 31.7% across 666 flights | returned after 2 months |
| Heathrow fire closure · Mar 2025 | Arrivals | 35.0% of 60 movements | 38.7% across 735 flights | returned the next month |
| Heathrow fire closure · Mar 2025 | Departures | 28.3% of 60 movements | 32.8% across 746 flights | returned the next month |
Definitions, denominators and limits
The baseline is the unweighted mean share over the twelve preceding calendar months. The return window is the following eight months, up to the end of the archive. Return means the first observed value at or below the baseline; it is not the duration of the disruption itself. If the event month is already below the baseline, counting still starts the month after. Gaps and suppressed cells are not treated as zeros or as recovery.
Which time of year has historically been hardest?
June has historically been the hardest month on this route: in a typical June, 50.5% of arrivals were disrupted, measured across 6 Junes in the archive. February has been the calmest, at 22.2% across 7 Februarys.
Even June has ranged from 39.1% to 58.6% in different years, so this is a record of what happened, not a forecast of what will. Lower is better throughout.
Each cell is one calendar month of one year; the number is the share of that month’s arrivals that were disrupted. Darker means worse. A blank cell means no published data, not zero.
Month-by-month table: median, observed range and sample
| Month | Median | Observed range | Sample |
|---|---|---|---|
| Jan | 25.0% | 11.5–38.3% | 7 months, 278 flights |
| Feb | 22.2% | 17.6–36.4% | 7 months, 290 flights |
| Mar | 35.0% | 13.9–53.8% | 7 months, 332 flights |
| Apr | 26.7% | 14.5–37.3% | 7 months, 376 flights |
| May | 34.2% | 27.0–51.5% | 6 months, 381 flights |
| Jun | 50.5% | 39.1–58.6% | 6 months, 370 flights |
| Jul | 47.3% | 37.7–58.9% | 5 months, 321 flights |
| Aug | 42.4% | 29.5–51.5% | 5 months, 335 flights |
| Sep | 44.8% | 31.8–59.7% | 5 months, 310 flights |
| Oct | 46.9% | 19.3–48.5% | 5 months, 272 flights |
| Nov | 30.7% | 18.0–45.5% | 4 months, 212 flights |
| Dec | 37.5% | 32.0–56.1% | 4 months, 209 flights |
Definitions, denominators and limits
The matrix shows the last eight calendar years, including an incomplete final year; the start of the archive is kept in the history above. Seasonal summaries use the whole available archive, excluding the pandemic regime 2020–2021; this is an observed range, not a forecast. Zero events, missing data and suppressed cells are marked separately. † marks a small sample, described but not ranked. For ranges the colour follows the upper bound.
Which airline has the better record here?
Only one carrier published enough flights here to report: Ba Cityflyer Ltd, 44.0% of 679 movements disrupted.
Figures cover arrivals, July 2025 to June 2026; lower is better in every column. Carriers with fewer than twenty published flights are suppressed rather than shown as zero. The page makes no ranking: the operations behind these shares are not matched for aircraft, time of day or season.
Airline comparison table: operations, cancellations, three-hour delays and data quality
| Airline | Operations | Disruption | Cancellations | >180 min | Data quality |
|---|---|---|---|---|---|
| Ba Cityflyer | 679 | 44.0% of 679 movements | 3.4% of 679 movements | 1.2% of 679 movements | descriptive comparison |
| City Jet | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Klm | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
The noise check is a descriptive approximation assuming independent operations. Delay correlation and mix differences are not estimated; no ranking is derived.
Would another UK airport have been better?
Among UK airports flying to this city with enough flights to publish, LGW had the lowest disruption share at 23.7% of 775 movements and EDI the highest at 52.0% of 50 movements. This route sits at 44.0% of 679 movements.
Each figure is arrivals into that UK airport, all carriers combined, over the same twelve months. It is a historical record, not a recommendation about where to fly from, and it says nothing about getting to or from each airport on the ground.
Airport comparison table: operations, cancellations, three-hour delays and data quality
| Other UK airport to the same city | Operations | Disruption | Cancellations | >180 min | Data quality |
|---|---|---|---|---|---|
| Bfs ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Bhd ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Bhx ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Brs ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Doncaster-Sheffield ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Edi ↔ Florence | 50 | 52.0% of 50 movements | 2.0% of 50 movements | no events in 50 movements | descriptive comparison |
| Ema ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Jer ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Lgw ↔ Florence | 775 | 23.7% of 775 movements | 1.4% of 775 movements | 0.3% of 775 movements | descriptive comparison |
| Lhr ↔ Florence | 519 | 27.7% of 519 movements | 1.5% of 519 movements | 1.9% of 519 movements | descriptive comparison |
| Lpl ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Ltn ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Man ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Sen ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Sou ↔ Florence | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed: fewer than twenty movements | suppressed |
| Stn ↔ Florence | 50 | 38.0% of 50 movements | no events in 50 movements | no events in 50 movements | descriptive comparison |
Does the direction you are flying change anything?
Yes: arrivals into LCY ran 44.0% of 679 movements disrupted, departures 29.5% of 685 movements.
It matters legally as well as practically: a departure from the UK and an arrival into the UK on a UK or EU carrier fall under different conditions, and a departure delay does not establish a late arrival at your final destination.
Arrivals and departures side by side
| Direction | Disruption | Cancellations | Over three hours |
|---|---|---|---|
| Arrivals into LCY | 44.0% of 679 movements | 3.4% of 679 movements | 1.2% of 679 movements |
| Departures from LCY | 29.5% of 685 movements | 0.7% of 685 movements | 0.4% of 685 movements |
Definitions, denominators and limits
How many flights here crossed the three-hour mark?
The table below counts arrivals and departures that ran more than three hours late — the threshold that is one of the conditions for compensation — across the whole archive and within the last six years.
The pound figure beside each count is arithmetic, not money anyone received: it is the count multiplied by the maximum statutory amount for this distance band. Whether any of those flights actually qualified is not knowable from this data.
| Direction | Window | Flights over three hours | Arithmetic statutory ceiling |
|---|---|---|---|
| Arrivals | Whole archive · Jan 2018–Jun 2026 | 52 flights out of 4,097 | 52 × £220 = £11,440 |
| Arrivals | Last 72 months · Jul 2020–Jun 2026 | 41 flights out of 3,272 | 41 × £220 = £9,020 |
| Departures | Whole archive · Jan 2018–Jun 2026 | 16 flights out of 4,165 | 16 × £220 = £3,520 |
| Departures | Last 72 months · Jul 2020–Jun 2026 | 11 flights out of 3,323 | 11 × £220 = £2,420 |
Definitions, denominators and limits
Full formula: the count is the sum of the two tail buckets across months, carriers and service types in one direction; the ceiling is that count multiplied by the maximum statutory amount for the distance band. The condition is: if every such delay had been the carrier's fault and a claim had been filed on every one of them.
This is conditional arithmetic over operations: passenger numbers, legal applicability and the number of claims are all unknown. For departures it is an arithmetic scenario only, because arrival at the final point is not observed. For long routes the maximum ceiling is used; any reduction in the payable amount is not calculated.
The archive window is counted from the last month of data, not from today: this is not a limitation check for an individual case. The CAA states six years for England and Wales and five for Scotland. CAA: time limits and how to complain. Information, not a legal service.
The facts about this route
Route reference table: codes, distance, frequency, archive span
| Field | Value |
|---|---|
| UK airport | LONDON CITY · LCY |
| Final point / country | FLORENCE / ITALY |
| Final point codes | FLR / LIRQ |
| Great-circle distance | 1,193 km |
| Maximum statutory amount for the band | £220 |
| Average operated arrivals per day | 1.80 |
| Presence in the latest twelve-month window | operations present in every month of the latest twelve-month window |
| First and last active month | Jan 2018–Jun 2026 |
| Months with operations in the archive | 90 |
origin_destination is the final point of the CAA service, not evidence of a nonstop connection. The distance joins the coordinates of the named airports; the actual track is unknown. Frequency describes published operations.
What this data cannot tell you
Delay cause is not published in the regulator's open data. Monthly aggregates describe a population, not a specific flight. Cells below twenty operations are suppressed; twenty to forty-nine are descriptive only and not ranked. Arrivals and departures do not add up. Cancellations are short-notice only, by the CAA definition. A movement is not the same as a scheduled flight.
0 operations (0.00%) excluded because their published percentages could not be reconciled to whole numbers. Excluded operations enter neither the numerator nor the denominator. Outcome figures and comparisons are unavailable when the excluded share exceeds fifteen percent.
Data-quality counters for this route
Zero observed events does not mean zero risk. Operator coverage against the Summary file is not established in this record; comparisons are limited to the published population.
Unmatched records: 0; all recorded operations: 679; excluded by quarantine: 0.
Quick answers
How often is this route disrupted?
44.0% of 679 movements over July 2025 to June 2026. Arrivals into the UK airport; all published carriers.
How many flights are cancelled at short notice?
3.4% of 679 movements in the same window.
How many delays crossed three hours?
1.2% of 679 movements in the same window; these are observed movements, not a count of claims.
What does the delay distribution look like?
rare but severe. The class compares the tail with short delays across routes in the corpus.
What distance is used?
1,193 km, great-circle.
Can compensation entitlement be established here?
No. The cause and the circumstances of an individual flight are unknown. Official CAA conditions.
Why do some cells say "no data"?
That month is absent from the published series. Small cells carry a separate "suppressed" marker; a gap is never replaced by a zero.
How this was calculated
Dataset version, input hashes and reconstruction rules
Dataset version: 396da8dde2874f14; method route-record-v2.1.
Versioned register of every number and the entity map · Input hashes · Correction log · Reconstruction and formulas.
Reconstruction: integer counts inside the rounding bounds of shares of D, summing to M. Ambiguity is preserved as a range of feasible counts; non-convergence stays in quarantine. The map of codes and coordinates is pinned by hash alongside the data. Raw CSV files are not included in the published output.
Your trip has already gone wrong — what now?
The official route to complain
Contact the airline first, then the relevant ADR body or the CAA. The right to care is assessed separately from compensation; time limits and circumstances are checked case by case. CAA: how to complain.