FILE DEPT

Field Report Archive

Private Skeptical Evidence Corpus

Case Files Map Source Manifest

← Back to Case Files

UFO/UAP
Single-Record File

FAA Report 237UAP00374: TCAS Alerts Near Fort Riley

Single-Record File: Only one inspectable record is attached. It documents a source or allegation but cannot independently corroborate the broader claim.
OverviewEvidenceTimelineAnalysisSources
2024-07-05
North of Topeka and vicinity of Fort Riley, Kansas, USA
7/10
6/10
Multiple aircraft received collision-avoidance alerts for traffic that was not shown on FAA or military radar.
Strong that the FAA recorded the operational report. Limited for identification and physical interpretation because the form contains no complete sensor package or final investigation.

Investigative Assessments

"The reported claim remains worth testing against the record: Multiple aircraft received collision-avoidance alerts for traffic that was not shown on FAA or military radar. The strongest documented reasons to keep the file open are: FAA Skywatch Incident Report 237UAP00374: The form records a visual report of three slow-moving light-gray objects, TCAS resolution advisories to two named flights, and five additional aircraft reporting nearby TCAS traffic.. Key unresolved lead: What caused TCAS alerts for at least seven aircraft without corresponding ATC radar traffic?"
"Evidentiary limitations: Strong that the FAA recorded the operational report. Limited for identification and physical interpretation because the form contains no complete sensor package or final investigation. Note that: FAA Skywatch Incident Report 237UAP00374 fails to support: It does not establish that every alert had one cause, identify the objects, or demonstrate anomalous technology.."

Case Summary

The form records a visual report of three slow-moving light-gray objects, TCAS resolution advisories to two named flights, and five additional aircraft reporting nearby TCAS traffic. The one-page FAA record preserves the report but does not establish the object’s identity or an extraordinary origin. This pilot synopsis is an intake summary requiring source-by-source verification.

Evidence Locker

1 inspectable evidence item. Claims and source findings are kept separate.

Official FAA incident report Local copy hash-verified

FAA Skywatch Incident Report 237UAP00374

Analyst rating: Primary operational record with the limitations stated on the form

“PIC reports receiving a TCAS RA and saw a flight of 2 followed by a single aircraft, all slow moving, opposite direction at FL 300, light grey in color.”
Record locationPDF page 1
Evidence classFAA operational incident record
Relationship to claimDirectly records the observation and the operational checks described by FAA.
Authenticity assessmentHigh for document authenticity as an official FAA Skywatch form preserved by NARA.
What this supportsThe form records a visual report of three slow-moving light-gray objects, TCAS resolution advisories to two named flights, and five additional aircraft reporting nearby TCAS traffic.
What it does not supportIt does not establish that every alert had one cause, identify the objects, or demonstrate anomalous technology.
ProvenanceOfficial FAA record transferred to NARA Record Group 615 and preserved in the NARA UAP bulk collection.
Chain of custodyFlight or controller report -> FAA Skywatch incident record -> NARA bulk archive -> hash-verified Casebook copy.
Open Document (Local PDF Document) Download Copy Canonical Agency Record

Documented Timeline

Not documented: No source-verified chronology has been assembled.

Named Participants and Roles

Not documented: Named participants and roles have not been source-verified.

Contradictions and Record Conflicts

Not documented: Record conflicts have not been analyzed.

Conventional Explanations

Not documented: Conventional explanations have not been evaluated against evidence.

Missing Evidence

Not documented: The evidence gap itself has not yet been fully inventory.

What Remains Unresolved

Not documented: No source-level unresolved findings have been established.

Investigative Hypotheses

  • Uncoordinated conventional aircraft or transponder-bearing targets produced TCAS alerts without expected radar correlation.
  • GPS or avionics interference produced false or displaced traffic alerts.
  • A physical object or objects remained unidentified because the available systems disagreed.

Open Questions

  • What caused TCAS alerts for at least seven aircraft without corresponding ATC radar traffic?
  • Were onboard TCAS logs or FALCON radar replays preserved?

Archival Landing Pages and Evidence Corpus

NARA Record Group 615, FAA UAP Records

Official Bulk Archive

External URL: https://catalog.archives.gov/id/493468575