sensors Mode-S transponder
A1F3AA
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N225AX · BOEING 767-200 · operated by CARGO AIRCRAFT MANAGEMENT INC
- Hex
- A1F3AA
- Octal
- 50371652
- Decimal
- 10,613,674
- Country
- US
- Tail
- N225AX
- Type
- B762
- Flights observed
- 49
- Distinct callsigns
- 13
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A1F3AA 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OAE2149 | Omni Air International | 7 | 2026-05-21 |
| OAE2147 | Omni Air International | 7 | 2026-05-13 |
| OAE2106 | Omni Air International | 7 | 2026-05-01 |
| CMB572 | - | 4 | 2026-05-29 |
| CMB377 | - | 4 | 2026-04-22 |
| OAE4019 | Omni Air International | 3 | 2026-04-26 |
| OAE2235 | Omni Air International | 3 | 2026-06-10 |
| OAE2166 | Omni Air International | 3 | 2026-05-08 |
| OAE2128 | Omni Air International | 3 | 2026-05-05 |
| CMB532 | - | 3 | 2026-05-07 |
| OAE2221 | Omni Air International | 2 | 2026-05-27 |
| OAE2176 | Omni Air International | 2 | 2026-05-09 |
| OAE377 | - | 1 | 2026-04-23 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | OAE2235 | AFW → RDU | Jun 10, 12:40 UTC | Jun 10, 15:30 UTC | 2h 50m |
| 2026-06-10 | OAE2235 | AFW → RDU | Jun 10, 01:40 UTC | Jun 10, 10:05 UTC | 8h 25m |
| 2026-06-09 | OAE2235 | AFW → RDU | Jun 9, 19:30 UTC | Jun 9, 21:00 UTC | 1h 30m |
| 2026-05-29 | CMB572 | - | May 29, 23:55 UTC | May 30, 04:05 UTC | 4h 10m |
| 2026-05-29 | CMB572 | - | May 29, 16:40 UTC | May 29, 23:50 UTC | 7h 10m |
| 2026-05-28 | CMB572 | - | May 28, 16:20 UTC | May 29, 02:10 UTC | 9h 50m |
| 2026-05-27 | CMB572 | - | May 27, 23:20 UTC | May 28, 02:05 UTC | 2h 45m |
| 2026-05-27 | OAE2221 | AFW → GPT | May 27, 16:25 UTC | May 27, 20:30 UTC | 4h 5m |
| 2026-05-27 | OAE2221 | AFW → GPT | May 27, 12:10 UTC | May 27, 13:25 UTC | 1h 15m |
| 2026-05-21 | OAE2149 | AFW → HRL | May 21, 22:50 UTC | May 22, 00:10 UTC | 1h 20m |
| 2026-05-21 | OAE2149 | AFW → HRL | May 21, 09:50 UTC | May 21, 20:30 UTC | 10h 40m |
| 2026-05-20 | OAE2149 | AFW → HRL | May 20, 08:45 UTC | May 20, 12:55 UTC | 4h 10m |
| 2026-05-20 | OAE2149 | AFW → HRL | May 20, 00:15 UTC | May 20, 06:15 UTC | 6h 1m |
| 2026-05-19 | OAE2149 | AFW → HRL | May 19, 20:40 UTC | May 19, 20:50 UTC | 10m |
| 2026-05-19 | OAE2149 | AFW → HRL | May 19, 17:00 UTC | May 19, 19:10 UTC | 2h 10m |
| 2026-05-19 | OAE2149 | AFW → HRL | May 19, 13:00 UTC | May 19, 14:05 UTC | 1h 5m |
| 2026-05-13 | OAE2147 | AFW → ANC | May 13, 11:05 UTC | May 13, 22:25 UTC | 11h 20m |
| 2026-05-13 | OAE2147 | AFW → ANC | May 13, 03:25 UTC | May 13, 05:35 UTC | 2h 10m |
| 2026-05-12 | OAE2147 | AFW → ANC | May 12, 09:45 UTC | May 12, 12:05 UTC | 2h 20m |
| 2026-05-12 | OAE2147 | AFW → ANC | May 12, 04:15 UTC | May 12, 06:20 UTC | 2h 5m |
| 2026-05-11 | OAE2147 | AFW → ANC | May 11, 09:15 UTC | May 11, 09:45 UTC | 30m |
| 2026-05-11 | OAE2147 | AFW → ANC | May 11, 00:30 UTC | May 11, 08:30 UTC | 8h 0m |
| 2026-05-10 | OAE2147 | AFW → ANC | May 10, 15:29 UTC | May 10, 22:05 UTC | 6h 35m |
| 2026-05-09 | OAE2176 | SJU → DSM | May 9, 22:39 UTC | May 10, 00:09 UTC | 1h 30m |
| 2026-05-09 | OAE2176 | SJU → DSM | May 9, 15:00 UTC | May 9, 20:05 UTC | 5h 5m |
| 2026-05-08 | OAE2166 | AFW → TCM | May 8, 21:35 UTC | May 9, 02:45 UTC | 5h 10m |
| 2026-05-08 | OAE2166 | AFW → TCM | May 8, 14:45 UTC | May 8, 19:05 UTC | 4h 20m |
| 2026-05-08 | OAE2166 | AFW → TCM | May 8, 08:34 UTC | May 8, 10:09 UTC | 1h 35m |
| 2026-05-07 | CMB532 | GDN → AFW | May 7, 18:50 UTC | May 8, 05:54 UTC | 11h 4m |
| 2026-05-06 | CMB532 | - | May 6, 16:20 UTC | May 7, 01:25 UTC | 9h 5m |
| 2026-05-05 | CMB532 | - | May 5, 23:15 UTC | May 6, 02:25 UTC | 3h 10m |
| 2026-05-05 | OAE2128 | AFW → STT | May 5, 18:25 UTC | May 5, 20:45 UTC | 2h 20m |
| 2026-05-05 | OAE2128 | AFW → STT | May 5, 14:05 UTC | May 5, 16:40 UTC | 2h 35m |
| 2026-05-05 | OAE2128 | AFW → STT | May 5, 07:10 UTC | May 5, 11:00 UTC | 3h 50m |
| 2026-05-01 | OAE2106 | MIA → AEX | May 1, 05:35 UTC | May 1, 06:25 UTC | 50m |
| 2026-04-30 | OAE2106 | MIA → AEX | Apr 30, 16:35 UTC | May 1, 03:40 UTC | 11h 5m |
| 2026-04-29 | OAE2106 | MIA → AEX | Apr 29, 19:20 UTC | Apr 29, 23:40 UTC | 4h 19m |
| 2026-04-29 | OAE2106 | MIA → AEX | Apr 29, 16:55 UTC | Apr 29, 17:20 UTC | 25m |
| 2026-04-29 | OAE2106 | MIA → AEX | Apr 29, 03:49 UTC | Apr 29, 04:25 UTC | 35m |
| 2026-04-28 | OAE2106 | MIA → AEX | Apr 28, 14:25 UTC | Apr 28, 23:05 UTC | 8h 40m |
| 2026-04-27 | OAE2106 | MIA → AEX | Apr 27, 01:45 UTC | Apr 27, 03:45 UTC | 2h 0m |
| 2026-04-26 | OAE4019 | AFW → BEL | Apr 26, 18:35 UTC | Apr 26, 22:35 UTC | 4h 0m |
| 2026-04-25 | OAE4019 | AFW → BEL | Apr 25, 20:35 UTC | Apr 26, 20:05 UTC | 23h 30m |
| 2026-04-25 | OAE4019 | AFW → BEL | Apr 25, 15:20 UTC | Apr 25, 20:45 UTC | 5h 25m |
| 2026-04-23 | OAE377 | - | Apr 23, 04:30 UTC | Apr 23, 05:15 UTC | 45m |
| 2026-04-22 | CMB377 | - | Apr 22, 14:00 UTC | Apr 23, 01:50 UTC | 11h 50m |
| 2026-04-22 | CMB377 | - | Apr 22, 03:35 UTC | Apr 22, 06:45 UTC | 3h 10m |
| 2026-04-20 | CMB377 | - | Apr 20, 15:05 UTC | Apr 21, 02:25 UTC | 11h 20m |
| 2026-04-20 | CMB377 | AFW → MCF | Apr 20, 09:00 UTC | Apr 20, 10:55 UTC | 1h 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 N225AX page for operator, model, and routing details .