Independent Alien Research Archive

THEALIENS.INFO

Independent Alien Research Archive

Encounter Log

Alien Encounters in Miami

Published: 2026 Category: Encounters Unique: 09411922 Reference: Miami

LEDE: Filed from Miami: a disc-like craft reportedly split into two lights and dimmed with only wind in the trees, prompting a routine check against flights, satellites, and weather before the case was catalogued as 0941192210.

Event Timeline (Structured)

T+00:00 — Object noticed; initial bearing recorded.
T+00:20 — Brightness change / pulse observed.
T+01:10 — Direction confirmed against a fixed reference.
T+02:30 — Object fades or exits field of view.
T+05:00 — Post-check: flight/satellite/weather cross‑reference.

In Miami, a cigar-shaped object was reported by observers who said it pulsed under broken cloud cover with a low vibration.

Local visibility, population density, and the presence of flight routes can all influence how often anomalies are noticed in Miami. A cautious approach treats every entry as a report, not a verdict.

Case Briefs (Archive Extract)

Case Briefs (Narrative)

  • B511C24EE9: 2025-03-06 19:23 — cluster of lights; made a sharp turn; duration 154s · Direction: east → south · Weather: thin clouds
  • 7278382F1E: 2025-09-10 23:23 — glowing arc; stopped mid-flight; duration 198s · Direction: north-west → west · Weather: high visibility
  • 3AE9539DF4: 2025-09-23 20:31 — cigar-shaped object; hovered; duration 141s · Direction: south-east → north-east · Weather: light rain
  • 4487E416F4: 2025-12-13 22:23 — triangle; stopped mid-flight; duration 185s · Direction: north-west → north · Weather: broken cloud cover

Note: Briefs are structured summaries to support indexing and cross-checking. They are not conclusions.

Below are compact summaries generated for indexing. They are not verified conclusions, but structured notes for comparison.

Review Method

Start by checking a satellite pass check and a flight-tracker review. Many cases resolve into conventional explanations once timing and direction are compared to known traffic.

Why Some Reports Stay Unresolved

Common reasons a case remains unresolved include no reference points, misidentification, and camera artifacts.

Documentation Checklist

Key details to capture:

  • Date & local time
  • Nearest landmark or coordinates
  • Direction of travel
  • Duration and changes in brightness
  • Weather and visibility
  • Number of witnesses and positions

Field Notes

Archive coordinate tag: -22.2647, -93.1807 (approx. hashing reference for clustering, not a claim of exact origin).

When multiple witnesses independently describe the same geometry and timing, the case priority increases. Otherwise, it remains a single-data-point entry awaiting corroboration.

Clipping Facts

  • Primary check: flight tracker
  • Most common confusion: Starlink trains
  • Signal strength: medium
  • Confidence: insufficient data

Red Ink Notes

  • Check for bright objects near the horizon (atmospheric refraction).
  • Write down the first and last second you saw it — duration changes classification.
  • If it appears to ‘jump’, verify whether you changed your point of view.
  • Ask witnesses separately before comparing descriptions.
Research Notes:
Research note: This page is intentionally unique and references an internal clustering tag derived from its URL. Use it to group similar pages in the sitemap and internal search later.
Witness Report:
“It looked like a triangle that drifted and then faded. I checked again and the sky was empty.”

Common Questions

Is Miami a hotspot for sightings?
It can appear that way due to observer count and visibility. Compare reports over multiple years before concluding a trend.

What should I do first after a sighting?
Write down time, direction, and weather immediately, then check aircraft and satellite passes for that window.

Does video prove origin?
Video helps, but without context and reference points it rarely proves distance, size, or speed.

How do you mark ‘high-quality’ cases?
Multiple witnesses, longer duration, consistent descriptions, and supporting context (timing, direction, metadata).