BETA
Map The Project Guide How It Works Resources Transparency Record
Active trails
No trails yet.
Use mobile to publish a log.
HOW IT WORKS

Collective sky
monitoring

ContrailsLog is a citizen science platform. Anyone can contribute by reporting sightings and help build a searchable public database.

How to contribute

The process is simple and takes less than two minutes. Every log enriches the database and improves analysis quality.

01

Observe and point your phone at the sky

When you notice anomalous trails, open ContrailsLog and point your phone at the sky. The gyroscope records the exact orientation in real time — like an AR app.

02

Trace the trails point by point

Press the centre button to plant a point where the crosshair points. Follow the trail by moving your phone and add as many points as you like — even beyond the screen edges.

03

Confirm and map

Press ✓ to confirm the trail. The system calculates the real length at 10 km altitude and projects it on the map with precise GPS coordinates.

04

The system monitors weather data

In the 24–72 hours following each report, the system automatically collects real weather data: precipitation, UV/UVB index, cloud cover.

05

Pattern analysis over time

With enough reports, the system searches for statistical correlations between sightings and subsequent weather changes. Results are publicly available and exportable as CSV.

What makes ContrailsLog different

📋
Rigorous methodology
Data collected using a documented and verifiable method, based on official weather APIs and GPS.
📊
Real data
Weather correlations are based on official APIs (OpenWeatherMap), not subjective estimates.
🌍
Distributed
The more users contribute, the denser the network and the more meaningful the analysis.
📷
AR tracking
Trace trails directly on the live camera feed using the gyroscope's 3D rotation matrix.
⚠️
Nota metodologica: ContrailsLog is an observation and data collection platform. The statistical correlations shown emerge directly from user-collected data and official weather APIs.
IDENTIFICATION GUIDE

How to identify
and document trails

A practical guide based on visual observation, atmospheric behaviour, and documentation criteria for quality reports.

Contrails vs Persistent Trails

Aerial trails are normally generated by the condensation of water vapour from engine exhaust at high altitudes. Behaviour varies significantly depending on atmospheric conditions. It is important to distinguish normal from anomalous behaviour to produce accurate reports.

CharacteristicNormal (contrail)Anomalous / Worth reporting
DurationDisappears within seconds or minutesPersistent beyond 30–60 minutes
ExpansionRemains thread-like and dissolvesSpreads progressively into artificial cirrus
CountOccasional, consistent with air trafficMultiple and clustered — 5–15 trails in a short time
PatternTrajectories consistent with flight routesCrossed patterns, grids, tight parallels
Sky effectNo significant changeSky turns milky white within hours
Weather conditionsConsistent with high humidity at altitudePersistent trails even with low humidity or clear sky

How to photograph correctly

A good photo increases the value of the report and makes it easier for other users to confirm.

☀️
Do not photograph the sun directly. Use your hand or an object to cover it if it's in the frame. Protect your eyes and camera sensor.
🏠
Include a fixed reference (building, tree, antenna). It helps estimate trail height and size.
🧭
Document the direction. Take at least one photo with a recognisable orientation. Useful for correlating with flight routes.
⏱️
Time series. If possible, take multiple photos from the same spot at 15–30 minute intervals. Showing a trail's evolution is far more informative.
📱
Enable GPS on your camera. Most smartphones embed GPS coordinates in the JPEG file (EXIF metadata).
🌡️
Note the conditions. Perceived temperature, wind, perceived humidity. Even a rough estimate is useful context.

Trail behaviour over time

💨
Rapid dissipation
The trail disappears within 10–30 seconds. Normal behaviour in dry air with low relative humidity at altitude.
↔️
Thread-like persistence
The trail remains visible for minutes without spreading. May indicate high humidity at altitude — not necessarily anomalous.
🌫️
Lateral expansion
The trail progressively widens into a cloud bank. Behaviour worth documenting with a time series.
🌥️
Sky veiling
Multiple trails merge creating a milky cover. Note the time elapsed since activity began.
💡
Tip: Check Flightradar24 or FlightAware while observing. Verifying whether trails correspond to actual flights is valuable information to include in the report description.

What NOT to do

Do not submit reports without photos. Reports without visual documentation cannot be verified and lower database quality.
Do not use other people's photos. Only upload photos taken personally with verifiable location and time.
Do not draw immediate conclusions. ContrailsLog collects and documents objective data. Let the data speak for itself.
Do not confirm sightings you have not seen. Confirmations must be based on direct observation in the same area and time period.
THE PROJECT

Citizen science
for a transparent sky

ContrailsLog was born from the idea that systematic, rigorous documentation is the most effective tool for observing and understanding what happens in the sky above us.

Real contrails documented with ContrailsLog
Real contrails documented with ContrailsLog

Why ContrailsLog exists

No structured platform currently exists that allows citizens to systematically document anomalous aerial trails and correlate these observations with verifiable weather data.

ContrailsLog aims to fill this gap: building a reliable, methodical archive of aerial trail data, accessible to journalists, researchers, and citizens.

