sensors Mode-S transponder
A4DCA4
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N412MC · BOEING 747-400 · operated by ATLAS AIR INC
- Hex
- A4DCA4
- Octal
- 51156244
- Decimal
- 10,804,388
- Country
- US
- Tail
- N412MC
- Type
- B744
- Flights observed
- 212
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- Jul 26, 21:35 UTC
Last known position
Country allocation
The ICAO 24-bit address A4DCA4 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 |
|---|---|---|---|
| GTI612 | Atlas Air | 9 | 2026-04-18 |
| GTI5528 | Atlas Air | 9 | 2026-04-17 |
| GTI8998 | - | 8 | 2026-06-28 |
| GTI8838 | Atlas Air | 8 | 2026-07-25 |
| GTI733 | Atlas Air | 7 | 2026-05-25 |
| GTI033 | Atlas Air | 7 | 2026-05-27 |
| GTI8997 | - | 6 | 2026-06-27 |
| GTI8296 | Atlas Air | 6 | 2026-06-15 |
| GTI8102 | Atlas Air | 6 | 2026-07-23 |
| GTI654 | - | 6 | 2026-06-17 |
| GTI8840 | Atlas Air | 4 | 2026-07-26 |
| GTI734 | Atlas Air | 4 | 2026-05-25 |
| GTI5529 | - | 4 | 2026-04-15 |
| GTI061 | - | 4 | 2026-07-11 |
| GTI040 | - | 4 | 2026-07-05 |
| GTI036 | Atlas Air | 4 | 2026-05-26 |
| GTI034 | Atlas Air | 4 | 2026-05-28 |
| GTI031 | Atlas Air | 4 | 2026-05-19 |
| GTI8920 | - | 3 | 2026-07-02 |
| GTI8788 | - | 3 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | GTI039 | MIA → MAO | Jul 26, 13:05 UTC | Jul 26, 21:35 UTC | 8h 30m |
| 2026-07-26 | GTI8840 | LGG → ZAZ | Jul 26, 00:55 UTC | Jul 26, 05:20 UTC | 4h 25m |
| 2026-07-25 | GTI8840 | LGG → ZAZ | Jul 25, 21:30 UTC | Jul 25, 21:40 UTC | 10m |
| 2026-07-25 | GTI8838 | MIA → LGG | Jul 25, 16:45 UTC | Jul 25, 17:25 UTC | 40m |
| 2026-07-25 | GTI8838 | MIA → LGG | Jul 25, 06:20 UTC | Jul 25, 14:45 UTC | 8h 25m |
| 2026-07-23 | GTI9271 | MIA → ANC | Jul 23, 14:50 UTC | Jul 24, 00:00 UTC | 9h 10m |
| 2026-07-23 | GTI8102 | DFW → ORD | Jul 23, 05:15 UTC | Jul 23, 11:20 UTC | 6h 5m |
| 2026-07-22 | GTI8102 | DFW → ORD | Jul 22, 20:15 UTC | Jul 23, 01:40 UTC | 5h 25m |
| 2026-07-22 | GTI8102 | ICN → ANC | Jul 22, 04:35 UTC | Jul 22, 18:15 UTC | 13h 40m |
| 2026-07-21 | GTI9371 | ORD → ICN | Jul 21, 12:25 UTC | Jul 22, 02:10 UTC | 13h 45m |
| 2026-07-21 | GTI518 | ANC → ORD | Jul 21, 03:50 UTC | Jul 21, 09:00 UTC | 5h 10m |
| 2026-07-19 | GTI518 | - | Jul 19, 15:00 UTC | Jul 20, 06:15 UTC | 15h 15m |
| 2026-07-19 | GTI518 | - | Jul 19, 09:05 UTC | Jul 20, 06:15 UTC | 21h 10m |
| 2026-07-19 | GTI517 | - | Jul 19, 07:45 UTC | Jul 20, 06:15 UTC | 22h 30m |
| 2026-07-19 | GTI517 | - | Jul 19, 05:05 UTC | Jul 20, 05:00 UTC | 23h 55m |
| 2026-07-19 | GTI517 | - | Jul 19, 03:30 UTC | Jul 20, 00:25 UTC | 20h 55m |
| 2026-07-18 | GTI365 | ANC → ORD | Jul 18, 18:25 UTC | Jul 18, 23:45 UTC | 5h 20m |
| 2026-07-17 | GTI365 | - | Jul 17, 21:05 UTC | Jul 18, 16:15 UTC | 19h 11m |
| 2026-07-17 | GTI365 | - | Jul 17, 20:15 UTC | Jul 18, 16:15 UTC | 20h 1m |
| 2026-07-17 | GTI364 | - | Jul 17, 11:04 UTC | Jul 18, 10:10 UTC | 23h 6m |
| 2026-07-17 | GTI364 | - | Jul 17, 10:35 UTC | Jul 18, 09:00 UTC | 22h 26m |
| 2026-07-16 | GTI8365 | ANC → LAX | Jul 16, 17:49 UTC | Jul 17, 07:25 UTC | 13h 35m |
| 2026-07-16 | GTI8365 | ICN → ANC | Jul 16, 02:05 UTC | Jul 16, 15:49 UTC | 13h 45m |
| 2026-07-15 | GTI8675 | - | Jul 15, 08:40 UTC | Jul 15, 19:45 UTC | 11h 5m |
| 2026-07-15 | GTI8675 | - | Jul 15, 07:40 UTC | Jul 15, 08:35 UTC | 55m |
| 2026-07-15 | GTI8675 | - | Jul 15, 00:15 UTC | Jul 15, 05:00 UTC | 4h 45m |
| 2026-07-14 | GTI056 | - | Jul 14, 07:45 UTC | Jul 14, 19:25 UTC | 11h 40m |
| 2026-07-13 | GTI055 | - | Jul 13, 18:30 UTC | Jul 14, 01:50 UTC | 7h 20m |
| 2026-07-12 | GTI634 | SCL → UIO | Jul 12, 19:45 UTC | Jul 12, 22:55 UTC | 3h 10m |
| 2026-07-12 | GTI634 | SCL → UIO | Jul 12, 15:25 UTC | Jul 12, 15:35 UTC | 10m |
| 2026-07-12 | GTI633 | - | Jul 12, 04:15 UTC | Jul 12, 06:45 UTC | 2h 30m |
| 2026-07-11 | GTI062 | - | Jul 11, 17:20 UTC | Jul 11, 22:05 UTC | 4h 45m |
| 2026-07-11 | GTI061 | - | Jul 11, 06:35 UTC | Jul 11, 09:20 UTC | 2h 45m |
| 2026-07-10 | GTI061 | - | Jul 10, 19:35 UTC | Jul 11, 02:50 UTC | 7h 15m |
| 2026-07-10 | GTI038 | - | Jul 10, 00:15 UTC | Jul 10, 15:30 UTC | 15h 15m |
| 2026-07-09 | GTI9271 | - | Jul 9, 12:00 UTC | Jul 9, 19:50 UTC | 7h 50m |
| 2026-07-09 | GTI8102 | - | Jul 9, 02:30 UTC | Jul 9, 08:20 UTC | 5h 50m |
| 2026-07-08 | GTI8102 | - | Jul 8, 18:15 UTC | Jul 8, 23:40 UTC | 5h 25m |
| 2026-07-07 | GTI8102 | ICN → ANC | Jul 7, 16:40 UTC | Jul 8, 06:00 UTC | 13h 20m |
| 2026-07-06 | GTI8903 | - | Jul 6, 16:40 UTC | Jul 7, 04:55 UTC | 12h 15m |
| 2026-07-06 | GTI8903 | - | Jul 6, 08:10 UTC | Jul 6, 13:00 UTC | 4h 50m |
| 2026-07-05 | GTI040 | - | Jul 5, 12:50 UTC | Jul 6, 05:10 UTC | 16h 20m |
| 2026-07-03 | GTI074 | - | Jul 3, 23:20 UTC | Jul 3, 23:55 UTC | 35m |
| 2026-07-03 | GTI073 | BOG → MIA | Jul 3, 14:55 UTC | Jul 3, 15:15 UTC | 20m |
| 2026-07-03 | GTI072 | - | Jul 3, 07:25 UTC | Jul 3, 07:55 UTC | 30m |
| 2026-07-02 | GTI071 | - | Jul 2, 22:35 UTC | Jul 3, 00:00 UTC | 1h 25m |
| 2026-07-02 | GTI8920 | - | Jul 2, 16:40 UTC | Jul 2, 18:00 UTC | 1h 20m |
| 2026-07-01 | GTI8920 | - | Jul 1, 15:10 UTC | Jul 1, 23:35 UTC | 8h 25m |
| 2026-06-30 | GTI8920 | - | Jun 30, 23:45 UTC | Jul 1, 08:50 UTC | 9h 5m |
| 2026-06-28 | GTI8998 | - | Jun 28, 10:50 UTC | Jun 28, 18:29 UTC | 7h 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 N412MC page for operator, model, and routing details .