Skip to main content
← Planes

SAM 99-0404 Flight

A US Air Force VIP transport — Special Air Mission (SAM) 99-0404, a C-37A Gulfstream V — was tracked into Fort Huachuca, AZ (the US Army Intelligence Center) on September 8-9, 2025, two days before the UVU shooting. Whistleblower reporting amplified by Candace Owens links the flight to a reported meeting of roughly 12 lieutenant colonels at Fort Huachuca on September 9. The account below is assembled from an anonymous tipster's email and from a military source named in later reporting as Mitch Snow (also referred to as "Harry Myers" in some retellings); it is presented as documented public claims, not as established fact, and no named individual has been shown to have committed any crime.

Note: the tail number is 99-0404, a US Air Force C-37A. Do not confuse it with 99-0004, the C-32A flown by Vice President JD Vance and covered on the 99-0004 Vance Flight page — the two tails differ by a single digit.

Aircraft identification

  • Tail number: 99-0404
  • Type: US Air Force C-37A Gulfstream V VIP jet
  • Base: Joint Base Andrews (Camp Springs, ADW)
  • Mission designator: SAM (Special Air Mission) — used to ferry senior executive-branch and Congressional officials
  • Reported government/VIP use: Operated by the US Air Force for government and VIP transport; aircraft of this Special Air Mission class are reported to carry senior officials, with commentary noting figures such as Defense Secretary Pete Hegseth among the kinds of officials such flights serve
  • Capacity: Approximately 12 passengers
  • Booking authority for the trip: Reported as Bradley Hansell's office
  • Reported callsigns: Investigation notes list this flight as "SAM-702 (or SAM-000 or SAM-112)" — three candidate Special Air Mission callsign readings for the same airframe. Each is tracked on its own page so the identifier is searchable: SAM702 (the primary reading), SAM-000, and SAM-112.

Flight pattern leading up to September 10

According to a tipster's email (December 10, 2025) circulated by Candace Owens:

  • September 7, 2025: Andrews → Colorado Springs.
  • September 8, 2025: Colorado Springs → Tucson, then 5 hours later Tucson → (transponder off).
  • September 9, 2025, 12:31 PM: Reappears flying Fort Huachuca → El Paso, then El Paso → Andrews. The tipster notes the aircraft is shown leaving the Fort Huachuca area around 11:43 AM on the 9th.
  • The call sign reportedly changed from RCH (Reach, the standard Air Mobility Command transport prefix) to SAM as the aircraft moved onto the Fort Huachuca leg. The same reporting ties the change to a passenger picked up in Colorado Springs — a detail investigators say they are still working to confirm.

This was reported as the only time the tipster had observed this aircraft at Fort Huachuca.

Connection to the September 9 lieutenant-colonel meeting

Candace Owens has reported that a military whistleblower (the source named in later reporting as Mitch Snow, also called "Harry Myers") walked into a high-clearance meeting at Fort Huachuca attended by approximately 12 lieutenant colonels — Pentagon-level brass — described by the source as a "final op planning session — isolated, high-clearance, no walk-ins allowed." A roughly seven-hour interrogation reportedly followed, led by a "Captain Neff," after which, the source says, military police were called and the visit logged as a possible bomb threat; Owens has stated she received an incident report indicating bomb dogs were called at 11:17 AM. The combination of the SAM-class aircraft, the call-sign change, and the meeting timing has been flagged by these commentators as warranting federal investigation.

Commentators have advanced various theories about what the flight could mean — reportedly ranging from a command-and-control role, to high-level official involvement, to cover-up elements — and have placed it within the broader scrutiny of government aviation in the investigation. In some citizen accounts the Fort Huachuca stop is further tied to a reported Las Vegas staging angle, with posters speculating that the September 9 meeting fed into an operational staging effort. These are presented as questions and reported theories about pre-event military and intelligence activity, not as established facts, and no named individual has been shown to have committed any crime.

Separately, some citizen investigators have linked Fort Huachuca — as the US Army's intelligence and signals-relay hub — to the parallel "Task Force Charlie" theory built around the N1098L Spy Plane, suggesting the base could serve as a command or relay node connecting the two aviation strands. This too is an unverified reported theory, not a documented finding.

Some online accounts have additionally claimed that Erika Kirk was seen with others at Fort Huachuca around this window. This is an unverified reported sighting circulating in OSINT commentary only — it has not been confirmed by any documented record, flight manifest, or official source, and it is included here solely as an open question for verification, not as a statement of fact.

Reported passenger and booking authority

Candace Owens has reported that Bradley Hansell — described by her as one of only four passengers on the flight that left Fort Huachuca on the morning of September 9 — was aboard. Hansell was confirmed by the Senate on July 22, 2025 as Under Secretary of Defense for Intelligence and Security, a role reporting to Defense Secretary Pete Hegseth and overseeing the Defense Intelligence apparatus. According to the investigation notes, Hansell's office booked the trip (Andrews → Colorado Springs → Tucson) before the call sign turned to SAM. A separate report cited by Owens places Hansell visiting JTF South Border leadership in Colorado Springs — the same unit the source Mitch Snow said he encountered at Fort Huachuca the next day.

