PUBLIC RELEASE SOURCE REVIEW ยท INDEPENDENT ANALYTIC CASE FILE
CASE FILE 10 / 237UAP00363
237UAP00363
Radar/correlation-focused public UAP report; score 76
IDENTIFIED NORMAL OBJECT
Report No.
UAP-OM-10-237UAP00363
Disposition
IDENTIFIED NORMAL OBJECT
Primary Case
237UAP00363
Generated
2026-05-20 18:32 UTC
Report Time
2024-03-16T01:57:00+00:00
Observer
30.59800, -99.81750
Source Case IDs
237UAP00363
Abstract
This case file assesses whether the public UAP report can be reconciled with a specific launch object. The principal candidate is STARLINK-G6-44 STACK, propagated to azimuth 163.53 degrees, elevation 25.01 degrees, and range 626.0 km at the report minute. The result is evaluated against the report's narrative language and assigned a identified confidence label.
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
237UAP00363 is assessed as an identified normal-object case. It was matched against a specific launch-object propagation. The best object is STARLINK-G6-44 STACK at azimuth 163.53 degrees, elevation 25.01 degrees, and range 626.0 km at the report minute. This is a strong argument for a normal aerospace object over an exotic hypothesis.
1.1 Key Findings
Source score 76 based on: radar/primary-return language, multiple aircraft/facility witnesses, NORAD/AMOC/EADS/CONR check, UAP/UFO language.
Report time used: 2024-03-16T01:57:00+00:00.
External object layer used: launch-object.
Disposition standard: IDENTIFIED 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: specific propagated launch object above horizon.
Remaining hard features: multiple witnesses/facilities.
Best object: STARLINK-G6-44 STACK at az 163.53 deg / el 25.01 deg / range 626.0 km.
No explicit Starlink/balloon wording was found in the source excerpt used for ranking.
1.2 Bottom Line
IDENTIFIED NORMAL OBJECT: A specific object is above the horizon at the report minute and the visual description independently matches a launch-object profile. Residual uncertainty is mainly sensor/witness perspective, not gross spacetime mismatch.
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.
OMIC reports, multiple aircraft in the vicinity of JCT VOR reported an unidentified aerial phenomenon believed to be some type of rocket. The device passed from below to above and then appeared to break up into pieces and/or disappear. The device was very bright and had smoke. Report was at 36,000 feet and device was moving west to east. The UAP was not observed on ATC facility radar system. NORAD notified. ZHU will file MOR and attach FALCON replay.
Report time used
2024-03-16T01:57:00+00:00
Observer coordinate used
30.59800, -99.81750
Observer source basis
aviation_fix:vicinity of JCT VOR (public text extract 237UAP00363)
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 https://celestrak.org/NORAD/elements/supplemental/sup-gp.php?FILE=starlink-g6-44&FORMAT=tle. The analytic mode for this case is CelesTrak supplemental TLE launch-object propagation.
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.
STARLINK-G6-44 STACK was above the horizon at the report minute: az 163.53 deg, elevation 25.01 deg, range 626.0 km.
Five minutes before the report it was low in the northwest: az 295.69 deg, elevation 1.68 deg.
Five minutes after the report it was below the southeast horizon: az 134.27 deg, elevation -5.49 deg.
The CelesTrak TLE epoch is close to the event window; this is much stronger than matching against mature Starlink constellation clutter.
5.6 Space-Track SATCAT Enrichment
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
2
SATCAT rows matched
0
Top owners
no matched SATCAT rows
Object types
no matched SATCAT rows
5.7 Space-Track Metadata for Top Propagated Objects
NORAD
Object Name
Type
Owner
Launch Date
Decay Date
No Space-Track SATCAT rows matched the top propagated objects for this case.
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-03-16, then filter +/-60 min and 250 nmi around 30.5980,-99.8175.
NASA POWER/Horizons/DONKI: batch context for 237UAP00363 at 2024-03-16T01:57: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.
KSOA 160155Z AUTO 03012KT 10SM 13/10 A3011 RMK AO2
KBBD
79.90
2024-03-16T01:55:00+00:00
10.00
OVC01600, M, M, M
30.00 / 13.00
KBBD 160155Z AUTO 03013KT 10SM OVC016 14/11 A3006 RMK AO2
5.16 NOAA IGRA Radiosonde Wind Profile
No nearby IGRA sounding was parsed within the +/-1 day window. 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
USM00072261
DEL RIO/INT.; TX.
172.50
no sounding
n/a
n/a
n/a
n/a at n/a 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.
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-16T01:57:00+00:00
Directly used in propagation; this is a hard filter, not descriptive context.
Location constraint
30.59800, -99.81750
Directly used as observer point for azimuth/elevation/range computation.
Count / pattern
multiple-object/light language present
Launch-object stack/single pair tested; report count language is secondary to rocket-like plume/stack geometry.
Motion language
moving, break up, disappear
Motion is tested through time-series samples around the report minute.
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
identified
237UAP00363 is assessed as an identified normal-object case. It was matched against a specific launch-object propagation. The best object is STARLINK-G6-44 STACK at azimuth 163.53 degrees, elevation 25.01 degrees, and range 626.0 km at the report minute. This is a strong argument for a normal aerospace object over an exotic hypothesis.
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.
Appendix A. Public Report Text Extracts
237UAP00363
SKYWATCH INCIDENT REPORT
PRIMARY CODE: UNIDENTIFIED AERIAL PHENOMENON
Date: 01:57 03/16/2024 Paged: YES
Status: Closed
POD: DEN
Reporting Facility: ZHU
REMARKS
OMIC reports, multiple aircraft in the vicinity of JCT VOR reported an unidentified aerial phenomenon believed to be some type
of rocket. The device passed from below to above and then appeared to break up into pieces and/or disappear. The device was
very bright and had smoke. Report was at 36,000 feet and device was moving west to east. The UAP was not observed on ATC
facility radar system. NORAD notified. ZHU will file MOR and attach FALCON replay.
SKYWATCH INCIDENT REPORT | DATE: 2024-03-16T01:57 | 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.
{
"mission": "Starlink Group 6-44",
"report_time_utc": "2024-03-16T01:57:00+00:00",
"source_excerpt": "OMIC reports, multiple aircraft in the vicinity of JCT VOR reported an unidentified aerial phenomenon believed to be some type of rocket. The device passed from below to above and then appeared to break up into pieces and/or disappear. The device was very bright and had smoke. Report was at 36,000 feet and device was moving west to east. The UAP was not observed on ATC facility radar system. NORAD notified. ZHU will file MOR and attach FALCON replay.",
"celestrak_url": "https://celestrak.org/NORAD/elements/supplemental/sup-gp.php?FILE=starlink-g6-44&FORMAT=tle",
"observer": {
"lat": 30.597999572753906,
"lon": -99.81749725341797,
"source": "aviation_fix:vicinity of JCT VOR (public text extract 237UAP00363)"
},
"case_id": "237UAP00363",
"interpretation": [
"STARLINK-G6-44 STACK was above the horizon at the report minute: az 163.53 deg, elevation 25.01 deg, range 626.0 km.",
"Five minutes before the report it was low in the northwest: az 295.69 deg, elevation 1.68 deg.",
"Five minutes after the report it was below the southeast horizon: az 134.27 deg, elevation -5.49 deg.",
"The CelesTrak TLE epoch is close to the event window; this is much stronger than matching against mature Starlink constellation clutter."
],
"best_object": {
"name": "STARLINK-G6-44 STACK",
"event_sample": {
"altitude_km": 284.9,
"azimuth_deg": 163.53,
"elevation_deg": 25.01,
"offset_seconds": 0,
"range_km": 626.0,
"subpoint_lat": 25.8877,
"subpoint_lon": -98.2819,
"time_utc": "2024-03-16T01:57:00+00:00"
},
"line1": "1 72000C 24049A 24076.06006134 .00026048 00000+0 65436-4 0 07",
"line2": "2 72000 42.9983 316.4223 0006365 224.4313 154.2116 15.94604985 18",
"samples": [
{
"altitude_km": 285.1,
"azimuth_deg": 301.26,
"elevation_deg": -12.97,
"offset_seconds": -600,
"range_km": 3860.4,
"subpoint_lat": 42.2777,
"subpoint_lon": -140.3919,
"time_utc": "2024-03-16T01:47:00+00:00"
},
{
"altitude_km": 284.7,
"azimuth_deg": 295.69,
"elevation_deg": 1.68,
"offset_seconds": -300,
"range_km": 1774.6,
"subpoint_lat": 36.1707,
"subpoint_lon": -117.067,
"time_utc": "2024-03-16T01:52:00+00:00"
},
{
"altitude_km": 284.9,
"azimuth_deg": 163.53,
"elevation_deg": 25.01,
"offset_seconds": 0,
"range_km": 626.0,
"subpoint_lat": 25.8877,
"subpoint_lon": -98.2819,
"time_utc": "2024-03-16T01:57:00+00:00"
},
{
"altitude_km": 285.5,
"azimuth_deg": 134.27,
"elevation_deg": -5.49,
"offset_seconds": 300,
"range_km": 2634.3,
"subpoint_lat": 13.3005,
"subpoint_lon": -82.9924,
"time_utc": "2024-03-16T02:02:00+00:00"
},
{
"altitude_km": 286.2,
"azimuth_deg": 130.98,
"elevation_deg": -17.87,
"offset_seconds": 600,
"range_km": 4697.8,
"subpoint_lat": -0.2613,
"subpoint_lon": -69.3879,
"time_utc": "2024-03-16T02:07:00+00:00"
}
]
}
}
Appendix C. Source Exhaustion Checklist
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: 237UAP00363
Time and observer coordinate
extracted
2024-03-16T01:57:00+00:00 at 30.59800, -99.81750
Orbital object propagation
screened
Starlink
Space-Track SATCAT metadata
screened
2 NORAD IDs checked; 0 matched in local SATCAT subset
Launch-object/SupGP layer
screened
Starlink Group 6-44
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
Aircraft/ADS-B layer
not exhausted
ADSB.lol historical release pattern is recorded separately; actual aircraft exhaustion requires targeted trace extraction
NOAA GOES imagery layer
not exhausted
Cloud/lightning imagery layer for the report hour
NOAA GOES ABI/GLM manifest
screened
Public S3 object listing for the report hour
NOAA/NEXRAD weather radar layer
not exhausted
Weather radar only; not ATC/primary radar
NOAA IGRA radiosonde layer
screened
Balloon drift plausibility layer
ASOS/METAR surface weather
screened
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
identified normal object
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
