sensors Mode-S transponder
A41C4C
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N364MS · CESSNA 172R Cutlass RG · operated by SKYHAWK AVIATION LLC
- Hex
- A41C4C
- Octal
- 51016114
- Decimal
- 10,755,148
- Country
- US
- Tail
- N364MS
- Type
- C72R
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 23, 22:15 UTC
Last known position
Country allocation
The ICAO 24-bit address A41C4C 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| N364MS | - | 49 | 2026-07-23 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | N364MS | - | Jul 23, 21:40 UTC | Jul 23, 22:15 UTC | 35m |
| 2026-07-22 | N364MS | - | Jul 22, 14:35 UTC | Jul 22, 15:30 UTC | 55m |
| 2026-07-17 | N364MS | - | Jul 17, 14:15 UTC | Jul 17, 15:20 UTC | 1h 5m |
| 2026-07-16 | N364MS | FET → FET | Jul 16, 15:35 UTC | Jul 16, 16:09 UTC | 35m |
| 2026-07-15 | N364MS | - | Jul 15, 02:40 UTC | Jul 15, 03:40 UTC | 1h 0m |
| 2026-07-14 | N364MS | - | Jul 14, 06:40 UTC | Jul 14, 07:10 UTC | 30m |
| 2026-07-13 | N364MS | - | Jul 13, 21:05 UTC | Jul 13, 21:45 UTC | 40m |
| 2026-07-13 | N364MS | - | Jul 13, 15:20 UTC | Jul 13, 16:45 UTC | 1h 25m |
| 2026-07-10 | N364MS | - | Jul 10, 18:20 UTC | Jul 10, 19:30 UTC | 1h 10m |
| 2026-07-07 | N364MS | FET → FET | Jul 7, 18:15 UTC | Jul 7, 19:25 UTC | 1h 10m |
| 2026-07-02 | N364MS | - | Jul 2, 01:55 UTC | Jul 2, 03:15 UTC | 1h 20m |
| 2026-07-01 | N364MS | - | Jul 1, 12:50 UTC | Jul 1, 13:40 UTC | 50m |
| 2026-06-30 | N364MS | - | Jun 30, 21:45 UTC | Jun 30, 21:55 UTC | 10m |
| 2026-06-25 | N364MS | FET → FET | Jun 25, 16:24 UTC | Jun 25, 17:09 UTC | 45m |
| 2026-06-19 | N364MS | FET → FET | Jun 19, 13:44 UTC | Jun 19, 14:39 UTC | 55m |
| 2026-06-09 | N364MS | - | Jun 9, 14:00 UTC | Jun 9, 15:05 UTC | 1h 5m |
| 2026-06-06 | N364MS | - | Jun 6, 18:50 UTC | Jun 6, 20:14 UTC | 1h 25m |
| 2026-06-06 | N364MS | - | Jun 6, 16:45 UTC | Jun 6, 17:19 UTC | 35m |
| 2026-06-03 | N364MS | - | Jun 3, 20:20 UTC | Jun 3, 21:10 UTC | 50m |
| 2026-06-02 | N364MS | - | Jun 2, 19:05 UTC | Jun 2, 20:40 UTC | 1h 35m |
| 2026-05-31 | N364MS | - | May 31, 20:50 UTC | May 31, 22:35 UTC | 1h 45m |
| 2026-05-28 | N364MS | - | May 28, 13:35 UTC | May 28, 14:15 UTC | 40m |
| 2026-05-25 | N364MS | - | May 25, 15:10 UTC | May 25, 16:40 UTC | 1h 30m |
| 2026-05-22 | N364MS | - | May 22, 01:25 UTC | May 22, 01:55 UTC | 30m |
| 2026-05-21 | N364MS | - | May 21, 23:55 UTC | May 22, 00:50 UTC | 55m |
| 2026-05-20 | N364MS | - | May 20, 14:00 UTC | May 20, 14:30 UTC | 30m |
| 2026-05-19 | N364MS | - | May 19, 19:10 UTC | May 19, 19:35 UTC | 25m |
| 2026-05-17 | N364MS | MIQ → FET | May 17, 17:25 UTC | May 17, 17:40 UTC | 15m |
| 2026-05-17 | N364MS | MIQ → MIQ | May 17, 15:35 UTC | May 17, 16:25 UTC | 50m |
| 2026-05-17 | N364MS | - | May 17, 13:35 UTC | May 17, 13:55 UTC | 20m |
| 2026-05-13 | N364MS | - | May 13, 20:05 UTC | May 13, 20:45 UTC | 40m |
| 2026-05-13 | N364MS | - | May 13, 14:05 UTC | May 13, 14:40 UTC | 35m |
| 2026-05-12 | N364MS | - | May 12, 16:25 UTC | May 12, 17:35 UTC | 1h 10m |
| 2026-05-11 | N364MS | - | May 11, 20:30 UTC | May 11, 21:05 UTC | 35m |
| 2026-05-11 | N364MS | - | May 11, 13:35 UTC | May 11, 14:35 UTC | 1h 0m |
| 2026-05-10 | N364MS | - | May 10, 01:20 UTC | May 10, 02:14 UTC | 55m |
| 2026-05-09 | N364MS | - | May 9, 13:25 UTC | May 9, 14:40 UTC | 1h 15m |
| 2026-05-07 | N364MS | - | May 7, 22:05 UTC | May 7, 23:19 UTC | 1h 15m |
| 2026-05-07 | N364MS | - | May 7, 19:10 UTC | May 7, 20:05 UTC | 55m |
| 2026-05-06 | N364MS | - | May 6, 16:45 UTC | May 6, 17:25 UTC | 40m |
| 2026-05-05 | N364MS | - | May 5, 19:05 UTC | May 5, 19:40 UTC | 35m |
| 2026-05-02 | N364MS | - | May 2, 02:00 UTC | May 2, 02:10 UTC | 10m |
| 2026-05-01 | N364MS | - | May 1, 23:10 UTC | May 1, 23:40 UTC | 30m |
| 2026-05-01 | N364MS | - | May 1, 14:05 UTC | May 1, 14:55 UTC | 50m |
| 2026-04-25 | N364MS | - | Apr 25, 00:10 UTC | Apr 25, 01:05 UTC | 55m |
| 2026-04-21 | N364MS | - | Apr 21, 14:05 UTC | Apr 21, 17:15 UTC | 3h 10m |
| 2026-04-20 | N364MS | - | Apr 20, 16:50 UTC | Apr 20, 17:35 UTC | 45m |
| 2026-04-19 | N364MS | - | Apr 19, 17:10 UTC | Apr 19, 17:35 UTC | 25m |
| 2026-04-19 | N364MS | - | Apr 19, 15:55 UTC | Apr 19, 16:20 UTC | 25m |
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 N364MS page for operator, model, and routing details .