LIVE
THE COUNCIL · CASE OF RECORD · THE COUNCIL · CASE OF RECORD · MMXXVI The Council
Search
THE COUNCIL · CASE OF RECORD · THE COUNCIL · CASE OF RECORD · MMXXVI
SIGHTINGS · MD · Standing reference

UAP sightings near Baltimore, MD

City
Baltimore, MD
Region
Mid-Atlantic
Coordinates
39.2904°, -76.6122°
Metro pop. (est.)
2,834,316
NUFORC reports (est.)
280
Nearest dark-sky site
Cherry Springs State Park, PA

The Council's standing reference for unidentified aerial phenomena in the Baltimore, MD metropolitan area: estimated public report counts, sky conditions, the nearest low-light-pollution observation site, and how to file a sighting that the Council can review.

The Council notes that the Baltimore, MD metropolitan area — population approximately 2,834,316 — has produced an estimated 280 publicly logged unidentified aerial phenomena reports through the National UFO Reporting Center (NUFORC) and the Mutual UFO Network (MUFON) databases between 1947 and 2025. That figure is approximate. NUFORC and MUFON record only voluntary submissions, and a substantial — and unknowable — share of observations is never filed. The number functions as a floor, not a ceiling.

The Baltimore metro sits at 39.2904 degrees N, 76.6122 degrees W. It is one of fifty United States metropolitan areas the Council maintains a standing sightings reference for. The page below summarises what is publicly known, what the standing data says, and how a credible local observation can be added to the record.

Notable cases

No case in the Council archive presently centres on the Baltimore metro. That absence is data: Baltimore-area observers can shift the record by filing what they see. The standing public databases — NUFORC and MUFON — accept reports from any U.S. address.

Sighting density

Across the modern record, the Baltimore metro accounts for an estimated 280 publicly logged reports. Normalised to its metro population of approximately 2,834,316, that works out to roughly 9.9 reports per 100,000 residents — a rate the Council treats as broadly typical of U.S. metropolitan areas of this size.

Two things are worth saying honestly. First, per-city peak years cannot be cited with the precision that headline writers prefer; NUFORC and MUFON’s public datasets are not granular enough at the metro level to support definitive year-by-year peaks for most cities. Second, the modern UAP wave — broadly the period between the 2017 New York Times AATIP disclosures and the 2024 AARO Historical Record Report — produced a measurable national uptick in filings. The Council treats 2017-2024 as the most-cited modern reporting window across the United States as a whole. Whether that pattern is mirrored exactly in Baltimore is not something we will assert without local data we cannot verify.

Local sky conditions

The Baltimore core sits inside a Bortle 8-9 light-pollution zone — the standard reading for any major U.S. metro. Conventional astronomy is constrained, and routine sky-watching from inside the metro is largely confined to the brightest objects: the Moon, Venus, Jupiter, Mars, and the brighter satellite passes. Most reports filed from within the metro core are of low-altitude lights, formations, or aircraft-adjacent anomalies rather than deep-sky phenomena.

The nearest publicly recognised dark-sky observation site is Cherry Springs State Park, PA, generally a Bortle 1-3 location on clear nights. Observers willing to drive to a designated dark-sky park materially improve both the quality of what they can see and the credibility of any submission they later file.

The most usable sky-condition window for the broader region is generally September-November, when high pressure dominates and humidity, smoke, and persistent overcast are at their lowest. The Council does not recommend filing reports from observation sessions conducted in marginal weather; ambiguous conditions produce ambiguous data.

What to do next

If you have observed something in the Baltimore-area sky that you cannot account for, the Council asks two things.

First, file the sighting — either to NUFORC, to MUFON, or directly to the Council via /sighting/new. The Council’s Filing a Sighting field guide covers what data to capture: time-stamp, exact coordinates, bearing, elevation, duration, witness count, weather, and any photographic or video record. Reports filed without those fields are not dismissed, but they are weighted lower by the verdict engine.

Second, carry recording gear next time. The single most-cited gap in submitted reports is the absence of corroborating media. The Council’s standing recommendation for Baltimore-area observers is the Celestron NexStar 8SE telescope — selected on the basis that it pairs directly with the sky conditions described above and produces the kind of evidence the Council can review.

The record of unidentified aerial phenomena is a public archive built one credible filing at a time. The Baltimore metro’s contribution to it is, at present, what its observers have made it.

Submit a sighting

File what you observed

The Council reviews every submission. Reports filed with time-stamp, coordinates, bearing, and any media are weighted higher by the verdict engine.

Submit a Baltimore-area sighting

Field guide

How to file what the Council can review

The standing field guide walks through the eight data fields the Council considers material in any sighting submission.

Read FG-001 →
← All metro sightings references