Not currently tracked · last seen 6h ago
- Flights observed
- 625 showing last 50
- Avg flight time
- 1h 2m
- Typical route
- ORD → CHA
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | ORD → CHA | Jul 14, 01:13 UTC | Jul 14, 02:17 UTC | 1h 4m |
| 2026-07-14 | ORD → CHA | Jul 14, 01:10 UTC | Jul 14, 02:20 UTC | 1h 10m |
| 2026-07-13 | - | Jul 13, 23:20 UTC | Jul 13, 23:55 UTC | 35m |
| 2026-07-13 | MSN → ORD | Jul 13, 23:23 UTC | Jul 13, 23:46 UTC | 23m |
| 2026-07-13 | - | Jul 13, 22:15 UTC | Jul 13, 22:40 UTC | 25m |
| 2026-07-13 | ORD → MSN | Jul 13, 22:14 UTC | Jul 13, 22:50 UTC | 36m |
| 2026-07-13 | - | Jul 13, 20:05 UTC | Jul 13, 20:40 UTC | 35m |
| 2026-07-13 | PIA → ORD | Jul 13, 19:51 UTC | Jul 13, 20:27 UTC | 36m |
| 2026-07-13 | - | Jul 13, 18:10 UTC | Jul 13, 18:35 UTC | 25m |
| 2026-07-13 | - | Jul 13, 14:35 UTC | Jul 13, 15:45 UTC | 1h 10m |
| 2026-07-13 | - | Jul 13, 12:05 UTC | Jul 13, 13:10 UTC | 1h 5m |
| 2026-07-12 | - | Jul 12, 21:45 UTC | Jul 12, 23:15 UTC | 1h 30m |
| 2026-07-12 | - | Jul 12, 19:25 UTC | Jul 12, 20:50 UTC | 1h 25m |
| 2026-07-12 | ORD → AVP | Jul 12, 19:26 UTC | Jul 12, 20:50 UTC | 1h 24m |
| 2026-07-12 | - | Jul 12, 14:40 UTC | Jul 12, 16:01 UTC | 1h 20m |
| 2026-07-12 | - | Jul 12, 12:30 UTC | Jul 12, 13:30 UTC | 1h 0m |
| 2026-07-12 | DAY → ORD | Jul 12, 09:50 UTC | Jul 12, 10:45 UTC | 55m |
| 2026-07-11 | - | Jul 11, 23:15 UTC | Jul 11, 23:55 UTC | 40m |
| 2026-07-11 | ORD → DAY | Jul 11, 23:24 UTC | Jul 11, 23:55 UTC | 31m |
| 2026-07-11 | - | Jul 11, 20:20 UTC | Jul 11, 21:25 UTC | 1h 5m |
| 2026-07-11 | - | Jul 11, 17:55 UTC | Jul 11, 19:05 UTC | 1h 10m |
| 2026-07-11 | - | Jul 11, 13:55 UTC | Jul 11, 15:40 UTC | 1h 45m |
| 2026-07-09 | - | Jul 9, 23:55 UTC | Jul 10, 01:25 UTC | 1h 30m |
| 2026-07-09 | - | Jul 9, 20:35 UTC | Jul 9, 22:00 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 18:30 UTC | Jul 9, 19:35 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 15:15 UTC | Jul 9, 16:50 UTC | 1h 35m |
| 2026-07-09 | - | Jul 9, 13:00 UTC | Jul 9, 14:25 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 10:35 UTC | Jul 9, 11:10 UTC | 35m |
| 2026-07-09 | GRR → ORD | Jul 9, 10:17 UTC | Jul 9, 10:58 UTC | 41m |
| 2026-07-08 | ORD → GRR | Jul 8, 22:55 UTC | Jul 8, 23:25 UTC | 30m |
| 2026-07-08 | - | Jul 8, 20:25 UTC | Jul 8, 21:10 UTC | 45m |
| 2026-07-08 | CVG → ORD | Jul 8, 20:27 UTC | Jul 8, 20:55 UTC | 28m |
| 2026-07-08 | - | Jul 8, 18:15 UTC | Jul 8, 19:05 UTC | 50m |
| 2026-07-08 | - | Jul 8, 15:25 UTC | Jul 8, 17:00 UTC | 1h 35m |
| 2026-07-08 | - | Jul 8, 12:50 UTC | Jul 8, 14:25 UTC | 1h 35m |
| 2026-07-07 | - | Jul 7, 23:50 UTC | Jul 8, 01:15 UTC | 1h 25m |
| 2026-07-07 | FSD → ORD | Jul 7, 23:46 UTC | Jul 8, 00:41 UTC | 55m |
| 2026-07-07 | - | Jul 7, 21:40 UTC | Jul 7, 22:45 UTC | 1h 5m |
| 2026-07-07 | - | Jul 7, 20:05 UTC | Jul 7, 20:15 UTC | 10m |
| 2026-07-07 | - | Jul 7, 18:50 UTC | Jul 7, 20:15 UTC | 1h 25m |
| 2026-07-07 | SCE → ORD | Jul 7, 18:35 UTC | Jul 7, 19:46 UTC | 1h 11m |
| 2026-07-07 | - | Jul 7, 16:05 UTC | Jul 7, 17:10 UTC | 1h 5m |
| 2026-07-07 | ORD → SCE | Jul 7, 15:58 UTC | Jul 7, 17:19 UTC | 1h 21m |
| 2026-07-07 | - | Jul 7, 13:25 UTC | Jul 7, 14:30 UTC | 1h 5m |
| 2026-07-07 | SGF → ORD | Jul 7, 13:09 UTC | Jul 7, 14:23 UTC | 1h 14m |
| 2026-07-07 | - | Jul 7, 02:45 UTC | Jul 7, 03:40 UTC | 55m |
| 2026-07-06 | ABE → ORD | Jul 6, 22:00 UTC | Jul 6, 23:50 UTC | 1h 50m |
| 2026-07-06 | - | Jul 6, 19:45 UTC | Jul 6, 20:00 UTC | 15m |
| 2026-07-06 | ORD → ABE | Jul 6, 19:54 UTC | Jul 6, 21:06 UTC | 1h 12m |
| 2026-07-06 | - | Jul 6, 17:00 UTC | Jul 6, 18:40 UTC | 1h 40m |
Specifications
| Registration | N516GJ |
| Operator | GOJET AIRLINES LLC |
| Mode-S code | A67858 · 51474130 (octal) |
Looking for transponder-level data? View the Mode-S A67858 page for country allocation, callsign history, and ADS-B signal details.
N516GJ frequently asked
Who operates N516GJ?
N516GJ is operated by GOJET AIRLINES LLC.
What is the Mode-S transponder code for N516GJ?
N516GJ broadcasts on Mode-S (ICAO 24-bit) address A67858 (octal 51474130). View the transponder page.
What route does N516GJ typically fly?
N516GJ most frequently flies between ORD and CHA based on observed flights.
Where is N516GJ right now?
N516GJ is not currently being tracked; last seen 6h ago.