RESEARCH_DATABASE // START_HERE
Use this timeline to locate source-linked event records, public claims, policy milestones, and related reporting. A timeline entry is a finding aid: it tells you what was reported, when it was placed in the record, and where to inspect the underlying material. Its presence here is not an endorsement of a witness, institution, interpretation, or proposed explanation.
What this timeline contains
The page has two research modes. UFO Events is organized around reported observations and incidents. Its records may show a title, event date and time, location, category, summary, mapped location, source link, and—when available—a related Countdown to Disclosure briefing. Disclosure Monitor follows attributed public claims and disclosure activity. Its searchable fields include the person or organization associated with a claim, claim type, country, date, summary, and source attribution.
The modes answer different questions. UFO Events helps you ask, “What was reported at this place and time?” Disclosure Monitor helps you ask, “Who made this public statement or took this disclosure-related action, in what setting, and where is the record?” A statement about an event is not the event itself, and repetition of a claim does not make it independently corroborated.
Search, map, and open a record
- Choose a mode. Select UFO Events or Disclosure Monitor before searching.
- Search the fields shown in the interface. In UFO Events, try a title, location, date, or term from the notes. In Disclosure Monitor, try a person, claim type, country, or date. The query narrows the visible list; it does not score credibility.
- Select a row. The active-record panel displays the available date, title, location or country, time or claim type, and summary. The synchronized map provides geographic context when the record contains a usable location; an empty or approximate map position should not be treated as contradictory evidence.
- Leave the overview when the question becomes specific. Follow Review primary source to inspect the cited material. Use the full-article or stable event-record link, when present, to save or cite an individual record rather than relying on the changing list view.
If a search returns nothing, shorten the query, try an alternate spelling, or search by year or country. Absence from this interface means only that no matching record is currently exposed by that query; it does not establish that an event, document, or investigation never existed.
Read dates, places, categories, and uncertainty carefully
The event date is the date assigned to the reported occurrence. It is separate from the publication date of a source, the date a briefing was written, and any later revision date. Some historical records preserve only a year, month, date range, or retrospective estimate. When the source is imprecise, read the displayed date as an organizing value and check the source before quoting it as exact.
Locations are normalized so records can be searched and mapped, but place names, boundaries, and spellings change. A country label may identify the reported setting, not the nationality of a witness or the jurisdiction of the source. Categories and claim types are navigation labels, not verdicts. “Unidentified,” “unresolved,” “classified,” and “not publicly explained” describe different limits in the available record; none of them, by itself, identifies an extraordinary origin.
From entry to evidence
Start with the source link and note who created the record, when it was created, whether it is original or retrospective, and what it directly supports. Then compare the summary with the site’s source and uncertainty standards and use the primary-source desk to locate issuer-owned repositories. For a repeatable check of evidence, inference, and missing information, work through Evaluate a UAP Claim.
Use research briefings for deeper context and topic clusters to follow a question across multiple records. If you find a broken source, date conflict, transcription error, or missing context, send the stable record URL and supporting documentation through the corrections and contact route. A useful correction identifies the exact field at issue and points to the closest available original record.