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
- 186
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Current 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 |
| GTI733 | Atlas Air | 7 | 2026-05-25 |
| GTI033 | Atlas Air | 7 | 2026-05-27 |
| GTI8997 | - | 6 | 2026-06-27 |
| GTI8838 | Atlas Air | 6 | 2026-05-31 |
| GTI8296 | Atlas Air | 6 | 2026-06-15 |
| GTI654 | - | 6 | 2026-06-17 |
| 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 |
| GTI8676 | Atlas Air | 3 | 2026-05-10 |
| GTI8102 | - | 3 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | GTI056 | - | Jul 14, 07:45 UTC | Jul 14, 09:05 UTC | 1h 20m |
| 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 |
| 2026-06-27 | GTI8998 | - | Jun 27, 15:30 UTC | Jun 28, 08:00 UTC | 16h 30m |
| 2026-06-27 | GTI8997 | ANC → ANC | Jun 27, 09:15 UTC | Jun 28, 08:00 UTC | 22h 45m |
| 2026-06-26 | GTI8997 | - | Jun 26, 22:49 UTC | Jun 27, 06:40 UTC | 7h 50m |
| 2026-06-26 | GTI038 | UIO → MIA | Jun 26, 18:49 UTC | Jun 26, 19:14 UTC | 25m |
| 2026-06-26 | GTI038 | UIO → MIA | Jun 26, 02:14 UTC | Jun 26, 17:44 UTC | 15h 30m |
| 2026-06-25 | GTI8998 | ANC → MIA | Jun 25, 06:30 UTC | Jun 25, 13:45 UTC | 7h 15m |
| 2026-06-24 | GTI8998 | - | Jun 24, 11:09 UTC | Jun 25, 04:14 UTC | 17h 5m |
| 2026-06-24 | GTI8998 | - | Jun 24, 07:05 UTC | Jun 25, 04:14 UTC | 21h 10m |
| 2026-06-24 | GTI8997 | ANC → ANC | Jun 24, 05:24 UTC | Jun 25, 04:14 UTC | 22h 50m |
| 2026-06-22 | GTI8997 | - | Jun 22, 22:10 UTC | Jun 23, 05:54 UTC | 7h 45m |
| 2026-06-21 | GTI040 | UIO → MIA | Jun 21, 13:20 UTC | Jun 22, 06:19 UTC | 17h 0m |
| 2026-06-20 | GTI075 | MIA → BOG | Jun 20, 00:39 UTC | Jun 20, 10:34 UTC | 9h 55m |
| 2026-06-19 | GTI8998 | - | Jun 19, 12:14 UTC | Jun 19, 19:29 UTC | 7h 15m |
| 2026-06-18 | GTI8998 | - | Jun 18, 14:15 UTC | Jun 19, 07:45 UTC | 17h 29m |
| 2026-06-18 | GTI8998 | - | Jun 18, 09:05 UTC | Jun 19, 07:45 UTC | 22h 39m |
| 2026-06-18 | GTI8997 | - | Jun 18, 08:30 UTC | Jun 19, 06:59 UTC | 22h 29m |
| 2026-06-17 | GTI8997 | - | Jun 17, 22:00 UTC | Jun 18, 06:15 UTC | 8h 15m |
| 2026-06-17 | GTI654 | ANC → MIA | Jun 17, 09:45 UTC | Jun 17, 16:30 UTC | 6h 45m |
| 2026-06-16 | GTI654 | HKG → ANC | Jun 16, 21:15 UTC | Jun 17, 06:40 UTC | 9h 25m |
| 2026-06-16 | GTI8138 | DEL → HAN | Jun 16, 11:45 UTC | Jun 16, 16:30 UTC | 4h 45m |
| 2026-06-16 | GTI8137 | HKG → DEL | Jun 16, 05:45 UTC | Jun 16, 09:34 UTC | 3h 50m |
| 2026-06-16 | GTI8137 | HKG → DEL | Jun 16, 04:45 UTC | Jun 16, 04:55 UTC | 10m |
| 2026-06-15 | GTI8296 | NGU → HHN | Jun 15, 18:50 UTC | Jun 15, 19:25 UTC | 35m |
| 2026-06-15 | GTI8296 | NGU → HHN | Jun 15, 11:24 UTC | Jun 15, 18:04 UTC | 6h 40m |
| 2026-06-14 | GTI8296 | NGU → HHN | Jun 14, 17:05 UTC | Jun 15, 16:49 UTC | 23h 44m |
| 2026-06-14 | GTI8296 | NGU → HHN | Jun 14, 15:05 UTC | Jun 15, 14:05 UTC | 23h 0m |
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 .