N351GC — University of South Carolina's Beechcraft King Air 350
Landed Columbia, SC
51 trips since July 2024 · home field Columbia.
History
- South Carolina-owned history — Charleston, SC → home26m
- South Carolina-owned history — → Charleston, SC4h 25m
- South Carolina's king air made a Tupelo turn before the ole miss game3h 36mTupelo and back
That's the last 7 days. The full record — 51 trips, every registry change — is a Jump Seat · $15/month.
Where it goes
| Columbia, SC — home field | 8 trips |
| Charleston, SC | 6 trips |
| Moncks Corner, SC | 4 trips |
| Florence, SC | 3 trips |
| Orlando, FL | 3 trips |
| Richmond, VA | 3 trips |
The aircraft
Airframe
- Type
- Beechcraft King Air 350
- Serial
- FL-56
Identity
- Registration
- N351GC
- Mode-S hex
- A3E91D
- Last tracked
- Nov 20, 2025
Registration
- Registrant
- University of South Carolina
- Registry
- United States
Title history
- Registered to University of South Carolina
- Registered to Yellowstone Leasing
Owner history
No registered-owner era is recorded for this airframe.
Every filing
No FAA registry change, filing, or document is on file for this airframe yet.
Full ownership file and every filing.
Jump Seat · $15/monthAttribution
RegistrantUniversity of South Carolina · FAA record
Attribution reflects public context; registration records show registrants, not passengers.
Who’s behind it
Airframe identityBeech B300 serial FL-56 · FAA Registry N375BC
FAA sale recordUniversity of South Carolina -> Yellowstone Leasing LLC · FAA CARES registration-history packet N375BC / FL-56
Pattern breakKCUB-heavy before, KAND/KMQY-heavy after
Built from JetSweep’s retained FAA registry snapshots. Dates shown are FAA recording and snapshot dates — the day a filing was indexed or a difference was first observed, not necessarily the day the underlying transaction happened. Part 135 rows come from dated workbook retrievals and bound a listing, never date it. We track the aircraft, not who is aboard.
Registration records show registrants, not beneficial owners; FAA recording dates lag transactions. How we source this →
