sensors Mode-S transponder
ABCF7F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N860GT · BOEING 747-8 · operated by WILMINGTON TRUST CO TRUSTEE
- Hex
- ABCF7F
- Octal
- 52747577
- Decimal
- 11,259,775
- Country
- US
- Tail
- N860GT
- Type
- B748
- Flights observed
- 54
- Distinct callsigns
- 18
- Country
- US
- Last broadcast
- 36m ago
Current position
Country allocation
The ICAO 24-bit address ABCF7F 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GTI8228 | Atlas Air | 8 | 2026-05-09 |
| GTI8030 | Atlas Air | 8 | 2026-04-30 |
| GTI8052 | Atlas Air | 7 | 2026-04-26 |
| GTI8975 | Atlas Air | 4 | 2026-05-13 |
| GTI8755 | Atlas Air | 3 | 2026-05-07 |
| GTI8691 | Atlas Air | 3 | 2026-04-29 |
| GTI8209 | Atlas Air | 3 | 2026-05-02 |
| GTI5561 | Atlas Air | 3 | 2026-05-07 |
| GTI8971 | Atlas Air | 2 | 2026-05-13 |
| GTI8208 | Atlas Air | 2 | 2026-04-30 |
| GTI8028 | Atlas Air | 2 | 2026-05-05 |
| GTI734 | Atlas Air | 2 | 2026-05-11 |
| GTI733 | Atlas Air | 2 | 2026-05-11 |
| GTI9567 | Atlas Air | 1 | 2026-05-11 |
| GTI8991 | Atlas Air | 1 | 2026-05-14 |
| GTI8049 | Atlas Air | 1 | 2026-05-09 |
| GTI6570 | Atlas Air | 1 | 2026-04-27 |
| GTI5560 | Atlas Air | 1 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-14 | GTI8991 | ORD → ANC | May 14, 19:05 UTC | May 14, 23:45 UTC | 4h 40m |
| 2026-05-13 | GTI8971 | TPE → ANC | May 13, 23:35 UTC | May 14, 05:05 UTC | 5h 30m |
| 2026-05-13 | GTI8971 | TPE → ANC | May 13, 12:50 UTC | May 13, 21:10 UTC | 8h 20m |
| 2026-05-13 | GTI8975 | MIA → MAD | May 13, 07:40 UTC | May 13, 08:30 UTC | 50m |
| 2026-05-12 | GTI8975 | MIA → MAD | May 12, 23:20 UTC | May 12, 23:30 UTC | 10m |
| 2026-05-12 | GTI8975 | MIA → MAD | May 12, 18:15 UTC | May 12, 20:55 UTC | 2h 40m |
| 2026-05-12 | GTI8975 | MIA → MAD | May 12, 02:45 UTC | May 12, 15:15 UTC | 12h 30m |
| 2026-05-11 | GTI9567 | MIA → DFW | May 11, 20:10 UTC | May 11, 22:35 UTC | 2h 24m |
| 2026-05-11 | GTI734 | SCL → MIA | May 11, 11:25 UTC | May 11, 16:10 UTC | 4h 45m |
| 2026-05-11 | GTI734 | SCL → MIA | May 11, 08:25 UTC | May 11, 08:35 UTC | 10m |
| 2026-05-11 | GTI733 | MIA → BOG | May 11, 04:25 UTC | May 11, 04:45 UTC | 20m |
| 2026-05-10 | GTI733 | MIA → BOG | May 10, 15:55 UTC | May 11, 00:19 UTC | 8h 25m |
| 2026-05-09 | GTI8049 | LAX → ICN | May 9, 17:49 UTC | May 9, 22:34 UTC | 4h 45m |
| 2026-05-09 | GTI8228 | ANC → MIA | May 9, 07:45 UTC | May 9, 09:10 UTC | 1h 25m |
| 2026-05-08 | GTI8228 | ANC → MIA | May 8, 21:25 UTC | May 9, 04:30 UTC | 7h 5m |
| 2026-05-08 | GTI8228 | ANC → MIA | May 8, 11:19 UTC | May 8, 18:20 UTC | 7h 0m |
| 2026-05-07 | GTI8228 | ANC → MIA | May 7, 21:35 UTC | May 8, 06:54 UTC | 9h 20m |
| 2026-05-07 | GTI8755 | LAX → ICN | May 7, 17:15 UTC | May 7, 17:30 UTC | 15m |
| 2026-05-07 | GTI8755 | LAX → ICN | May 7, 14:25 UTC | May 7, 14:55 UTC | 30m |
| 2026-05-07 | GTI5561 | MIA → AMS | May 7, 05:20 UTC | May 7, 05:30 UTC | 10m |
| 2026-05-06 | GTI5561 | MIA → AMS | May 6, 15:30 UTC | May 7, 04:25 UTC | 12h 54m |
| 2026-05-06 | GTI5561 | MIA → AMS | May 6, 02:45 UTC | May 6, 10:50 UTC | 8h 5m |
| 2026-05-05 | GTI5560 | SDF → MSP | May 5, 10:55 UTC | May 5, 23:15 UTC | 12h 20m |
| 2026-05-05 | GTI8028 | LAX → ICN | May 5, 02:50 UTC | May 5, 07:40 UTC | 4h 50m |
| 2026-05-04 | GTI8028 | LAX → ICN | May 4, 23:45 UTC | May 4, 23:55 UTC | 10m |
| 2026-05-04 | GTI8228 | ANC → MIA | May 4, 17:35 UTC | May 4, 17:55 UTC | 20m |
| 2026-05-04 | GTI8228 | ANC → MIA | May 4, 07:05 UTC | May 4, 14:45 UTC | 7h 40m |
| 2026-05-03 | GTI8228 | ANC → MIA | May 3, 19:45 UTC | May 4, 02:15 UTC | 6h 30m |
| 2026-05-03 | GTI8228 | ANC → MIA | May 3, 08:05 UTC | May 3, 17:29 UTC | 9h 25m |
| 2026-05-02 | GTI8755 | LAX → ICN | May 2, 22:50 UTC | May 2, 23:15 UTC | 25m |
| 2026-05-02 | GTI8209 | MIA → AMS | May 2, 19:50 UTC | May 2, 20:05 UTC | 15m |
| 2026-05-02 | GTI8209 | MIA → AMS | May 2, 08:30 UTC | May 2, 18:55 UTC | 10h 25m |
| 2026-05-01 | GTI8209 | MIA → AMS | May 1, 09:30 UTC | May 1, 18:05 UTC | 8h 35m |
| 2026-04-30 | GTI8208 | UIO → MIA | Apr 30, 22:50 UTC | May 1, 06:35 UTC | 7h 45m |
| 2026-04-30 | GTI8208 | UIO → MIA | Apr 30, 19:35 UTC | Apr 30, 19:45 UTC | 10m |
| 2026-04-30 | GTI8030 | LAX → GRU | Apr 30, 13:55 UTC | Apr 30, 14:30 UTC | 35m |
| 2026-04-30 | GTI8030 | LAX → GRU | Apr 30, 04:10 UTC | Apr 30, 10:35 UTC | 6h 25m |
| 2026-04-30 | GTI8030 | LAX → GRU | Apr 30, 03:05 UTC | Apr 30, 03:20 UTC | 15m |
| 2026-04-29 | GTI8030 | LAX → GRU | Apr 29, 16:35 UTC | Apr 29, 23:40 UTC | 7h 4m |
| 2026-04-29 | GTI8030 | LAX → GRU | Apr 29, 06:25 UTC | Apr 29, 14:40 UTC | 8h 16m |
| 2026-04-29 | GTI8030 | LAX → GRU | Apr 29, 05:35 UTC | Apr 29, 05:50 UTC | 15m |
| 2026-04-29 | GTI8691 | ORD → ICN | Apr 29, 00:20 UTC | Apr 29, 00:40 UTC | 20m |
| 2026-04-28 | GTI8691 | ORD → ICN | Apr 28, 09:35 UTC | Apr 28, 23:45 UTC | 14h 10m |
| 2026-04-28 | GTI8691 | ORD → ICN | Apr 28, 01:20 UTC | Apr 28, 06:50 UTC | 5h 30m |
| 2026-04-27 | GTI6570 | UIO → MIA | Apr 27, 12:50 UTC | Apr 27, 22:00 UTC | 9h 10m |
| 2026-04-27 | GTI8030 | LAX → GRU | Apr 27, 09:20 UTC | Apr 27, 09:45 UTC | 25m |
| 2026-04-27 | GTI8030 | LAX → GRU | Apr 27, 05:10 UTC | Apr 27, 08:10 UTC | 3h 0m |
| 2026-04-26 | GTI8052 | ANC → MIA | Apr 26, 19:15 UTC | Apr 26, 19:55 UTC | 40m |
| 2026-04-26 | GTI8052 | ANC → MIA | Apr 26, 15:45 UTC | Apr 26, 16:00 UTC | 15m |
| 2026-04-26 | GTI8052 | ANC → MIA | Apr 26, 10:05 UTC | Apr 26, 11:45 UTC | 1h 40m |
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 N860GT page for operator, model, and routing details .