PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 66 / 237UAP00378
237UAP00378
Radar/correlation-focused public UAP report; score 52
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-66-237UAP00378
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00378
Generated
2026-05-20 18:32 UTC
Report Time
2024-09-15T07:15:00+00:00
Observer
35.90042, -82.86661
Source Case IDs
237UAP00378
Abstract
This case file evaluates a reported UAP sighting against historical Starlink orbital elements. The primary external-object candidate is a 4-object same-launch group from 2021-02-16, spanning azimuth 316.83-341.49 deg and elevation 10.86-26.02 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
237UAP00378 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: plausible ADS-B aircraft candidate F-HUVF A359 39d2a5 at 112.8 km, azimuth 294.2 deg, elevation 5.19 deg, 0.01 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-09-15T07:15:00+00:00.
External object layer used: Starlink.
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: plausible ADS-B aircraft candidate F-HUVF A359 39d2a5 at 112.8 km, azimuth 294.2 deg, elevation 5.19 deg, 0.01 min from report.
Non-causal context / rejection screens: very dense orbital-object sky background; context only, not causation.
Objects above horizon: 325; at/above 10 deg: 141.
Top compact same-launch/designator group: 4 objects from 2021-02-16.
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 while NE bound at FL410, 50NM E of VXV. The unknown phenomenon was three white lights in trail of each other at a slightly higher altitude in the distance. The UAP was not observed on ATC facility radar system.
Report time used
2024-09-15T07:15:00+00:00
Observer coordinate used
35.90042, -82.86661
Observer source basis
aviation_offset:50NM E of VXV (public text extract 237UAP00378)
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
6400
Historical element rows
6381
Above horizon at report minute
325
At/above 10 deg
141
Largest same-sky cluster
132
5.2 Same-Launch / Same-Designator Candidate Groups
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
34
SATCAT rows matched
34
Top owners
US: 34
Object types
PAYLOAD: 34
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
56688
STARLINK-30122
PAYLOAD
US
2023-05-19
n/a
59703
STARLINK-32086
PAYLOAD
US
2024-05-08
n/a
57785
STARLINK-30381
PAYLOAD
US
2023-09-04
n/a
59235
STARLINK-31467
PAYLOAD
US
2024-03-16
n/a
44952
STARLINK-1117
PAYLOAD
US
2020-01-07
2025-06-01
49149
STARLINK-3053
PAYLOAD
US
2021-09-14
2025-04-10
46754
STARLINK-1923
PAYLOAD
US
2020-10-24
2024-12-02
57151
STARLINK-5776
PAYLOAD
US
2023-06-23
n/a
52090
STARLINK-3712
PAYLOAD
US
2022-03-19
n/a
58844
STARLINK-31269
PAYLOAD
US
2024-01-24
n/a
55429
STARLINK-5645
PAYLOAD
US
2023-01-31
n/a
56379
STARLINK-6157
PAYLOAD
US
2023-05-04
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-09-15, then filter +/-60 min and 250 nmi around 35.9004,-82.8666.
NASA POWER/Horizons/DONKI: batch context for 237UAP00378 at 2024-09-15T07:15: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 219.7 deg at 2.58 m/s; a passive balloon could drift about 18.6 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
USM00072318
BLACKSBURG; VA.
262.70
2024-09-15T12:00:00+00:00
219.70
2.58
18.60
35.80 at 14525.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-09-15T06:00:00+00:00 to 2024-09-15T08:30:00+00:00
Radius
300.00 nmi
Trace files scanned
59403
Tracks retained
196
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
9
Reporting-aircraft tracks excluded
1
Weak candidates
19
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N538QS C68A a6cf94
reporting aircraft track; excluded from support counts
93.82
15.30
0.08
41000
345.90
37.86
F-HUVF A359 39d2a5
plausible aircraft candidate
61.51
105.90
0.01
37000
294.20
5.19
N274AH PC24 a2b560
plausible aircraft candidate
45.02
142.80
0.03
28200
44.20
2.51
N222SH EC30 a1ea07
plausible aircraft candidate
44.59
126.80
0.08
1700
157.40
-0.42
N585QS C68A a789ea
plausible aircraft candidate
40.03
48.80
0.10
16350
222.50
6.79
N200A GLF6 a19203
plausible aircraft candidate
35.90
51.60
0.05
41000
21.10
8.33
N135NK EC35 a08efa
plausible aircraft candidate
30.91
119.40
10.99
1550
178.70
-0.31
N362CM B763 a413f8
plausible aircraft candidate
16.69
62.10
0.03
5350
323.50
3.23
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-09-15T07:15:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
35.90042, -82.86661
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
three-object/light language present
Primary same-launch group contains 4 propagated objects in a compact sky sector.
Motion language
in trail
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
237UAP00378 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: plausible ADS-B aircraft candidate F-HUVF A359 39d2a5 at 112.8 km, azimuth 294.2 deg, elevation 5.19 deg, 0.01 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
237UAP00378
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 07:15 09/15/2024 Callsign: EJA538 Origin: HOU
Status: Closed Aircraft: C68A Destination: JFK
POD: DEN Tail Number: New Destination:
Reporting Facility: ZTL Operator: EJA Operator Type: Commercial
Paged: YES MOR Init: YES
MOR ID: ZTL-M-2024/09/15-0001
REMARKS
Aircraft reported an unidentified aerial phenomenon while NE bound at FL410, 50NM E of VXV. The unknown phenomenon was
three white lights in trail of each other at a slightly higher altitude in the distance. The UAP was not observed on ATC facility
radar system.
SKYWATCH INCIDENT REPORT | DATE: 2024-09-15T07:15 | 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: 237UAP00378
Time and observer coordinate
extracted
2024-09-15T07:15:00+00:00 at 35.90042, -82.86661
Orbital object propagation
screened
Starlink
Space-Track SATCAT metadata
screened
34 NORAD IDs checked; 34 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/