Pilatus PC-12 (Unconfirmed)
A Pilatus PC-12 — a single-engine turboprop widely used for utility, charter, and some surveillance roles — appears in scattered online commentary as an aircraft reportedly seen "circling" near the Utah Valley University area around September 10, 2025. Unlike every other aircraft catalogued in this section, this report comes with no confirmed tail number and no confirmed ADS-B flight track. It is recorded here only so the claim is logged and clearly caveated — not because it has been substantiated.
This is the weakest-sourced aircraft entry on the site. Treat everything below as an unverified report, not as evidence.
Why this entry exists
The site catalogs every aircraft that researchers have raised in connection with the case, including the ones that do not hold up, so readers can see the full picture and weigh the credibility of each. The Pilatus PC-12 belongs in the "raised but unconfirmed" tier. Logging it — with an explicit note that it is unconfirmed — is more useful than silently omitting it, because it lets readers know the claim was considered and why it carries little weight.
What is claimed
- A Pilatus PC-12 was reportedly observed circling in the general Orem / Provo / UVU area on or around September 10, 2025.
- The claim is vague and second-hand. It appears only as occasional references inside compilation posts — not as a standalone, sourced sighting with attribution.
- In those discussions the PC-12 is grouped into the "local planes contracted to do back-and-forth passes" category — the same bucket that holds ISR / survey types such as N1098L and the MARC survey plane N59906. Unlike those two, the PC-12 has nothing concrete attached to it.
What is missing
The report fails the basic identification tests that the better-documented aircraft on this site pass:
- No tail number. Every confirmable aircraft in this section is tied to a registration (for example N1098L, SU-BTT, N59906). This one has none.
- No flight track. There is no cited FlightRadar24 or ADS-B Exchange track placing a specific PC-12 over or near UVU at a specific time.
- No timestamps or altitude data. The "circling" description is not backed by logged times, headings, or altitudes.
- No operator or owner. Without a tail number, there is no way to identify who operated the aircraft.
How to weigh it
A Pilatus PC-12 is an extremely common type — thousands are in service across charter, medevac, cargo, and private operators — so even a confirmed sighting near a regional airport like Provo would not by itself be unusual. Some PC-12 variants are configured for surveillance work, which is presumably why the type drew comment, but no such configuration has been linked to the specific aircraft alleged here. Until a tail number and a flight track surface, this report should be treated as a rumor pending a concrete flight track — unconfirmed and low priority relative to the documented aircraft in this section.
It is logged at this low tier only so the mention is not lost. If a tail number or a tracked flight ever surfaces, this entry should be promoted to a full, sourced aircraft page. Until then, nothing here should be read as evidence.
Open questions
- Is there any photograph, video, or eyewitness account that pins a specific PC-12 to a time and place near UVU on September 10, 2025?
- Does any public ADS-B history show a PC-12 circling the Orem area in the relevant window, and if so, what is its tail number?
- If a tail number surfaces, who operates the aircraft, and is it a surveillance-configured variant or a routine charter/utility airframe?
The standard this page is applying, stated once for the whole section
This page exists because a tail or type entered the discussion without evidence behind it. That is worth turning into an explicit test, because the same problem recurs across this section and the section is only as credible as its weakest entry.
A flight claim is usable when it carries at least one of these:
- A hex code. The ICAO 24-bit Mode S address —
A7C14D,0101D3,AC3C75. This is the only identifier that survives retyping, and it is what a raw ADS-B archive indexes on. A claim with a hex code can be checked by anyone in minutes. - A serial number (MSN). Ties the claim to a physical airframe independent of what registration it wears.
- A dated tracker capture with the data panel legible — registration, type, altitude, groundspeed, squawk, and a timestamp with its time zone shown.
- A named, primary document — an FAA registry entry, an FBO record, an operator statement, a trade press release.
A flight claim is not usable when it consists of:
- A tail number with no track behind it.
- An aircraft type with no tail number ("a Pilatus PC-12 was seen").
- A cropped screenshot where the aircraft-identification panel is cut off.
- A "same plane" assertion pointing back to an earlier post that is not shown.
- A converted time with no time zone stated. In this case that failure alone has generated multiple false claims — Utah was UTC−6 on September 10, 2025, and Arizona is UTC−7 year-round.
By that test, this page's subject fails at the first hurdle: there is no tail number, so there is nothing to check. A PC-12 is one of the most widely operated single-engine turboprops in North America, flown by air ambulances, freight operators, government agencies, charter companies and private owners in the thousands. Without a registration, "a PC-12 was in the area" is not a claim about an aircraft — it is a claim about a category.
Why unsourced entries cost more than they add
The temptation with a thin claim is to leave it in place on the reasoning that it might firm up later. In an investigation being read by hostile reviewers, that calculation runs the wrong way.
The overlap-sheet audit is the clearest illustration available. That sheet's genuine findings — SU-BTT at Provo from 4 to 10 September, SU-BND parked from May to September, the 10 September departure — survived a hostile line-by-line audit intact. But they were published inside a list where two-thirds of the rows were wrong and several were duplicated, and the result is that the whole document is now cited as discredited. The good rows are paying for the bad ones.
The same dynamic applies to this section. Every unsourced tail number sitting next to N59906's hex code, squawk, serial number and timestamped capture makes the N59906 record easier to dismiss, not the unsourced tail easier to believe.
So thin claims are kept here, labelled as thin, rather than either deleted or mixed in with the documented ones. That is the point of this page and of the equivalent entries elsewhere in the section — not to suppress a lead, but to keep it from contaminating the leads that can actually be defended.
What would move this specific entry
- A registration. Any N-number for a PC-12 alleged to have been in the Utah Valley on or around 10 September 2025.
- A raw archive query. ADS-B Exchange retains historical tracks; a search of the Provo/Orem area for type
PC12on that date either returns aircraft or does not. That single query would resolve this page permanently, in either direction, and nobody has published it. - An origin for the claim. Where and when it was first posted, and by whom. Right now the assertion circulates without a traceable first appearance — which is itself a reason for caution, because a claim with no origin cannot be corrected at its source.
A candidate identification: N315NG
The PC-12 report on this page has always lacked a tail number, which is why it is the weakest-sourced aircraft entry on the site. There is, however, an obvious candidate that has not been checked against it.
A search of the FAA Civil Aviation Registry for PC-12s based in Utah returns N315NG — a Pilatus PC-12/47E, built 2011, serial 1315, registered to Intermountain Medical Transport LLC of Salt Lake City. It is an air ambulance.
That is worth stating plainly because of what it would mean. A medical-transport PC-12 orbiting or transiting near Utah Valley University on 10 September 2025 is not an anomaly requiring explanation — it is the single most ordinary aircraft that could possibly be over the scene of a mass-casualty event in Utah County. An air ambulance is what you would expect to see, and its presence would be evidence of a functioning emergency response rather than of surveillance.
This is offered as a hypothesis, not an identification. No source has tied N315NG to the sighting, no ADS-B track has been produced for either the sighting or this aircraft on that date, and the original report may refer to a different airframe entirely or to no real aircraft at all. It is recorded here because the responsible way to handle an untailed sighting is to name the mundane candidates before entertaining exotic ones.
What would settle it: FlightRadar24 or ADS-B Exchange playback for N315NG on 2025-09-10, and Intermountain's own dispatch record for that afternoon.
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Pilatus PC-12/47E, built 2011, serial 1315
- Registered owner: INTERMOUNTAIN MEDICAL TRANSPORT LLC (Salt Lake City UT)
- Still built today? No — 47E succeeded by PC-12 NGX / PC-12 PRO
- Priced against: Pilatus PC-12 PRO
- Cost to buy new today: ~$6.8 million
PC-12 PRO is the current production model at ~$6.8M typically equipped.
List price is for a green airframe — interior completion, avionics options and any mission equipment are extra, and fleet buyers do not pay list. The full table for all 33 priced airframes in this investigation, with the method behind each figure, is on Aircraft Costs.
Interesting In This Area
- No tail number and no ADS-B track exist, unlike every other entry.
- N59906 is the aircraft actually documented over campus that morning.
- Catalogued and caveated beats deleted, which is why thin tails stay listed.
- Compare it against a well-sourced entry such as SU-BTT.
Interesting In Other Areas
- The drones section handles most low-altitude sighting claims.
- Eyewitness phone video is what most sighting claims actually rest on.
- Theories is the hub that grades claims rather than repeating them.
- More theories collects the ones that never reached evidence.
Other Pages In This Section
The working memo for the aircraft angle — ISR passes, the Egyptian fleet, shadowing counts, SAM movements and transponder gaps, each with the record that would settle it. Start here if you want the questions rather than the tails.
Read thisThe fifth tail in the armada researchers count through Provo, and the one with the least written about it. Its weight comes entirely from the fleet pattern, not from any single documented event.
Read thisTwo more foreign tails flagged when the Egypt story grew from two jets to five. Route detail is thin; they appear in the source notes grouped simply as more planes for disclosure.
Read this
Air Force Two carried the casket from Salt Lake City to Phoenix on September 11, with the Vice President aboard. It is the one flight in this section that nobody disputes.
Read thisElsewhere In The Investigation
The hub for airspace as evidence: an Army ISR jet over campus, a media drone TPUSA later acknowledged, and counter-drone testing at Provo the same week. Documented flights first, theories last.
Read this
Dozens of phones were recording. Their combined coverage is more complete than the institutional cameras that were never released, which is why the crowd's footage keeps mattering.
Read this
TPUSA internal conflict, a foreign state other than Israel, a multi-actor coordination, and the staged-event claim — each set out with the little evidence it actually rests on. Several experienced investigators land here rather than on any single-actor account.
Read thisSources
- Uncorroborated online commentary describing a Pilatus PC-12 "circling" near UVU around September 10, 2025. No primary source, tail number, or flight track has been identified.
Laws (Charlie Kirk)
- A complete, subpoenaed record of every aircraft operating near UVU on September 10, 2025 — including any PC-12 — is exactly the kind of disclosure the proposed Charlie Kirk Investigation Laws are designed to force into the open, which would either confirm or finally retire reports like this one.
Citizen Investigator Claims on X
(Aircraft OSINT and attributed claims — not findings that any pilot, passenger, or official ordered or carried out the assassination.)
- Citizen OSINT tracks N-numbers near TPUSA events, Provo FBO activity, and foreign VIP tails; flight logs ≠ intent.
- Competing tallies exist for “shadowing” Charlie vs Erika; debunk and counter-debunk cycles continue on X.
- This page’s focus (Pilatus PC-12 (Unconfirmed)) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.
This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.
Interesting
- The low-flying surveillance aircraft launched from an Army airfield at Fort Bliss.
- A 1994 Air Force paper describes pulsed energy weapons in this DEW history.
- U.S. intelligence funded remote viewing for 23 years under Stargate and its predecessors.