Skip to main content
← Planes

SAM702 Flight

SAM702 is the primary Special Air Mission (SAM) callsign reported in the investigation notes for the US government VIP flight tied to tail number 99-0404 — the aircraft associated with the September 8-9, 2025 Fort Huachuca, Arizona window two days before the UVU shooting. The source material lists this flight as "SAM-702 (or SAM-000 or SAM-112)", so SAM702 is the leading callsign reading for the same airframe covered on the SAM 99-0404 Flight page, with SAM-000 and SAM-112 as the two alternate readings. SAM702 is the callsign most heavily discussed in Candace Owens' podcast coverage of the case. Nothing here alleges wrongdoing by any person.

Why this callsign is the focal point​

Of the three candidate callsigns for tail 99-0404, SAM702 is the one that recurs most often in citizen-investigator discussion and in Candace Owens' broadcasts. The interest is twofold: the Special Air Mission designation means it was a senior-official transport, and its position at Fort Huachuca — a US Army intelligence base — one day before the assassination places a high-level government flight at a sensitive node in the timeline. Until the official flight log is produced, SAM702 remains an open identifier that researchers want matched to a confirmed route, callsign, and passenger manifest.

Aircraft identification​

  • Callsign (as reported): SAM702 — the primary of three callsigns (SAM-702 / SAM-000 / SAM-112) listed in the source for this flight
  • Tail number: 99-0404
  • Type: Possibly a US Air Force C-37A (the Gulfstream V VIP transport used for Special Air Mission flights)
  • Window: Around September 8-9, 2025 (the Fort Huachuca timeframe)
  • Reported associated official: Discussed in commentary alongside senior defense officials; see the SAM 99-0404 page for the Hegseth-linked framing

Note: tail 99-0404 (this flight) is a distinct aircraft from tail 99-0004, the C-32A covered on the 99-0004 Vance Flight page. The two tail numbers differ by a single digit and are easy to confuse.

The reported Fort Huachuca meeting​

According to coverage circulated by Candace Owens, a high-level meeting took place at Fort Huachuca on or around September 9, 2025 — the day before Charlie Kirk's assassination. The full account of the reported 12-lieutenant-colonel session, the whistleblower material, and the call-sign change is on the SAM 99-0404 page. Some citizen-investigator posts have additionally speculated about who else may have been connected to a Fort Huachuca meeting in that window — names raised in discussion include figures such as Charlie Kirk's wife Erika Kirk and his security chief Brian Harpole. These are reported as unverified online speculation, not established fact; no record has placed any named living person at such a meeting, and nothing here alleges any wrongdoing by them.

The Las Vegas staging theory​

A separate strand of online discussion ties SAM702 — or the broader cluster of government VIP flights around this window — to Las Vegas flights and possible "staging" the day before a meeting. This overlaps with the separately documented Las Vegas VIP-flight question on the 99-0004 Vance Flight page. The Las Vegas angle is presented here as a reported theory raised in citizen tracking, not as a verified connection.

Companion SAM flights and the reported itinerary​

A set of X/OSINT threads discusses SAM702 alongside a companion Special Air Mission callsign, SAM650, treating the two as part of the same cluster of government VIP movements in the days around the assassination. According to these posts, the SAM flights showed "suspicious itineraries" — one route described as Wilmington (Delaware) → Joint Base Andrews → Nashville — and what users called timeline "syncs" with Colorado Springs, Colorado, a military and intelligence hub. Posters tie that Colorado Springs activity back to the alleged Fort Huachuca, Arizona meeting window of September 8-9, 2025.

These are unverified citizen-tracking claims circulated on X, not confirmed flight records, and no manifest, route, or meeting has been independently verified. The Wilmington → Andrews → Nashville reading appears in the same threads that critics say rely on loose overlap criteria. As Liz Wheeler argued of the broader plane-overlap analysis, narrowing the parameters to same-day, same-location matches collapses most of the claimed overlaps, and reviewers have flagged UTC-versus-local time errors and misattributed locations in the underlying spreadsheets. Public ADS-B data, per Grok responses cited in the threads, shows aircraft activity but no proven surveillance or assassination link; the official finding remains a lone shooter.

The AES Tennessee flyover claim​

The same notes report that this flight reduced altitude — flying low and slow — over the Accurate Energetic Systems (AES) plant in Tennessee. According to Stew Peters, who presents this as his own allegation, the Defense Secretary's plane (tail 99-0404, which he cites under callsign SAM702) flew over the AES facility that later detonated on October 10, 2025. These are presented as reported allegations for verification, not established facts. See AES Factory Explosion and Stew Peters Broke the AES / Mic Connection for the fuller account.

Command-and-control coordination theory​

Beyond the route-overlap discussion, a strand of the X OSINT / SAM-flight threads frames SAM702 — bundled with SAM650 and SAM 99-0404 — as evidence of an alleged command-and-control / high-level coordination posture in the days around the assassination. Per these theories, clusters of Special Air Mission (government VIP) movements syncing with Colorado Springs and the alleged Fort Huachuca meetings would, if confirmed, indicate senior officials gathering and coordinating in the September 8-9, 2025 window, one day before the September 10 shooting.

This is user theory only. There is no official link connecting SAM702 to any meeting, coordination effort, or the assassination — no flight log, manifest, route, or attendee roster has been produced or independently verified, and nothing here asserts wrongdoing by any person or agency. The "command-and-control" reading is the interpretation offered in citizen-tracking posts, not a finding of any investigation.

Relevant dates​

  • Reported tracking window: around September 8-11, 2025 — covering both the pre-event activity (the alleged Fort Huachuca window of September 8-9) and the event/aftermath days surrounding the September 10 shooting.
  • All dates are per X OSINT / SAM-flight threads and remain unverified against official ADS-B or flight-log records.

Open questions​

  1. Was the flight's actual callsign SAM702, SAM-000, or SAM-112?
  2. Who was aboard tail 99-0404 during the September 8-9 window?
  3. Did any high-level meeting occur at Fort Huachuca on September 9, and who attended?
  4. Is there any substance to the Las Vegas staging theory, or is it coincidental?
  5. Do the reported SAM650 companion flight and the Wilmington → Andrews → Nashville itinerary hold up against actual ADS-B records, or are they artifacts of loose overlap criteria?

Sources​

  • Charlie Kirk investigation notes listing the flight as "SAM-702 (or SAM-000 or SAM-112), 99-0404, possibly USAF C-37A."
  • Candace Owens podcast and broadcast coverage of the Fort Huachuca timeline.
  • Stew Peters' public claim tying tail 99-0404 to the AES plant flyover (presented as his allegation).
  • Public ADS-B tracking for tail 99-0404.

Laws (Charlie Kirk)​

  • The confirmed callsign, manifest, and route of the 99-0404 Special Air Mission flight and the attendee roster of any September 9 Fort Huachuca meeting are the kind of records that the Charlie Kirk Investigation Laws may result in powerful truths coming out that aren't out yet.

Track This Aircraft​

SAM702 is a callsign for tail 99-0404 (USAF C-37A). Research the airframe on both major flight-tracking sites — they differ in one important way, and for a military jet the unfiltered site and the ICAO hex matter most:

Tip: SAM flights broadcast under rotating callsigns (this airframe appears as SAM-702 / SAM-000 / SAM-112), so search by the hex AE04F9, not the callsign. See also SAM 99-0404 Flight.