God's Eye // UAP

▶ Open the live app

It runs in your browser with nothing to install and no sign-up or API keys.

Open it in your language: English · Español · Français · Deutsch · Português · Italiano · Nederlands · Polski · Türkçe · Русский · العربية · हिन्दी · Bahasa Indonesia · 日本語 · 한국어 · 中文

made by domw99

Features · Quick start · How it works · Open data · Data sources · Reading it honestly · Contributing

---

God's Eye // UAP puts every well-documented UFO/UAP encounter on a 3D globe. You can replay each one along a reconstructed flight path, read the official U.S. and French files, search 22,000 pages of the MUFON, APRO, NICAP and CUFOS journals, and watch the footage. You can also check the ordinary explanations yourself: what was in the sky, the weather, military airspace and rocket launches. Beside the Earth is the Moon (EARTH | MOON in the top bar), a globe of it in the same layout with its landing sites and the lunar reports. It is a UAP-only edition of Bilawal Sidhu's God's Eye View.

USS Nimitz "Tic Tac", 2004. From the globe of cases into the encounter off San Diego: the flight paths replay as the view circles, then it switches to night vision. ▶ Watch the 22-second video (MP4)

261 curated case files1561 → 2026, 47 countries and territories	174 official U.S. releasesAARO / PURSUE footage via DVIDS	10,096 Project Blue Book filesUSAF scans, 1947–1969, on the map	2,768 GEIPAN filesFrance's official cases, graded A–D
485 MUFON Journal issues1967–2008 · 2,517 report places mapped	873 research journal issuesAPRO · NICAP · CUFOS · MUFON chapters	22,000 journal pagesfull-text searchable in the app	80,332 civilian reportsNUFORC, as a density layer

Features

🌍 Every documented encounter on one globe

• 261 curated case files from 1561 to 2026, in 47 countries and territories. New in 2.11, ten more: the Trinity crash story, New Mexico's green fireballs, McDivitt's sighting on Gemini 4, the Betz sphere, the Allagash abductions, Paul Bennewitz and the lights over Manzano, the Yukon "mothership", the Haiti videos, the Miami mall "alien" and the drones that closed Europe's airports in 2025. New in 2.6, 77 more cases: 21 from the United States (Blue Book files such as the Long Beach F-86s, the cutter Sebago and Captain Killian, Malmstrom 1975, Lake Michigan 1994, America West 564, and solved ones like the Aztec hoax, the 2010 "mystery missile" contrail and the Navy image shown to Congress that was drones), 18 from Europe and the former Soviet Union (Tunguska, Fátima, the MoD's Flying Saucer Working Party, Ummo, four GEIPAN files, the KGB's Kapustin Yar package, Howden Moor), 19 from Latin America (Gravataí, Trancas, VASP 169, Corporal Valdés, Chile's CEFAA and Uruguay's CRIDOVNI rulings, the Chinese balloon over Colombia, the "Nazca mummies", the Long March plume over Buenos Aires) and 19 from Canada, Asia, Oceania, Africa and the Middle East (Nowra 1954, CFS Falconbridge, the Moroccan re-entry cables, Kuwait's oil fields, Chelyabinsk, the Naga fireballs, Jeffreys Bay, the Falcon 9 spirals, and AARO's Gulf of Oman, UAE and Syria releases). New in 2.5: Ellsworth AFB (1953), the Zond IV re-entry (1968), Jimmy Carter's light at Leary (1969), the Cergy-Pontoise hoax (1979), the 1990 Proton re-entry over France, the Ladakh "drones" that were Jupiter and Venus (2012), the Iridium-4 launch over Los Angeles (2017), AARO's Southeast Asia triangles (2017) and Eglin balloon (2023) resolutions, the Sendai balloon (2020), the FBI's north-eastern orb files (2021), the Las Vegas backyard call (2023) and the Yemen Hellfire video shown to Congress (2024). Examples: Kenneth Arnold, Washington 1952, the Kinross F-89, the RB-47, Socorro, the Hills, Minot AFB 1968, Rendlesham, Tehran 1976, JAL 1628, the Belgian wave, the Phoenix Lights, the Nimitz "Tic Tac", Gimbal/GoFast, Aguadilla, the 2023 shoot-downs and the 2024 New Jersey drones. Latest additions: the 1913 Great Meteor Procession, Clyde Tombaugh's 1949 sighting, the Kirtland AFB tower (1957), the Antarctic sightings of 1965, the Paulding Light, Wurtsmith AFB and its tanker chase (1975), Alitalia over Kent (1991), Air France 3532 (1994), British Airways 5061 (1995), Bariloche (1995), the Colorado drones (2019), Langley AFB (2023) and the 2024 drones over the U.S. bases in England. New in 1.3: Cussac, Quarouble, Zanfretta, the Broad Haven schoolchildren, Ilkley Moor, the Wonsan B-29s, the Vilas-Boas claim, Coyame, the 2018 Irish airline sightings and American 2292. New in 1.2: the Delphos ring, Pascagoula, the Coyne helicopter, Loring AFB, La Joya, Boianai, Dalnegorsk, the Knowles family, the 1991 Mexico City eclipse videos, Chile's 2014 Navy helicopter video, Ubatuba and Maury Island.
• Each case has evidence tags, witnesses, a timeline, a 0–10 documentation score and a status: , , or . The official or best-supported explanation is shown first.

