For researchers & educators

Open
the archive

Everything below comes from the same independent station behind the rest of this site — one fixed terrace under the LPPT approach path, no official airport data mixed in. Free to reuse for coursework, papers or your own analysis. If you publish something with it, we'd genuinely like to hear about it.

Why this exists
Lisbon Finals has always been a citizen-science project first — a single sensor, openly measuring, rather than a claim of official authority. Opening the raw exports is the natural next step: anyone teaching or studying airport noise gets real, dated, local measurements instead of having to take our on-site summaries at face value.
Before you open the archive
One question: why does this data interest you?

It helps us understand who uses the work of a volunteer-run station — and, if you'd like, lets us notify you when new months of data are added. No account needed.

No account, no password, no name required. Nothing here is sold or shared — see the CC BY 4.0 license below.
Access unlocked — enjoy the data.
Flight events

One row per detected aircraft

Every flight the station captured: callsign, aircraft type and airline when identified, flight phase, altitude and speed, plus the acoustic reading tied to that exact pass — peak level, time spent above 70dB, and peak vibration on the terrace. One CSV per month, since the station's first day.

Files current as of 26 Sept 2026, regenerated periodically, not live.
flights_2026-05.csv
9,120 flights · 875 KB
Download CSV
flights_2026-06.csv
9,634 flights · 956 KB
Download CSV
flights_2026-07.csv
10,450 flights · 1.0 MB
Download CSV
flights_2026-08.csv
10,549 flights · 1.0 MB
Download CSV
flights_2026-09.csv
in progress · 8,560 flights · 924 KB
Download CSV
date, time
Detection date/time, UTC.
callsign
ADS-B callsign, or the aircraft's ICAO hex code when no callsign was broadcast.
registration, aircraft_type, airline
Identified when the aircraft's transponder data resolves to a known registration — left blank otherwise.
phase, direction
Landing / takeoff / cruise, and arrival/departure.
altitude_ft, speed_kmh
Altitude and ground speed at closest point to the station.
spl_db, spl_duration_above_s
Peak sound level measured on the terrace, and seconds spent above the 70dB threshold during that single pass.
vibration_peak_mg
Peak terrace vibration during the pass, in milli-g.
wind_speed_kmh, wind_dir_deg
Ambient wind at the time of detection, when logged.
data_quality
Blank when nothing is known to be wrong with the row. Otherwise: peak_corrected (a sensor spike had been recorded as the peak; spl_db now holds the level measured as the plane passed), peak_not_corroborated (a peak of 85dB or more that the station's real-time check could not confirm, value kept), spl_unverifiable (sound value doubtful and impossible to check), sensor_box_moved (sound and vibration disturbed by handling of the sensor box), capture_corrupted_by_restart (capture cut short by a service restart). Values are always left as recorded: filter as your analysis requires.
Continuous ambient data

The raw signal, not just the events

Sound and vibration sampled roughly once per second, around the clock — not just when a flight is detected. This is the same continuous log the station uses internally to catch its own measurement glitches, so it's a genuine working dataset, not a demo export.

Shorter history than the flight tables: continuous logging only started once this need came up.
Files current as of 26 Sept 2026, regenerated periodically, not live.
date, timestamp
Calendar day, and Unix epoch (UTC) for the individual reading.
spl_db / vib_mg
Instantaneous sound level (dB) or vibration (milli-g) at that second — a sample, not a running average.
Using this data
License & attribution
Released under CC BY 4.0 — reuse, adapt and redistribute freely, with credit. A line like Data: Lisbon Finals (lisbonfinals.com) in your methodology section or references is enough.
Worth knowing before you crunch the numbers
This is one consumer-grade sensor (IEC 651 type 2, ±1.5dB manufacturer tolerance) on one terrace, not a calibrated reference network — treat it as local, independent evidence, and cross-check anything load-bearing for your own conclusions.
Questions about the data, or planning to use it for a course or a paper? Write to chronos@lisbonfinals.com — always happy to hear what it's used for.