Python tool for aircraft Doppler audio geolocation using historical ADS-B flight data (Source-available)
ENF timestamp recovery: research status
Electrical Network Frequency (ENF) may provide recording-time evidence when a real mains-related signal is captured in the audio and a matching, timestamped grid reference exists. A stationary 50/60 Hz tone by itself is not enough: fans, power supplies, motors and other equipment can produce similar tones. ENF cannot be reported as a timestamp until the extracted frequency variation has been matched to an independent reference and ambiguity and clock drift have been assessed.
Current prototype
scripts/scan_enf_signal.py screens real audio
for peaks near 50/60 Hz and their first three harmonics. It reports per-window
frequency estimates, local spectral prominence and coverage in a new output
directory. It does not identify grid hum, compare a historical reference,
estimate UTC, infer a location, or alter the aircraft search request. A strong
screen result is only a reason to investigate the trace further.
Example for a new output directory:
python scripts/scan_enf_signal.py recording.mp3 \
--output-dir results/enf-screening-v1
The default uses the same 4 kHz mono decoding path already used by DOPPLERGEIST. The 4-second window and 1-second hop are screening settings, not a calibrated ENF extractor. A future timestamp estimator should test each usable band against real references. One sufficiently strong line can be evaluated at its known or hypothesized harmonic order; additional harmonics are optional corroboration, not an acceptance requirement. Longer windows and held-out real recordings are still needed to validate frequency precision and false-match risk.
First real-audio screen (2026-11-03)
The prototype screened 50 real recordings at 4 kHz: 24 files from the publisher-site-labelled corpus, 5 videos without an exact microphone point, 20 AeroSonic recordings, and the active one-hour upload. The site labels are not independent recording-time evidence. The scanner did not read truth-coordinate files or pass any result into aircraft search.
For this exploratory summary, a persistent tone candidate means at least one of the six 50/60 Hz harmonic bands had local prominence of at least 10 dB in at least 80% of its complete 4-second windows (1-second hop). This is only a spectral peak threshold; it does not distinguish grid frequency from a motor, power supply, interference or other sound.
| Real-audio group | Recordings | Persistent tone candidate | Two harmonics at one nominal base (descriptive) |
|---|---|---|---|
| Publisher-site-labelled corpus | 24 | 2 | 0 |
| Unknown exact microphone point | 5 | 0 | 0 |
| AeroSonic recordings | 20 | 0 | 0 |
| Active one-hour upload | 1 | 0 | 0 |
Two recordings had at least one persistent tone candidate: site-914.mp3 (a
50 Hz fundamental and a separate 120 Hz band) and site-919.mp3 (a 50 Hz
fundamental). No recording had two persistent bands at one nominal base. That
last column is descriptive only: one coherent line remains eligible for a
future reference match, and the lack of a second harmonic is not grounds to
reject it. The one-hour upload had no band meeting this screen's persistence
threshold; that does not prove its audio lacks a weaker or longer-window ENF
trace. No reference matching or UTC estimate was attempted, so this screen
establishes neither ENF availability nor timestamp recovery rates.
Full per-window traces, summaries and SHA-256 receipts are preserved locally
at /home/cinna/.local/state/dopplergeist-enf-screening-20261103/corpus-v1.
The recordings and their local paths are not included in the repository.
Reference-data audit
- The official FNET/GridEye real-time display describes its live plot as real-time frequency measurements.
- The FNET table display warns that displayed frequency values are sample data, not current grid measurements, and that actual values have been hidden from that display since 2018.
- OpenENF documents public references for parts of Europe and says public North American reference data is unavailable.
- nate-griff/enf is a useful implementation reference. Its README describes QIFFT harmonic extraction and FFT-accelerated sliding correlation, but labels the tool an investigative aid rather than a proof system. Its documented collector captures the current FNET chart, and its checked-in daily CSVs cover 2026-03-20 through 2026-05-12. That archive cannot match the active 2026-09-08 upload.
- A 2025 ENF extraction evaluation reports that target duration, reference duration and signal-to-noise ratio affect timestamp accuracy: Maiberger, Gusakov and Routtenberg, CISS 2025.
FNET can support building a prospective archive by collecting its real-time charts, but this does not create historical references for past recordings. The repository's image-derived reference series also needs independent validation of sampling cadence, frequency calibration, missing-data handling and redistribution terms before it can be used for an accepted timestamp.
Integration gate
Only consider passing an ENF-derived time window into the existing aircraft
pipeline after real recordings with independently established sample-zero UTC
have been matched to a genuine historical grid reference. Keep extraction
quality, reference provenance, clock-rate drift, alternative timestamp peaks
and match separation in the result. Do not require multiple harmonics: one
well-tracked line can support a timestamp when its independent reference match
is unique and strong enough under the measured uncertainty. Other harmonics
can strengthen that evidence when present. If no usable line exists, the
reference is missing, or the match remains ambiguous, return the existing
needs_input/inconclusive path. ENF region identification is at most coarse
interconnection evidence; it is not an observer coordinate.
The initial screen must run on DOPPLERGEIST's real audio only. Do not synthesize hum, fill missing reference intervals, tune the matcher on the recording under evaluation, or feed recording truth into extraction or reference search.