sensors Mode-S transponder
A22FE9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N24ZD · GULFSTREAM AEROSPACE Gulfstream G100 · operated by NEXT WAVE AVIATION LLC
- Hex
- A22FE9
- Octal
- 50427751
- Decimal
- 10,629,097
- Country
- US
- Tail
- N24ZD
- Type
- ASTR
- Flights observed
- 84
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A22FE9 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | N24ZD | - | Jul 14, 00:25 UTC | Jul 14, 02:15 UTC | 1h 50m |
| 2026-07-12 | N24ZD | ANC → CTS | Jul 12, 22:35 UTC | Jul 13, 07:20 UTC | 8h 45m |
| 2026-07-12 | N24ZD | CCR → ANC | Jul 12, 03:15 UTC | Jul 12, 07:31 UTC | 4h 16m |
| 2026-07-11 | N24ZD | - | Jul 11, 20:50 UTC | Jul 12, 01:15 UTC | 4h 25m |
| 2026-07-11 | N24ZD | - | Jul 11, 11:40 UTC | Jul 11, 19:30 UTC | 7h 50m |
| 2026-07-11 | N24ZD | - | Jul 11, 05:50 UTC | Jul 11, 10:35 UTC | 4h 45m |
| 2026-07-10 | N24ZD | - | Jul 10, 23:50 UTC | Jul 11, 03:25 UTC | 3h 35m |
| 2026-07-09 | N24ZD | - | Jul 9, 23:20 UTC | Jul 10, 03:15 UTC | 3h 55m |
| 2026-07-08 | N24ZD | - | Jul 8, 23:40 UTC | Jul 9, 07:30 UTC | 7h 50m |
| 2026-07-06 | N24ZD | - | Jul 6, 06:15 UTC | Jul 6, 07:15 UTC | 1h 0m |
| 2026-07-06 | N24ZD | - | Jul 6, 04:10 UTC | Jul 6, 05:00 UTC | 50m |
| 2026-07-01 | N24ZD | - | Jul 1, 03:45 UTC | Jul 1, 03:55 UTC | 10m |
| 2026-07-01 | N24ZD | - | Jul 1, 02:55 UTC | Jul 1, 03:10 UTC | 15m |
| 2026-06-28 | N24ZD | - | Jun 28, 05:55 UTC | Jun 28, 11:50 UTC | 5h 55m |
| 2026-06-27 | N24ZD | - | Jun 27, 07:04 UTC | Jun 27, 12:29 UTC | 5h 25m |
| 2026-06-26 | N24ZD | - | Jun 26, 13:34 UTC | Jun 26, 17:40 UTC | 4h 5m |
| 2026-06-26 | N24ZD | - | Jun 26, 08:40 UTC | Jun 26, 12:14 UTC | 3h 35m |
| 2026-06-24 | N24ZD | - | Jun 24, 06:59 UTC | Jun 24, 07:10 UTC | 10m |
| 2026-06-21 | N24ZD | - | Jun 21, 00:14 UTC | Jun 21, 07:14 UTC | 7h 0m |
| 2026-06-20 | N24ZD | - | Jun 20, 04:39 UTC | Jun 20, 07:00 UTC | 2h 20m |
| 2026-06-19 | N24ZD | - | Jun 19, 08:20 UTC | Jun 20, 07:00 UTC | 22h 40m |
| 2026-06-19 | N24ZD | - | Jun 19, 06:20 UTC | Jun 20, 05:14 UTC | 22h 55m |
| 2026-06-19 | N24ZD | - | Jun 19, 06:14 UTC | Jun 19, 08:59 UTC | 2h 45m |
| 2026-06-19 | N24ZD | - | Jun 19, 01:50 UTC | Jun 19, 05:14 UTC | 3h 25m |
| 2026-06-18 | N24ZD | - | Jun 18, 23:20 UTC | Jun 19, 00:55 UTC | 1h 34m |
| 2026-06-18 | N24ZD | - | Jun 18, 07:10 UTC | Jun 18, 08:55 UTC | 1h 45m |
| 2026-06-16 | N24ZD | - | Jun 16, 14:25 UTC | Jun 16, 15:15 UTC | 50m |
| 2026-06-16 | N24ZD | - | Jun 16, 09:34 UTC | Jun 16, 10:25 UTC | 50m |
| 2026-06-15 | N24ZD | - | Jun 15, 11:30 UTC | Jun 16, 10:15 UTC | 22h 45m |
| 2026-06-15 | N818WB | - | Jun 15, 06:55 UTC | Jun 15, 11:54 UTC | 5h 0m |
| 2026-06-14 | N24ZD | - | Jun 14, 07:40 UTC | Jun 14, 09:00 UTC | 1h 20m |
| 2026-06-14 | N24ZD | - | Jun 14, 04:40 UTC | Jun 14, 04:55 UTC | 15m |
| 2026-06-14 | N24ZD | - | Jun 14, 03:35 UTC | Jun 14, 04:10 UTC | 35m |
| 2026-06-12 | N24ZD | - | Jun 12, 07:15 UTC | Jun 12, 15:55 UTC | 8h 40m |
| 2026-06-11 | N24ZD | - | Jun 11, 06:10 UTC | Jun 11, 17:00 UTC | 10h 50m |
| 2026-05-25 | N24ZD | - | May 25, 06:10 UTC | May 25, 09:20 UTC | 3h 10m |
| 2026-05-24 | N24ZD | - | May 24, 12:20 UTC | May 25, 09:20 UTC | 21h 0m |
| 2026-05-24 | N24ZD | - | May 24, 11:15 UTC | May 25, 09:20 UTC | 22h 5m |
| 2026-05-24 | N24ZD | - | May 24, 07:50 UTC | May 25, 06:15 UTC | 22h 25m |
| 2026-05-24 | N24ZD | - | May 24, 05:55 UTC | May 24, 06:35 UTC | 40m |
| 2026-05-19 | N24ZD | - | May 19, 03:30 UTC | May 19, 03:40 UTC | 10m |
| 2026-05-18 | N24ZD | - | May 18, 00:25 UTC | May 18, 02:15 UTC | 1h 50m |
| 2026-05-17 | N24ZD | - | May 17, 09:10 UTC | May 17, 09:50 UTC | 40m |
| 2026-05-16 | N24ZD | - | May 16, 06:25 UTC | May 16, 06:35 UTC | 10m |
| 2026-05-15 | N24ZD | - | May 15, 05:40 UTC | May 15, 09:35 UTC | 3h 55m |
| 2026-05-14 | N24ZD | - | May 14, 10:25 UTC | May 15, 09:35 UTC | 23h 10m |
| 2026-05-14 | N24ZD | - | May 14, 09:40 UTC | May 15, 06:00 UTC | 20h 20m |
| 2026-05-14 | N24ZD | - | May 14, 02:40 UTC | May 14, 12:00 UTC | 9h 20m |
| 2026-05-13 | N24ZD | - | May 13, 05:55 UTC | May 13, 09:25 UTC | 3h 30m |
| 2026-05-13 | N24ZD | - | May 13, 03:20 UTC | May 13, 04:50 UTC | 1h 30m |
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 N24ZD page for operator, model, and routing details .