Skip to main content
← Table drill-downs

The rows where Erika Kirk's presence is actually established

Where this came from. On the Following overview, the table that splits the overlap register by who the row claims was being followed carries a cell reading "Overlaps where Erika Kirk's presence is established". This page is that cell. The count in it is 0. Every other cell in that table drills down into a list of rows; this one drills down into an empty list, and the empty list is the point.

What this slice is

A row qualifies for this list only if some source independently places Erika Kirk herself at the claimed city on the claimed date — a published itinerary, a dated photograph, a venue record, a manifest, a named appearance. Being written in the "Erika location" cell of the compiler's spreadsheet does not qualify: that cell is the claim, not evidence for the claim. An aircraft being at the airport does not qualify either, because a trace locates an airframe and never a passenger. Filter overlaps.csv for rows carrying independent, dated, sourced confirmation of Erika Kirk's own physical presence and the filter returns nothing. That is how this page ends up with zero rows.

At a glance

MeasureValue
Rows in this slice0
Distinct dates0
Aircraft namednone
Airportsnone
Statesnone
ADS-B verdicts representednone
Ground-position confirmations0
Rows landing on 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

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

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

What the specifics show

There are no specifics, and that is the finding. The three tables above are the real generated output for this slice — they carry their headers and not a single data row, because the join that produced every other cuts page returned an empty set here.

This matters because of where the register's weight sits. In the same index of slices, the Erika-side lists are the large ones: the register counts 70 rows that involve Erika Kirk at all and 61 that rest on her alone, against 18 that involve Charlie Kirk in any way. So the majority of the "following" claim is carried by a person whose presence is confirmed on zero of its rows. The supporting material for those 70 rows is a location cell on a circulated spreadsheet — sometimes a state, sometimes two states, sometimes hedged — and no dated itinerary behind it.

The nearest thing the register has to a sourced Erika appearance is not in this register at all. On the refuted-Erika slice, the row for 18 June 2025 records that the only well-dated joint Charlie-and- Erika appearance in the whole pre-September-10 window is Grapevine, Texas, 13–15 June 2025 — and no aircraft in this investigation was in Texas for it. That is the strongest available Erika datum, and it points away from the claim rather than toward it.

What this list cannot tell you

  • A trace proves an aircraft was there. It never proves who was aboard. Every corroborated row elsewhere in this register corroborates a tail number and a position, nothing more. No ADS-B record in existence can put a named passenger in a cabin.
  • Erika Kirk's presence is not established on any row. Her flight logs are reported erased and no dated itinerary was ever published. Every claim about where she was on these dates is attributed to the compiler's spreadsheet.
  • Zero here is not proof she was elsewhere. An empty list means nobody has produced sourced evidence of her presence to this register. It does not establish absence, and it is not an accusation against anyone. It is a statement about the state of the sourcing.
  • This page contains no archive verdicts, so no archive gap is being read as anything. Where NOT_HEARD and NO_ARCHIVE_COVERAGE appear on sibling pages they are limits of what volunteer ADS-B archives hold — never deletions, never suppression.
  • Where the overview and this register disagree, both figures get printed. The tracking-site audit worked from 78 rows; this register holds 85. Counts sourced from the audit and counts sourced from the register will not match, and neither is being quietly preferred.

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: