sensors Mode-S transponder
A57362
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N450PA · BOEING 747-400 · operated by ATLAS AIR INC
- Hex
- A57362
- Octal
- 51271542
- Decimal
- 10,842,978
- Country
- US
- Tail
- N450PA
- Type
- B744
- Flights observed
- 172
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4m ago
Current position
Country allocation
The ICAO 24-bit address A57362 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 |
|---|---|---|---|
| GTI518 | Atlas Air | 23 | 2026-06-08 |
| GTI517 | Atlas Air | 23 | 2026-06-09 |
| GTI365 | Atlas Air | 9 | 2026-06-06 |
| GTI364 | Atlas Air | 9 | 2026-06-05 |
| GTI8560 | Atlas Air | 8 | 2026-04-16 |
| GTI8275 | - | 7 | 2026-07-11 |
| GTI8274 | - | 7 | 2026-07-10 |
| GTI8243 | Atlas Air | 7 | 2026-05-25 |
| GTI8174 | - | 6 | 2026-07-13 |
| GTI8559 | - | 4 | 2026-07-14 |
| GTI8365 | - | 4 | 2026-07-09 |
| GTI512 | Atlas Air | 4 | 2026-06-10 |
| GTI8676 | Atlas Air | 3 | 2026-05-03 |
| GTI8173 | - | 3 | 2026-07-12 |
| GTI9680 | Atlas Air | 2 | 2026-04-28 |
| GTI8865 | Atlas Air | 2 | 2026-06-28 |
| GTI863 | Atlas Air | 2 | 2026-06-27 |
| GTI862 | Atlas Air | 2 | 2026-06-23 |
| GTI8553 | Atlas Air | 2 | 2026-05-12 |
| GTI8537 | Atlas Air | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | GTI8559 | - | Jul 14, 20:25 UTC | Jul 14, 20:30 UTC | 5m |
| 2026-07-14 | GTI8559 | - | Jul 14, 05:15 UTC | Jul 14, 16:50 UTC | 11h 35m |
| 2026-07-13 | GTI8174 | - | Jul 13, 19:05 UTC | Jul 13, 22:00 UTC | 2h 55m |
| 2026-07-13 | GTI8174 | - | Jul 13, 09:05 UTC | Jul 13, 15:15 UTC | 6h 10m |
| 2026-07-12 | GTI8174 | - | Jul 12, 14:01 UTC | Jul 13, 07:05 UTC | 17h 5m |
| 2026-07-12 | GTI8173 | - | Jul 12, 04:35 UTC | Jul 13, 01:25 UTC | 20h 50m |
| 2026-07-12 | GTI8173 | - | Jul 12, 04:05 UTC | Jul 13, 01:25 UTC | 21h 20m |
| 2026-07-11 | GTI8275 | - | Jul 11, 15:45 UTC | Jul 11, 20:25 UTC | 4h 40m |
| 2026-07-10 | GTI8275 | - | Jul 10, 22:00 UTC | Jul 11, 13:35 UTC | 15h 35m |
| 2026-07-10 | GTI8275 | - | Jul 10, 16:35 UTC | Jul 11, 13:35 UTC | 21h 1m |
| 2026-07-10 | GTI8274 | - | Jul 10, 14:55 UTC | Jul 11, 13:35 UTC | 22h 40m |
| 2026-07-10 | GTI8274 | - | Jul 10, 12:35 UTC | Jul 11, 12:30 UTC | 23h 56m |
| 2026-07-10 | GTI8274 | - | Jul 10, 12:00 UTC | Jul 11, 07:40 UTC | 19h 40m |
| 2026-07-09 | GTI8365 | - | Jul 9, 19:25 UTC | Jul 10, 08:20 UTC | 12h 55m |
| 2026-07-09 | GTI8365 | ICN → ANC | Jul 9, 00:25 UTC | Jul 9, 17:20 UTC | 16h 55m |
| 2026-06-28 | GTI9191 | ORD → ICN | Jun 28, 20:39 UTC | Jun 29, 07:55 UTC | 11h 15m |
| 2026-06-28 | GTI8866 | PSM → RMS | Jun 28, 09:15 UTC | Jun 28, 16:55 UTC | 7h 40m |
| 2026-06-28 | GTI8865 | BWI → IAH | Jun 28, 04:20 UTC | Jun 28, 05:15 UTC | 55m |
| 2026-06-27 | GTI8865 | BWI → IAH | Jun 27, 17:09 UTC | Jun 28, 01:40 UTC | 8h 30m |
| 2026-06-27 | GTI863 | PVG → GYD | Jun 27, 03:25 UTC | Jun 27, 07:39 UTC | 4h 15m |
| 2026-06-26 | GTI863 | PVG → GYD | Jun 26, 01:20 UTC | Jun 26, 01:34 UTC | 15m |
| 2026-06-23 | GTI862 | HSV → LUX | Jun 23, 17:09 UTC | Jun 24, 03:04 UTC | 9h 55m |
| 2026-06-22 | GTI862 | HSV → LUX | Jun 22, 07:25 UTC | Jun 22, 15:05 UTC | 7h 40m |
| 2026-06-21 | GTI604 | LUX → HSV | Jun 21, 18:20 UTC | Jun 22, 03:24 UTC | 9h 5m |
| 2026-06-21 | GTI8672 | OKO → EDF | Jun 21, 06:14 UTC | Jun 21, 13:59 UTC | 7h 45m |
| 2026-06-21 | GTI8500 | SUU → PSM | Jun 21, 00:55 UTC | Jun 21, 02:24 UTC | 1h 30m |
| 2026-06-19 | GTI038 | UIO → MIA | Jun 19, 04:19 UTC | Jun 19, 20:44 UTC | 16h 25m |
| 2026-06-18 | GTI064 | VCP → LIM | Jun 18, 12:35 UTC | Jun 19, 00:29 UTC | 11h 54m |
| 2026-06-18 | GTI063 | MIA → VCP | Jun 18, 01:50 UTC | Jun 18, 08:50 UTC | 7h 0m |
| 2026-06-17 | GTI032 | VCP → MIA | Jun 17, 11:50 UTC | Jun 17, 19:05 UTC | 7h 15m |
| 2026-06-17 | GTI031 | GIG → VCP | Jun 17, 06:45 UTC | Jun 17, 07:40 UTC | 55m |
| 2026-06-16 | GTI031 | GIG → VCP | Jun 16, 20:20 UTC | Jun 17, 03:55 UTC | 7h 35m |
| 2026-06-16 | GTI734 | SCL → MIA | Jun 16, 11:05 UTC | Jun 16, 16:10 UTC | 5h 5m |
| 2026-06-16 | GTI734 | SCL → MIA | Jun 16, 08:05 UTC | Jun 16, 08:15 UTC | 10m |
| 2026-06-16 | GTI733 | MIA → BOG | Jun 16, 03:39 UTC | Jun 16, 04:00 UTC | 20m |
| 2026-06-15 | GTI733 | MIA → BOG | Jun 15, 15:59 UTC | Jun 16, 00:10 UTC | 8h 10m |
| 2026-06-14 | GTI040 | UIO → MIA | Jun 14, 12:35 UTC | Jun 15, 05:04 UTC | 16h 29m |
| 2026-06-12 | GTI8422 | ANC → MIA | Jun 12, 09:00 UTC | Jun 12, 16:25 UTC | 7h 25m |
| 2026-06-11 | GTI8422 | ANC → MIA | Jun 11, 18:15 UTC | Jun 12, 06:45 UTC | 12h 31m |
| 2026-06-10 | GTI8421 | HHN → PSM | Jun 10, 23:50 UTC | Jun 11, 12:40 UTC | 12h 50m |
| 2026-06-10 | GTI512 | ANC → ORD | Jun 10, 19:05 UTC | Jun 10, 20:40 UTC | 1h 35m |
| 2026-06-10 | GTI512 | ANC → ORD | Jun 10, 17:35 UTC | Jun 10, 17:45 UTC | 10m |
| 2026-06-10 | GTI512 | ANC → ORD | Jun 10, 07:30 UTC | Jun 10, 13:15 UTC | 5h 45m |
| 2026-06-09 | GTI512 | ANC → ORD | Jun 9, 08:35 UTC | Jun 10, 04:30 UTC | 19h 55m |
| 2026-06-09 | GTI517 | ANC → ICN | Jun 9, 07:05 UTC | Jun 10, 04:30 UTC | 21h 25m |
| 2026-06-09 | GTI517 | ANC → ICN | Jun 9, 04:35 UTC | Jun 10, 04:30 UTC | 23h 55m |
| 2026-06-09 | GTI517 | ANC → ICN | Jun 9, 03:00 UTC | Jun 9, 23:00 UTC | 20h 0m |
| 2026-06-08 | GTI518 | ANC → ORD | Jun 8, 11:45 UTC | Jun 8, 17:20 UTC | 5h 35m |
| 2026-06-07 | GTI518 | ANC → ORD | Jun 7, 14:45 UTC | Jun 8, 10:00 UTC | 19h 15m |
| 2026-06-07 | GTI517 | ANC → ICN | Jun 7, 08:35 UTC | Jun 8, 08:30 UTC | 23h 55m |
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 N450PA page for operator, model, and routing details .