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.
·
·
·
1.37 km

JSON

SensorGrid Lden
sensorgrid_*

lf_*_est

status
n_flights, n_events_over_70db, n_flights_no_event, n_flights_no_data
avg_peak_db, avg_duration_over_70_s, total_duration_over_70_s
avg_temp_c, avg_wind_kmh, dominant_wind_dir
noise_weather_3h.csv

N 100.6 m · AIP Lisbon Finals 1.37 km

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.
hex
heading_deg, vertical_rate_fpm, speed_kts
unix_time, spl_peak_unix_time
temperature_c, humidity_pct, pressure_hpa
cpa_unix_time, cpa_lat, cpa_lon, cpa_dist_m, cpa_slant_m, cpa_alt_amsl_m
peak_lat, peak_lon, peak_dist_m, peak_slant_m, peak_alt_amsl_m
cpa_alt_baro_ft, cpa_alt_geom_ft, peak_alt_baro_ft, cpa_nac_p
tracks_*.zip

date, timestamp
spl_db / vib_mg

time_utc, unix_time / date, timestamp
model_time_local
wind_speed_kmh, wind_gust_kmh, wind_dir_deg
temperature_c, humidity_pct
pressure_hpa, pressure_msl_hpa
precipitation_mm, cloud_cover_pct

date, timestamp
pm1, pm25, pm10
pm1_std, pm25_std, pm10_std
p03, p05, p10, p25, p50, p100
n_frames
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.