sensors Mode-S transponder
A5FFF9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N486MC · BOEING 747-400 · operated by UMB BANK NA TRUSTEE
- Hex
- A5FFF9
- Octal
- 51377771
- Decimal
- 10,878,969
- Country
- US
- Tail
- N486MC
- Type
- B744
- Flights observed
- 167
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address A5FFF9 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 |
|---|---|---|---|
| GTI8120 | - | 16 | 2026-07-02 |
| GTI8117 | - | 15 | 2026-06-30 |
| GTI8560 | - | 13 | 2026-06-26 |
| GTI812 | - | 9 | 2026-07-08 |
| GTI518 | - | 9 | 2026-07-03 |
| GTI8559 | - | 7 | 2026-06-25 |
| GTI8243 | Atlas Air | 6 | 2026-05-03 |
| GTI8242 | Atlas Air | 6 | 2026-05-01 |
| GTI811 | - | 5 | 2026-07-09 |
| GTI8275 | - | 4 | 2026-07-05 |
| GTI8153 | Atlas Air | 4 | 2026-05-23 |
| GTI364 | Atlas Air | 4 | 2026-06-19 |
| GTI8860 | - | 3 | 2026-07-12 |
| GTI8676 | Atlas Air | 3 | 2026-06-08 |
| GTI8373 | Atlas Air | 3 | 2026-05-10 |
| GTI8274 | - | 3 | 2026-07-04 |
| GTI824A | Atlas Air | 3 | 2026-05-30 |
| GTI8193 | Atlas Air | 3 | 2026-05-29 |
| GTI654 | Atlas Air | 3 | 2026-05-20 |
| GTI517 | - | 3 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | GTI862 | HSV → LUX | Jul 13, 09:15 UTC | Jul 13, 17:40 UTC | 8h 25m |
| 2026-07-12 | GTI604 | - | Jul 12, 18:01 UTC | Jul 13, 02:35 UTC | 8h 35m |
| 2026-07-12 | GTI8672 | - | Jul 12, 06:20 UTC | Jul 12, 14:25 UTC | 8h 5m |
| 2026-07-12 | GTI8860 | - | Jul 12, 01:45 UTC | Jul 12, 03:01 UTC | 1h 15m |
| 2026-07-11 | GTI8860 | - | Jul 11, 18:15 UTC | Jul 11, 23:20 UTC | 5h 5m |
| 2026-07-11 | GTI8860 | ICN → ANC | Jul 11, 08:30 UTC | Jul 11, 16:05 UTC | 7h 35m |
| 2026-07-10 | GTI893 | - | Jul 10, 03:15 UTC | Jul 10, 05:15 UTC | 2h 0m |
| 2026-07-09 | GTI892 | ICN → NRT | Jul 9, 16:25 UTC | Jul 10, 00:55 UTC | 8h 30m |
| 2026-07-09 | GTI811 | - | Jul 9, 05:45 UTC | Jul 9, 07:50 UTC | 2h 5m |
| 2026-07-08 | GTI811 | - | Jul 8, 18:10 UTC | Jul 9, 05:35 UTC | 11h 25m |
| 2026-07-08 | GTI812 | ANC → YYZ | Jul 8, 09:35 UTC | Jul 8, 15:15 UTC | 5h 40m |
| 2026-07-07 | GTI812 | ICN → ANC | Jul 7, 18:35 UTC | Jul 8, 07:30 UTC | 12h 55m |
| 2026-07-07 | GTI9511 | - | Jul 7, 03:40 UTC | Jul 7, 16:10 UTC | 12h 30m |
| 2026-07-05 | GTI8275 | - | Jul 5, 12:40 UTC | Jul 5, 17:10 UTC | 4h 30m |
| 2026-07-04 | GTI8275 | - | Jul 4, 17:05 UTC | Jul 5, 09:45 UTC | 16h 40m |
| 2026-07-04 | GTI8274 | - | Jul 4, 07:00 UTC | Jul 5, 03:55 UTC | 20h 55m |
| 2026-07-03 | GTI518 | - | Jul 3, 23:10 UTC | Jul 4, 03:50 UTC | 4h 40m |
| 2026-07-03 | GTI518 | - | Jul 3, 02:20 UTC | Jul 3, 21:20 UTC | 19h 0m |
| 2026-07-02 | GTI517 | - | Jul 2, 20:20 UTC | Jul 3, 20:15 UTC | 23h 55m |
| 2026-07-02 | GTI517 | - | Jul 2, 16:20 UTC | Jul 3, 15:40 UTC | 23h 20m |
| 2026-07-02 | GTI517 | - | Jul 2, 15:00 UTC | Jul 3, 14:15 UTC | 23h 15m |
| 2026-07-02 | GTI8120 | ANC → ORD | Jul 2, 06:30 UTC | Jul 2, 12:00 UTC | 5h 30m |
| 2026-07-01 | GTI8120 | ICN → ANC | Jul 1, 15:40 UTC | Jul 1, 22:40 UTC | 7h 0m |
| 2026-07-01 | GTI8120 | - | Jul 1, 13:05 UTC | Jul 1, 13:25 UTC | 20m |
| 2026-06-30 | GTI8117 | - | Jun 30, 14:00 UTC | Jun 30, 14:20 UTC | 20m |
| 2026-06-30 | GTI8117 | - | Jun 30, 06:55 UTC | Jun 30, 11:00 UTC | 4h 5m |
| 2026-06-29 | GTI8117 | ORD → ICN | Jun 29, 02:50 UTC | Jun 29, 16:04 UTC | 13h 15m |
| 2026-06-28 | GTI8091 | FRA → ORD | Jun 28, 05:24 UTC | Jun 28, 14:19 UTC | 8h 55m |
| 2026-06-26 | GTI8092 | ORD → FRA | Jun 26, 21:15 UTC | Jun 27, 05:10 UTC | 7h 55m |
| 2026-06-26 | GTI8560 | ANC → ORD | Jun 26, 02:54 UTC | Jun 26, 08:24 UTC | 5h 30m |
| 2026-06-25 | GTI8560 | - | Jun 25, 17:25 UTC | Jun 26, 00:50 UTC | 7h 25m |
| 2026-06-25 | GTI8560 | - | Jun 25, 08:20 UTC | Jun 25, 08:55 UTC | 35m |
| 2026-06-25 | GTI8559 | - | Jun 25, 00:55 UTC | Jun 25, 01:19 UTC | 25m |
| 2026-06-23 | GTI8559 | - | Jun 23, 18:55 UTC | Jun 23, 22:34 UTC | 3h 40m |
| 2026-06-23 | GTI8559 | ORD → ICN | Jun 23, 00:50 UTC | Jun 23, 14:10 UTC | 13h 20m |
| 2026-06-22 | GTI812 | - | Jun 22, 17:29 UTC | Jun 22, 18:49 UTC | 1h 20m |
| 2026-06-22 | GTI812 | - | Jun 22, 08:19 UTC | Jun 22, 13:59 UTC | 5h 40m |
| 2026-06-21 | GTI812 | ICN → ANC | Jun 21, 16:14 UTC | Jun 22, 06:00 UTC | 13h 45m |
| 2026-06-20 | GTI8117 | ORD → ICN | Jun 20, 21:19 UTC | Jun 21, 10:49 UTC | 13h 30m |
| 2026-06-20 | GTI365 | ANC → YYZ | Jun 20, 08:19 UTC | Jun 20, 13:34 UTC | 5h 15m |
| 2026-06-19 | GTI365 | ANC → YYZ | Jun 19, 14:19 UTC | Jun 20, 06:10 UTC | 15h 50m |
| 2026-06-19 | GTI364 | ORD → ICN | Jun 19, 08:20 UTC | Jun 20, 06:10 UTC | 21h 50m |
| 2026-06-19 | GTI364 | ORD → ICN | Jun 19, 06:59 UTC | Jun 20, 06:10 UTC | 23h 10m |
| 2026-06-19 | GTI364 | ORD → ICN | Jun 19, 04:19 UTC | Jun 20, 00:14 UTC | 19h 55m |
| 2026-06-19 | GTI364 | ORD → ICN | Jun 19, 04:04 UTC | Jun 20, 00:14 UTC | 20h 10m |
| 2026-06-18 | GTI8365 | PVG → ANC | Jun 18, 07:30 UTC | Jun 18, 21:30 UTC | 14h 0m |
| 2026-06-17 | GTI8365 | PVG → ANC | Jun 17, 15:55 UTC | Jun 18, 05:20 UTC | 13h 25m |
| 2026-06-16 | GTI811 | YYZ → ICN | Jun 16, 20:40 UTC | Jun 17, 10:20 UTC | 13h 40m |
| 2026-06-16 | GTI812 | - | Jun 16, 11:49 UTC | Jun 16, 17:24 UTC | 5h 35m |
| 2026-06-15 | GTI812 | - | Jun 15, 21:50 UTC | Jun 16, 09:20 UTC | 11h 30m |
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 N486MC page for operator, model, and routing details .