✈️ Replay the encounter, from the witness's seat

🎛 See it through a sensor

Betty and Barney Hill, 1961. The car's route and the craft's reported path replayed over the White Mountains, cycling through Normal → NVG → FLIR → Ironbow.

There are seven sensor looks, rendered as real-time post-processing shaders (keys 1–7). They keep the picture sharp at any zoom, so markers and labels stay readable; the look comes from tone, grain and scanlines, not blur:

• Normal
• NVG: image-intensifier gain, shot noise and raster lines.
• FLIR white-hot and FLIR Ironbow, with a cold-to-hot scale on screen.
• CRT: scanlines, a shadow mask and a slightly curved glass.
• Noir and Snow (new in 1.2, an idea from the original God's Eye View): high-contrast film grain with a vignette, and a cold, frosted look with falling flakes.

3D buildings are free, and off until you want them. Turn on OpenStreetMap buildings (via OpenFreeMap) under MAP or in the layer list, and they appear as you zoom into any town; Fly to ground view on a case turns them on for you. If you want Google's photorealistic 3D tiles instead, paste your own key under MAP.

🗺 Map styles, day and night, and a real sky

New in 1.1: a real star sky and city lights, day and night lighting, four map styles, and NASA's picture of a case's day from orbit. ▶ Watch the 21-second video (MP4)

• Map style (MAP or M): Satellite, Dark, Streets or Topographic, all keyless. Over the satellite map you can add place names and borders, which fade out close in where 3D buildings take over.

• Lighting: Auto lights an open case by the sun at the moment it happened, with city lights on the night side; Day and Night hold that look everywhere; Off, where a first visit starts, keeps the globe evenly lit. The four-button switch in the top bar (☀ auto, day, night, off) changes it in one click, without opening any settings.

• Hide the years bar (HIDE on the bar, or Y) for more room; the panels grow into the space, the choice is remembered, and ▲ YEARS brings it back.

• Earthquakes (new in 1.2): the last 24 hours from the USGS, sized and coloured by magnitude. Strong quakes are sometimes reported as booms or odd lights, so it helps check a same-day sighting.

• Fireballs (new in 2.0): the 888 bright meteors that U.S. government sensors have recorded since 1988 (NASA CNEOS), drawn as comets sized by energy, with the year bar filtering them. A fireball outshines the Moon for a few seconds, so it is a familiar cause of "a light that crossed the sky and went out". Press B to turn the view north up and P to tilt it; the compass turns with the view.

• A symbol for every layer: rings for cases, diamonds for official releases, triangles for your own sightings, and a file, shield, hexagon, open book, spark and seismograph for Blue Book, GEIPAN, MUFON, the research archives, civilian reports and earthquakes, so you can tell the dots apart at a glance.

🔭 Check it yourself

• What did I see? (E) Enter a time, place, direction and how it moved. The app ranks the ordinary explanations it can test:

  • planets, bright stars and the Moon;
  • sunlit satellites, Starlink trains and the ISS;
  • rocket launches;
  • lanterns or balloons on the wind;
  • aircraft from an airfield near you (about 11,000 airports and military fields, from OurAirports);
  • the aurora, when the geomagnetic Kp index was high enough for it to reach your latitude in a dark sky;
  • a bright fireball in NASA's record close to you in time and place (new in 2.0).

  Live flights need a server, so aircraft elsewhere are listed as not checkable. Above, a bright, still light low in the WSW at dusk comes back as Venus; a coloured glow over North Dakota at midnight on 14 March 1989 comes back as the aurora of the great storm (Kp 8-).

• The sky at that moment, for every case: Sun, Moon phase, planets and bright stars. Objects named in the official explanation are circled. For the Hills in 1961, Jupiter sits low in the SSW beside the Moon, just as the Air Force file says.

• Historical weather since 1940 (ERA5): cloud layers, wind at 10 m and 100 m, and whether a slow object moved with the wind.

• That day from orbit, for cases since 2000: NASA's true-colour picture of the whole Earth that day (MODIS on the Terra satellite) laid over the globe. Below, O'Hare on 7 November 2006 under the solid overcast the witnesses described.

• Military airspace: which FAA restricted or warning areas a case falls in.

• Geomagnetic activity, for every case since 1932: the Kp index for the three hours of the case (GFZ Potsdam), NOAA's storm scale, and whether an aurora could have been seen from there (it needs a dark sky and a latitude the auroral oval reaches at that Kp). It is a classic cause of strange lights at low latitudes.

• Bright fireballs nearby, for every case since 1988: any fireball in NASA's record within 600 km and 3 hours, with how long before or after, how far and in which direction. The record holds only the bigger events, so an empty answer does not rule one out.

• Nearest airfields: the closest airports and military fields, with the distance and direction, and a note that aircraft on approach (landing lights, apparently hanging still) are a common cause of reports near them. The list is of airfields as they are today, and says so.

🗂 The official record

🇫🇷 GEIPAN: France's official UAP files

GEIPAN is the UAP office of CNES, the French space agency, and the longest-running government UAP office in the world (since 1977, first as GEPAN). It has published its case files since 2007. The GEIPAN layer (blue) puts all 2,768 cases from its published files (1937–2018) on the map:

• Each case sits at its commune, geocoded offline from GeoNames. 95% are placed to the commune; the rest to their department.
• GEIPAN's own finding comes first: A (identified), B (probably identified), C (not enough information) or D (unidentified after investigation). The status filters use it, and the unexplained D cases are drawn brightest.
• The dossier shows GEIPAN's summary in French, with a link to the full file (testimonies, investigation, often photos) and a one-click English translation.
• 2,607 cases have an observation time, so the dossier adds the sky, the weather and the day/night lighting at that moment, as it does for curated cases.
• Curated French cases list their GEIPAN files. Trans-en-Provence and Valensole both link to their class D files.

🛸 The MUFON files

MUFON and The Black Vault released the Mutual UFO Network's journal free as "The MUFON Archive". The app brings it onto the map:

• 485 issues of Skylook and the MUFON UFO Journal (1967–2008), readable page by page inside the app. The library (G) lists every issue by year, plus 61 series of MUFON chapter newsletters.
• The MUFON files layer (violet) marks 2,517 places named in the journal's sighting reports. They were found automatically in the OCR text and geocoded offline. Each links to the exact page, with a short quote.
• Case dossiers list the journal pages that discuss them. 119 of the 261 cases have coverage, for example:
  • 26 pages on Lonnie Zamora's 1964 Socorro sighting;
  • 60 on Travis Walton;
  • 39 on the 2008 Stephenville lights.
• MUFON's live case database (CMS) is members-only, and its terms forbid redistribution, so the app links to it and to MUFON's reporting form rather than copying it.

📚 The research archives, searchable

📊 Statistics, and cards to share

🎬 Story mode and side-by-side comparison

🌙 Space & Moon

Space & Moon (SPACE & MOON in the top bar, or K) collects reports from beyond the atmosphere, 18 in all, each with what was reported, what is documented and the best explanation, and with its sources.

• In orbit (8): the Mercury "fireflies", Gemini 4's cylinder over Hawaii, Gemini 7's "bogey", the object Apollo 11 saw on the way to the Moon, Apollo 17's drifting particles, the Apollo "light flashes" (cosmic rays crossing the eye), the STS-48 video and the STS-75 tether incident. Where the position is known, SHOW ON THE GLOBE flies there.
• The Moon (6): transient lunar phenomena on a photograph of the near side with numbered pins: Gervase of Canterbury in 1178, Herschel's "volcanoes" in 1787, Kozyrev's spectrum at Alphonsus in 1958, Greenacre and Barr at Aristarchus in 1963, the Apollo crews' flashes, and NASA's brightest recorded impact flash (2013), which was solved. Reports at the same place fan out above a dot so none is hidden.
• Deep space (4): the "Face on Mars", the "Wow!" signal, 'Oumuamua and 3I/ATLAS.
• NASA's own files are linked. The NASA documents and recordings in the 2026 PURSUE releases (the Mercury flights, the Apollo 12, 14, 16 and 17 debriefings, Cooper's 1962 interview) are listed with the reports they bear on, and open in the app like the other official records.

