sensors Mode-S transponder
A486BE
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N391CM · BOEING 767-300 · operated by CARGO AIRCRAFT MANAGEMENT INC
- Hex
- A486BE
- Octal
- 51103276
- Decimal
- 10,782,398
- Country
- US
- Tail
- N391CM
- Type
- B763
- Flights observed
- 94
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 29m ago
Current position
Country allocation
The ICAO 24-bit address A486BE 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 |
|---|---|---|---|
| ABX901 | ABX Air | 11 | 2026-05-13 |
| ABX880 | ABX Air | 9 | 2026-04-23 |
| ABX902 | ABX Air | 7 | 2026-05-13 |
| ABX403 | - | 7 | 2026-07-11 |
| ABX110 | - | 7 | 2026-07-07 |
| ABX552 | - | 6 | 2026-07-11 |
| ABX510 | - | 6 | 2026-07-06 |
| ABX803 | - | 3 | 2026-07-10 |
| ABX105 | - | 3 | 2026-07-14 |
| ABX814 | ABX Air | 2 | 2026-04-22 |
| ABX797 | - | 2 | 2026-07-09 |
| ABX505 | - | 2 | 2026-07-13 |
| ABX414 | ABX Air | 2 | 2026-04-23 |
| ABX397 | - | 2 | 2026-07-10 |
| ABX1845 | ABX Air | 2 | 2026-04-26 |
| ABX102 | ABX Air | 2 | 2026-05-09 |
| ABX036 | ABX Air | 2 | 2026-07-03 |
| ABX841 | ABX Air | 1 | 2026-04-20 |
| ABX805 | ABX Air | 1 | 2026-04-24 |
| ABX585 | ABX Air | 1 | 2026-05-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ABX105 | - | Jul 14, 06:50 UTC | Jul 14, 09:30 UTC | 2h 40m |
| 2026-07-14 | ABX105 | - | Jul 14, 04:50 UTC | Jul 14, 05:15 UTC | 25m |
| 2026-07-14 | ABX105 | - | Jul 14, 00:40 UTC | Jul 14, 02:20 UTC | 1h 40m |
| 2026-07-13 | ABX505 | - | Jul 13, 10:15 UTC | Jul 13, 11:10 UTC | 55m |
| 2026-07-13 | ABX505 | - | Jul 13, 04:55 UTC | Jul 13, 08:01 UTC | 3h 5m |
| 2026-07-12 | ABX322 | - | Jul 12, 14:50 UTC | Jul 12, 16:40 UTC | 1h 50m |
| 2026-07-12 | ABX321 | - | Jul 12, 10:25 UTC | Jul 12, 12:15 UTC | 1h 50m |
| 2026-07-11 | ABX1152 | JFK → CVG | Jul 11, 16:30 UTC | Jul 11, 18:05 UTC | 1h 35m |
| 2026-07-11 | ABX552 | - | Jul 11, 12:30 UTC | Jul 11, 13:50 UTC | 1h 20m |
| 2026-07-11 | ABX403 | - | Jul 11, 03:30 UTC | Jul 11, 07:05 UTC | 3h 35m |
| 2026-07-10 | ABX803 | - | Jul 10, 10:45 UTC | Jul 10, 14:45 UTC | 4h 0m |
| 2026-07-10 | ABX397 | - | Jul 10, 04:50 UTC | Jul 10, 05:30 UTC | 40m |
| 2026-07-09 | ABX797 | CVG → ORD | Jul 9, 12:00 UTC | Jul 9, 12:50 UTC | 50m |
| 2026-07-09 | ABX397 | ORD → CVG | Jul 9, 04:50 UTC | Jul 9, 05:40 UTC | 50m |
| 2026-07-08 | ABX797 | CVG → ORD | Jul 8, 11:30 UTC | Jul 8, 12:20 UTC | 50m |
| 2026-07-07 | ABX110 | ATL → CVG | Jul 7, 04:50 UTC | Jul 7, 05:45 UTC | 55m |
| 2026-07-06 | ABX510 | - | Jul 6, 04:10 UTC | Jul 6, 05:10 UTC | 1h 0m |
| 2026-07-05 | ABX306 | - | Jul 5, 20:45 UTC | Jul 5, 22:10 UTC | 1h 25m |
| 2026-07-05 | ABX305 | - | Jul 5, 15:00 UTC | Jul 5, 16:30 UTC | 1h 30m |
| 2026-07-03 | ABX036 | CVG → TPA | Jul 3, 23:35 UTC | Jul 4, 01:35 UTC | 2h 0m |
| 2026-05-14 | ABX036 | CVG → TPA | May 14, 18:50 UTC | May 14, 20:30 UTC | 1h 40m |
| 2026-05-13 | ABX902 | MIA → CVG | May 13, 13:40 UTC | May 14, 03:30 UTC | 13h 50m |
| 2026-05-13 | ABX901 | MIA → PTY | May 13, 09:25 UTC | May 13, 11:30 UTC | 2h 5m |
| 2026-05-12 | ABX902 | MIA → CVG | May 12, 13:45 UTC | May 13, 04:00 UTC | 14h 15m |
| 2026-05-12 | ABX901 | MIA → PTY | May 12, 09:15 UTC | May 12, 11:15 UTC | 2h 0m |
| 2026-05-11 | ABX901 | MIA → PTY | May 11, 13:05 UTC | May 12, 03:30 UTC | 14h 26m |
| 2026-05-11 | ABX901 | MIA → PTY | May 11, 04:55 UTC | May 11, 07:00 UTC | 2h 5m |
| 2026-05-10 | ABX403 | LAX → CVG | May 10, 09:35 UTC | May 10, 13:14 UTC | 3h 40m |
| 2026-05-09 | ABX803 | CVG → LAX | May 9, 09:50 UTC | May 9, 13:50 UTC | 4h 0m |
| 2026-05-09 | ABX102 | DFW → CVG | May 9, 03:40 UTC | May 9, 05:25 UTC | 1h 45m |
| 2026-05-08 | ABX502 | CVG → DFW | May 8, 11:30 UTC | May 8, 13:40 UTC | 2h 10m |
| 2026-05-08 | ABX185 | MSP → CVG | May 8, 02:29 UTC | May 8, 03:49 UTC | 1h 20m |
| 2026-05-07 | ABX585 | CVG → MSP | May 7, 10:30 UTC | May 7, 11:55 UTC | 1h 25m |
| 2026-05-06 | ABX1902 | SJO → CVG | May 6, 13:35 UTC | May 7, 04:00 UTC | 14h 24m |
| 2026-05-06 | ABX901 | MIA → PTY | May 6, 09:15 UTC | May 6, 11:15 UTC | 2h 0m |
| 2026-05-06 | ABX102 | DFW → CVG | May 6, 03:25 UTC | May 6, 05:00 UTC | 1h 35m |
| 2026-05-05 | ABX017 | CVG → LAX | May 5, 22:45 UTC | May 6, 00:55 UTC | 2h 10m |
| 2026-05-04 | ABX902 | MIA → CVG | May 4, 13:30 UTC | May 5, 04:45 UTC | 15h 16m |
| 2026-05-04 | ABX901 | MIA → PTY | May 4, 04:24 UTC | May 4, 06:25 UTC | 2h 0m |
| 2026-05-03 | ABX403 | LAX → CVG | May 3, 09:45 UTC | May 3, 13:25 UTC | 3h 40m |
| 2026-05-02 | ABX803 | CVG → LAX | May 2, 09:50 UTC | May 2, 13:50 UTC | 4h 0m |
| 2026-05-02 | ABX152 | JFK → CVG | May 2, 03:40 UTC | May 2, 05:20 UTC | 1h 40m |
| 2026-05-01 | ABX552 | CVG → JFK | May 1, 10:00 UTC | May 1, 11:25 UTC | 1h 25m |
| 2026-04-30 | ABX902 | MIA → CVG | Apr 30, 13:55 UTC | May 1, 04:15 UTC | 14h 20m |
| 2026-04-30 | ABX901 | MIA → PTY | Apr 30, 09:35 UTC | Apr 30, 11:40 UTC | 2h 5m |
| 2026-04-30 | ABX902 | MIA → CVG | Apr 30, 00:15 UTC | Apr 30, 04:15 UTC | 4h 0m |
| 2026-04-29 | ABX901 | MIA → PTY | Apr 29, 14:10 UTC | Apr 29, 15:50 UTC | 1h 40m |
| 2026-04-29 | ABX901 | MIA → PTY | Apr 29, 09:10 UTC | Apr 29, 11:10 UTC | 2h 0m |
| 2026-04-28 | ABX902 | MIA → CVG | Apr 28, 16:00 UTC | Apr 29, 03:49 UTC | 11h 50m |
| 2026-04-28 | ABX901 | MIA → PTY | Apr 28, 10:55 UTC | Apr 28, 13:45 UTC | 2h 50m |
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 N391CM page for operator, model, and routing details .