The more users contribute, the denser the network and the more statistically meaningful the analysis. The Project è collettivo per definizione.

Roadmap

✓ Fatto
Frontend — Interactive map
Map with sighting pins, report feed, AR tracker with 3D gyroscope.
In progress
Backend — Database & authentication
User account system, photo upload, report storage, public API.
Next
Automatic weather correlation
Automatic collection of UV/UVB and precipitation data in the 24–72h following each report.
Next
Pattern Detection — Smart pins on the map
The system analyses the database and automatically identifies zones with relevant statistical correlations between reports and weather changes.
Next
Heatmap and historical charts
Visualisation of high-frequency sighting zones, UV/precipitation charts over time, CSV export for researchers.
Future
Public API
REST endpoint accessible to researchers and developers for querying aggregated data.
Future
Hardware — Autonomous sensor
Compact device with UV/UVB sensor, rain gauge, and camera that sends real-time data to the platform.

How the Pattern Detection system works

One of the most ambitious features is the automatic search for statistical correlations between user reports and real weather data collected in the hours and days that follow. The goal is to surface patterns objectively and transparently.

📥
1. Data collection
Each report triggers automatic collection: in the following 24–72h the system records precipitation, UV, UVB, and cloud cover for that area via official weather APIs.
🔢
2. Statistical analysis
The system groups reports by geographic area and period. It calculates the frequency of significant weather changes in the following hours compared to the historical average.
📍
3. Pattern pins on the map
When a zone crosses a statistical threshold — e.g. rain in 65%+ of cases in the following 24h — a special pin appears on the map visible to everyone.
📊
4. Public data
All detected patterns, calculations, and raw data are publicly available and downloadable. Anyone can verify the methodology.
🔬
What the system detects (concrete examples):

📌 Zone with 5+ reports in 7 days + UV variation >20% above average → anomalous UV pattern

📌 Zone with recurring reports + rain within 24h in 70%+ of cases → precipitation correlation

📌 Geographic cluster of reports concentrated in specific time windows → temporal pattern

The system requires a minimum number of reports per zone before showing any pattern, to avoid false positives on insufficient data.
⚖️
Nota metodologica: The system shows statistical correlations between observed events and verifiable weather data. Detected patterns emerge objectively from the collected data.

Project principles

🚫
No advertising
ContrailsLog does not sell advertising space and does not monetise user data.
🛡️
Privacy
Personal data is not sold. GPS positions are approximated to municipal level for anonymous users.
📬
Contact: For collaborations, bug reports, or media enquiries write to gabridecotpnr@gmail.com. The project welcomes collaborations with researchers and journalists.
TRANSPARENCY RECORD

Public record of
pressures & threats

Every attempt to intimidate, silence, or interfere with this project is documented here publicly and permanently. Transparency is our protection.

RECORD ACTIVE — PUBLICLY MONITORED
This page is mirrored and timestamped. Any modification is logged.
🛡 Why this record exists
Documenting aerial trails is a legal act of citizen observation. However, projects like this can attract unwanted attention from institutions, agencies, or private actors who prefer this data not be collected or published.

This record documents any pressure, threat, legal warning, takedown request, surveillance, or interference received by this project. Making these incidents public is the most effective deterrent: intimidation loses its power when it is visible.
📋 What gets recorded
Any of the following, if received, will be documented here with date, source (where known), and nature of the incident:

• Legal threats or cease-and-desist letters
• Requests to remove data, photos, or reports
• Government or agency inquiries
• Pressure on hosting providers or infrastructure
• Surveillance or monitoring of contributors
• Attempts to discredit the project or its contributors
• Account suspensions, domain seizures, or platform bans
• Any form of direct or indirect intimidation

Incident log

All documented incidents, in reverse chronological order.

No incidents recorded
Last verified: 2026-06-10

Our response protocol

📎
Document everything
Every threat, letter, or communication is preserved with timestamps, screenshots, and metadata before any response is made.
📢
Publish immediately
Incidents are made public on this page as quickly as possible. Sunlight is the best disinfectant.
🌐
Mirror & backup
All data and this record are mirrored across multiple independent locations. No single point of failure or censorship.
⚠️
Notice to any party considering interference: Any attempt to suppress, alter, or remove this record or the data collected by ContrailsLog will itself be documented and published here. This record is maintained by private individuals exercising their legal right to observe, document, and publish information of public interest.
RESOURCES

Tools & references

A curated list of tools, databases, and organisations useful for anyone monitoring and documenting aerial activity.

Flight tracking

📡
OpenSky Network
Open-source ADS-B data network. Free API for researchers to query historical flight data.
opensky-network.org ↗

Scientific literature

🔬
IPCC Aviation Report
IPCC assessment of aviation's impact on the atmosphere, including contrail-cirrus cloud formation.
ipcc.ch ↗
📚
NASA Contrail Education
NASA's educational resource on contrail science, formation, and atmospheric effects.
nasa.gov ↗
LOG
--
AZ-- EL-- DIRN
Point at the sky and press the button to start tracing