sensors Mode-S transponder
A5DC31
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N477MC · BOEING 747-400 · operated by ATLAS AIR INC
- Hex
- A5DC31
- Octal
- 51356061
- Decimal
- 10,869,809
- Country
- US
- Tail
- N477MC
- Type
- B744
- Flights observed
- 98
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address A5DC31 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 |
|---|---|---|---|
| GTI8193 | Atlas Air | 10 | 2026-06-11 |
| GTI8523 | - | 7 | 2026-07-13 |
| GTI8284 | - | 7 | 2026-07-14 |
| GTI863 | - | 6 | 2026-07-08 |
| GTI862 | - | 5 | 2026-07-07 |
| GTI8676 | Atlas Air | 4 | 2026-05-31 |
| GTI8192 | Atlas Air | 4 | 2026-06-10 |
| GTI9976 | Atlas Air | 3 | 2026-06-03 |
| GTI8522 | - | 3 | 2026-07-12 |
| GTI8102 | Atlas Air | 3 | 2026-05-28 |
| GTI6081 | Atlas Air | 3 | 2026-06-18 |
| GTI6075 | Atlas Air | 3 | 2026-06-20 |
| THY6092 | - | 2 | 2026-06-19 |
| THY6075 | Turkish Airlines | 2 | 2026-06-20 |
| GTI9462 | Atlas Air | 2 | 2026-05-30 |
| GTI9460 | Atlas Air | 2 | 2026-06-10 |
| GTI9045 | - | 2 | 2026-07-12 |
| GTI8865 | Atlas Air | 2 | 2026-07-02 |
| GTI8153 | - | 2 | 2026-06-27 |
| GTI648 | Atlas Air | 2 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | GTI8284 | - | Jul 14, 07:05 UTC | Jul 14, 08:15 UTC | 1h 10m |
| 2026-07-13 | GTI8284 | - | Jul 13, 18:00 UTC | Jul 14, 03:25 UTC | 9h 25m |
| 2026-07-13 | GTI8284 | - | Jul 13, 12:55 UTC | Jul 13, 14:50 UTC | 1h 55m |
| 2026-07-13 | GTI8523 | ANC → ORD | Jul 13, 04:25 UTC | Jul 13, 09:45 UTC | 5h 20m |
| 2026-07-12 | GTI8523 | HKG → ANC | Jul 12, 17:10 UTC | Jul 13, 02:35 UTC | 9h 25m |
| 2026-07-12 | GTI8523 | - | Jul 12, 13:01 UTC | Jul 12, 14:30 UTC | 1h 30m |
| 2026-07-12 | GTI8522 | - | Jul 12, 09:30 UTC | Jul 12, 09:40 UTC | 10m |
| 2026-07-12 | GTI8522 | - | Jul 12, 08:20 UTC | Jul 12, 08:30 UTC | 10m |
| 2026-07-12 | GTI9045 | - | Jul 12, 03:40 UTC | Jul 12, 03:55 UTC | 15m |
| 2026-07-12 | GTI9045 | - | Jul 12, 01:00 UTC | Jul 12, 03:05 UTC | 2h 5m |
| 2026-07-11 | GTI8898 | - | Jul 11, 22:25 UTC | Jul 11, 23:00 UTC | 35m |
| 2026-07-11 | GTI894 | - | Jul 11, 03:15 UTC | Jul 11, 23:00 UTC | 19h 45m |
| 2026-07-10 | GTI892 | ICN → NRT | Jul 10, 16:00 UTC | Jul 11, 00:35 UTC | 8h 35m |
| 2026-07-09 | GTI890 | - | Jul 9, 08:10 UTC | Jul 9, 22:30 UTC | 14h 20m |
| 2026-07-08 | GTI891 | - | Jul 8, 20:45 UTC | Jul 9, 04:25 UTC | 7h 40m |
| 2026-07-08 | GTI863 | - | Jul 8, 00:05 UTC | Jul 8, 14:00 UTC | 13h 55m |
| 2026-07-07 | GTI863 | - | Jul 7, 17:40 UTC | Jul 8, 14:00 UTC | 20h 20m |
| 2026-07-07 | GTI863 | - | Jul 7, 14:55 UTC | Jul 8, 14:00 UTC | 23h 5m |
| 2026-07-07 | GTI862 | - | Jul 7, 10:20 UTC | Jul 8, 10:15 UTC | 23h 55m |
| 2026-07-07 | GTI862 | - | Jul 7, 08:30 UTC | Jul 8, 00:20 UTC | 15h 50m |
| 2026-07-06 | GTI862 | - | Jul 6, 09:15 UTC | Jul 6, 17:00 UTC | 7h 45m |
| 2026-07-05 | GTI604 | - | Jul 5, 19:25 UTC | Jul 6, 04:20 UTC | 8h 55m |
| 2026-07-02 | GTI8866 | PSM → RMS | Jul 2, 12:30 UTC | Jul 2, 20:05 UTC | 7h 35m |
| 2026-07-02 | GTI8865 | BWI → IAH | Jul 2, 08:40 UTC | Jul 2, 09:30 UTC | 50m |
| 2026-07-01 | GTI8865 | BWI → IAH | Jul 1, 21:30 UTC | Jul 2, 06:30 UTC | 9h 0m |
| 2026-06-30 | GTI863 | PVG → GYD | Jun 30, 23:05 UTC | Jul 1, 12:35 UTC | 13h 30m |
| 2026-06-30 | GTI863 | PVG → GYD | Jun 30, 16:35 UTC | Jul 1, 12:35 UTC | 20h 0m |
| 2026-06-30 | GTI863 | PVG → GYD | Jun 30, 10:20 UTC | Jul 1, 09:40 UTC | 23h 20m |
| 2026-06-30 | GTI862 | HSV → LUX | Jun 30, 07:05 UTC | Jun 30, 23:30 UTC | 16h 25m |
| 2026-06-29 | GTI862 | HSV → LUX | Jun 29, 08:35 UTC | Jun 29, 16:19 UTC | 7h 45m |
| 2026-06-28 | GTI604 | - | Jun 28, 19:59 UTC | Jun 29, 04:39 UTC | 8h 40m |
| 2026-06-28 | GTI8154 | AMS → LUX | Jun 28, 13:59 UTC | Jun 28, 14:34 UTC | 35m |
| 2026-06-27 | GTI8153 | - | Jun 27, 07:10 UTC | Jun 27, 11:44 UTC | 4h 35m |
| 2026-06-26 | GTI8153 | ICN → AMS | Jun 26, 15:15 UTC | Jun 27, 11:44 UTC | 20h 30m |
| 2026-06-25 | GTI8522 | ORD → ICN | Jun 25, 21:10 UTC | Jun 26, 11:05 UTC | 13h 55m |
| 2026-06-25 | GTI8523 | ANC → ORD | Jun 25, 11:39 UTC | Jun 25, 16:59 UTC | 5h 20m |
| 2026-06-24 | GTI8523 | HKG → ANC | Jun 24, 23:50 UTC | Jun 25, 09:25 UTC | 9h 35m |
| 2026-06-24 | GTI8523 | - | Jun 24, 21:00 UTC | Jun 24, 21:29 UTC | 30m |
| 2026-06-24 | GTI8523 | - | Jun 24, 19:59 UTC | Jun 24, 20:30 UTC | 30m |
| 2026-06-24 | GTI8132 | DEL → HKG | Jun 24, 13:40 UTC | Jun 24, 17:29 UTC | 3h 50m |
| 2026-06-24 | GTI8131 | HKG → DEL | Jun 24, 05:24 UTC | Jun 24, 10:04 UTC | 4h 40m |
| 2026-06-23 | GTI8284 | - | Jun 23, 16:24 UTC | Jun 23, 19:19 UTC | 2h 55m |
| 2026-06-23 | GTI8284 | - | Jun 23, 01:59 UTC | Jun 23, 16:20 UTC | 14h 20m |
| 2026-06-22 | GTI8284 | - | Jun 22, 14:24 UTC | Jun 22, 23:10 UTC | 8h 45m |
| 2026-06-22 | GTI8284 | - | Jun 22, 08:35 UTC | Jun 22, 10:44 UTC | 2h 10m |
| 2026-06-20 | GTI6075 | LGG → MIA | Jun 20, 18:29 UTC | Jun 21, 03:40 UTC | 9h 10m |
| 2026-06-20 | THY6075 | BOM → HKG | Jun 20, 12:50 UTC | Jun 20, 15:29 UTC | 2h 40m |
| 2026-06-19 | THY6092 | - | Jun 19, 23:19 UTC | Jun 20, 09:09 UTC | 9h 50m |
| 2026-06-19 | GTI6091 | - | Jun 19, 10:44 UTC | Jun 19, 18:54 UTC | 8h 10m |
| 2026-06-19 | THY6091 | - | Jun 19, 05:09 UTC | Jun 19, 07:45 UTC | 2h 35m |
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 N477MC page for operator, model, and routing details .