PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 05 / 237UAP00618
237UAP00618
Radar/correlation-focused public UAP report; score 92
NORMAL-OBJECT FAVORED
Report No.
UAP-OM-05-237UAP00618
Disposition
NORMAL-OBJECT FAVORED
Primary Case
237UAP00618
Generated
2026-05-20 18:32 UTC
Report Time
2024-03-02T09:56:00+00:00
Observer
40.20629, -100.59209
Source Case IDs
237UAP00618
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
237UAP00618 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate C-FLKO B38M c01e1f at 64.8 km, azimuth 251.6 deg, elevation 9.02 deg, 8.00 min from report. Dense satellite presence alone is not treated as causation in this packet.
1.1 Key Findings
Source score 92 based on: radar/primary-return language, multiple aircraft/facility witnesses, negative official correlation, high-altitude report, UAP/UFO language.
Report time used: 2024-03-02T09:56: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 C-FLKO B38M c01e1f at 64.8 km, azimuth 251.6 deg, elevation 9.02 deg, 8.00 min from report.
Non-causal context / rejection screens: very dense orbital-object sky background; context only, not causation.
Remaining hard features: multiple witnesses/facilities; hard maneuver language.
Objects above horizon: 272; at/above 10 deg: 135.
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.
Washington Operations Center Date: 3/2/2024 3:56:00 AM (-06 CST) Title: EJA316 UFO-UAP ACTIVITY 03-02-2024 Latitude: 40.206292220000002 Latitude: -100.59209389999999 DESCRIPTION PRELIM INFO FROM FAA OPS: MC COOK, NE/UFO-UAP ACTIVITY/0356C/DENVER ARTCC ADVISED NETJETS 316, E55P, LAS - OMA, REPORTED UNIDENTIFIED AERIAL PHENOMENON WHILE E BOUND AT FL410 VCNTY MCK. PHENOMENON WAS RAPIDLY MOVING DIM AND BRIGHT LIGHTS. MULTIPLE ACFT REPORTING SEEING SIMILAR PHENOMENA. UAP WAS NOT OBSERVED ON ATC RADAR SYSTEMS. WOC 7-3333 MO/TJ
Report time used
2024-03-02T09:56:00+00:00
Observer coordinate used
40.20629, -100.59209
Observer source basis
(public text extract 237UAP00618)
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
5527
Historical element rows
5496
Above horizon at report minute
272
At/above 10 deg
135
Largest same-sky cluster
121
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
57641
STARLINK-30312
PAYLOAD
US
2023-08-17
n/a
46080
STARLINK-1568
PAYLOAD
US
2020-08-07
n/a
57060
STARLINK-6227
PAYLOAD
US
2023-06-22
n/a
46337
STARLINK-1750
PAYLOAD
US
2020-09-03
2026-03-03
58518
STARLINK-31021
PAYLOAD
US
2023-12-07
n/a
55998
STARLINK-5902
PAYLOAD
US
2023-03-24
n/a
56893
STARLINK-6216
PAYLOAD
US
2023-06-12
n/a
58513
STARLINK-30998
PAYLOAD
US
2023-12-07
n/a
58092
STARLINK-30615
PAYLOAD
US
2023-10-18
n/a
48369
STARLINK-2641
PAYLOAD
US
2021-05-04
2025-04-07
58012
STARLINK-30525
PAYLOAD
US
2023-10-05
n/a
58487
STARLINK-30987
PAYLOAD
US
2023-12-03
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-03-02, then filter +/-60 min and 250 nmi around 40.2063,-100.5921.
NASA POWER/Horizons/DONKI: batch context for 237UAP00618 at 2024-03-02T09:56: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 2.5-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 62.0 deg at 19.39 m/s; a passive balloon could drift about 139.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
USM00072562
NORTH PLATTE/LEE BIRD; NE.
103.40
2024-03-02T12:00:00+00:00
62.00
19.39
139.60
36.00 at 11780.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-03-02T08:26:00+00:00 to 2024-03-02T11:26:00+00:00
Radius
300.00 nmi
Trace files scanned
43919
Tracks retained
269
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
1
Plausible candidates
22
Reporting-aircraft tracks excluded
2
Weak candidates
29
5.19 Top ADS-B Candidate Tracks
Aircraft
Status
Score
Min dist km
Nearest dt min
Alt ft
Az
El
C-FLKO B38M c01e1f
strong aircraft candidate
60.81
2.80
0.11
35000
251.60
9.02
N316QS E55P a35e8a
reporting aircraft track; excluded from support counts
59.27
34.30
0.04
41000
281.00
9.45
N342DN A321 a3c514
plausible aircraft candidate
67.53
23.70
0.05
37000
316.80
23.71
N846SY B738 ab97ca
plausible aircraft candidate
50.36
138.30
0.03
35025
348.40
3.31
N434AN A21N a53207
plausible aircraft candidate
49.87
138.10
2.33
31000
144.40
3.21
N536JB A320 a6c781
plausible aircraft candidate
46.79
65.80
0.01
23375
324.50
8.34
N284AK B739 a2dce1
plausible aircraft candidate
45.24
3.40
0.08
33000
294.00
11.74
N380DA B738 a45b96
plausible aircraft candidate
42.70
63.50
0.00
33000
197.20
7.63
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-03-02T09:56:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
40.20629, -100.59209
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
three-object/light language present
No compact same-launch count match; retained for unresolved report features.
Motion language
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
237UAP00618 is assessed as normal-object favored because the available public evidence gives a case-specific ordinary-object candidate: strong ADS-B aircraft candidate C-FLKO B38M c01e1f at 64.8 km, azimuth 251.6 deg, elevation 9.02 deg, 8.00 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
237UAP00618
Washington Operations Center
Date: 3/2/2024 3:56:00 AM (-06 CST)
Title: EJA316 UFO-UAP ACTIVITY 03-02-2024
Latitude: 40.206292220000002 Latitude: -100.59209389999999
DESCRIPTION
PRELIM INFO FROM FAA OPS: MC COOK, NE/UFO-UAP ACTIVITY/0356C/DENVER ARTCC ADVISED NETJETS 316,
E55P, LAS - OMA, REPORTED UNIDENTIFIED AERIAL PHENOMENON WHILE E BOUND AT FL410 VCNTY MCK.
PHENOMENON WAS RAPIDLY MOVING DIM AND BRIGHT LIGHTS. MULTIPLE ACFT REPORTING SEEING SIMILAR
PHENOMENA. UAP WAS NOT OBSERVED ON ATC RADAR SYSTEMS. WOC 7-3333 MO/TJ
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: 237UAP00618
Time and observer coordinate
extracted
2024-03-02T09:56:00+00:00 at 40.20629, -100.59209
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
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/