Seminole Boosters

Aviation Activity Intelligence

Event intelligence — aircraft activity around a single event

← All FSU events

FSU at Pitt

Event start: 7:00 PM EST · Away Game

Pittsburgh, Pennsylvania

Monitoring window
−1d / +1d
Nov 12 – Nov 14

Game-day aviation intelligence

Fly-in / fly-out
0
0 pre-event start candidates
Repeat aircraft
0
Matched fly-in / fly-out at more than one event
Watchlisted aircraft
0
Watchlist aircraft seen in the pre-event window
Unique aircraft
0
Monitoring window

Fly-In / Fly-Out aircraft

Aircraft that landed at KTLH shortly before the event start, remained on the ground through the event, and departed KTLH shortly after the recorded event end. Timing only — it does not indicate who was onboard or why the aircraft travelled.

Windows: arrival ≤ 4h before event start · departure ≤ 4h after event end
Fly-in / fly-out analysis will finalize after the actual game end time is recorded.

Pre-game arrival candidates

Aircraft that landed inside the pre-event start window and are not yet classified against the recorded event end.

Tail numberAircraftRegistered ownerOriginArrivalBefore event startDepartureDestinationAfter event endOn groundRepeat gamesStatus
No aircraft landed at KTLH inside the pre-event arrival window.

Upcoming Arrivals

Flight schedules are not yet available for this event.

Live arrival monitoring begins approximately 48 hours before the applicable flight times. Coverage expands automatically at each scheduled sync. All times Eastern.

Focus:

Event flight map

No flights match the current window and filters.
Arrival into KTLHDeparture from KTLHUpcoming / en routeFly-in / fly-out legApproximate route — origin/destination onlyActual Flight Track

Top origins (into KTLH)

  • No activity in this window.

Top destinations (out of KTLH)

  • No activity in this window.

Event Staff Notes

Internal staff context — not verified aviation data
  • No staff notes recorded.

Flight times, airports, and registration data come from the connected feed. Position-level tracks are not supplied yet, so routes are drawn as approximate lines. Flights are associated with this event solely because their date falls inside the monitoring window above — that association describes aircraft movement, not the purpose of a trip or who was onboard.