sensors Mode-S transponder
A4C02D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N405KZ · BOEING 747-400 · operated by WILMINGTON TRUST CO TRUSTEE
- Hex
- A4C02D
- Octal
- 51140055
- Decimal
- 10,797,101
- Country
- US
- Tail
- N405KZ
- Type
- B744
- Flights observed
- 195
- Distinct callsigns
- 18
- Country
- US
- Last broadcast
- 11m ago
Current position
Country allocation
The ICAO 24-bit address A4C02D 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GTI8977 | - | 80 | 2026-07-14 |
| GTI8976 | - | 61 | 2026-07-13 |
| GTI8970 | Atlas Air | 11 | 2026-05-09 |
| GTI8998 | Atlas Air | 6 | 2026-06-07 |
| GTI8603 | - | 6 | 2026-06-28 |
| GTI8193 | - | 6 | 2026-04-14 |
| GTI8997 | Atlas Air | 4 | 2026-06-06 |
| GTI8969 | Atlas Air | 4 | 2026-05-08 |
| GTI079 | Atlas Air | 3 | 2026-05-31 |
| GTI8602 | - | 2 | 2026-06-27 |
| GTI812 | Atlas Air | 2 | 2026-04-25 |
| GTI080 | Atlas Air | 2 | 2026-05-31 |
| GTI062 | Atlas Air | 2 | 2026-06-14 |
| GTI061 | Atlas Air | 2 | 2026-06-13 |
| GTI9844 | - | 1 | 2026-04-14 |
| GTI928 | - | 1 | 2026-06-14 |
| GTI9050 | - | 1 | 2026-06-20 |
| GTI8192 | Atlas Air | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | GTI8977 | - | Jul 14, 10:45 UTC | Jul 14, 11:15 UTC | 30m |
| 2026-07-13 | GTI8977 | - | Jul 13, 15:05 UTC | Jul 14, 08:05 UTC | 17h 0m |
| 2026-07-13 | GTI8977 | - | Jul 13, 09:20 UTC | Jul 14, 08:05 UTC | 22h 45m |
| 2026-07-13 | GTI8976 | - | Jul 13, 08:45 UTC | Jul 14, 07:15 UTC | 22h 30m |
| 2026-07-12 | GTI8976 | JFK → ANC | Jul 12, 23:50 UTC | Jul 13, 06:50 UTC | 7h 0m |
| 2026-07-11 | GTI8977 | ANC → JFK | Jul 11, 11:15 UTC | Jul 11, 17:25 UTC | 6h 10m |
| 2026-07-10 | GTI8977 | - | Jul 10, 16:35 UTC | Jul 11, 09:05 UTC | 16h 31m |
| 2026-07-10 | GTI8977 | ANC → ANC | Jul 10, 09:25 UTC | Jul 11, 09:05 UTC | 23h 40m |
| 2026-07-09 | GTI8976 | JFK → ANC | Jul 9, 23:00 UTC | Jul 10, 05:55 UTC | 6h 55m |
| 2026-07-09 | GTI8977 | ANC → JFK | Jul 9, 10:45 UTC | Jul 9, 17:35 UTC | 6h 50m |
| 2026-07-08 | GTI8977 | - | Jul 8, 13:55 UTC | Jul 9, 07:55 UTC | 18h 0m |
| 2026-07-08 | GTI8977 | - | Jul 8, 09:30 UTC | Jul 9, 07:55 UTC | 22h 25m |
| 2026-07-08 | GTI8976 | - | Jul 8, 08:10 UTC | Jul 9, 07:15 UTC | 23h 5m |
| 2026-07-07 | GTI8976 | JFK → ANC | Jul 7, 23:20 UTC | Jul 8, 06:00 UTC | 6h 40m |
| 2026-07-07 | GTI8977 | ANC → JFK | Jul 7, 13:20 UTC | Jul 7, 19:30 UTC | 6h 10m |
| 2026-07-06 | GTI8977 | - | Jul 6, 15:20 UTC | Jul 7, 11:10 UTC | 19h 50m |
| 2026-07-06 | GTI8977 | - | Jul 6, 14:55 UTC | Jul 7, 11:10 UTC | 20h 15m |
| 2026-07-06 | GTI8976 | - | Jul 6, 09:30 UTC | Jul 7, 05:15 UTC | 19h 45m |
| 2026-07-06 | GTI8976 | - | Jul 6, 08:25 UTC | Jul 7, 05:15 UTC | 20h 50m |
| 2026-07-06 | GTI8976 | JFK → ANC | Jul 6, 00:10 UTC | Jul 6, 06:55 UTC | 6h 45m |
| 2026-07-04 | GTI8977 | ANC → JFK | Jul 4, 10:40 UTC | Jul 4, 17:25 UTC | 6h 45m |
| 2026-07-03 | GTI8977 | - | Jul 3, 15:25 UTC | Jul 4, 07:50 UTC | 16h 25m |
| 2026-07-03 | GTI8977 | - | Jul 3, 09:20 UTC | Jul 4, 07:50 UTC | 22h 30m |
| 2026-07-03 | GTI8976 | - | Jul 3, 08:10 UTC | Jul 4, 07:15 UTC | 23h 5m |
| 2026-07-02 | GTI8976 | JFK → ANC | Jul 2, 22:55 UTC | Jul 3, 05:35 UTC | 6h 40m |
| 2026-07-02 | GTI8977 | ANC → JFK | Jul 2, 10:05 UTC | Jul 2, 16:35 UTC | 6h 30m |
| 2026-07-01 | GTI8977 | - | Jul 1, 14:05 UTC | Jul 2, 07:50 UTC | 17h 45m |
| 2026-07-01 | GTI8977 | - | Jul 1, 09:25 UTC | Jul 2, 07:50 UTC | 22h 25m |
| 2026-07-01 | GTI8976 | - | Jul 1, 08:10 UTC | Jul 2, 07:15 UTC | 23h 5m |
| 2026-06-30 | GTI8976 | - | Jun 30, 23:45 UTC | Jul 1, 06:40 UTC | 6h 55m |
| 2026-06-30 | GTI8977 | ANC → JFK | Jun 30, 13:30 UTC | Jun 30, 20:05 UTC | 6h 35m |
| 2026-06-29 | GTI8977 | - | Jun 29, 13:59 UTC | Jun 30, 08:55 UTC | 18h 55m |
| 2026-06-29 | GTI8977 | - | Jun 29, 09:20 UTC | Jun 30, 08:55 UTC | 23h 35m |
| 2026-06-29 | GTI8976 | - | Jun 29, 07:55 UTC | Jun 30, 03:10 UTC | 19h 16m |
| 2026-06-28 | GTI8976 | - | Jun 28, 22:55 UTC | Jun 29, 05:50 UTC | 6h 55m |
| 2026-06-28 | GTI8603 | - | Jun 28, 11:04 UTC | Jun 28, 17:19 UTC | 6h 15m |
| 2026-06-27 | GTI8603 | - | Jun 27, 13:20 UTC | Jun 28, 09:05 UTC | 19h 45m |
| 2026-06-27 | GTI8603 | - | Jun 27, 12:45 UTC | Jun 28, 09:05 UTC | 20h 20m |
| 2026-06-27 | GTI8602 | JFK → ANC | Jun 27, 02:35 UTC | Jun 27, 09:15 UTC | 6h 40m |
| 2026-06-25 | GTI8977 | ANC → JFK | Jun 25, 23:44 UTC | Jun 26, 06:04 UTC | 6h 20m |
| 2026-06-25 | GTI8977 | - | Jun 25, 13:24 UTC | Jun 25, 20:59 UTC | 7h 35m |
| 2026-06-24 | GTI8977 | - | Jun 24, 17:20 UTC | Jun 25, 14:55 UTC | 21h 35m |
| 2026-06-24 | GTI8976 | - | Jun 24, 15:24 UTC | Jun 25, 14:55 UTC | 23h 30m |
| 2026-06-24 | GTI8976 | - | Jun 24, 09:00 UTC | Jun 24, 17:29 UTC | 8h 30m |
| 2026-06-24 | GTI8976 | JFK → ANC | Jun 24, 00:20 UTC | Jun 24, 07:05 UTC | 6h 45m |
| 2026-06-23 | GTI8977 | - | Jun 23, 12:40 UTC | Jun 23, 19:10 UTC | 6h 30m |
| 2026-06-22 | GTI8977 | - | Jun 22, 17:25 UTC | Jun 23, 09:40 UTC | 16h 15m |
| 2026-06-22 | GTI8977 | - | Jun 22, 11:19 UTC | Jun 23, 09:40 UTC | 22h 20m |
| 2026-06-22 | GTI8976 | JFK → ANC | Jun 22, 01:55 UTC | Jun 22, 08:35 UTC | 6h 40m |
| 2026-06-21 | GTI8603 | ANC → JFK | Jun 21, 15:09 UTC | Jun 21, 21:14 UTC | 6h 5m |
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 N405KZ page for operator, model, and routing details .