Skip to main content
← Table drill-downs

The five rows logged as “SU-BTT or SU-BND”

Where this came from. On the Following overview, the table that splits the register by which aircraft was named carries a line reading “SU-BTT or SU-BND” — the source could not tell which. That cell is the count 5. These are those five rows.

What this slice is

A row lands here when the register records the aircraft as one of the two Egyptian-registered jets without saying which. Both tails are carried on the row and both ICAO hex codes are stored — 0101D3 for SU-BTT and 01003E for SU-BND — because the source distinguished neither. To reproduce the list from overlaps.csv, take every row whose following-tail field names both tails as alternatives rather than as a pair observed together. That last distinction matters: three other rows in the register name both tails because both aircraft were logged on the same day at the same field, and those three are a different slice entirely. The five rows here name both because the compiler could not narrow it to one.

At a glance

MeasureValue
Rows in this slice5
Distinct dates0 — no row carries a date
Date rangenone — no date was ever published for any of these rows
By yearno date: 5
Aircraft named"SU-BTT or SU-BND": 5 — both tails carried, neither confirmed
Airportsnone named on any row
Statesnone named on any row
Who is claimedErika Kirk alone: 5
ADS-B verdictNo date named: 5
Audit verdictNever published: 5
Ground-position confirmations0
Rows with a same-day sourced Kirk or TPUSA appearance0

TABLE A — the following aircraft

RowDate claimedAirportCity / StateFollowing aircraftTypeICAO hexArrived fromDeparted toGround stay logged, arrivedDepartedDaysTransponder / ground flagADS-B verdictClosest approach
UNPUB-001no date was ever publishednone namednone namedSU-BTT, SU-BNDsource could not tell whichnot stated0101D3; 01003Enot recordednot recordedno logged stay covers this dateNo date named
UNPUB-002no date was ever publishednone namednone namedSU-BTT, SU-BNDsource could not tell whichnot stated0101D3; 01003Enot recordednot recordedno logged stay covers this dateNo date named
UNPUB-003no date was ever publishednone namednone namedSU-BTT, SU-BNDsource could not tell whichnot stated0101D3; 01003Enot recordednot recordedno logged stay covers this dateNo date named
UNPUB-004no date was ever publishednone namednone namedSU-BTT, SU-BNDsource could not tell whichnot stated0101D3; 01003Enot recordednot recordedno logged stay covers this dateNo date named
UNPUB-005no date was ever publishednone namednone namedSU-BTT, SU-BNDsource could not tell whichnot stated0101D3; 01003Enot recordednot recordedno logged stay covers this dateNo date named

TABLE B — who they are claimed to have been following

RowDate claimedWho the sheet claims was presentErika location as the sheet gives itSourced Kirk / TPUSA appearance same dayVenueLocal timeNearest airport to that venueKirk-side aircraft on record
UNPUB-001no date was ever publishedCharlie: not claimed · Erika: claimednever statedNone same-day. Neither this register's own nearest-event column nor a date join against the sourced speaking-events catalog finds a Kirk or TPUSA appearance within three days.none recorded
UNPUB-002no date was ever publishedCharlie: not claimed · Erika: claimednever statedNone same-day. Neither this register's own nearest-event column nor a date join against the sourced speaking-events catalog finds a Kirk or TPUSA appearance within three days.none recorded
UNPUB-003no date was ever publishedCharlie: not claimed · Erika: claimednever statedNone same-day. Neither this register's own nearest-event column nor a date join against the sourced speaking-events catalog finds a Kirk or TPUSA appearance within three days.none recorded
UNPUB-004no date was ever publishedCharlie: not claimed · Erika: claimednever statedNone same-day. Neither this register's own nearest-event column nor a date join against the sourced speaking-events catalog finds a Kirk or TPUSA appearance within three days.none recorded
UNPUB-005no date was ever publishedCharlie: not claimed · Erika: claimednever statedNone same-day. Neither this register's own nearest-event column nor a date join against the sourced speaking-events catalog finds a Kirk or TPUSA appearance within three days.none recorded

