sensors Mode-S transponder
A5ED66
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N481MC · BOEING 747-400 · operated by ATLAS AIR INC
- Hex
- A5ED66
- Octal
- 51366546
- Decimal
- 10,874,214
- Country
- US
- Tail
- N481MC
- Type
- B744
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address A5ED66 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 |
|---|---|---|---|
| GTI8842 | - | 6 | 2026-04-16 |
| CMB502 | - | 5 | 2026-05-13 |
| GTI8184 | Atlas Air | 3 | 2026-05-05 |
| CMB504 | - | 3 | 2026-05-15 |
| GTI8841 | - | 2 | 2026-04-14 |
| GTI8828 | Atlas Air | 2 | 2026-04-13 |
| CMB574 | - | 2 | 2026-05-06 |
| CMB548 | - | 2 | 2026-05-20 |
| GTI9902 | Atlas Air | 1 | 2026-05-01 |
| GTI9891 | Atlas Air | 1 | 2026-04-21 |
| GTI9889 | Atlas Air | 1 | 2026-04-27 |
| GTI9851 | Atlas Air | 1 | 2026-05-07 |
| GTI9591 | Atlas Air | 1 | 2026-05-20 |
| GTI8827 | - | 1 | 2026-04-13 |
| GTI8330 | Atlas Air | 1 | 2026-04-30 |
| GTI8309 | Atlas Air | 1 | 2026-04-21 |
| GTI8302 | Atlas Air | 1 | 2026-04-26 |
| GTI8202 | Atlas Air | 1 | 2026-04-19 |
| CMB592 | - | 1 | 2026-04-19 |
| CMB534 | - | 1 | 2026-04-20 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-20 | GTI9591 | WRI → ANC | May 20, 21:35 UTC | May 20, 23:20 UTC | 1h 45m |
| 2026-05-20 | CMB548 | - | May 20, 07:20 UTC | May 20, 18:15 UTC | 10h 55m |
| 2026-05-18 | CMB548 | - | May 18, 21:35 UTC | May 19, 06:00 UTC | 8h 25m |
| 2026-05-15 | CMB504 | - | May 15, 14:30 UTC | May 15, 23:10 UTC | 8h 39m |
| 2026-05-14 | CMB504 | - | May 14, 16:30 UTC | May 14, 18:50 UTC | 2h 20m |
| 2026-05-13 | CMB504 | - | May 13, 19:35 UTC | May 14, 18:50 UTC | 23h 15m |
| 2026-05-13 | CMB502 | - | May 13, 17:35 UTC | May 14, 17:30 UTC | 23h 55m |
| 2026-05-13 | CMB502 | - | May 13, 16:55 UTC | May 13, 19:45 UTC | 2h 50m |
| 2026-05-13 | CMB502 | - | May 13, 10:50 UTC | May 13, 13:20 UTC | 2h 30m |
| 2026-05-12 | CMB502 | - | May 12, 12:05 UTC | May 13, 11:30 UTC | 23h 25m |
| 2026-05-12 | CMB502 | - | May 12, 05:40 UTC | May 12, 12:10 UTC | 6h 30m |
| 2026-05-07 | GTI9851 | KUN → CVG | May 7, 07:45 UTC | May 7, 16:55 UTC | 9h 10m |
| 2026-05-06 | CMB574 | POZ → KUN | May 6, 13:45 UTC | May 6, 14:40 UTC | 55m |
| 2026-05-06 | CMB574 | - | May 6, 10:15 UTC | May 6, 11:15 UTC | 1h 0m |
| 2026-05-05 | GTI8184 | VAD → SOF | May 5, 22:55 UTC | May 6, 04:25 UTC | 5h 30m |
| 2026-05-05 | GTI8184 | VAD → SOF | May 5, 19:30 UTC | May 5, 22:50 UTC | 3h 20m |
| 2026-05-05 | GTI8184 | VAD → SOF | May 5, 12:25 UTC | May 5, 14:35 UTC | 2h 10m |
| 2026-05-01 | GTI9902 | ROZ → BWI | May 1, 10:05 UTC | May 1, 18:35 UTC | 8h 30m |
| 2026-04-30 | CMB518 | - | Apr 30, 22:40 UTC | May 1, 05:35 UTC | 6h 55m |
| 2026-04-30 | GTI8330 | LIM → JFK | Apr 30, 16:00 UTC | Apr 30, 17:10 UTC | 1h 10m |
| 2026-04-27 | GTI9889 | ORD → ICN | Apr 27, 10:25 UTC | Apr 27, 18:40 UTC | 8h 15m |
| 2026-04-26 | CMB508 | - | Apr 26, 08:10 UTC | Apr 26, 15:40 UTC | 7h 30m |
| 2026-04-26 | GTI8302 | PTY → MIA | Apr 26, 01:55 UTC | Apr 26, 02:55 UTC | 1h 0m |
| 2026-04-21 | GTI9891 | GRK → CVG | Apr 21, 08:15 UTC | Apr 21, 10:05 UTC | 1h 50m |
| 2026-04-21 | GTI8309 | LGG → IAH | Apr 21, 04:45 UTC | Apr 21, 05:45 UTC | 1h 0m |
| 2026-04-20 | CMB534 | - | Apr 20, 15:05 UTC | Apr 21, 01:35 UTC | 10h 30m |
| 2026-04-19 | CMB592 | - | Apr 19, 12:45 UTC | Apr 19, 20:35 UTC | 7h 50m |
| 2026-04-19 | GTI8202 | FFD → KUN | Apr 19, 05:05 UTC | Apr 19, 06:05 UTC | 1h 0m |
| 2026-04-16 | GTI8842 | - | Apr 16, 19:15 UTC | Apr 16, 19:45 UTC | 30m |
| 2026-04-16 | GTI8842 | - | Apr 16, 17:15 UTC | Apr 16, 19:10 UTC | 1h 55m |
| 2026-04-16 | GTI8842 | - | Apr 16, 15:45 UTC | Apr 16, 17:10 UTC | 1h 25m |
| 2026-04-16 | GTI8842 | - | Apr 16, 12:09 UTC | Apr 16, 12:24 UTC | 15m |
| 2026-04-16 | GTI8842 | - | Apr 16, 07:49 UTC | Apr 16, 08:15 UTC | 25m |
| 2026-04-15 | GTI8842 | - | Apr 15, 23:15 UTC | Apr 15, 23:45 UTC | 30m |
| 2026-04-14 | GTI8841 | - | Apr 14, 23:10 UTC | Apr 14, 23:50 UTC | 40m |
| 2026-04-14 | GTI8841 | - | Apr 14, 13:50 UTC | Apr 14, 14:10 UTC | 20m |
| 2026-04-13 | GTI8828 | ORD → DOV | Apr 13, 16:50 UTC | Apr 13, 17:15 UTC | 25m |
| 2026-04-13 | GTI8828 | ORD → DOV | Apr 13, 07:50 UTC | Apr 13, 08:15 UTC | 25m |
| 2026-04-13 | GTI8827 | - | Apr 13, 01:35 UTC | Apr 13, 02:10 UTC | 35m |
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 N481MC page for operator, model, and routing details .