PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 24 / 237UAP00330
237UAP00330
Radar/correlation-focused public UAP report; score 66
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-24-237UAP00330
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00330
Generated
2026-05-20 18:32 UTC
Report Time
2023-12-23T03:46:00+00:00
Observer
39.80746, -105.74509
Source Case IDs
237UAP00330
Abstract
This case file evaluates a reported UAP sighting against historical Starlink orbital elements. The primary external-object candidate is a 3-object same-launch group from 2023-05-14, spanning azimuth 274.38-292.25 deg and elevation 11.7-22.91 deg. The analysis distinguishes plausible geometric overlap from unresolved witness-language features.
This is a standalone independent analysis prepared from public-source records and public orbital datasets. It is not an official government determination, classification marking, or agency-authored report.
1. Executive Summary
237UAP00330 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N903JB A321 ac7b1b at 37.6 km, azimuth 182.1 deg, elevation 14.38 deg, 0.21 min from report. Dense satellite presence alone is not treated as causation in this packet.
1.1 Key Findings
Source score 66 based on: radar/primary-return language, high-altitude report, maneuvering/motion anomaly, UAP/UFO language.
Report time used: 2023-12-23T03:46:00+00:00.
External object layer used: Starlink.
Disposition standard: NORMAL-OBJECT requires case-specific causal fit. Satellite density above the horizon is context only and cannot by itself resolve the report.
Case-specific ordinary-object evidence: strong ADS-B aircraft candidate N903JB A321 ac7b1b at 37.6 km, azimuth 182.1 deg, elevation 14.38 deg, 0.21 min from report.
Top compact same-launch/designator group: 3 objects from 2023-05-14.
No explicit Starlink/balloon wording was found in the source excerpt used for ranking.
1.2 Bottom Line
NORMAL-OBJECT FAVORED: A case-specific ordinary-object candidate exists from source language, orbital geometry, launch-object context, or compact trajectory grouping. Dense ordinary sky traffic alone is not treated as causation.
2. Source Control
The source-control table identifies the public report records reviewed for this case and lists public access links where available. The table is included so this PDF remains interpretable when distributed by itself.
Aircraft reported an unidentified aerial phenomenon off the left side while NW bound at FL320, 50 NM West of DEN. The unknown phenomenon was a group of red lights circling each other at approximately FL400. The UAP was not observed on ATC facility radar system. AWO notified.
Report time used
2023-12-23T03:46:00+00:00
Observer coordinate used
39.80746, -105.74509
Observer source basis
aviation_offset:50 NM West of DEN (public text extract 237UAP00330)
4. Methodology
Spacetime extraction. The report time and observer coordinate were extracted from the public text report and normalized to UTC. Aviation fixes/radials were resolved during earlier preprocessing where applicable.
External object dataset. The object layer used historical Space-Track/TLE-derived Starlink element rows. The analytic mode for this case is historical Starlink element propagation and same-launch/designator sky grouping.
Propagation. Orbital elements were propagated to the report minute and observer location. For launch-object checks, samples around the report minute were retained. For Starlink group checks, objects above the horizon were clustered by sky position and filtered for same-launch groupings.
Comparison. The output was compared against the report's count of lights, direction cue, motion language, altitude/radar language, and whether the file itself already suggested a satellite explanation.
Causation standard. Mere object presence above the horizon is treated as background context only. A normal-object disposition requires a case-specific causal fit, such as a named launch object, a compact same-launch trajectory group, or source language that directly supports that object class.
Disposition assignment.Identified means a specific normal object fits the report spacetime and the hard reported features do not materially conflict. Normal-object favored means a case-specific ordinary aerospace/orbital candidate exists, but it is not a full named identification. Insufficient means the file is too thin to carry high anomaly value. High-value unresolved is used when radar, video, rapid maneuver, or multi-witness features remain after reasonable normal-object checks.
5. External Object Evidence
5.1 Search Volume and Density
This table is a screening layer only. Objects above the horizon show background opportunity; they do not establish causation unless a specific object or compact trajectory group matches the reported behavior.
Starlink catalog IDs considered
5248
Historical element rows
5202
Above horizon at report minute
246
At/above 10 deg
124
Largest same-sky cluster
48
5.2 Same-Launch / Same-Designator Candidate Groups
#
Launch Date
Count
Azimuth Span
Elevation Span
Motion Labels
Members
1
2023-05-14
3
274.38-292.25 deg
11.7-22.91 deg
eastward, rising, westward, rising
STARLINK-5302, STARLINK-6308, STARLINK-5775
5.3 Primary Group Members
Object
NORAD
Launch
Az
El
Range km
Apparent Motion
Element Age h
STARLINK-5302
56556
2023-05-14
292.25
22.91
1213.67
eastward, rising
0.43
STARLINK-6308
56534
2023-05-14
274.38
12.22
1701.95
westward, rising
0.49
STARLINK-5775
56503
2023-05-14
285.57
11.7
1736.01
westward, rising
0.45
5.4 Bright-Sky Context: Top Starlink Objects by Elevation
Space-Track SATCAT metadata was pulled as a cached subset for NORAD catalog IDs appearing in this packet's evidence tables. This section adds owner/type/status context to the propagated object candidates.
Packet SATCAT subset rows
5370
Fetched
2026-05-19T01:19:50+00:00
This case NORAD IDs checked
33
SATCAT rows matched
33
Top owners
US: 33
Object types
PAYLOAD: 33
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
57104
STARLINK-6130
PAYLOAD
US
2023-06-23
n/a
51769
STARLINK-3621
PAYLOAD
US
2022-02-25
n/a
53604
STARLINK-4690
PAYLOAD
US
2022-08-28
n/a
54087
STARLINK-5184
PAYLOAD
US
2022-10-20
n/a
46677
STARLINK-1766
PAYLOAD
US
2020-10-18
2024-09-15
57307
STARLINK-30209
PAYLOAD
US
2023-07-10
2026-03-03
57418
STARLINK-30221
PAYLOAD
US
2023-07-20
n/a
57376
STARLINK-6367
PAYLOAD
US
2023-07-16
n/a
53620
STARLINK-4615
PAYLOAD
US
2022-08-28
n/a
56457
STARLINK-5994
PAYLOAD
US
2023-05-10
n/a
54063
STARLINK-5225
PAYLOAD
US
2022-10-20
2026-02-08
56504
STARLINK-5716
PAYLOAD
US
2023-05-14
n/a
5.9 NASA / NOAA / ADS-B Expansion Layer
NASA POWER/Horizons/DONKI batch context had not yet been written for this case at packet build time.
Requires targeted extraction from large daily history archives before claiming aircraft exhaustion.
NOAA GOES imagery
not yet exhausted
Needed for cloud/lightning visual context.
NOAA GOES ABI/GLM manifest
screened/present
Public S3 object availability for the report hour.
NOAA NEXRAD weather radar
not yet exhausted
Weather radar only; not ATC radar.
NOAA IGRA radiosonde
screened/present
Needed for balloon drift plausibility.
ASOS/METAR weather observations
screened/present
Nearest station surface observations around report time.
ADSB.lol historical: extract aircraft traces from adsblol/globe_history_2023 for 2023-12-23, then filter +/-60 min and 250 nmi around 39.8075,-105.7451.
NASA POWER/Horizons/DONKI: batch context for 237UAP00330 at 2023-12-23T03:46:00+00:00.
NOAA GOES: pull nearest ABI/GLM products for the UTC hour and render cloud/lightning map.
NOAA NEXRAD: select nearest radar stations and render Level-II/III weather radar sweep around event time.
NOAA IGRA: find nearest radiosonde station launches bracketing the event and model wind drift for balloon-like descriptions.
Space-Track gp_history/decay: fetch exact historical element rows and decay/reentry status for top candidate NORAD IDs.
5.12 Weather, Imagery, and Balloon Query Plan
This plan identifies the concrete free sources needed for the next case-specific weather and balloon checks. These are not treated as completed exclusions until the data are downloaded and plotted.
surface visibility ranged 10-10 statute miles; no precipitation was reported in the retained observations; no low broken/overcast cloud ceiling was evident in the retained station observations. Surface ASOS/METAR observations describe airport-level weather and visibility; they do not by themselves prove conditions at the sighting altitude or line of sight.
Nearest sounding implies mean 0-12 km wind drift toward 261.8 deg at 13.19 m/s; a passive balloon could drift about 94.9 km in two hours under this crude layer-average model. Radiosonde winds are sparse station soundings; balloon drift remains approximate without launch time, ascent rate, object altitude, and exact line-of-sight bearing.
Station
Name
Distance km
Sounding UTC
Mean drift bearing
Mean speed m/s
2h drift km
Max wind
USM00072476
GRAND JUNCTION/WALKER FIELD; C
250.60
2023-12-23T00:00:00+00:00
261.80
13.19
94.90
30.90 at 21621.00 m
5.17 NOAA GOES ABI/GLM Public File Manifest
GOES public S3 objects are listed for the report hour where available. This is an availability manifest, not yet a rendered satellite image.
This layer uses the downloaded ADSB.lol daily history archive to test actual aircraft tracks near the report coordinate and minute. It is not treated as a primary-radar substitute; it is a transponder/receiver-derived aircraft screen.
Archive window
2023-12-23T02:46:00+00:00 to 2023-12-23T04:46:00+00:00
Radius
250.00 nmi
Trace files scanned
39960
Tracks retained
673
Support status
aircraft strong candidate present
Best-candidate note
ordinary-object favored if the report's count, color, direction, and motion can be reconciled with the candidate track(s).
Strong candidates
25
Plausible candidates
159
Reporting-aircraft tracks excluded
2
Weak candidates
141
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N903JB A321 ac7b1b
strong aircraft candidate
83.02
36.10
0.11
32000
182.10
14.38
N68801 B739 a92361
strong aircraft candidate
81.61
14.20
0.03
28600
178.90
27.90
N950JT A321 ad3581
strong aircraft candidate
81.37
26.20
0.11
34025
15.70
20.36
N646JB A320 a87c4f
strong aircraft candidate
76.20
59.70
0.14
35975
25.90
10.13
N773CK B77L aa7468
strong aircraft candidate
73.49
46.70
0.05
35000
180.00
11.73
N620MA C560 a81751
strong aircraft candidate
72.97
34.80
0.09
23550
142.70
10.25
N767FL GLF5 aa5c11
strong aircraft candidate
71.92
3.60
0.08
45025
69.90
19.03
N373FR A20N a43f7d
strong aircraft candidate
71.48
67.10
0.14
36000
321.40
7.93
6. Annotated Evidence Figure
Generated figure copied from the local evidence-plot output. It is included as an analytic visualization, not as original sensor imagery.
7. Analytic Comparison
Criterion
Report Evidence
Analytic Treatment
Time constraint
2023-12-23T03:46:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
39.80746, -105.74509
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
not explicit
Primary same-launch group contains 3 propagated objects in a compact sky sector.
Motion language
circling
Apparent motion labels in the object table provide a plausible but not definitive comparison.
Radar / official check
not observed on ATC radar
No ATC radar return can be consistent with distant orbital objects or visual aircraft-light hypotheses, but it does not prove the match.
Analytic disposition
normal-object
237UAP00330 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N903JB A321 ac7b1b at 37.6 km, azimuth 182.1 deg, elevation 14.38 deg, 0.21 min from report. Dense satellite presence alone is not treated as causation in this packet.
8. Caveats, Limitations, and Collection Gaps
No raw cockpit video, ATC replay, radar plot, or witness interview transcript was reviewed unless explicitly stated in the public source text.
Aviation-derived coordinates can represent a nearby fix/radial or report point, not necessarily the actual line-of-sight intercept point.
Starlink visibility depends on illumination, observer altitude, atmospheric conditions, and apparent brightness; this analysis tests geometry, not photometry. No brightness model is used unless explicitly stated elsewhere in the case file.
TLE propagation is appropriate for screening and reconstruction but is not a substitute for authoritative operational ephemerides.
When many satellites are above the horizon, generic presence is weak evidence and is not treated as causation. The report emphasizes named launch-object checks or compact same-launch trajectory groups.
Normal-object favored is not the same as a perfect named-object identification; it requires a case-specific ordinary-object candidate stronger than simple object density.
Appendix A. Public Report Text Extracts
237UAP00330
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 03:46 12/23/2023 Callsign: DAL750 Origin: TPA
Status: Closed Aircraft: B738 Destination: SEA
POD: DEN Tail Number: New Destination:
Reporting Facility: ZDV Operator: DAL Operator Type: Commercial
Paged: YES
REMARKS
Aircraft reported an unidentified aerial phenomenon off the left side while NW bound at FL320, 50 NM West of DEN. The
unknown phenomenon was a group of red lights circling each other at approximately FL400. The UAP was not observed on ATC
facility radar system. AWO notified.
SKYWATCH INCIDENT REPORT | DATE: 2023-12-23T03:46 | POD: DEN | PAGE 1 of 1
Appendix B. Computational Evidence Digest
This appendix preserves the principal computed values used in the assessment, shortened to the fields most relevant to audit and review.
This checklist records which source layers were actually applied to this individual report. It separates checked evidence from unexhausted collection gaps so the disposition is auditable when the PDF is read alone.
Source Layer
Status
Case-Specific Note
NARA public UAP/FAA report
reviewed
Source IDs: 237UAP00330
Time and observer coordinate
extracted
2023-12-23T03:46:00+00:00 at 39.80746, -105.74509
Orbital object propagation
screened
Starlink
Space-Track SATCAT metadata
screened
33 NORAD IDs checked; 33 matched in local SATCAT subset
Launch-object/SupGP layer
not applicable
not a launch-object case
NASA/JPL known small-body layer
not selected
CAD/Horizons secondary screen included when this case had NEO-relevant timing/geometry
NASA POWER/Horizons/DONKI context
not exhausted
Hourly weather, sky geometry, and space-weather context where local JSON is present
Nearest station visibility, cloud, wind, precipitation, and METAR observations
Weather/balloon source plan
planned
Nearest weather-airport, GOES, and radiosonde queries are listed where local plan JSON is present
Final analytic disposition
normal-object favored
Presence-only satellite density is context only; a stronger case-specific fit is required for normal-object disposition
References and Source Links
National Archives and Records Administration. Records Related to Unidentified Flying Objects (UFOs) and Unidentified Anomalous Phenomena (UAPs) at the National Archives.https://www.archives.gov/research/topics/uaps
National Archives Catalog. Records from the Federal Aviation Administration Relating to Unidentified Anomalous Phenomena, National Archives Identifier 493468575.https://catalog.archives.gov/id/493468575
Space-Track.org. Public source for the underlying U.S. Space Surveillance Network TLE distribution referenced by the historical TLE archive.https://www.space-track.org/