A practical guide to participating in the global citizen-science observation effort modeled on Project Hessdalen. Covers protocol design, data collection standards, equipment requirements, and how to contribute observations that professional researchers can actually use.
The most-credible model for sustained UAP observation in the public record is Project Hessdalen (Case #00131): four decades of continuous instrumented monitoring of a persistent unexplained phenomenon, producing data published in the open scientific literature. The Hessdalen approach is the Council’s recommended template for any amateur effort that aspires to produce data of professional value.
This guide describes how to participate in (or initiate) a Hessdalen-style citizen science effort.
What this guide does NOT do
This guide does not promise that your individual contributions will revolutionize UAP science. Citizen science works at scale: many observers contributing modest, calibrated observations over long periods. Your individual contribution is one data point in a larger dataset. That data point’s value depends entirely on whether it is calibrated, traceable, and consistent with other observers’ data.
Why citizen science matters for UAP
UAP is structurally well-suited to distributed citizen science:
- Phenomena are spatially distributed. A network of geographically dispersed observers covers more sky than any single facility could.
- Phenomena are temporally unpredictable. A network operating continuously catches events single observers would miss.
- Equipment requirements are within civilian budget. A serious observation kit is achievable for $1,500–4,000.
- Most-needed data is straightforward. Position, time, instrumented record, calibration metadata. Not exotic.
The challenge is discipline and standardization — making sure individual contributions can actually be aggregated into useful datasets.
The standardization framework
For your observations to be aggregable with other observers’ data, six things must be standardized:
1. Time, with millisecond-level accuracy
Your device clock must be synchronized to UTC via NTP or GPS. A clock that is “approximately right” is approximately useless when correlating events across observers.
- GPS-based time (from a Garmin GPSMAP 67 or smartphone GPS) is sub-second accurate.
- Network time via NTP is sub-second accurate when the device has reasonable connectivity.
- Verify before each session. Drift accumulates; check it.
2. Position, with sub-meter accuracy
Coordinates of your observation point must be precise. The Council’s standard is the Garmin GPSMAP 67, which provides sub-meter multi-band GNSS accuracy. Phone GPS is typically 3–5m accurate, which is adequate for most aggregation purposes.
Record:
- Latitude (decimal degrees, 5 places minimum)
- Longitude (decimal degrees, 5 places minimum)
- Elevation (meters above sea level)
3. Pointing direction, with degree-level accuracy
For any observation of a specific direction (an object in the sky), record:
- Azimuth (compass bearing in degrees)
- Elevation angle (degrees above horizon)
A smartphone with a digital compass is adequate for most amateur work; a magnetic compass with declination correction works.
4. Instrument metadata
For any recorded media:
- Camera/instrument model
- Lens or sensor specifications (focal length, aperture, sensor size)
- Settings used (ISO, shutter speed, gain, exposure time)
- File format and any post-processing applied
Original files only. Re-encoded social-share files lose the metadata that makes them useful for analysis.
5. Environmental context
For each session:
- Weather (clear, partly cloudy, overcast, fog)
- Visibility (estimated naked-eye limiting magnitude is the photographer-friendly metric)
- Moon phase and altitude
- Approximate light pollution (Bortle scale 1–9)
6. Calibrated baseline
Before recording any observation as anomalous, you should have a documented baseline of:
- What conventional aircraft look like through your equipment, in your location, at typical altitudes.
- What satellites look like (Starlink, ISS, others).
- What bright planets look like at your magnification.
- The local EMF background (Trifield TF2 baseline at your observation point).
The baseline is what lets you recognize anomaly. Without it, “I saw something I couldn’t explain” is unverifiable; with it, “I saw something inconsistent with the X classes of phenomena I am familiar with” is data.
Recommended equipment kit
For productive citizen-science participation:
Minimum kit ($600–800):
- Vortex Diamondback HD 10×42 binoculars
- Rite in the Rain notebook
- Garmin GPSMAP 67 (or equivalent dedicated GPS)
- A smartphone with a planetarium app (Stellarium, SkySafari)
Productive kit ($2,500–3,500):
- The above, plus:
- Celestron StarSense Explorer DX 130AZ (telescope)
- SiOnyx Aurora Pro (night vision recording)
- Trifield TF2 (EMF baseline)
Serious kit ($5,000–8,000):
- The above, plus:
- Celestron NexStar 8SE (replacement primary scope)
- Manfrotto 055 tripod
- Pulsar Helion 2 XP50 (thermal monocular)
- GoPro HERO13 (continuous monitoring)
The Council’s editorial position is that the productive kit is the right entry point for serious citizen-science participation. The minimum kit is for testing whether you have the discipline; the serious kit is for those who already do.
Where to contribute data
Several venues accept structured citizen-science observations:
- The Council — aliencouncil.com/sighting/new accepts structured submissions and adds them to the verdict-engine queue. See Field Guide FG-001 for the submission discipline.
- NUFORC (nuforc.org) — accepts unstructured public reports; useful for aggregate trend analysis.
- MUFON Case Management System (mufon.com) — accepts structured reports for MUFON field-investigator follow-up.
- Project Hessdalen (hessdalen.org) — accepts observations specific to the Hessdalen Valley.
- Local astronomy societies — increasingly accept UAP-adjacent observations as part of their broader sky-monitoring efforts.
Submitting to multiple venues is appropriate. The Council encourages it.
The discipline of negative observation
A subtle but critical aspect of citizen-science discipline is submitting negative observations: nights where you observed and saw nothing anomalous. This is often more valuable than reports of unusual sightings, because it characterizes the observation rate and the typical content of your dataset.
A reporter who submits 200 sessions per year of which 196 are “nothing anomalous, normal sky traffic only” and 4 are “something I cannot identify” is producing far more useful data than a reporter who submits only 4 reports of unusual sightings per year. The former characterizes a sampling base; the latter characterizes only the perceived anomalies.
The Council accepts negative-observation submissions through the same form as positive ones.
Long-term cadence
Sustained citizen-science participation requires sustainable cadence. The Council recommends:
- One full observation session per week at minimum.
- Daily quick check of any continuous-monitoring footage.
- Monthly logbook review of your own data.
- Quarterly review of equipment calibration (clock drift, GPS accuracy, mount alignment, lens cleanliness).
- Annual baseline refresh — re-document your local EMF, light-pollution, and typical-traffic environment.
This is more discipline than most casual observers maintain. It is also the level of discipline that produces data worth aggregating.
Council recommended
For citizen-science participation specifically:
- Garmin GPSMAP 67 — sub-meter coordinates and time
- Rite in the Rain notebook — disciplined logging
- Trifield TF2 — EMF baseline characterization
- SiOnyx Aurora Pro — geotagged low-light recording
Combined with the observation post setup described in Field Guide FG-010, this kit produces submissions the Council scores at the top of its evidentiary tiers.
Related cases
- Case #00131 — Hessdalen lights — the citizen-science model this guide is built on
- Case #00482 — 3I/Atlas — the active 2026 phenomenon citizen-science observation can productively address