PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 86 / 237UAP00288
237UAP00288
Multiple-witness public UAP report; score 44
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-86-237UAP00288
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00288
Generated
2026-05-20 18:32 UTC
Report Time
2023-08-16T06:00:00+00:00
Observer
34.56220, -86.75071
Source Case IDs
237UAP00288
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
237UAP00288 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N559UW A321 a722b1 at 42.1 km, azimuth 336.5 deg, elevation 14.44 deg, 0.33 min from report. Dense satellite presence alone is not treated as causation in this packet.
1.1 Key Findings
Source score 44 based on: multiple aircraft/facility witnesses, maneuvering/motion anomaly, UAP/UFO language.
Report time used: 2023-08-16T06:00: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: strong ADS-B aircraft candidate N559UW A321 a722b1 at 42.1 km, azimuth 336.5 deg, elevation 14.44 deg, 0.33 min from report.
Remaining hard features: multiple witnesses/facilities; hard maneuver language.
Objects above horizon: 204; at/above 10 deg: 79.
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 in the vicinity of HSV of what appeared to be two aircraft refueling well above their altitude of FL340. The unknown phenomenon was described as two bright lights 60 miles N of BHM circling at a very high altitude. The lights would stay on for a few minutes and then disappear. Multiple aircraft and facilities are reporting the same description of lights in the general area. NKS2866, Birmingham Tower personnel, and reports from aircraft in Atlanta Center's airspace. AWO notified.
Report time used
2023-08-16T06:00:00+00:00
Observer coordinate used
34.56220, -86.75071
Observer source basis
aviation_offset:60 miles N of BHM (public text extract 237UAP00288)
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
4597
Historical element rows
4391
Above horizon at report minute
204
At/above 10 deg
79
Largest same-sky cluster
45
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 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
30
SATCAT rows matched
30
Top owners
US: 30
Object types
PAYLOAD: 30
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
56133
STARLINK-5566
PAYLOAD
US
2023-03-29
n/a
52494
STARLINK-3857
PAYLOAD
US
2022-05-06
n/a
51135
STARLINK-3363
PAYLOAD
US
2022-01-19
n/a
56556
STARLINK-5302
PAYLOAD
US
2023-05-14
n/a
53566
STARLINK-4576
PAYLOAD
US
2022-08-19
n/a
56103
STARLINK-6096
PAYLOAD
US
2023-03-29
n/a
51136
STARLINK-3253
PAYLOAD
US
2022-01-19
n/a
47366
STARLINK-2081
PAYLOAD
US
2021-01-20
n/a
45047
STARLINK-1131
PAYLOAD
US
2020-01-29
n/a
54052
STARLINK-5189
PAYLOAD
US
2022-10-20
n/a
53839
STARLINK-4784
PAYLOAD
US
2022-09-19
n/a
51122
STARLINK-3373
PAYLOAD
US
2022-01-19
2024-07-04
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
34.56, -86.75
Close-approach objects
16
Above horizon
11
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 QH5
2023-Aug-15 18:05
0.0378396842051172
24.55
240.69
49.06
19.09
2010 PK9
2023-Aug-16 11:36
0.147072701659612
21.81
202.83
70.21
19.14
2023 PH1
2023-Aug-16 21:57
0.0134076266864546
27.68
207.26
23.68
19.61
2023 PX
2023-Aug-15 23:30
0.033259322093466
25.91
207.22
16.84
19.95
2023 QC1
2023-Aug-15 00:24
0.0802665965328313
25.22
184.90
41.82
20.14
2023 QL2
2023-Aug-15 09:17
0.0593953536369405
24.91
182.55
11.85
20.16
2017 BZ5
2023-Aug-16 20:01
0.127749610247471
22.27
46.96
57.25
20.30
2023 PG
2023-Aug-16 08:52
0.0646262494499499
24.49
254.00
71.02
20.32
2023 QN1
2023-Aug-15 19:53
0.0776351100690678
24.27
164.10
79.38
20.34
2023 QQ2
2023-Aug-16 17:49
0.0771828080989217
25.11
250.71
52.74
21.35
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 16 near-Earth close approaches in the event-date +/-1 day window within 0.2 au.
Horizons placed 11 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
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_2023 for 2023-08-16, then filter +/-60 min and 250 nmi around 34.5622,-86.7507.
NASA POWER/Horizons/DONKI: batch context for 237UAP00288 at 2023-08-16T06:00: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 251.0 deg at 13.3 m/s; a passive balloon could drift about 95.8 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
USM00072230
BIRMINGHAM; AL
153.80
2023-08-16T00:00:00+00:00
251.00
13.30
95.80
35.00 at 174.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
2023-08-16T05:00:00+00:00 to 2023-08-16T07:00:00+00:00
Radius
250.00 nmi
Trace files scanned
55125
Tracks retained
199
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
3
Plausible candidates
16
Reporting-aircraft tracks excluded
0
Weak candidates
25
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
N559UW A321 a722b1
strong aircraft candidate
81.72
40.30
0.33
36000
336.50
14.44
N414CY C208 a4e345
strong aircraft candidate
68.67
14.80
5.14
3900
111.00
4.41
N959NK A20N ad574c
strong aircraft candidate
56.99
70.80
1.09
31975
176.40
6.65
N541FL FA20 a6dc2b
plausible aircraft candidate
48.90
95.50
0.15
35975
77.00
5.32
N677ST PC12 a8f75b
plausible aircraft candidate
47.21
115.70
2.21
1600
179.70
-0.28
N511DN A359 a6657e
plausible aircraft candidate
42.69
160.90
0.13
30925
32.20
2.18
N8887Q B38M ac3ee9
plausible aircraft candidate
41.34
152.20
0.06
5350
352.40
-0.08
N8310C B738 ab5e6c
plausible aircraft candidate
35.36
152.40
1.17
1000
1.70
-0.66
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
2023-08-16T06:00:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
34.56220, -86.75071
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
circling, disappear
Apparent motion labels in the object table provide a plausible but not definitive comparison.
Radar / official check
not specified
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
237UAP00288 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate N559UW A321 a722b1 at 42.1 km, azimuth 336.5 deg, elevation 14.44 deg, 0.33 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
237UAP00288
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 06:00 08/16/2023 Callsign: AAL1397 Origin: MIA
Status: Closed Aircraft: B738 Destination: MCI
POD: DEN Tail Number: New Destination:
Reporting Facility: ZME Operator: AAL Operator Type: Commercial
Paged: YES
REMARKS
Aircraft reported an unidentified aerial phenomenon in the vicinity of HSV of what appeared to be two aircraft refueling well above
their altitude of FL340. The unknown phenomenon was described as two bright lights 60 miles N of BHM circling at a very high
altitude. The lights would stay on for a few minutes and then disappear. Multiple aircraft and facilities are reporting the same
description of lights in the general area. NKS2866, Birmingham Tower personnel, and reports from aircraft in Atlanta Center's
airspace. AWO notified.
SKYWATCH INCIDENT REPORT | DATE: 2023-08-16T06:00 | 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: 237UAP00288
Time and observer coordinate
extracted
2023-08-16T06:00:00+00:00 at 34.56220, -86.75071
Orbital object propagation
screened
Starlink
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
screened
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/