Skip to main content
← Planes

SAM-112 Flight

SAM-112 is one of the Special Air Mission (SAM) callsigns reported in the investigation notes for the US government VIP flight tied to tail number 99-0404 — the aircraft associated with Defense Secretary Pete Hegseth around the September 8–9, 2025 Fort Huachuca window. The source lists this flight as "SAM-702 (or SAM-000 or SAM-112)", so SAM-112 is a reported-but-uncertain callsign reading for the same airframe covered on the SAM 99-0404 Flight page. This page tracks the SAM-112 callsign thread on its own so the identifier is searchable and its open questions are recorded. Nothing here alleges wrongdoing by any person.

Why this callsign is interesting​

The investigation could only narrow this government VIP flight to one of three possible SAM callsigns — SAM-702, SAM-000, or SAM-112 — all over tail 99-0404. SAM-112 matters because callsign uncertainty on a Special Air Mission flight is unusual: SAM flights are deliberately logged so executive-branch movements can be tracked. A flight that surfaces under multiple candidate callsigns is precisely the record researchers want a formal disclosure process to resolve into a single confirmed identifier, route, and passenger manifest.

Aircraft identification​

  • Callsign (as reported): SAM-112 — one 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)
  • Associated official: Reported as Defense Secretary Pete Hegseth's flight
  • Window: Around September 8–9, 2025 (the Fort Huachuca timeframe)

Note: tail 99-0404 also appears under the primary callsign SAM702 on the SAM 99-0404 Flight page. SAM-112 and SAM-000 are the two alternate callsigns reported for the same flight. They are documented separately here at the request of the investigation, but readers should treat all three as candidate identifiers for one government VIP aircraft until the official record resolves which is correct.

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, Defense Secretary Hegseth's plane (tail 99-0404, which he cites under callsign SAM702) flew over the AES facility that later detonated (Building 602, reportedly ~24,000 lbs of explosives) on October 10, 2025 — a claim he ties to the "exploding-mic" theory and a reported ~$440k Department of Defense order to AES. These are presented as reported allegations for verification, not established facts. See Stew Peters Broke the AES / Mic Connection for the fuller account.

Parallel SAM-flight threads​

In parallel with the 99-0404 discussion, X/OSINT researchers compiling Israel/Egyptian-plane spreadsheets also flagged other Special Air Mission callsigns — notably SAM650 and SAM702 — as part of the same Fort Huachuca / Colorado Springs timeline. According to those posts, the SAM flights showed an alleged itinerary running Wilmington → Andrews → Nashville, with what researchers describe as "Colorado Springs syncs" lining up against the September 8–9, 2025 window. These are unverified online claims drawn from public ADS-B screenshots, not established findings, and they do not name SAM-112 specifically; they are noted here only because they concern the same SAM-flight thread that produced the candidate callsigns for tail 99-0404. Grok responses to similar posts note that public ADS-B data shows aircraft activity but no proven surveillance or assassination link, and the official investigation continues to focus on a lone shooter.

Open questions​

  1. Was the flight's actual callsign SAM-702, SAM-000, or SAM-112?
  2. Who was aboard tail 99-0404 during the September 8–9 window?
  3. Did the aircraft in fact reduce altitude over the AES Tennessee plant, and if so, why?
  4. What was the flight's full route and purpose?
  5. Are the SAM650 / SAM702 callsigns researchers cite (alleged Wilmington → Andrews → Nashville routing) the same airframe as 99-0404, or separate Special Air Mission flights?

Sources​

  • Charlie Kirk investigation notes listing the flight as "SAM-702 (or SAM-000 or SAM-112), 99-0404, possibly USAF C-37A."
  • Stew Peters' public claim tying tail 99-0404 to the AES plant flyover (presented as his allegation).
  • X/OSINT compilation posts citing parallel SAM callsigns (SAM650, SAM702) with an alleged Wilmington → Andrews → Nashville routing and "Colorado Springs syncs" — unverified screenshot claims.
  • 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 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​

This callsign is reported over tail 99-0404. Research that aircraft's flight history yourself on both major flight-tracking sites. They differ in one important way:

  • FlightRadar24 — 99-0404 — large commercial tracker that honors the FAA's LADD block list, so flights an owner or the government has asked to hide can be missing.
  • ADS-B Exchange — 99-0404 — volunteer-fed, unfiltered tracker that does not honor LADD, so it often shows blocked aircraft and tracks the filtered sites leave out.

Track This Aircraft​

SAM-112 is one reported 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: Resolve the three candidate callsigns (SAM-702 / SAM-000 / SAM-112) by searching the hex AE04F9 rather than any one callsign. See also SAM 99-0404 Flight and SAM702 Flight.