PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 67 / 237UAP00384
237UAP00384
Radar/correlation-focused public UAP report; score 52
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-67-237UAP00384
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00384
Generated
2026-05-20 18:32 UTC
Report Time
2024-10-21T01:36:00+00:00
Observer
37.96867, -72.70900
Source Case IDs
237UAP00384
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
237UAP00384 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N586JB A320 a78cfc at 30.2 km, azimuth 100.4 deg, elevation 19.27 deg, 7.10 min from report. Dense satellite presence alone is not treated as causation in this packet.
1.1 Key Findings
Source score 52 based on: radar/primary-return language, high-altitude report, UAP/UFO language.
Report time used: 2024-10-21T01:36: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 N586JB A320 a78cfc at 30.2 km, azimuth 100.4 deg, elevation 19.27 deg, 7.10 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 front side while NW bound at FL360, 125NM SE of ACY. The unknown phenomenon was several orbs traveling multiple directions at approximately FL400 to FL600. The UAP was not observed on ATC facility radar system.
Report time used
2024-10-21T01:36:00+00:00
Observer coordinate used
37.96867, -72.70900
Observer source basis
aviation_offset:125NM SE of ACY (public text extract 237UAP00384)
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
19695
Historical element rows
19695
Above horizon at report minute
1179
At/above 10 deg
570
Largest same-sky cluster
570
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
29
Top owners
US: 12, PRC: 10, CIS: 6, UK: 1
Object types
DEBRIS: 15, PAYLOAD: 14
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
52354
STARLINK-3876
PAYLOAD
US
2022-04-29
2025-08-04
58860
STARLINK-31213
PAYLOAD
US
2024-01-29
n/a
58367
STARLINK-30891
PAYLOAD
US
2023-11-18
n/a
34454
COSMOS 2251 DEB
DEBRIS
CIS
1993-06-16
n/a
53005
STARLINK-4288
PAYLOAD
US
2022-07-07
n/a
55036
UMBRA-05
PAYLOAD
US
2023-01-03
2025-11-19
6764
COSMOS 249 DEB
DEBRIS
CIS
1968-10-20
n/a
56777
STARLINK-5582
PAYLOAD
US
2023-05-31
n/a
30182
FENGYUN 1C DEB
DEBRIS
PRC
1999-05-10
n/a
60382
QIANFAN-4
PAYLOAD
PRC
2024-08-06
n/a
30677
FENGYUN 1C DEB
DEBRIS
PRC
1999-05-10
n/a
40975
SNAP-3 JIMI
PAYLOAD
US
2015-10-08
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-10-21, then filter +/-60 min and 250 nmi around 37.9687,-72.7090.
NASA POWER/Horizons/DONKI: batch context for 237UAP00384 at 2024-10-21T01:36: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 346.4 deg at 8.42 m/s; a passive balloon could drift about 60.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
USM00072402
WALLOPS ISLAND; VA.
243.30
2024-10-21T00:00:00+00:00
346.40
8.42
60.70
35.20 at 19595.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-10-21T00:21:00+00:00 to 2024-10-21T02:51:00+00:00
Radius
300.00 nmi
Trace files scanned
43463
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
2
Plausible candidates
6
Reporting-aircraft tracks excluded
0
Weak candidates
51
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N586JB A320 a78cfc
strong aircraft candidate
74.45
29.60
0.05
35000
100.40
19.27
N316RK B38M a35e9c
strong aircraft candidate
67.90
65.30
0.01
36000
32.40
8.20
N1605 B763 a0f4b5
plausible aircraft candidate
52.02
117.60
0.15
35000
292.60
3.94
N838DN B739 ab766a
plausible aircraft candidate
48.37
149.10
0.01
34000
280.20
2.91
PS-BTG GL7T e49688
plausible aircraft candidate
42.66
147.00
0.26
42975
75.10
3.89
N814VL B738 ab1a1e
plausible aircraft candidate
34.97
175.90
0.05
33725
322.50
2.69
N612NK A320 a7f762
plausible aircraft candidate
32.67
175.80
0.02
36000
298.70
2.69
N78004 B772 aa92fb
plausible aircraft candidate
16.98
147.00
7.02
33000
63.90
2.68
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-10-21T01:36:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
37.96867, -72.70900
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
multiple-object/light language present
No compact same-launch count match; retained for unresolved report features.
Motion language
not explicit
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
237UAP00384 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N586JB A320 a78cfc at 30.2 km, azimuth 100.4 deg, elevation 19.27 deg, 7.10 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
237UAP00384
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 01:36 10/21/2024 Callsign: AAL2694 Origin: SYCJ
Status: Closed Aircraft: B38M Destination: JFK
POD: DEN Tail Number: New Destination:
Reporting Facility: ZNY Operator: AAL Operator Type: Commercial
Paged: YES
REMARKS
Aircraft reported an unidentified aerial phenomenon off the front side while NW bound at FL360, 125NM SE of ACY. The
unknown phenomenon was several orbs traveling multiple directions at approximately FL400 to FL600. The UAP was not
observed on ATC facility radar system.
SKYWATCH INCIDENT REPORT | DATE: 2024-10-21T01:36 | 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: 237UAP00384
Time and observer coordinate
extracted
2024-10-21T01:36:00+00:00 at 37.96867, -72.70900
Orbital object propagation
screened
public LEO catalog objects
Space-Track SATCAT metadata
screened
30 NORAD IDs checked; 29 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/