PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 25 / 237UAP00336
237UAP00336
Radar/correlation-focused public UAP report; score 66
HIGH-VALUE UNRESOLVED
Report No.
UAP-OM-25-237UAP00336
Disposition
HIGH-VALUE UNRESOLVED
Primary Case
237UAP00336
Generated
2026-05-20 18:32 UTC
Report Time
2024-01-02T01:43:00+00:00
Observer
42.36231, -74.01885
Source Case IDs
237UAP00336
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 2020-09-03, spanning azimuth 22.83-38.88 deg and elevation 16.04-16.57 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
237UAP00336 remains high-value unresolved after screening against historical Starlink orbital elements. The strongest compact object grouping contains 3 objects from 2020-09-03; however, this does not close the case because hard report features remain: radar/primary evidence, hard maneuver language. Context noted but not treated as causation: very dense orbital-object sky background; context only, not causation; NASA/JPL known-small-body rejection screen present.
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: 2024-01-02T01:43:00+00:00.
External object layer used: Starlink.
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: strong ADS-B aircraft candidate N22805 G280 a2012f at 5.7 km, azimuth 327.4 deg, elevation 36.31 deg, 1.66 min from report.
Non-causal context / rejection screens: very dense orbital-object sky background; context only, not causation; NASA/JPL known-small-body rejection screen present.
Remaining hard features: radar/primary evidence; hard maneuver language.
Objects above horizon: 274; at/above 10 deg: 143.
Top compact same-launch/designator group: 3 objects from 2020-09-03.
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.
Aircraft reported an unidentified aerial phenomenon off their front while SW bound at FL260, 25NM SSW of ALB over 42.2105N, -74.375W. The unknown phenomenon was bright orange and moved quickly at near level altitude and would jump in altitude to around FL500. Pilot kept reporting the same maneuvers all the way down near DNY intersection. It appears some radar data was acquired up until 0155Z.
Report time used
2024-01-02T01:43:00+00:00
Observer coordinate used
42.36231, -74.01885
Observer source basis
aviation_offset:25NM SSW of ALB (public text extract 237UAP00336)
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
5268
Historical element rows
5246
Above horizon at report minute
274
At/above 10 deg
143
Largest same-sky cluster
134
5.2 Same-Launch / Same-Designator Candidate Groups
#
Launch Date
Count
Azimuth Span
Elevation Span
Motion Labels
Members
1
2020-09-03
3
22.83-38.88 deg
16.04-16.57 deg
eastward, setting
STARLINK-1707, STARLINK-1770, STARLINK-1653
5.3 Primary Group Members
Object
NORAD
Launch
Az
El
Range km
Apparent Motion
Element Age h
STARLINK-1707
46359
2020-09-03
36.43
16.57
1446.07
eastward, setting
1.14
STARLINK-1770
46383
2020-09-03
38.88
16.1
1468.48
eastward, setting
1.26
STARLINK-1653
46352
2020-09-03
22.83
16.04
1472.14
eastward, setting
1.21
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
55495
STARLINK-5100
PAYLOAD
US
2023-02-02
n/a
53843
STARLINK-4769
PAYLOAD
US
2022-09-19
n/a
52845
STARLINK-4168
PAYLOAD
US
2022-06-17
n/a
46786
STARLINK-1893
PAYLOAD
US
2020-10-24
n/a
47394
STARLINK-2115
PAYLOAD
US
2021-01-20
2024-12-31
47402
STARLINK-2124
PAYLOAD
US
2021-01-20
2025-01-13
57259
STARLINK-5505
PAYLOAD
US
2023-07-07
2024-03-02
51974
STARLINK-3672
PAYLOAD
US
2022-03-09
n/a
57934
STARLINK-30458
PAYLOAD
US
2023-09-24
2025-10-07
53931
STARLINK-5015
PAYLOAD
US
2022-09-24
2025-11-27
45695
STARLINK-1420
PAYLOAD
US
2020-06-04
n/a
55648
STARLINK-5501
PAYLOAD
US
2023-02-17
n/a
5.6 NASA/JPL Near-Earth Object Screen
This secondary object screen checks NASA/JPL close-approach objects near the report date and propagates their observer geometry through Horizons at the report coordinate. It is a known-object rejection layer, not a generic astronomy backdrop.
NASA/JPL CAD window
event date +/- 1 day, dist-max 0.2 au
Coordinate used
42.36, -74.02
Close-approach objects
20
Above horizon
9
Bright-ish above horizon
0 using apparent magnitude <= 10 screen
5.7 NASA/JPL Objects Above Horizon
Object
Close Approach UTC
Dist au
H
Az
El
App Mag
2023 YR
2024-Jan-02 03:18
0.0115640803252806
24.90
265.42
68.92
17.48
2024 AA
2024-Jan-02 16:39
0.00408142072236893
27.41
65.07
40.40
18.25
2023 YR1
2024-Jan-01 02:48
0.0166144160264511
25.68
358.07
63.59
18.94
2019 KK5
2024-Jan-02 21:21
0.0260972744624454
22.79
314.96
10.74
19.39
2023 YY1
2024-Jan-01 20:09
0.0271321168847435
25.77
147.48
75.71
19.41
2011 YP10
2024-Jan-02 12:59
0.0704899553763525
23.94
47.96
53.17
19.62
2024 AA6
2024-Jan-01 12:30
0.0491415516379195
25.12
118.04
7.17
20.19
2023 XZ4
2024-Jan-02 15:23
0.144999914734518
24.05
236.49
27.20
22.95
2025 AB
2024-Jan-01 11:34
0.158379265423944
27.13
239.35
59.03
25.45
5.8 NASA/JPL Bright-Candidate Result
Object
Az
El
App Mag
No above-horizon close-approach object met the apparent magnitude <= 10 screen.
NASA/JPL CAD listed 20 near-Earth close approaches in the event-date +/-1 day window within 0.2 au.
Horizons placed 9 of those objects above the local horizon at the report coordinate/time.
None of the above-horizon close-approach objects were remotely bright enough for naked-eye explanation using the mag<=10 screen.
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-01-02, then filter +/-60 min and 250 nmi around 42.3623,-74.0188.
NASA POWER/Horizons/DONKI: batch context for 237UAP00336 at 2024-01-02T01:43: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 59.6 deg at 3.22 m/s; a passive balloon could drift about 23.2 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
USM00072518
ALBANY COUNTY AIRPORT; NY.
46.70
2024-01-02T00:00:00+00:00
59.60
3.22
23.20
35.90 at 25232.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-01-02T00:43:00+00:00 to 2024-01-02T02:43:00+00:00
Radius
250.00 nmi
Trace files scanned
32153
Tracks retained
800
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
7
Plausible candidates
114
Reporting-aircraft tracks excluded
4
Weak candidates
199
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N22805 G280 a2012f
strong aircraft candidate
87.68
5.10
0.01
13800
327.40
36.31
G-YMMJ B772 4007f5
strong aircraft candidate
77.94
3.50
0.02
23975
81.40
52.07
N538AS B738 a6ce36
strong aircraft candidate
69.70
72.60
0.02
34000
343.80
7.18
N848BC FA7X ab9dad
strong aircraft candidate
66.73
35.10
0.03
20550
74.90
6.98
N421YX E75L a50192
strong aircraft candidate
61.04
35.10
0.05
8725
186.80
7.72
N540GJ CRJ7 a6d88b
strong aircraft candidate
55.68
23.60
7.55
375
23.30
-0.05
N761YX E75L aa477b
strong aircraft candidate
49.30
64.00
0.06
18600
115.00
5.97
N821NW A333 ab35d3
reporting aircraft track; excluded from support counts
95.32
10.10
0.13
37000
199.90
45.87
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-01-02T01:43:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
42.36231, -74.01885
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
not explicit
Reported motion remains only partly explained; this is a principal reason for high-value unresolved status.
Radar / official check
not specified
Radar or hard maneuvering language is treated as a conflict/collection gap, not hand-waved away.
Analytic disposition
unresolved
237UAP00336 remains high-value unresolved after screening against historical Starlink orbital elements. The strongest compact object grouping contains 3 objects from 2020-09-03; however, this does not close the case because hard report features remain: radar/primary evidence, hard maneuver language. Context noted but not treated as causation: very dense orbital-object sky background; context only, not causation; NASA/JPL known-small-body rejection screen present.
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
237UAP00336
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 01:43 01/02/2024 Callsign: PDT5795 Origin: BOS
Status: Closed Aircraft: E145 Destination: MDT
POD: DEN Tail Number: New Destination:
Reporting Facility: ZBW Operator: PDT Operator Type: Commercial
Paged: YES MOR Init: YES
MOR ID: ZBW-M-2024/01/01-0002
REMARKS
Aircraft reported an unidentified aerial phenomenon off their front while SW bound at FL260, 25NM SSW of ALB over 42.2105N,
-74.375W. The unknown phenomenon was bright orange and moved quickly at near level altitude and would jump in altitude to
around FL500. Pilot kept reporting the same maneuvers all the way down near DNY intersection. It appears some radar data
was acquired up until 0155Z.
SKYWATCH INCIDENT REPORT | DATE: 2024-01-02T01:43 | 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: 237UAP00336
Time and observer coordinate
extracted
2024-01-02T01:43:00+00:00 at 42.36231, -74.01885
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
screened
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
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/