TABLE C — sourcing and both verdicts

RowSheet indexAudit verdict (tracking-site pass)ADS-B verdict (position data)What the position data saysSource of the claimSource postFull row page
UNPUB-001Never publishedNo date namedThe claim carries no date, so no archive can be asked about it. Untestable as published.Candace Owens, Operation Mocking-Plane, 17 Nov 2025: '68 overlaps. I have since been able to add now 73 times that this overlapped.'postopen
UNPUB-002Never publishedNo date namedThe claim carries no date, so no archive can be asked about it. Untestable as published.Candace Owens, Operation Mocking-Plane, 17 Nov 2025: '68 overlaps. I have since been able to add now 73 times that this overlapped.'postopen
UNPUB-003Never publishedNo date namedThe claim carries no date, so no archive can be asked about it. Untestable as published.Candace Owens, Operation Mocking-Plane, 17 Nov 2025: '68 overlaps. I have since been able to add now 73 times that this overlapped.'postopen
UNPUB-004Never publishedNo date namedThe claim carries no date, so no archive can be asked about it. Untestable as published.Candace Owens, Operation Mocking-Plane, 17 Nov 2025: '68 overlaps. I have since been able to add now 73 times that this overlapped.'postopen
UNPUB-005Never publishedNo date namedThe claim carries no date, so no archive can be asked about it. Untestable as published.Candace Owens, Operation Mocking-Plane, 17 Nov 2025: '68 overlaps. I have since been able to add now 73 times that this overlapped.'postopen

What the specifics show

These five rows are identical to one another in every column. All five — UNPUB-001 through UNPUB-005 — carry the same single source: Candace Owens, in the broadcast the register cites as Operation Mocking-Plane of 17 November 2025, saying "68 overlaps. I have since been able to add now 73 times that this overlapped." The register holds these five as placeholders for the difference between the two figures she gave. Nothing beyond the count was ever itemised, which is why every one of them has an empty date column, an empty airport column, an empty state column, and an aircraft entry naming both jets because the source distinguished neither.

That makes this slice a statement about the sourcing rather than about any aircraft movement. All five are attributed to Erika Kirk alone and none to Charlie Kirk; none has a sourced Turning Point or Kirk appearance within three days, which is automatic, because with no date there is nothing to compare an appearance against. The tracking-site audit records all five as Never published, and the position-data pass records all five as No date named — the only two verdicts either pass can return on a row with no date. They are counted in the register's 85 because the source asserted them; they contribute nothing testable to it.

What this list cannot tell you

  • These five rows are untestable as published. With no date and no airport, no archive can be queried at all — this is not an archive gap and not a removal, it is a claim that was never itemised in the first place.
  • Nothing here shows that either aircraft moved, or that either was anywhere in particular. The rows record an aggregate assertion, not an observation.
  • A trace proves an aircraft was at a place on a date. It never proves who was aboard. On these five rows there is no trace and no date, so there is nothing to place anyone against.
  • Erika Kirk's presence is established on zero rows of the register, and all five rows in this slice are logged as Erika Kirk alone. Her flight logs are reported erased and no itinerary was ever published, so the Erika column here records what the compiler asserted and nothing that has been shown.
  • The aircraft columns must not be read as evidence about either airframe. Both tails and both hex codes appear on every row precisely because the source could not say which, so nothing here can be added to the case for or against SU-BTT or SU-BND individually.
  • Nothing here establishes that any person committed any offence. The claim is attributed above to the broadcast that made it.
  • Counts on this page come from the 85-row register. The tracking-site audit worked from 78 rows and never covered these five, which is exactly what its Never published verdict records; a figure printed on the overview page from the audit side will therefore not include them.

Flight-record pages for what is on this page

This investigation keeps one page per airport and one page per recorded ground contact, built directly from the recovered ADS-B traces. These are the ones this page touches.

Aircraft named on this page:

  • SU-BND — full recovered movement record, every airport and every leg
  • SU-BTT — full recovered movement record, every airport and every leg

The two indexes: