sensors Mode-S transponder
A62778
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N496MC · BOEING 747-400 · operated by ATLAS AIR INC
- Hex
- A62778
- Octal
- 51423570
- Decimal
- 10,889,080
- Country
- US
- Tail
- N496MC
- Type
- B744
- Flights observed
- 151
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 18d ago
Last known position
Country allocation
The ICAO 24-bit address A62778 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 |
|---|---|---|---|
| GTI8977 | Atlas Air | 7 | 2026-06-06 |
| GTI612 | - | 7 | 2026-07-11 |
| GTI046 | - | 7 | 2026-06-26 |
| GTI8418 | - | 6 | 2026-07-05 |
| GTI8577 | Atlas Air | 5 | 2026-06-21 |
| GTI061 | - | 5 | 2026-07-17 |
| GTI036 | - | 5 | 2026-07-01 |
| GTI8417 | - | 4 | 2026-07-03 |
| GTI8230 | Atlas Air | 4 | 2026-04-23 |
| GTI080 | Atlas Air | 4 | 2026-07-19 |
| GTI079 | - | 4 | 2026-07-19 |
| GTI056 | Atlas Air | 4 | 2026-07-25 |
| GTI038 | - | 4 | 2026-07-16 |
| GTI033 | - | 4 | 2026-06-25 |
| GTI8976 | Atlas Air | 3 | 2026-06-05 |
| GTI8676 | - | 3 | 2026-06-30 |
| GTI634 | Atlas Air | 3 | 2026-05-10 |
| GTI064 | Atlas Air | 3 | 2026-05-06 |
| GTI062 | Atlas Air | 3 | 2026-07-18 |
| GTI055 | - | 3 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | GTI1021 | BOS → RFD | Jul 26, 14:00 UTC | Jul 26, 16:10 UTC | 2h 10m |
| 2026-07-26 | GTI1021 | BOS → RFD | Jul 26, 12:20 UTC | Jul 26, 12:30 UTC | 10m |
| 2026-07-26 | GTI8681 | IAH → HND | Jul 26, 00:35 UTC | Jul 26, 08:55 UTC | 8h 21m |
| 2026-07-25 | GTI057 | MIA → VCP | Jul 25, 13:25 UTC | Jul 25, 20:40 UTC | 7h 15m |
| 2026-07-25 | GTI056 | VCP → LIM | Jul 25, 04:45 UTC | Jul 25, 06:30 UTC | 1h 45m |
| 2026-07-20 | GTI056 | - | Jul 20, 11:00 UTC | Jul 20, 12:20 UTC | 1h 20m |
| 2026-07-19 | GTI055 | - | Jul 19, 23:35 UTC | Jul 20, 06:45 UTC | 7h 10m |
| 2026-07-19 | GTI080 | BOG → MIA | Jul 19, 13:35 UTC | Jul 19, 16:35 UTC | 3h 0m |
| 2026-07-19 | GTI079 | - | Jul 19, 07:00 UTC | Jul 19, 10:00 UTC | 3h 0m |
| 2026-07-18 | GTI062 | SCL → MIA | Jul 18, 07:00 UTC | Jul 18, 11:40 UTC | 4h 40m |
| 2026-07-17 | GTI061 | - | Jul 17, 23:25 UTC | Jul 17, 23:39 UTC | 15m |
| 2026-07-17 | GTI061 | - | Jul 17, 20:00 UTC | Jul 17, 22:49 UTC | 2h 50m |
| 2026-07-17 | GTI061 | - | Jul 17, 09:15 UTC | Jul 17, 16:34 UTC | 7h 20m |
| 2026-07-16 | GTI038 | - | Jul 16, 12:09 UTC | Jul 17, 04:44 UTC | 16h 35m |
| 2026-07-11 | GTI612 | - | Jul 11, 06:05 UTC | Jul 11, 07:40 UTC | 1h 35m |
| 2026-07-10 | GTI612 | ANC → HSV | Jul 10, 21:50 UTC | Jul 11, 04:05 UTC | 6h 15m |
| 2026-07-10 | GTI612 | - | Jul 10, 11:55 UTC | Jul 10, 19:30 UTC | 7h 35m |
| 2026-07-10 | GTI612 | - | Jul 10, 09:45 UTC | Jul 10, 10:05 UTC | 20m |
| 2026-07-10 | GTI612 | - | Jul 10, 05:55 UTC | Jul 10, 06:15 UTC | 20m |
| 2026-07-09 | GTI611 | - | Jul 9, 22:35 UTC | Jul 9, 23:15 UTC | 40m |
| 2026-07-08 | GTI8898 | - | Jul 8, 16:20 UTC | Jul 9, 01:45 UTC | 9h 25m |
| 2026-07-08 | GTI8439 | - | Jul 8, 08:40 UTC | Jul 8, 13:50 UTC | 5h 10m |
| 2026-07-07 | GTI8692 | - | Jul 7, 01:25 UTC | Jul 7, 14:00 UTC | 12h 35m |
| 2026-07-06 | GTI8692 | HKG → ANC | Jul 6, 13:45 UTC | Jul 6, 23:30 UTC | 9h 45m |
| 2026-07-05 | GTI8418 | - | Jul 5, 07:05 UTC | Jul 5, 19:25 UTC | 12h 20m |
| 2026-07-03 | GTI8418 | - | Jul 3, 22:25 UTC | Jul 4, 06:25 UTC | 8h 0m |
| 2026-07-03 | GTI8417 | - | Jul 3, 06:15 UTC | Jul 3, 18:05 UTC | 11h 50m |
| 2026-07-02 | GTI8417 | DFW → VCP | Jul 2, 18:50 UTC | Jul 3, 03:55 UTC | 9h 5m |
| 2026-07-02 | GTI8417 | - | Jul 2, 13:55 UTC | Jul 2, 16:25 UTC | 2h 30m |
| 2026-07-01 | GTI036 | - | Jul 1, 05:35 UTC | Jul 1, 21:40 UTC | 16h 5m |
| 2026-06-30 | GTI8676 | - | Jun 30, 07:50 UTC | Jul 1, 01:40 UTC | 17h 50m |
| 2026-06-29 | GTI8676 | - | Jun 29, 20:54 UTC | Jun 30, 02:40 UTC | 5h 45m |
| 2026-06-28 | GTI8676 | ICN → ANC | Jun 28, 11:39 UTC | Jun 29, 00:24 UTC | 12h 45m |
| 2026-06-28 | GTI8418 | - | Jun 28, 04:50 UTC | Jun 28, 05:20 UTC | 30m |
| 2026-06-27 | GTI8418 | - | Jun 27, 17:04 UTC | Jun 28, 03:59 UTC | 10h 55m |
| 2026-06-27 | GTI8418 | - | Jun 27, 04:00 UTC | Jun 27, 11:35 UTC | 7h 35m |
| 2026-06-26 | GTI046 | - | Jun 26, 17:50 UTC | Jun 26, 18:24 UTC | 35m |
| 2026-06-26 | GTI046 | - | Jun 26, 03:29 UTC | Jun 26, 06:35 UTC | 3h 5m |
| 2026-06-25 | GTI045 | MIA → GIG | Jun 25, 17:25 UTC | Jun 26, 00:59 UTC | 7h 35m |
| 2026-06-25 | GTI034 | - | Jun 25, 11:54 UTC | Jun 25, 13:45 UTC | 1h 50m |
| 2026-06-25 | GTI034 | - | Jun 25, 06:20 UTC | Jun 25, 06:30 UTC | 10m |
| 2026-06-25 | GTI033 | - | Jun 25, 00:59 UTC | Jun 25, 01:24 UTC | 25m |
| 2026-06-24 | GTI033 | - | Jun 24, 13:54 UTC | Jun 24, 22:10 UTC | 8h 15m |
| 2026-06-23 | GTI036 | UIO → MIA | Jun 23, 11:04 UTC | Jun 24, 04:00 UTC | 16h 55m |
| 2026-06-21 | GTI080 | BOG → MIA | Jun 21, 22:44 UTC | Jun 21, 23:14 UTC | 30m |
| 2026-06-21 | GTI079 | MIA → BOG | Jun 21, 11:34 UTC | Jun 21, 13:09 UTC | 1h 35m |
| 2026-06-21 | GTI8577 | MST → GSP | Jun 21, 06:14 UTC | Jun 21, 08:20 UTC | 2h 5m |
| 2026-06-20 | GTI8577 | MST → GSP | Jun 20, 20:14 UTC | Jun 21, 01:45 UTC | 5h 30m |
| 2026-06-20 | GTI8577 | MST → GSP | Jun 20, 11:20 UTC | Jun 20, 17:59 UTC | 6h 40m |
| 2026-06-20 | GTI8577 | MST → GSP | Jun 20, 09:39 UTC | Jun 20, 09:59 UTC | 20m |
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 N496MC page for operator, model, and routing details .