← Planes That Followed Them

Table drill-downs — every number, opened up

The Following overview is a page of counts. *85. 61. 25. 37. "At the claimed airport." "No archive coverage." An investigator reading it wants to click the number and see the rows — which aircraft, which airport, what date it landed and what date it left, who it is claimed to have been following, and what every verdict on that row actually was. Each page below is one of those cells, opened.

• Every claimed overlap, all 85 rows — 85 rows
• The nine rows claiming Charlie Kirk without Erika — 9 rows
• Every row that involves Erika Kirk at all — 70 rows
• Every row naming SU-BTT, the yellow plane — 57 rows
• The nine rows that cannot name the aircraft — 9 rows
• The rows where Erika Kirk's presence is actually established — empty by construction
• The three rows refuted by recovered position data — 3 rows
• The ten rows no free archive reaches — 10 rows
• The ten ground-position confirmations — 10 rows
• The Charlie/TPUSA rows position data refutes — there are none — empty by construction
• The 12 Erika rows position data corroborates — 12 rows
• Rows the tracking-site audit called accurate — 21 rows
• Rows the audit could not assess — 2 rows
• Rows within three days of a sourced Kirk or TPUSA appearance in the same state — 17 rows
• Kansas — every overlap, every landing, every event — 18 rows

• The 80 rows that carry a date — 80 rows
• The nine rows claiming both Kirks together — 9 rows
• The 61 rows resting on Erika Kirk alone — 61 rows
• Every row naming SU-BND, the blue plane — 16 rows
• The five rows logged as “SU-BTT or SU-BND” — 5 rows
• The 61 rows where no Kirk can be placed at all — 61 rows
• The one row that is right area, wrong field — 1 row
• The four rows that name no aircraft — 4 rows
• The Charlie Kirk and TPUSA ledger — all 24 rows — 24 rows
• The Charlie/TPUSA rows the archives cannot decide — 11 rows
• The three Erika rows position data refutes — 3 rows
• Rows the tracking-site audit called inaccurate — 44 rows
• Rows the audit never reached — 5 rows
• Utah — every overlap, every landing, every event — 15 rows
• Delaware — every overlap, every landing, every event — 11 rows

• The five rows that were never published — 5 rows
• Every row that involves Charlie Kirk at all — 18 rows
• The six rows matched to a Turning Point event with neither Kirk — 6 rows
• The three rows naming both tails at once — 3 rows
• The four rows with no tail number at all — 4 rows
• The 25 rows corroborated by recovered position data — 25 rows
• The 37 rows the archives cover but do not hear — 37 rows
• The five rows that name no date — 5 rows
• The 13 Charlie/TPUSA rows position data corroborates — 13 rows
• The Erika Kirk ledger — all 56 dated rows — 56 rows
• The Erika rows the archives cannot decide — 41 rows
• Rows the tracking-site audit called partially accurate — 8 rows
• Rows that land on a day this site independently sources a Kirk or TPUSA appearance — 10 rows
• Nebraska — every overlap, every landing, every event — 19 rows
• Missouri — every overlap, every landing, every event — 9 rows

What is on every one of these pages

Each drill-down carries the same three tables, generated straight out of this directory's register rather than retyped, so a page cannot drift from the data behind it.

Table A — the following aircraft. The row ID, the claimed date, the airport with its code and full name, the city and state, the tail number linked to that aircraft's own page, the airframe type, the ICAO hex the ADS-B network actually broadcasts, where the leg arrived from and departed to, the arrival and departure dates of any logged ground stay covering that date, how many days it sat, the transponder or on-ground flag, the ADS-B verdict, and the measured closest approach in kilometres.

Table B — who they are claimed to have been following. Whether Charlie Kirk and Erika Kirk are each claimed present, the Erika-location cell exactly as the source sheet gives it, the sourced Turning Point or Kirk appearance on that same day where one exists, that event's venue and local start time, the nearest airport to the venue with its distance in miles, and any Kirk-side aircraft on record. Where there is no same-day appearance the table names the nearest sourced one and how many days off it is, rather than leaving the cell blank.

Table C — sourcing and both verdicts. The index the row carries on the original sheet, the tracking-site audit verdict, the ADS-B position verdict, what the position data actually says, who published the claim, a link to the source post, and a link to that row's own full page.

The five state pages carry two more: Table D, every logged ground presence by every following aircraft at that state's fields with arrival and departure dates, and Table E, every sourced Kirk or TPUSA appearance in that state with venue, time and nearest airport.

Three things every one of these pages says, because they are true of all of them

A trace locates an aircraft. It never places a person aboard. A verdict of at the claimed airport confirms the aircraft half of a pairing and nothing else. It does not put Charlie Kirk or Erika Kirk anywhere.

Erika Kirk's presence is established on none of the 85 rows. Her flight logs are reported as erased and no dated itinerary has ever been published by anyone. What the source sheet has instead is a column that usually names a whole state, sometimes two states at once, and sometimes nothing.

An empty archive is not a deletion. Not heard means a volunteer network holds no trace for that airframe on that date. Parked with the transponder off, outside receiver coverage, and a wrong claimed date all look identical from the outside. Before any absence here was written down, unrelated control aircraft with no connection to this case were queried on the same dates and the same endpoints.

Related

• Planes That Followed Them — the overview these pages open up
• The overlap index — one page per claimed overlap
• The 73 overlaps — the reconstructed source list
• Speaking events — the Kirk and TPUSA side of every pairing
• What "overlap" meant — the window definition
• Flight Data Recovery — the archives the position data came from
• Erika's erased flight logs — why her side cannot be checked

---

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:

• Every airport in this investigation — 290 fields, each with its complete recovered ground-visit and flight-leg record
• Every interesting date, all aircraft — 147 ground contacts near a sourced event, across 110 pages
• Investigating Deleted Flights — how the data was recovered, how much of it we hold, and where it is still missing