AGP · EN
Flight Data Methodology for Málaga-Costa del Sol Airport
The platform collects airport-scoped flight observations, stores source evidence, normalizes identities and duplicate listings, and derives public views only when their own coverage and quality gates pass. Recorded data is useful evidence, not an official airport record or a promise of a future schedule.
Source and airport scope
Operational flight observations are collected from AirLabs for Málaga-Costa del Sol Airport (AGP) and stored under the airport's own identity. Aena, airline channels and terminal displays remain the appropriate places to confirm a time-critical passenger decision. The database and statistics published here are independently processed records, not an official Aena report.
Every public query is scoped to AGP. Records belonging to another airport must not enter this airport's counts, pages or schema.
Collection, local time and freshness
The operational collector runs on an automated schedule. Public boards show a data date and freshness state so a cached or incomplete result is not silently presented as live. Source timestamps are stored consistently and displayed in the airport's local timezone, Europe/Madrid.
A successful empty provider response may correctly mean that no current flights were returned. It is not automatically treated as a collection failure.
Normalization and physical-flight counting
Source records are normalized before publication. The process reconciles flight-number formats, airport and airline identities, direction, scheduled date and time, and operational status. Duplicate provider snapshots and identical records are suppressed. Codeshare or marketing listings are grouped where the evidence supports one physical operated flight.
Unusable or unresolved rows may be withheld from a public table. The page exposes input and output counts where relevant so suppression is visible rather than hidden.
How punctuality is measured
Timing analysis requires both a usable scheduled time and an observed actual time. A flight is classed as early when it is more than 3 minutes before schedule, on time from 3 minutes early through 5 minutes late, and late when it is more than 5 minutes after schedule. Flights without a usable actual time are excluded from that timing denominator.
Average delay refers to the observed delay among flights included by the relevant view. A cancellation is reported separately and is not converted into an invented arrival or departure delay.
Statistics, samples and partial states
Counts, shares, route rankings, airline activity and delay summaries are derived from the retained observations that pass each view's contract. Percentages show their measured denominator. Small samples can produce a partial or collecting state and may suppress a percentage, ranking or narrative claim.
A recorded route proves activity within the stated evidence window only. It does not prove year-round operation, a future frequency or ticket availability.
Archive completeness and search indexing
A historical arrivals or departures page becomes eligible for indexing only when the day is complete and the direction has sufficient usable identity coverage and public rows. Current, partial, stale or weak-evidence pages can remain reachable while carrying a noindex instruction.
Retained flight data may cover up to 1095 days, but the actual public history begins when reliable collection for this airport began. The maximum retention period is not a claim that every day in that period exists.
Corrections and reprocessing
Identity mappings, normalization rules and quality gates may be corrected when evidence improves. A correction can cause historical counts or derived statistics to be recalculated. We prefer a revised, explainable result to preserving a known error.
To report a data problem, identify the URL, flight date, direction and the disputed value, then write to contact (at) malagaairports (dot) com. Do not send booking credentials or payment data.
Important limitations
Provider feeds can be delayed, incomplete, duplicated or temporarily empty. Airline names, operating-carrier relationships and route identities can change. The platform uses fail-closed gates to limit unsupported public claims, but no automated feed can guarantee perfect real-time accuracy.
Always confirm boarding, gate, terminal, baggage and disruption instructions with the operating airline and the responsible official airport channel.
Methodology owner
This methodology and the derived public data products are maintained by Domino Services Ltd., the independent publisher of this guide. Questions and evidence-backed corrections can be sent to contact (at) malagaairports (dot) com.