These are reported attributions, not confirmed facts. The plane is reported to hold about 12 people, and investigators say they are still working to confirm who else was aboard. Nothing here establishes that Hansell, Hegseth, or any other named official committed any crime; their presence or office activity, where reported, is described as part of the open record researchers want resolved.

Other reported users of this aircraft

According to the same tipster, Pam Bondi reportedly flew on SAM 99-0404 approximately five months prior, from the Tampa area back to DC. This is presented as the tipster's observation from public tracking data, not as evidence of any wrongdoing.

The AES Tennessee flyover claim

A separate strand of reporting ties this same airframe to 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, cited under callsign SAM702) reduced altitude — flying low and slow — over the AES facility that later detonated on October 10, 2025, killing 16 workers. He ties this to the "exploding-mic" theory and a reported Department of Defense order to AES. 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.

Parallel SAM-flight routing claims

A separate strand of X/OSINT discussion — circulated in the same threads that compiled the Israel/Egyptian SU-series flights and amplified to Candace Owens — groups this airframe with other Special Air Mission callsigns (cited as SAM650 and SAM702) and points to additional routing said to "sync" with the case timeline. According to those posts, the suspicious SAM itineraries include a leg described as Wilmington → Andrews → Nashville, alongside the Colorado Springs synchronizations already covered above. These users tie the Wilmington (Delaware) end of that routing to the separate claim that an Israel/Egyptian plane landed and stayed in Delaware the night of September 10, and to the "920 King St" joint-operations allegation Owens posted. All of this is presented as unverified online claims and reported theories, not as established fact.

These routing overlaps are framed by the posters as evidence of coordination, but the same skepticism that applies to the Israel/Egyptian-plane overlaps applies here. Critics note that "overlap" claims across these threads often rely on loose same-region, plus-or-minus-several-days criteria rather than same-day, same-airport matches, and that UTC versus local-time errors have produced wrong departure timings elsewhere in the dataset. In response to the broader flight-tracking allegations, Grok has stated that public ADS-B data shows aircraft activity but no proven surveillance or assassination link, and that the official investigation centers on a lone shooter. No named individual has been shown to have committed any crime.

Open questions

  1. Who was on SAM 99-0404 between Colorado Springs and Tucson on September 8, and who were the other passengers on a 12-seat aircraft?
  2. Why did the call sign change from RCH to SAM mid-trip, and who was the passenger reportedly picked up in Colorado Springs that the source ties to the change?
  3. Who attended the Fort Huachuca meeting on September 9, and what was its purpose?
  4. Why did Bradley Hansell's office reportedly book this trip, and what was the connection to JTF South Border?
  5. Why was the transponder reportedly off between Tucson on September 8 and Fort Huachuca on September 9?
  6. Do the parallel SAM-flight claims (SAM650 / SAM702, and a reported Wilmington → Andrews → Nashville leg) hold up under same-day, same-airport scrutiny, or do they collapse like the loose-criteria Israel/Egyptian-plane overlaps?

Sources

  • Tipster email forwarded to Candace Owens (Dec 10, 2025) titled "Flights - Fort Huachuca Sept 9. 2025."
  • Candace Owens podcast and broadcast coverage of the Fort Huachuca meeting, the named source Mitch Snow, and the identification of Bradley Hansell as a reported passenger.
  • X / citizen-investigator posts amplifying the SAM702 / 99-0404 thread.
  • Public ADS-B and flight-tracking logs for tail 99-0404.

Laws (Charlie Kirk)

  • The passenger manifest of SAM 99-0404 into Fort Huachuca and the attendee roster of the September 9 lieutenant-colonel meeting and why the call sign changed from RCH to SAM mid-trip are things that the Charlie Kirk Investigation Laws may result in powerful truths coming out that aren't out yet.

Citizen Investigator Claims on X

(Aircraft OSINT and attributed claims — not findings that any pilot, passenger, or official ordered or carried out the assassination.)

  • Pre-event SAM / VIP traffic to Fort Huachuca (incl. SAM-702 / 99-0404 cluster) is central to Candace Owens / Mitch Snow meeting claims and Brian Harpole’s defamation response — competing Dallas-receipts vs open morning-window notes.
  • Distinguish VIP tails carefully: 99-0404 pre-event vs 99-0004 AF2 casket flight — conflation is a frequent X error.
  • This page’s focus (SAM 99-0404 Flight) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.

Track This Aircraft

Research this 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.

Note: 99-0404 is a military registration, and military/government tails often do not resolve cleanly on civil trackers — records may be sparse, delayed, or absent, especially around the reported transponder-off leg. If the registration lookup returns nothing, search the SAM callsign forms (SAM702 / SAM-000 / SAM-112) or the aircraft's ICAO hex on ADS-B Exchange instead.

Aircraft ID: USAF C-37A (Gulfstream V) Special Air Mission jet · tail 99-0404 · ICAO hex AE04F9 · operated by the 89th Airlift Wing, Joint Base Andrews. Military flights are frequently limited or absent on FlightRadar24, so the ADS-B Exchange hex link above is usually the most reliable. SAM aircraft also broadcast under rotating callsigns (this airframe appears as SAM-702 / SAM-000 / SAM-112), so search the hex, not a callsign.