PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 70 / 237UAP00607
237UAP00607
Radar/correlation-focused public UAP report; score 52
HIGH-VALUE UNRESOLVED
Report No.
UAP-OM-70-237UAP00607
Disposition
HIGH-VALUE UNRESOLVED
Primary Case
237UAP00607
Generated
2026-05-20 18:32 UTC
Report Time
2024-02-04T11:11:00+00:00
Observer
39.57672, -109.26713
Source Case IDs
237UAP00607
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
237UAP00607 was screened against historical public LEO catalog objects orbital elements at the extracted time and observer coordinate. The screen did not produce enough mundane evidence to close the case under the normal-object favored standard. Hard features retained for follow-up: radar/primary evidence.
1.1 Key Findings
Source score 52 based on: radar/primary-return language, high-altitude report, UAP/UFO language.
Report time used: 2024-02-04T11:11:00+00:00.
External object layer used: public LEO catalog objects.
Disposition standard: UNRESOLVED 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: plausible ADS-B aircraft candidate N7901A B738 aaba81 at 89.5 km, azimuth 291.5 deg, elevation 7.52 deg, 5.01 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
HIGH-VALUE UNRESOLVED: Hard report features remain after the normal-object screens, such as primary/radar evidence, multiple witnesses, footage references, or motion language that still conflicts with the available object layer.
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.
Washington Operations Center Date: 2/4/2024 4:11:00 AM (-07 MST) Title: SCX3053 UFO-UAP ACTIVITY 02-04-2024 Latitude: 39.576718900000003 Latitude: -109.2671314 DESCRIPTION PRELIM INFO FROM FAA OPS: MYTON, UT/UFO-UAP ACTIVITY/0411M/DENVER ARTCC ADVISED SUN COUNTRY 3053, B738, PDX - AFW, REPORTED AN UNIDENTIFIED AERIAL PHENOMENON OFF THE LEFT SIDE WHILE SE BOUND AT FL410 60 SE MYTON VOR (MTU). THE UAP APPEARED TO BE 5 SEPARATE CRAFT WITH WHITE LIGHTS TRAVELING BETWEEN FL600 AND FL800. NO PRIMARY TARGETS OBSERVED ON RADAR. WOC 7-3333 HM/JE
Report time used
2024-02-04T11:11:00+00:00
Observer coordinate used
39.57672, -109.26713
Observer source basis
(public text extract 237UAP00607)
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
19608
Historical element rows
19608
Above horizon at report minute
1061
At/above 10 deg
526
Largest same-sky cluster
526
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
US: 16, CIS: 10, PRC: 2, UK: 2
Object types
PAYLOAD: 16, DEBRIS: 13, ROCKET BODY: 1
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
57664
STARLINK-30302
PAYLOAD
US
2023-08-22
2025-02-27
23488
SL-19 DEB
DEBRIS
CIS
1994-12-26
n/a
53896
STARLINK-5037
PAYLOAD
US
2022-09-24
n/a
49459
STARLINK-3141
PAYLOAD
US
2021-11-13
n/a
1572
COSMOS 82
PAYLOAD
CIS
1965-09-03
n/a
47775
STARLINK-2198
PAYLOAD
US
2021-03-04
2025-01-20
45427
ONEWEB-0090
PAYLOAD
UK
2020-03-21
n/a
23548
PEGASUS R/B
ROCKET BODY
US
1995-04-03
n/a
57818
STARLINK-30401
PAYLOAD
US
2023-09-09
n/a
26504
COSMOS 1249 COOLANT
DEBRIS
CIS
1981-03-05
n/a
38664
CZ-4C DEB
DEBRIS
PRC
2012-05-29
n/a
15951
SCOUT G-1 DEB
DEBRIS
US
1985-08-03
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_2024 for 2024-02-04, then filter +/-60 min and 250 nmi around 39.5767,-109.2671.
NASA POWER/Horizons/DONKI: batch context for 237UAP00607 at 2024-02-04T11:11: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 257.0 deg at 11.95 m/s; a passive balloon could drift about 86.1 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
81.60
2024-02-04T12:00:00+00:00
257.00
11.95
86.10
36.00 at 3595.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-02-04T10:11:00+00:00 to 2024-02-04T12:11:00+00:00
Radius
250.00 nmi
Trace files scanned
45226
Tracks retained
47
Support status
aircraft plausible candidate present
Best-candidate note
ordinary-object favored only if source wording is weak; high-value reports with radar/video/rapid maneuver language remain unresolved residuals.
Strong candidates
0
Plausible candidates
1
Reporting-aircraft tracks excluded
0
Weak candidates
9
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N7901A B738 aaba81
plausible aircraft candidate
59.37
89.50
5.01
41000
291.50
7.52
N382UP B763 a46488
weak aircraft candidate
43.05
193.30
0.02
39025
62.30
1.74
N397AZ B763 a49ce2
weak aircraft candidate
21.90
130.20
8.72
37000
65.80
4.35
N241AZ B763 a233ce
weak aircraft candidate
14.34
159.10
7.16
37000
312.00
3.33
LX-SCV B744 4d0128
weak aircraft candidate
8.67
207.90
17.53
35000
56.60
2.00
N211UA B772 a1befc
weak aircraft candidate
8.64
208.00
30.73
34300
112.90
1.93
N774UA B772 aa79a6
weak aircraft candidate
8.57
217.00
32.61
33350
110.30
1.70
N991AU A321 add66d
weak aircraft candidate
8.52
123.80
20.35
34975
75.80
1.55
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-02-04T11:11:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
39.57672, -109.26713
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
not explicit
Reported motion remains only partly explained; this is a principal reason for high-value unresolved status.
Radar / official check
radar observation claimed
Radar or hard maneuvering language is treated as a conflict/collection gap, not hand-waved away.
Analytic disposition
unresolved
237UAP00607 was screened against historical public LEO catalog objects orbital elements at the extracted time and observer coordinate. The screen did not produce enough mundane evidence to close the case under the normal-object favored standard. Hard features retained for follow-up: radar/primary evidence.
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.
This case is retained as high-value unresolved because the hardest reported behavior is not resolved by the current normal-object layers.
Appendix A. Public Report Text Extracts
237UAP00607
Washington Operations Center
Date: 2/4/2024 4:11:00 AM (-07 MST)
Title: SCX3053 UFO-UAP ACTIVITY 02-04-2024
Latitude: 39.576718900000003 Latitude: -109.2671314
DESCRIPTION
PRELIM INFO FROM FAA OPS: MYTON, UT/UFO-UAP ACTIVITY/0411M/DENVER ARTCC ADVISED SUN COUNTRY 3053,
B738, PDX - AFW, REPORTED AN UNIDENTIFIED AERIAL PHENOMENON OFF THE LEFT SIDE WHILE SE BOUND AT
FL410 60 SE MYTON VOR (MTU). THE UAP APPEARED TO BE 5 SEPARATE CRAFT WITH WHITE LIGHTS TRAVELING
BETWEEN FL600 AND FL800. NO PRIMARY TARGETS OBSERVED ON RADAR. WOC 7-3333 HM/JE
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: 237UAP00607
Time and observer coordinate
extracted
2024-02-04T11:11:00+00:00 at 39.57672, -109.26713
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
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
high-value unresolved
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/