The pins are placed by a mapping fitted to known craters on the photograph (Gregory H. Revera, CC BY-SA 3.0), so they are accurate to about a degree. Every report has its own link (#/space/<id>), and ⧉ COPY LINK on a card copies it.

The Moon, beside the Earth

New in 1.3 and 1.4: the Moon beside the Earth, Space & Moon, and 10 more cases. ▶ Watch the 34-second video (MP4)

EARTH | MOON at the left of the top bar (or U) switches between the two worlds, and the Moon is laid out like the Earth: the same top bar, the list of places on the left with search, layers and sorting, a dossier on the right, the HUD, the zoom and reset controls, and the same sensor looks and lighting. It also opens from the Moon tab of Space & Moon, or with a link: #/moon, or #/moon/<place or report> such as #/moon/apollo-17 or #/moon/tycho.

• A real globe. Drag to turn it, scroll or pinch to zoom, from the whole Moon down to about a kilometre above the surface. It is drawn on the Moon's own ellipsoid (radius 1,737.4 km) with the Lunar Reconnaissance Orbiter Camera global mosaic from NASA Moon Trek, 100 metres to the pixel. If NASA's tiles can't be reached, a 2,048-pixel copy of the mosaic that ships with the app keeps the Moon turning.
• Layers, as on the Earth. Lunar reports, landing sites, seas and basins, craters, and mountains and valleys each turn on and off, on the globe and in the list. Relief lays the laser altimeter's colour-coded heights over the photographs. 89 named places are labelled as you zoom in (the names button in the map controls, or N, hides them), and the 25 landing and impact sites run from Luna 2 (1959) through Apollo 11 to 17 and Chang'e 3 to 6 to Chandrayaan-3, SLIM and IM-1.
• Symbols, as on the Earth. Each kind of place has its own map symbol, on the globe, in the list and in the layer switches: a flag for the six crewed Apollo landings, a lander for the 18 robotic ones, a starburst where Luna 2 struck, waves for the seas, rings for the great basins, a crater, peaks for the mountains and valleys, and a numbered ring for each report; reports at the same place (Aristarchus has three) stand side by side. The landing symbols and report pins shrink as you back away, so the whole Moon stays readable on a phone, and come back to full size as you close in.
• A dossier for every place and report. Click a pin, or a row in the list, to fly there and open it on the right: what the place is and where, when a mission landed and how high the Sun stood, or for a lunar report its assessment, summary, NASA files and sources. The six reports are numbered as in Space & Moon, including the far-side one the photograph can't show (Giordano Bruno, for Gervase of Canterbury).
• Lit by the Sun of the moment. With the lighting on AUTO, a landing site is lit as the Sun stood at the landing (Apollo 11 touched down with the Sun 10.7° up, and the map shows the terminator just west of Tranquility Base), and a report with a known night is lit for that night. DAY lights the Moon from where you look, NIGHT shows it by earthshine, and OFF lights it evenly. The Sun's position comes from the IAU model of the Moon's rotation; the Apollo landings come out within half a degree of their documented Sun angles.
• The sensor looks (1–7: NVG, FLIR, Ironbow, CRT, Noir, Snow) work on the Moon too.
• Search by name, English name ("Sea of Tranquility"), mission or year, and sort by kind, date or name. Arrow keys turn the Moon, + − zoom, 0 or R resets, [ ] step through the list, and Esc closes the dossier, then returns to the Earth. On a phone the list is a sheet at the bottom that folds away, as on the Earth.

📱 Works on a phone, installs like an app, and speaks 16 languages

The first visit on a phone says the app has more room on a computer (once). On phones and tablets the buttons are sized for a finger, and the layout holds up with the phone held sideways (the top bar keeps to two rows). Playing a flight path clears the screen down to the globe and a slim playback bar (DETAILS brings the panels back), the phone's Back button closes an open dialog, and the on-screen keyboard no longer covers the field you are typing in.

New in 1.2: Noir and Snow looks, lighting in the top bar, a hideable years bar, 16 languages, live earthquakes and 12 more cases. ▶ Watch the 23-second video (MP4)

Save it as an app: on a phone, ⤓ INSTALL APP in the top bar installs it in one tap where the browser allows it, and otherwise shows the exact steps for your browser (Share → Add to Home Screen on iPhone, the ⋮ menu on Android). It opens full screen, respects the notch and the home bar, reopens quickly, and works offline for what you have already looked at. Press and hold the icon for shortcuts: a random case, WHAT DID I SEE?, the official files and the Moon. The globe only draws when something changes and matches its sharpness to the device, so it stays smooth and easy on the battery. Phones get a lighter copy of the star sky. If your system is set to reduce motion, the camera cuts instead of flying.

Your language. A link can open in a chosen language by adding ?lang= and a code, for example ?lang=es. The picker in the top bar switches the whole interface between English, Español, Français, Deutsch, Português, Italiano, Nederlands, Polski, Türkçe, Русский, العربية (right to left), हिन्दी, Bahasa Indonesia, 日本語, 한국어 and 中文. It starts in your browser's language and remembers your choice. Buttons, labels, filters, the sky, weather and launch lines, and the messages are translated; the case texts, archive descriptions and quotations stay as published, so the evidence is never paraphrased. To add or improve a language, edit one file in src/i18n/locales/ (keys are the English texts); a test checks that every language covers every text the code asks for.

Also included:

• Similar cases at the end of each case file: the cases most like it by kind of encounter, evidence, shape, country and era.
• Keyboard and screen readers: a skip link, labelled regions, dialogs that keep the keyboard inside them and make the page behind inert, and focus that moves into a case file and back to its row in the list. The browser tests run an automated accessibility check (axe) on the start screen, a case file and the dialogs.
• Reference photos, films and audio for each case.
• One-click Google satellite, Street View and Google Earth 3D links.
• A ground-view fly-in.
• A guided tour (T).
• A personal sighting log (L), kept in your browser and exportable as GeoJSON, with links to report officially.
• Suggest a correction on every case.

Quick start

git clone https://github.com/domw99/Gods-Eye-UAPs.git
cd Gods-Eye-UAPs
npm ci
npm run dev        # http://localhost:5173

That's it. Nothing needs a key: the imagery, terrain, 3D buildings, weather, launches, satellites and place search all use free, keyless services.

In the app, click MAP (or press M) and paste a Google Maps Platform key with the Map Tiles API enabled. The key stays in that browser's localStorage and is sent only to tile.googleapis.com. You can remove it there at any time.

If you host your own copy, you can build keys in instead: copy .env.example to .env.

Key	What it adds
VITE_GOOGLE_MAPS_API_KEY	Google Photorealistic 3D Tiles for every visitor (Map Tiles API)
VITE_CESIUM_ION_TOKEN	Cesium World Terrain, plus Google 3D Tiles through ion

Restrict browser keys to your domain, because anything built into the site is public.

Key	Action	Key	Action
1–7	Sensor modes (…, Noir, Snow)	E	What did I see?
/	Search	V	Witness view (during playback)
[ ]	Previous / next case	M	Map: style, place names, lighting, 3D
Space	Play / pause the flight path	G	Files library (government + MUFON)
T	Guided tour	L	Log a sighting
R	Reset view (whole globe, north up)	+ −	Zoom toward the centre
N	Near me	S	Statistics
B	North up (turn the view so north is at the top)	P	Tilt the view, or look straight down again
K	Space & Moon	U	Switch between the Earth and the Moon (on the Moon: arrows turn, + − zoom, 0 reset, N names)
C	Group nearby markers on / off	Esc	Close, or back to the previous dialog
H	Hide the HUD	Browser Back	The record you had open before
Y	Hide / show the years bar	`	Show the frame rate
D	Lighting: off (the start) → auto → day → night	F	Clean view: hide every panel
O	Orbit the middle of the screen; from far out, turn the Earth	← ↑ → ↓	Fly the camera (Shift: turn and tilt)
years bar (focused)	← → move the range · Shift later end · Alt earlier end · PageUp PageDown ten years	Esc	Clear the range

Link	Opens
#/case/nimitz-tic-tac-2004	A curated case
#/official/1007777	An official release (DVIDS id)
#/bluebook/1952-07-7273984-Tremonton-Utah-1377-	A Blue Book file
#/geipan/1981-01-00849	A GEIPAN file (Trans-en-Provence)
#/mufon/2002_05/1	A MUFON Journal page (issue, page index)
#/journal/AFU_19711100_APRO_Bulletin_November-December/0	A research-archive page (APRO Bulletin, Nov–Dec 1971)
#/near/33.3943,-104.5230/Roswell	Everything reported near a place
?mode=nvg	Start in a sensor mode
?layers=bluebook,geipan,mufon	Start with extra layers on
?view=-104.5,33.7,25000,0,-35	Start at a camera position (lon, lat, height m, heading°, pitch°)

How it works

It is a static site with no backend. Datasets are built by scripts ahead of time and shipped as JSON. Everything live is fetched straight from keyless public APIs in the browser, and the sky and satellite positions are computed on the device.

flowchart LR
  subgraph build["Build time: scripts/ and weekly CI"]
    direction TB
    DVIDS["DVIDS / AARO<br/>official releases"] --> S1["sync-dvids.mjs"]
    IA["Internet Archive<br/>Blue Book scans"] --> S2["build-bluebook.mjs"]
    FAA["FAA special-use<br/>airspace"] --> S3["build-airspace.mjs"]
    NUF["NUFORC<br/>(geocoded)"] --> S4["build-nuforc.mjs"]
    KP["GFZ Potsdam<br/>Kp index"] --> S8["build-kp.mjs"]
    FB["NASA CNEOS<br/>fireballs"] --> S10["build-fireballs.mjs"]
    OA["OurAirports<br/>airfields"] --> S9["build-airfields.mjs"]
    MUF["MUFON Journal<br/>OCR (Internet Archive)"] --> S5["build-mufon.mjs"]
    GEI["GEIPAN<br/>published CSV"] --> S6["build-geipan.mjs"]
    ARC["APRO · NICAP · CUFOS<br/>OCR (Internet Archive)"] --> S7["build-journals.mjs"]
    S5 & S7 --> S11["build-textindex.mjs"]
  end
  S1 & S2 & S3 & S4 & S5 & S6 & S7 & S8 & S9 & S10 & S11 --> DATA[("public/data/*.json")]
  CASES["src/data/cases/*.js<br/>261 curated cases"] --> APP
  DATA --> APP["<b>Browser app</b><br/>Vite · CesiumJS<br/>astronomy-engine<br/>satellite.js"]
  LIVE["<b>Live, keyless APIs</b><br/>Esri imagery · terrain<br/>OpenFreeMap buildings<br/>CelesTrak TLEs<br/>Launch Library 2<br/>USGS earthquakes<br/>Open-Meteo weather<br/>Wikipedia · Photon"] --> APP

Built to stay quick. The globe draws only when something changes, and a still globe redraws every 2 s. It starts without waiting for the imagery's service description (the loading screen clears about 40% sooner in local tests), asks the map servers for up to 18 tiles at a time, and uses coarser tiles while the camera moves. Markers and labels keep their GPU buffers when they change: with every layer on, a search uploads about 3 MB instead of 35 MB. Repeat visits load Cesium and the data from the offline cache without rewriting it.

Layer	Code
Globe, imagery, terrain, 3D tiles, key handling	src/app/viewer.js
Rendering on demand, device quality, dynamic resolution	src/app/quality.js
Map styles and place names; centred zoom-out; keyboard flying and orbit	src/app/basemap.js, src/app/zoom.js, src/app/flycam.js
NVG / FLIR / Ironbow / CRT / Noir / Snow shaders	src/app/effects.js
Interface languages (t(), dictionaries loaded on demand, right-to-left)	src/i18n/index.js, src/i18n/locales/*.js
Save to the home screen (one-tap install, steps per browser)	src/app/install.js
Case markers, flight paths & playback, witness view	src/layers/items.js, src/layers/tracks.js
Label decluttering; Blue Book, GEIPAN, MUFON, research-archive, NUFORC & earthquake points, satellites, launches, airspace, buildings	src/layers/*.js
Sky, weather, launches, airspace, GEIPAN classes, journal pages and full-text search, sighting-checker scoring	src/services/*.js
Dossier, list, timeline, modals, sky chart, story mode, statistics, share cards, Space & Moon	src/ui/*.js
Space & Moon entries and the Moon picture; "similar cases" ranking	src/data/space.js, public/space/, src/data/similar.js
The Moon: places, landing sites and their times, the globe on the Moon's ellipsoid, the Sun's position on it, the Earth-style layout	src/data/moon.js, src/app/moonglobe.js, src/app/moonsun.js, src/ui/moonview.js, public/space/moon-wac-2k.jpg

src/
  app/        viewer.js (globe, imagery, terrain, 3D tiles, star sky) · effects.js (NVG/FLIR/CRT shaders)
              quality.js (render on demand, device quality) · horizon.js (markers hidden behind the Earth)
              basemap.js (map styles, place names) · zoom.js (centred zoom-out) · flycam.js (keys, orbit)
  data/       cases/ (curated case files) · govFiles.js · regions.js · taxonomy.js · items.js
  layers/     items.js (case & release markers) · tracks.js (flight paths + playback) · billboard-buffers.js (markers keep their GPU buffers)
              points.js (Blue Book / GEIPAN / MUFON / NUFORC) · satellites.js (live SGP4)
              buildings.js (keyless OpenStreetMap 3D buildings) · launches.js (launch pads)
              airspace.js (military airspace volumes) · declutter.js (label overlap)
  services/   wiki.js (Wikipedia summaries, Commons media) · sky.js (planets, Moon, stars) · places.js (place search)
              launches.js (Launch Library 2) · weather.js (Open-Meteo) · airspace.js (FAA SUA)
              geomagnetic.js (Kp, aurora) · airfields.js (nearest airfields) · fireballs.js (NASA fireballs)
              explain.js (sighting checker scoring) · mufon.js (MUFON Journal issues & page text)
              geipan.js (GEIPAN classes, dates, links) · journals.js (APRO, NICAP, CUFOS)
              textsearch.js (journal full-text search)
  ui/         list.js · dossier.js · timeline.js · modals.js · skychart.js · story.js
              stats.js (statistics charts) · sharecard.js (share images)
scripts/      sync-dvids.mjs · build-bluebook.mjs · build-nuforc.mjs · build-airspace.mjs
              build-kp.mjs · build-fireballs.mjs · build-airfields.mjs · mcp-server.mjs (MCP server for AI assistants)
              build-mufon.mjs · build-geipan.mjs · build-journals.mjs · build-textindex.mjs
              build-cards.mjs (case preview images) · indexnow.mjs (search engines) · archive-pages.mjs (Wayback Machine)
              build-skybox.py (NASA star map → sky box)
              verify-media.mjs · check-links.mjs · fix-cesium-base.mjs
              lib/ (GeoNames gazetteer · page-shell.mjs: the frame the static pages share · case-pages.mjs: a page per case, the case index + sitemap · browse-pages.mjs: the pages by country, decade, status and more · open-data.mjs: JSON, CSV, GeoJSON · llms.mjs: robots.txt, llms.txt, llms-full.txt; all made at build)
public/cards/ the preview image for each case page
tests/        Vitest suites · e2e/ Playwright browser tests
docs/         KNOWN-ISSUES.md (limits of the app and the data) · MCP.md (the AI-assistant server) · media/ (README pictures and videos)
AGENTS.md     the developer guide (commands, conventions, releases); CLAUDE.md points to it
CONTRIBUTING.md · SECURITY.md · CODE_OF_CONDUCT.md · CHANGELOG.md · DATA_SOURCES.md · THIRD_PARTY_NOTICES.md

Open data

The 261 case files are free to reuse, under the same MIT licence as the code, from the open data page:

File	What's in it
cases.json	Every field: date and place with coordinates, category, evidence, status and explanation, summary, timeline, sources, and the 70 reconstructed flight paths with what each is based on
cases.csv	One row per case, for spreadsheets
cases.geojson	A point per case and a 3D line per flight path, for GIS tools and web maps

They are made from src/data/cases/ on every build, with the page describing them as a schema.org Dataset so dataset search engines can find it. There is also a plain list of all case files, with no 3D globe needed, and pages that browse them by country, decade, status, kind of encounter, evidence and shape.

For AI assistants: llms.txt and llms-full.txt describe the site and give every case as plain text, and npm run mcp starts a local Model Context Protocol server (no network, no dependencies) with tools to search the cases (and count them by status, country, decade, evidence or shape), read one, find the cases near a place, list a date's, check for a bright fireball near a sighting and make a link to the globe. See docs/MCP.md for Claude Code and Claude Desktop.

Where the data comes from

All datasets ship in public/data/ and are rebuilt by scripts:

Command	Source	Output
npm run sync:official	DVIDS search, then each asset page (title, date, description, duration, thumbnail). Regions are resolved by src/data/regions.js. Runs weekly in CI.	official-uap-media.json
npm run build:bluebook	Internet Archive collection project-blue-book, geocoded offline with GeoNames cities1000	bluebook.json
npm run build:airspace	FAA special-use airspace (ArcGIS open data), simplified	airspace.json
npm run build:kp	The Kp geomagnetic index every three hours since 1932 from GFZ Potsdam (CC BY 4.0), packed one character per interval	kp.json
npm run build:fireballs	NASA/JPL CNEOS fireball data API (U.S. government data, public domain): bright meteors since 1988 with a position, packed as compact events	fireballs.json
npm run build:airfields	OurAirports (public domain): large and medium airports, small ones with an ICAO code or flights, and military fields by name	airfields.json
npm run build:nuforc	planetsig/ufo-reports (geocoded NUFORC), facts only with the narratives removed	nuforc.json
npm run build:mufon	The MUFON Archive on the Internet Archive (). It reads each issue's OCR text page by page, finds "Town, State" places in sighting reports (skipping addresses, meetings and hometowns), geocodes them with GeoNames and matches pages to curated cases. Only places, page numbers and short quotes are stored.

Adding a case:

1. Add it to src/data/cases/*.js. Track points are p(lat, lon, altitudeFeet, secondsFromStart, note).
2. Run npm run verify:media && npm test.

It then appears on the globe.

How to read the map honestly

• Status matters. Many famous cases have ordinary explanations and are shown with the explanation first:

  • Roswell: Project Mogul.
  • Phoenix Lights: A-10s and flares.
  • Hudson Valley: a Cessna formation.
  • Aguadilla: AARO found objects drifting at wind speed.

  Unresolved means there isn't enough data, not "alien".

• Paths are reconstructions from the cited reports and radar accounts, and each track states its basis. Average speeds are simply distance ÷ time between reported points.

• Official releases are often region-only. The magenta ring is the whole area named in the release.

• Blue Book pins mark the town in the file name, not the exact spot.

• GEIPAN pins mark the commune named in the file. GEIPAN's classification is its own: a class D case is unexplained after investigation, not proven extraordinary.

• NUFORC reports are unverified. They show where people report things.

• MUFON and research-archive places are found automatically. A violet or teal pin is a town named in a journal report. That's usually where the sighting was, but sometimes it's a witness's hometown or where a report was filed. Every pin links to its page so you can check.

• Night-side city lights are today's. When a case lights the globe for its moment, the lights on the night side are NASA's 2016 Black Marble, not the lights of the case year.

• Times can be approximate. 54 older cases record only the date or part of the day. They are marked time approx., and the sky, weather and story say so.

Deploy your own

.github/workflows/pages.yml tests and builds the site on every push to the default branch, then publishes it to a gh-pages branch that GitHub Pages serves.

1. Fork the repository and keep it public. Free plans serve Pages only from public repositories.
2. Push once. The workflow creates gh-pages.
3. Go to Settings → Pages → Deploy from a branch and pick gh-pages / (root).
4. Your copy appears at https://<user>.github.io/<repository>/.

Any other static host works too. Run SITE_URL=https://your.site/ npm run build (SITE_URL goes into the link previews and the sitemap; add BASE_PATH=/subpath/ when it is not served from the root), then upload dist/. To try it in a container: docker run --rm -p 8080:80 -v "$PWD/dist:/usr/share/nginx/html:ro" nginx:alpine.

ci.yml runs the tests and a build on every push and pull request (codeql.yml scans the code, and Dependabot proposes dependency updates weekly). sync-official.yml re-syncs the official DVIDS releases every Monday (and the geomagnetic Kp series and the fireball record on the first Monday of the month), commits any change and redeploys the site. After each deploy, indexnow.yml sends the sitemap to Bing and the other IndexNow search engines and asks the Wayback Machine to keep a copy of the main pages. release.yml publishes a GitHub release from .github/release-notes/<tag>.md.

The build writes a page per case (case/<id>/), an index of them (case/), pages that group the cases by country, decade, status, kind of encounter, evidence and shape (browse/; a group needs two cases), the open data (open-data/), a sitemap.xml, and robots.txt, llms.txt and llms-full.txt (the cases as plain text for AI assistants; crawlers read these at the root of a host, so on a github.io/<repo>/ address they matter only on a custom domain). A case page opens the case on the globe at once only when its link ends in #globe, as links shared from the app do; reached any other way (a search result) it stays a readable page, so search engines index it. They use the address in SITE_URL, which pages.yml sets to https://<owner>.github.io/<repository>/. After changing cases, refresh their preview images with node scripts/build-cards.mjs against a running build, or run cards.yml from the Actions tab, which draws them on GitHub (with the satellite imagery) and commits them. For IndexNow, replace public/<key>.txt with your own key.

Contributing

Corrections and new cases are welcome, especially with sources. CONTRIBUTING.md has the details, and AGENTS.md is the developer guide.

• In the app, every case has Suggest a correction and Suggest a case buttons. They open pre-filled issue forms.
• For code changes, open a pull request. Run npm test first, and npm run verify:media if you touched case files. Interface text goes in all 15 languages (npm run i18n:add).
• Something not working? Check known issues and limits, then file a bug.
• Security reports go to the private form described in SECURITY.md. Please follow the code of conduct.
• What changed in each release: CHANGELOG.md.

Credits & licences

• Made by domw99.
• Code: MIT (see LICENSE).
• Translations: written for this project (Spanish, French, German, Portuguese, Italian, Dutch, Polish, Turkish, Russian, Arabic, Hindi, Indonesian, Japanese, Korean, Chinese); corrections from native speakers are welcome as pull requests to src/i18n/locales/.
• Inspiration:
  • The visual language follows God's Eye View by Bilawal Sidhu (MIT).
  • Its space-launch layer, cockpit view, in-app key panel and URL camera inspired the launch layer, witness view, MAP panel and view links here.
  • Its Noir and Snow sensor styles, frame-rate readout and sharable scene links inspired the same-named looks, the ` key and the share links here.
  • The shaders and code here are original.
• Globe: CesiumJS (Apache-2.0).
• Map data:
  • Imagery: Esri World Imagery ("Powered by Esri").
  • Terrain: Re:Earth / Mapterhorn (CC BY 4.0).
  • OSM fallback: © OpenStreetMap contributors.
  • Earthquakes: USGS Earthquake Hazards Program (public domain).
  • 3D buildings: © OpenMapTiles © OpenStreetMap contributors, served by OpenFreeMap.
• Media & sources:
  • Official footage: DVIDS / U.S. Department of War (public domain).
  • Media: Wikimedia Commons. The licence and author of each file are shown in the app.
  • Summaries: Wikipedia (CC BY-SA).
  • Blue Book scans: Internet Archive / NARA.
  • GEIPAN files: GEIPAN / CNES. Case data from its published CSV files; each case links to its full file on cnes-geipan.fr.
  • The MUFON files: Skylook / MUFON UFO Journal © Mutual UFO Network, released as "The MUFON Archive" by MUFON and The Black Vault. Mirrored on the under CC BY-NC-ND 4.0. The app links to the pages and quotes short excerpts with attribution. Chapter newsletters were scanned by the Archives for the Unexplained (AFU).

Third-party data keeps its own licence; the MIT licence covers only the code.