No detections in the last 24 hours. The funnel will populate once the public detections feed has activity, or when the ML box POSTs a signed scan artifact to /api/public/scans/ingest.
An autonomous monitoring system has tracked 0 unique aircraft over 0h in Kern County and surrounding airspace. 0% of detections triggered anomaly flags — persistent low-altitude loitering, masked identities, and night operations inconsistent with normal traffic. Shell companies, law enforcement helicopters, and military aircraft appear in coordinated patterns. The FAA has been formally notified. This is the evidence.
Watchtower 2.0 — Live.
AOI headline / global context. The red numbers count detections inside our Area of Interest — the counties this project was built to watch. The grey "/ monitored total" is every detection our receivers picked up, including LA-basin overflow. Same table, same hashes, just two lenses. 0% flagged during baseline — by design. The system observes for 48 hours to learn what normal looks like before it identifies abnormal. After baseline, math chooses.
Recent low-altitude detections
Default view is your AO — the Central-Southern San Joaquin Valley (Kern, Kings, Tulare, Fresno). Los Angeles is included as an opt-in comparison view because our receivers reach that far south, but LAPD/LA County volume was drowning out the Valley signal. Consecutive passes by the same tail are collapsed into one row — click to expand.
Patterned low-altitude overflights that enable visual or electronic intrusion are not "plain view" — they are search by aerial proxy.
ADS-B is unencrypted public broadcast. FAA registry is public record. Documenting and publishing is protected speech.
Altitude deviations, patterned overflights, and operator identity — exactly as received, hashed for chain of custody.
Below 1,500 ft AGL, excluding aircraft on the ground. Altitudes from ADS-B barometric pressure; ±50–100 ft from true AGL depending on terrain.
Pattern Surveillance Indicator — deviation from 48-hour baseline; flags for review, no allegation. Stalking Statute + FAR 91.119 — below FAA minimum safe altitude over populated area.
Hex codes with no N-number or owner are not in the public FAA registry. Possible causes: military, blocked registration, international aircraft, transponder anomaly. Logged as received.
GPS coordinates outside our primary 4-county zone (Kern, Kings, Tulare, Fresno) or within transition airspace between counties.
0 ft with on-ground = true means the aircraft just landed (taxi/ramp). A reading below −100 ft while airborne is an unconfirmed anomaly (no RF layer) — a transponder/barometric outlier that we cannot corroborate against a raw radio-frequency capture. We suppress those from this feed and surface them on ML detections, clearly labeled as unconfirmed until an RF or MLAT source verifies the signal.
| When | Aircraft | Identified owner (FAA registry) | Altitude | Rule | Speed | County | Share |
|---|---|---|---|---|---|---|---|
| No low-altitude activity in this county for the current window. | |||||||
Identification cross-referenced against the public FAA Aircraft Registry (0+ matched operators). Rule column matches active baselines in /rules.
Our ADS-B receivers cover lat 34.0–37.5 / lon −120.5 to −116.5 — roughly LA basin north through the Central Valley. Aircraft detected at latitudes below ~35° (e.g. LAPD Air Support over Los Angeles) appear in our feed but are not operating in Kern/Kings/Tulare/Fresno. Those rows are tagged county OTHER.
Identified operators in this airspace
Mode-S hex matched against the FAA Aircraft Registry. All data is public-source and independently verifiable.