PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 53 / 237UAP00362
237UAP00362
Radar/correlation-focused public UAP report; score 54
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-53-237UAP00362
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00362
Generated
2026-05-20 18:32 UTC
Report Time
2024-03-03T10:00:00+00:00
Observer
41.88899, -104.57831
Source Case IDs
237UAP00362
Abstract
This case file evaluates a reported UAP sighting against the available orbital-object layer. No compact same-launch group fully identifies the file by itself. The final disposition is assigned under a normal-object favored standard, where ordinary aerospace/orbital explanations are preferred when they reasonably fit the report.
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
237UAP00362 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N973AK B39M ad8ed4 at 27.8 km, azimuth 15.6 deg, elevation 18.66 deg, 0.94 min from report. Dense satellite presence alone is not treated as causation in this packet.
1.1 Key Findings
Source score 54 based on: radar/primary-return language, negative official correlation, UAP/UFO language.
Report time used: 2024-03-03T10:00:00+00:00.
External object layer used: public LEO catalog objects.
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 N973AK B39M ad8ed4 at 27.8 km, azimuth 15.6 deg, elevation 18.66 deg, 0.94 min from report.
Non-causal context / rejection screens: very dense orbital-object sky background; context only, not causation.
No compact same-launch/designator group survived the report threshold.
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 12 to 1 O' Clock while NE bound at FL350, 49NM W of BFF. The unknown phenomenon was 2-3 bright white lights, possibly more, moving in several directions; up and down, left and right. The UAP was not observed on ATC facility radar system.
Report time used
2024-03-03T10:00:00+00:00
Observer coordinate used
41.88899, -104.57831
Observer source basis
aviation_offset:49NM W of BFF (public text extract 237UAP00362)
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 public LEO catalog objects element rows. The analytic mode for this case is historical public LEO catalog objects 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.
public LEO catalog objects catalog IDs considered
20128
Historical element rows
20128
Above horizon at report minute
1066
At/above 10 deg
534
Largest same-sky cluster
534
No compact same-launch/designator group survived the report threshold. In this condition, satellite density remains context only and cannot by itself resolve a report with hard features.
5.2 Same-Launch / Same-Designator Candidate Groups
#
Launch Date
Count
Azimuth Span
Elevation Span
Motion Labels
Members
No same-launch group identified.
5.3 Primary Group Members
Object
NORAD
Launch
Az
El
Range km
Apparent Motion
Element Age h
No members available.
5.4 Bright-Sky Context: Top public LEO catalog objects 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
30
SATCAT rows matched
30
Top owners
CIS: 12, US: 11, PRC: 3, UK: 3, JPN: 1
Object types
PAYLOAD: 17, DEBRIS: 12, ROCKET BODY: 1
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
29287
SL-8 DEB
DEBRIS
CIS
1981-12-17
n/a
7559
OPS 6630 DEB
DEBRIS
US
1973-11-10
n/a
38737
BREEZE-KM R/B
ROCKET BODY
CIS
2012-07-28
n/a
42115
COSMOS 1275 DEB
DEBRIS
CIS
1981-06-04
n/a
57618
STARLINK-30249
PAYLOAD
US
2023-08-11
n/a
57087
STARLINK-6251
PAYLOAD
US
2023-06-22
n/a
4914
THORAD AGENA D DEB
DEBRIS
US
1970-04-08
n/a
56918
STARLINK-5951
PAYLOAD
US
2023-06-12
n/a
10587
COSMOS 980
PAYLOAD
CIS
1978-01-10
n/a
28455
RITE TARGET 2
PAYLOAD
JPN
2002-12-14
n/a
7439
COSMOS 681
PAYLOAD
CIS
1974-09-19
n/a
27728
DELTA 1 DEB
DEBRIS
US
1976-07-29
n/a
5.9 NASA / NOAA / ADS-B Expansion Layer
This source layer adds free NASA context that was previously missing from most packet cases. It is contextual evidence; it does not replace aircraft, satellite, balloon, or radar causation tests.
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_2024 for 2024-03-03, then filter +/-60 min and 250 nmi around 41.8890,-104.5783.
NASA POWER/Horizons/DONKI: batch context for 237UAP00362 at 2024-03-03T10:00: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; low/broken/overcast cloud layers were present in at least one observation. 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 37.6 deg at 16.2 m/s; a passive balloon could drift about 116.7 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
USM00072662
RAPID CITY WFO; SD.
267.10
2024-03-03T12:00:00+00:00
37.60
16.20
116.70
31.90 at 11500.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
2024-03-03T08:45:00+00:00 to 2024-03-03T11:15:00+00:00
Radius
300.00 nmi
Trace files scanned
44286
Tracks retained
154
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
4
Plausible candidates
10
Reporting-aircraft tracks excluded
3
Weak candidates
18
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N973AK B39M ad8ed4
strong aircraft candidate
85.63
27.10
0.06
31025
15.60
18.66
N251TH a25ce6
strong aircraft candidate
70.07
73.00
1.90
64300
5.50
13.92
N805SY B738 aaf617
strong aircraft candidate
68.98
78.50
0.12
33025
141.20
6.83
JA823A B788 86d5d8
strong aircraft candidate
58.53
51.90
0.12
35975
195.00
8.17
C-FNWD B38M c02494
reporting aircraft track; excluded from support counts
94.52
13.70
0.02
38000
214.90
37.30
N639JB A320 a85ff5
reporting aircraft track; excluded from support counts
87.30
8.60
0.09
35050
17.90
49.65
D-AALR B77L 3c4592
plausible aircraft candidate
72.20
3.30
8.67
31000
326.30
70.89
D-AALN B77L 3c458e
plausible aircraft candidate
66.38
3.70
0.39
35000
55.00
70.96
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
2024-03-03T10:00:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
41.88899, -104.57831
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
three-object/light language present
No compact same-launch count match; retained for unresolved report features.
Motion language
moving
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
237UAP00362 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N973AK B39M ad8ed4 at 27.8 km, azimuth 15.6 deg, elevation 18.66 deg, 0.94 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
237UAP00362
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 10:00 03/03/2024 Callsign: BOX473 Origin: LAX
Status: Closed Aircraft: B77L Destination: EDDF
POD: DEN Tail Number: New Destination:
Reporting Facility: ZDV Operator: BOX Operator Type: Commercial
Paged: YES MOR Init: YES
MOR ID: ZDV-M-2024/03/03-0001
REMARKS
Aircraft reported an unidentified aerial phenomenon 12 to 1 O' Clock while NE bound at FL350, 49NM W of BFF. The unknown
phenomenon was 2-3 bright white lights, possibly more, moving in several directions; up and down, left and right. The UAP was
not observed on ATC facility radar system.
SKYWATCH INCIDENT REPORT | DATE: 2024-03-03T10:00 | 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: 237UAP00362
Time and observer coordinate
extracted
2024-03-03T10:00:00+00:00 at 41.88899, -104.57831
Orbital object propagation
screened
public LEO catalog objects
Space-Track SATCAT metadata
screened
30 NORAD IDs checked; 30 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
screened
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/