PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 50 / 237UAP00346
237UAP00346
Radar/correlation-focused public UAP report; score 54
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-50-237UAP00346
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00346
Generated
2026-05-20 18:32 UTC
Report Time
2024-01-27T03:20:00+00:00
Observer
40.91294, -78.87430
Source Case IDs
237UAP00346
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
237UAP00346 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N240JQ E75L a230d6 at 12.5 km, azimuth 354.3 deg, elevation 36.21 deg, 7.99 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-01-27T03:20: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 N240JQ E75L a230d6 at 12.5 km, azimuth 354.3 deg, elevation 36.21 deg, 7.99 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 off the right side while W bound at FL200, 40 NM W of PSB. The unknown phenomenon was 2 lights, white then turning red, chasing each other moving in the vicinity of EWC above the aircraft, fast moving. The UAP was not observed on ATC facility radar system.
Report time used
2024-01-27T03:20:00+00:00
Observer coordinate used
40.91294, -78.87430
Observer source basis
aviation_offset:40 NM W of PSB (public text extract 237UAP00346)
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
19023
Historical element rows
19023
Above horizon at report minute
1110
At/above 10 deg
591
Largest same-sky cluster
591
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.
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
6849
COSMOS 592
PAYLOAD
CIS
1973-10-02
n/a
26077
SL-16 DEB
DEBRIS
CIS
2000-02-03
n/a
12976
COSMOS 1321
PAYLOAD
CIS
1981-11-28
n/a
42263
DMSP 5D-2 F13 DEB
DEBRIS
US
1995-03-24
n/a
45580
STARLINK-1333
PAYLOAD
US
2020-04-22
n/a
31206
FENGYUN 1C DEB
DEBRIS
PRC
1999-05-10
n/a
44733
STARLINK-1028
PAYLOAD
US
2019-11-11
2025-02-14
44509
ARIANE 42P DEB
DEBRIS
FR
1992-08-10
n/a
58518
STARLINK-31021
PAYLOAD
US
2023-12-07
n/a
57580
OBJECT A
UNKNOWN
PRC
2023-08-10
2025-05-27
18160
COSMOS 1864
PAYLOAD
CIS
1987-07-06
n/a
48609
FALCON 9 DEB
DEBRIS
US
2021-05-15
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-01-27, then filter +/-60 min and 250 nmi around 40.9129,-78.8743.
NASA POWER/Horizons/DONKI: batch context for 237UAP00346 at 2024-01-27T03:20: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 4-10 statute miles; precipitation was reported in at least one observation; 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 6.4 deg at 3.12 m/s; a passive balloon could drift about 22.5 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
USM00072520
PITTSBURGH; PA.
120.80
2024-01-27T00:00:00+00:00
6.40
3.12
22.50
34.30 at 26697.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-27T02:05:00+00:00 to 2024-01-27T04:35:00+00:00
Radius
300.00 nmi
Trace files scanned
31420
Tracks retained
1200
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
16
Plausible candidates
89
Reporting-aircraft tracks excluded
2
Weak candidates
120
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N240JQ E75L a230d6
strong aircraft candidate
82.89
12.10
0.01
30000
354.30
36.21
N591NN CRJ9 a7a257
strong aircraft candidate
80.99
30.90
0.08
35000
105.00
18.51
N116DU BCS1 a042db
strong aircraft candidate
76.97
23.30
0.10
30975
337.70
21.46
N989SF GLEX adce29
strong aircraft candidate
73.72
35.20
0.14
43000
166.20
19.00
N910AN B738 ac96b8
strong aircraft candidate
71.89
42.00
0.15
31000
348.30
11.79
N27213 B738 a2b081
strong aircraft candidate
71.69
42.20
0.11
29000
348.20
10.96
N179DN B763 a13af4
strong aircraft candidate
71.12
59.10
0.08
36000
160.30
8.43
N318NB A319 a365b7
strong aircraft candidate
69.80
11.20
0.04
35000
231.90
15.49
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-27T03:20:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
40.91294, -78.87430
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
two-object/light language present
No compact same-launch count match; retained for unresolved report features.
Motion language
turning, 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
237UAP00346 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N240JQ E75L a230d6 at 12.5 km, azimuth 354.3 deg, elevation 36.21 deg, 7.99 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
237UAP00346
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 03:20 01/27/2024 Callsign: RPA4809 Origin: JFK
Status: Closed Aircraft: E75S Destination: PIT
POD: DEN Tail Number: New Destination:
Reporting Facility: ZOB Operator: RPA Operator Type: Commercial
Paged: YES MOR Init: YES
MOR ID: ZOB-M-2024/01/26-0003
REMARKS
Aircraft reported an unidentified aerial phenomenon off the right side while W bound at FL200, 40 NM W of PSB. The unknown
phenomenon was 2 lights, white then turning red, chasing each other moving in the vicinity of EWC above the aircraft, fast
moving. The UAP was not observed on ATC facility radar system.
SKYWATCH INCIDENT REPORT | DATE: 2024-01-27T03:20 | 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: 237UAP00346
Time and observer coordinate
extracted
2024-01-27T03:20:00+00:00 at 40.91294, -78.87430
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/