sensors Mode-S transponder
A1AC1A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N207AX · BOEING 767-200 · operated by CARGO AIRCRAFT MANAGEMENT INC
- Hex
- A1AC1A
- Octal
- 50326032
- Decimal
- 10,595,354
- Country
- US
- Tail
- N207AX
- Type
- B762
- Flights observed
- 92
- Distinct callsigns
- 19
- Country
- US
- Last broadcast
- 19d ago
Last known position
Country allocation
The ICAO 24-bit address A1AC1A 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CMB538 | - | 11 | 2026-04-15 |
| OAE2062 | Omni Air International | 8 | 2026-05-09 |
| OAE2272 | - | 7 | 2026-06-14 |
| OAE2267 | Omni Air International | 7 | 2026-07-20 |
| OAE2066 | Omni Air International | 7 | 2026-04-18 |
| OAE2148 | Omni Air International | 6 | 2026-06-10 |
| OAE2264 | - | 5 | 2026-06-20 |
| OAE2214 | Omni Air International | 5 | 2026-06-02 |
| OAE2113 | Omni Air International | 5 | 2026-04-21 |
| CMB578 | - | 5 | 2026-04-25 |
| OAE2326 | - | 4 | 2026-07-03 |
| OAE2177 | Omni Air International | 4 | 2026-05-23 |
| OAE2241 | Omni Air International | 3 | 2026-06-03 |
| OAE2196 | - | 3 | 2026-06-22 |
| OAE2160 | - | 3 | 2026-06-26 |
| OAE2129 | Omni Air International | 3 | 2026-05-20 |
| OAE2077 | - | 3 | 2026-07-06 |
| OAE2276 | Omni Air International | 2 | 2026-07-26 |
| OAE2026 | Omni Air International | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | OAE2276 | BWI → ADW | Jul 26, 16:00 UTC | Jul 26, 21:00 UTC | 5h 0m |
| 2026-07-26 | OAE2276 | BWI → ADW | Jul 26, 12:40 UTC | Jul 26, 12:50 UTC | 10m |
| 2026-07-20 | OAE2267 | BWI → PDX | Jul 20, 06:05 UTC | Jul 20, 12:45 UTC | 6h 40m |
| 2026-07-19 | OAE2267 | BWI → PDX | Jul 19, 18:05 UTC | Jul 20, 03:45 UTC | 9h 40m |
| 2026-07-18 | OAE2267 | BWI → PDX | Jul 18, 16:40 UTC | Jul 18, 18:50 UTC | 2h 10m |
| 2026-07-18 | OAE2267 | BWI → PDX | Jul 18, 07:55 UTC | Jul 18, 13:30 UTC | 5h 35m |
| 2026-07-18 | OAE2267 | BWI → PDX | Jul 18, 06:50 UTC | Jul 18, 07:00 UTC | 10m |
| 2026-07-17 | OAE2267 | BWI → PDX | Jul 17, 15:20 UTC | Jul 18, 03:00 UTC | 11h 41m |
| 2026-07-17 | OAE2267 | BWI → PDX | Jul 17, 07:14 UTC | Jul 17, 12:15 UTC | 5h 0m |
| 2026-07-06 | OAE2077 | - | Jul 6, 07:35 UTC | Jul 6, 08:25 UTC | 50m |
| 2026-07-05 | OAE2077 | - | Jul 5, 03:30 UTC | Jul 5, 03:50 UTC | 20m |
| 2026-07-04 | OAE2077 | - | Jul 4, 21:25 UTC | Jul 4, 23:50 UTC | 2h 25m |
| 2026-07-03 | OAE2326 | - | Jul 3, 03:20 UTC | Jul 3, 06:50 UTC | 3h 30m |
| 2026-07-02 | OAE2326 | - | Jul 2, 15:15 UTC | Jul 3, 00:35 UTC | 9h 20m |
| 2026-07-02 | OAE2326 | - | Jul 2, 11:20 UTC | Jul 2, 12:10 UTC | 50m |
| 2026-07-02 | OAE2326 | - | Jul 2, 09:20 UTC | Jul 2, 09:45 UTC | 25m |
| 2026-06-26 | OAE2160 | - | Jun 26, 13:15 UTC | Jun 26, 20:24 UTC | 7h 10m |
| 2026-06-25 | OAE2160 | - | Jun 25, 14:39 UTC | Jun 25, 22:14 UTC | 7h 35m |
| 2026-06-25 | OAE2160 | - | Jun 25, 08:04 UTC | Jun 25, 10:25 UTC | 2h 20m |
| 2026-06-22 | OAE2196 | - | Jun 22, 08:44 UTC | Jun 22, 11:09 UTC | 2h 25m |
| 2026-06-22 | OAE2196 | - | Jun 22, 06:00 UTC | Jun 22, 07:00 UTC | 1h 0m |
| 2026-06-21 | OAE2196 | - | Jun 21, 23:24 UTC | Jun 22, 02:50 UTC | 3h 25m |
| 2026-06-20 | OAE2264 | - | Jun 20, 01:39 UTC | Jun 20, 02:29 UTC | 50m |
| 2026-06-19 | OAE2264 | - | Jun 19, 13:09 UTC | Jun 19, 22:49 UTC | 9h 40m |
| 2026-06-18 | OAE2264 | - | Jun 18, 08:00 UTC | Jun 18, 21:00 UTC | 13h 0m |
| 2026-06-17 | OAE2264 | - | Jun 17, 20:10 UTC | Jun 18, 05:20 UTC | 9h 10m |
| 2026-06-16 | OAE2264 | - | Jun 16, 17:30 UTC | Jun 16, 20:00 UTC | 2h 31m |
| 2026-06-14 | OAE2272 | - | Jun 14, 08:00 UTC | Jun 14, 10:05 UTC | 2h 5m |
| 2026-06-13 | OAE2272 | - | Jun 13, 20:00 UTC | Jun 14, 05:55 UTC | 9h 55m |
| 2026-06-12 | OAE2272 | - | Jun 12, 10:35 UTC | Jun 13, 04:55 UTC | 18h 19m |
| 2026-06-12 | OAE2272 | - | Jun 12, 09:50 UTC | Jun 13, 04:55 UTC | 19h 4m |
| 2026-06-12 | OAE2272 | - | Jun 12, 02:35 UTC | Jun 13, 00:55 UTC | 22h 20m |
| 2026-06-12 | OAE2272 | - | Jun 12, 01:05 UTC | Jun 13, 00:30 UTC | 23h 25m |
| 2026-06-11 | OAE2272 | - | Jun 11, 19:15 UTC | Jun 11, 20:00 UTC | 45m |
| 2026-06-10 | OAE2148 | BWI → ANC | Jun 10, 20:35 UTC | Jun 11, 02:10 UTC | 5h 35m |
| 2026-06-10 | OAE2148 | BWI → ANC | Jun 10, 03:15 UTC | Jun 10, 15:35 UTC | 12h 20m |
| 2026-06-09 | OAE2148 | BWI → ANC | Jun 9, 03:20 UTC | Jun 9, 10:05 UTC | 6h 45m |
| 2026-06-08 | OAE2148 | BWI → ANC | Jun 8, 07:30 UTC | Jun 8, 08:10 UTC | 40m |
| 2026-06-08 | OAE2148 | BWI → ANC | Jun 8, 00:50 UTC | Jun 8, 02:10 UTC | 1h 20m |
| 2026-06-07 | OAE2148 | BWI → ANC | Jun 7, 14:35 UTC | Jun 7, 21:50 UTC | 7h 15m |
| 2026-06-03 | OAE2241 | BWI → WRI | Jun 3, 19:45 UTC | Jun 3, 22:00 UTC | 2h 15m |
| 2026-06-03 | OAE2241 | BWI → WRI | Jun 3, 15:30 UTC | Jun 3, 17:50 UTC | 2h 20m |
| 2026-06-03 | OAE2241 | BWI → WRI | Jun 3, 10:20 UTC | Jun 3, 11:00 UTC | 40m |
| 2026-06-02 | OAE2214 | BWI → SID | Jun 2, 12:45 UTC | Jun 2, 16:40 UTC | 3h 55m |
| 2026-06-02 | OAE2214 | BWI → SID | Jun 2, 07:10 UTC | Jun 2, 10:10 UTC | 3h 0m |
| 2026-06-01 | OAE2214 | BWI → SID | Jun 1, 13:10 UTC | Jun 1, 22:15 UTC | 9h 5m |
| 2026-05-30 | OAE2214 | BWI → SID | May 30, 09:50 UTC | May 30, 17:50 UTC | 8h 0m |
| 2026-05-29 | OAE2214 | BWI → SID | May 29, 13:05 UTC | May 29, 13:45 UTC | 40m |
| 2026-05-23 | OAE2177 | BWI → DSM | May 23, 22:50 UTC | May 24, 02:25 UTC | 3h 35m |
| 2026-05-23 | OAE2177 | BWI → DSM | May 23, 20:00 UTC | May 23, 20:20 UTC | 20m |
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 N207AX page for operator, model, and routing details .