sensors Mode-S transponder
A97CB5
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N710GT · BOEING 777-200LR · operated by TITAN AVIATION LEASING LTD - AMERICAS INC
- Hex
- A97CB5
- Octal
- 52276265
- Decimal
- 11,107,509
- Country
- US
- Tail
- N710GT
- Type
- B77L
- Flights observed
- 212
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A97CB5 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GTI354 | - | 33 | 2026-07-07 |
| GTI346 | - | 28 | 2026-06-25 |
| GTI345 | Atlas Air | 12 | 2026-06-24 |
| GTI340 | - | 11 | 2026-07-12 |
| GTI349 | - | 9 | 2026-07-13 |
| GTI353 | Atlas Air | 8 | 2026-07-04 |
| GTI3019 | - | 8 | 2026-06-27 |
| GTI7413 | - | 7 | 2026-04-29 |
| GTI3595 | - | 7 | 2026-07-10 |
| GTI348 | Atlas Air | 7 | 2026-05-02 |
| GTI3411 | Atlas Air | 7 | 2026-04-28 |
| GTI3596 | - | 6 | 2026-07-12 |
| GTI337 | Atlas Air | 5 | 2026-05-20 |
| GTI334 | Atlas Air | 5 | 2026-05-15 |
| GTI3152 | - | 5 | 2026-06-30 |
| GTI3151 | Atlas Air | 4 | 2026-06-30 |
| GTI3093 | Atlas Air | 4 | 2026-06-10 |
| GTI3090 | Atlas Air | 4 | 2026-06-09 |
| GTI3035 | - | 4 | 2026-07-09 |
| GTI3013 | Atlas Air | 4 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | GTI300 | - | Jul 13, 22:55 UTC | Jul 14, 05:15 UTC | 6h 20m |
| 2026-07-13 | GTI349 | - | Jul 13, 14:35 UTC | Jul 13, 19:55 UTC | 5h 20m |
| 2026-07-12 | GTI349 | - | Jul 12, 20:15 UTC | Jul 13, 12:30 UTC | 16h 15m |
| 2026-07-12 | GTI349 | - | Jul 12, 15:20 UTC | Jul 13, 12:30 UTC | 21h 10m |
| 2026-07-12 | GTI340 | - | Jul 12, 13:20 UTC | Jul 13, 12:30 UTC | 23h 10m |
| 2026-07-12 | GTI340 | - | Jul 12, 13:01 UTC | Jul 13, 11:15 UTC | 22h 15m |
| 2026-07-12 | GTI340 | - | Jul 12, 09:20 UTC | Jul 13, 06:40 UTC | 21h 20m |
| 2026-07-12 | GTI340 | - | Jul 12, 08:35 UTC | Jul 13, 06:40 UTC | 22h 5m |
| 2026-07-12 | GTI3596 | - | Jul 12, 00:55 UTC | Jul 12, 06:10 UTC | 5h 15m |
| 2026-07-11 | GTI3596 | - | Jul 11, 07:40 UTC | Jul 11, 22:55 UTC | 15h 15m |
| 2026-07-10 | GTI3595 | - | Jul 10, 22:00 UTC | Jul 11, 21:15 UTC | 23h 15m |
| 2026-07-09 | GTI3035 | - | Jul 9, 01:35 UTC | Jul 9, 11:05 UTC | 9h 30m |
| 2026-07-08 | GTI3035 | - | Jul 8, 22:25 UTC | Jul 8, 23:00 UTC | 35m |
| 2026-07-08 | GTI3035 | - | Jul 8, 21:00 UTC | Jul 8, 21:10 UTC | 10m |
| 2026-07-08 | GTI3035 | - | Jul 8, 17:55 UTC | Jul 8, 18:45 UTC | 50m |
| 2026-07-07 | GTI3024 | - | Jul 7, 17:45 UTC | Jul 8, 08:15 UTC | 14h 30m |
| 2026-07-07 | GTI354 | - | Jul 7, 09:40 UTC | Jul 7, 12:50 UTC | 3h 10m |
| 2026-07-07 | GTI354 | - | Jul 7, 00:15 UTC | Jul 7, 06:25 UTC | 6h 10m |
| 2026-07-06 | GTI354 | - | Jul 6, 12:45 UTC | Jul 6, 21:45 UTC | 9h 0m |
| 2026-07-04 | GTI353 | MST → MST | Jul 4, 20:10 UTC | Jul 5, 09:05 UTC | 12h 55m |
| 2026-07-03 | GTI3037 | ANC → ORD | Jul 3, 09:00 UTC | Jul 3, 14:35 UTC | 5h 35m |
| 2026-07-02 | GTI3037 | TPE → ANC | Jul 2, 22:45 UTC | Jul 3, 07:15 UTC | 8h 30m |
| 2026-07-02 | GTI3037 | - | Jul 2, 18:25 UTC | Jul 2, 19:40 UTC | 1h 15m |
| 2026-07-02 | GTI3026 | - | Jul 2, 10:45 UTC | Jul 2, 10:55 UTC | 10m |
| 2026-07-01 | GTI3026 | - | Jul 1, 19:05 UTC | Jul 2, 09:20 UTC | 14h 15m |
| 2026-06-30 | GTI3152 | - | Jun 30, 18:10 UTC | Jul 1, 03:55 UTC | 9h 45m |
| 2026-06-30 | GTI3152 | - | Jun 30, 13:00 UTC | Jun 30, 16:05 UTC | 3h 5m |
| 2026-06-30 | GTI3151 | LAX → HAN | Jun 30, 10:05 UTC | Jun 30, 10:20 UTC | 15m |
| 2026-06-29 | GTI3151 | LAX → HAN | Jun 29, 20:09 UTC | Jun 30, 09:35 UTC | 13h 25m |
| 2026-06-29 | GTI354 | - | Jun 29, 14:04 UTC | Jun 29, 17:10 UTC | 3h 5m |
| 2026-06-29 | GTI354 | - | Jun 29, 04:00 UTC | Jun 29, 08:54 UTC | 4h 55m |
| 2026-06-28 | GTI354 | - | Jun 28, 18:25 UTC | Jun 29, 01:25 UTC | 7h 0m |
| 2026-06-27 | GTI353 | MST → MST | Jun 27, 23:34 UTC | Jun 28, 11:55 UTC | 12h 20m |
| 2026-06-27 | GTI3019 | - | Jun 27, 04:15 UTC | Jun 27, 13:30 UTC | 9h 15m |
| 2026-06-26 | GTI3019 | - | Jun 26, 21:50 UTC | Jun 27, 01:44 UTC | 3h 55m |
| 2026-06-26 | GTI3081 | LAX → HAN | Jun 26, 04:14 UTC | Jun 26, 19:39 UTC | 15h 25m |
| 2026-06-25 | GTI347 | ANC → ORD | Jun 25, 23:44 UTC | Jun 26, 00:59 UTC | 1h 15m |
| 2026-06-25 | GTI347 | ANC → ORD | Jun 25, 22:04 UTC | Jun 25, 22:14 UTC | 10m |
| 2026-06-25 | GTI346 | - | Jun 25, 12:19 UTC | Jun 25, 18:15 UTC | 5h 55m |
| 2026-06-24 | GTI346 | - | Jun 24, 17:40 UTC | Jun 25, 09:45 UTC | 16h 5m |
| 2026-06-24 | GTI346 | - | Jun 24, 13:20 UTC | Jun 25, 09:45 UTC | 20h 25m |
| 2026-06-24 | GTI345 | ORD → HKG | Jun 24, 11:20 UTC | Jun 25, 09:45 UTC | 22h 25m |
| 2026-06-24 | GTI345 | ORD → HKG | Jun 24, 10:59 UTC | Jun 25, 09:14 UTC | 22h 15m |
| 2026-06-24 | GTI345 | ORD → HKG | Jun 24, 07:20 UTC | Jun 25, 03:50 UTC | 20h 30m |
| 2026-06-24 | GTI345 | ORD → HKG | Jun 24, 06:20 UTC | Jun 25, 03:50 UTC | 21h 30m |
| 2026-06-23 | GTI3596 | ANC → ORD | Jun 23, 05:39 UTC | Jun 23, 11:04 UTC | 5h 25m |
| 2026-06-22 | GTI3596 | - | Jun 22, 11:09 UTC | Jun 23, 03:39 UTC | 16h 30m |
| 2026-06-22 | GTI3595 | - | Jun 22, 05:29 UTC | Jun 23, 03:39 UTC | 22h 10m |
| 2026-06-22 | GTI3595 | - | Jun 22, 01:29 UTC | Jun 22, 21:19 UTC | 19h 50m |
| 2026-06-20 | GTI303 | - | Jun 20, 23:45 UTC | Jun 21, 02:55 UTC | 3h 10m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the N710GT page for operator, model, and routing details .