N37468 — Boeing 737-900
Landed Fort Riley (Junction City), KS
Registered since 2013 · 3 trips since November 2025 · home field Lafayette.
History
- Kansas state wildcats team charter matched a football travel window1h 39mSalt Lake City, UT → Fort Riley (Junction City), KS
- Ohio state buckeyes team charter matched a football travel window2h 48mChicago, IL → Columbus, OH
Where it goes
| Columbus, OH | 1 trip |
| Fort Riley (Junction City), KS | 1 trip |
The aircraft
Airframe
- Type
- Boeing 737-900
- Make and model on the certificate
- BOEING 737-924ER
- Category and class
- Fixed wing, multi engine · 2 × turbofan
- Serial
- 32836
- Built
- 2013
- Engines
- CFM INTL CFM56-7B27E
- Seats
- 191
- Airworthiness
- Feb 18, 2013
Identity
- Registration
- N37468
- Mode-S hex
- A445F2
- Last tracked
- Nov 23, 2025
Registration
- Registrant
- UNITED AIRLINES INC
- Address of record
- CHICAGO, IL
- FAA status
- Valid
- Certificate issued
- Feb 21, 2013
- Registration expires
- Feb 28, 2029
- Registry
- United States
FAA Registry N37468, snapshot Sep 23, 2026.
Title history
- N37468 assigned — first registration
- Registered to UNITED AIRLINES INC
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | UNITED AIRLINES INC | Chicago, IL | Open — still the registered owner of record |
Every filing
No FAA registry change, filing, or document is on file for this airframe yet.
Attribution
RegistrantUNITED AIRLINES INC · FAA record
Attribution reflects public context; registration records show registrants, not passengers.
Built from JetSweep’s retained FAA registry snapshots, sourced from FAA Registry N37468 (snapshot Sep 23, 2026). 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 →