sensors Mode-S transponder
A118E7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N17XF · DASSAULT Falcon 7X · operated by CARGO SOLUTION EXPRESS INC
- Hex
- A118E7
- Octal
- 50214347
- Decimal
- 10,557,671
- Country
- US
- Tail
- N17XF
- Type
- FA7X
- Flights observed
- 45
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address A118E7 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 |
|---|---|---|---|
| N17XF | - | 45 | 2026-07-18 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | N17XF | - | Jul 18, 00:04 UTC | Jul 18, 00:19 UTC | 15m |
| 2026-07-17 | N17XF | - | Jul 17, 19:25 UTC | Jul 17, 20:00 UTC | 35m |
| 2026-07-17 | N17XF | - | Jul 17, 16:04 UTC | Jul 17, 17:05 UTC | 1h 0m |
| 2026-07-11 | N17XF | - | Jul 11, 20:40 UTC | Jul 11, 21:35 UTC | 55m |
| 2026-07-11 | N17XF | - | Jul 11, 14:05 UTC | Jul 11, 15:00 UTC | 55m |
| 2026-07-10 | N17XF | VNY → ONT | Jul 10, 23:55 UTC | Jul 11, 00:10 UTC | 15m |
| 2026-07-08 | N17XF | - | Jul 8, 16:35 UTC | Jul 8, 17:25 UTC | 50m |
| 2026-07-07 | N17XF | - | Jul 7, 19:10 UTC | Jul 7, 22:15 UTC | 3h 5m |
| 2026-07-07 | N17XF | - | Jul 7, 17:20 UTC | Jul 7, 18:05 UTC | 45m |
| 2026-07-05 | N17XF | - | Jul 5, 18:40 UTC | Jul 5, 21:50 UTC | 3h 10m |
| 2026-07-05 | N17XF | - | Jul 5, 16:45 UTC | Jul 5, 17:40 UTC | 55m |
| 2026-07-02 | N17XF | - | Jul 2, 16:55 UTC | Jul 2, 18:15 UTC | 1h 20m |
| 2026-07-01 | N17XF | - | Jul 1, 20:05 UTC | Jul 1, 21:15 UTC | 1h 10m |
| 2026-06-30 | N17XF | - | Jun 30, 20:10 UTC | Jun 30, 21:25 UTC | 1h 15m |
| 2026-06-30 | N17XF | - | Jun 30, 14:00 UTC | Jun 30, 15:15 UTC | 1h 15m |
| 2026-06-26 | N17XF | - | Jun 26, 20:29 UTC | Jun 26, 21:15 UTC | 45m |
| 2026-06-26 | N17XF | - | Jun 26, 12:19 UTC | Jun 26, 19:39 UTC | 7h 20m |
| 2026-06-25 | N17XF | CPH → LTN | Jun 25, 11:25 UTC | Jun 25, 12:50 UTC | 1h 25m |
| 2026-06-24 | N17XF | - | Jun 24, 17:50 UTC | Jun 24, 19:10 UTC | 1h 20m |
| 2026-06-22 | N17XF | - | Jun 22, 04:49 UTC | Jun 22, 13:44 UTC | 8h 55m |
| 2026-06-22 | N17XF | - | Jun 22, 03:19 UTC | Jun 22, 04:00 UTC | 40m |
| 2026-06-07 | N17XF | - | Jun 7, 22:00 UTC | Jun 7, 22:40 UTC | 40m |
| 2026-06-07 | N17XF | - | Jun 7, 21:10 UTC | Jun 7, 21:20 UTC | 10m |
| 2026-06-07 | N17XF | - | Jun 7, 10:35 UTC | Jun 7, 20:00 UTC | 9h 25m |
| 2026-06-03 | N17XF | - | Jun 3, 09:40 UTC | Jun 3, 13:10 UTC | 3h 30m |
| 2026-06-03 | N17XF | KGS → ATH | Jun 3, 07:45 UTC | Jun 3, 08:15 UTC | 30m |
| 2026-05-31 | N17XF | ATH → KGS | May 31, 13:25 UTC | May 31, 14:00 UTC | 35m |
| 2026-05-31 | N17XF | - | May 31, 08:35 UTC | May 31, 12:25 UTC | 3h 50m |
| 2026-05-28 | N17XF | - | May 28, 09:25 UTC | May 28, 09:50 UTC | 25m |
| 2026-05-25 | N17XF | - | May 25, 17:20 UTC | May 25, 17:55 UTC | 35m |
| 2026-05-23 | N17XF | - | May 23, 00:30 UTC | May 23, 02:25 UTC | 1h 55m |
| 2026-05-09 | N17XF | - | May 9, 15:00 UTC | May 9, 20:00 UTC | 5h 0m |
| 2026-05-07 | N17XF | - | May 7, 15:20 UTC | May 7, 23:19 UTC | 7h 59m |
| 2026-05-06 | N17XF | - | May 6, 10:50 UTC | May 6, 11:25 UTC | 35m |
| 2026-05-06 | N17XF | - | May 6, 07:10 UTC | May 6, 09:55 UTC | 2h 45m |
| 2026-05-05 | N17XF | - | May 5, 15:45 UTC | May 5, 16:10 UTC | 25m |
| 2026-04-29 | N17XF | - | Apr 29, 08:10 UTC | Apr 29, 08:34 UTC | 25m |
| 2026-04-23 | N17XF | - | Apr 23, 05:40 UTC | Apr 23, 06:20 UTC | 40m |
| 2026-04-23 | N17XF | - | Apr 23, 04:45 UTC | Apr 23, 04:55 UTC | 10m |
| 2026-04-22 | N17XF | - | Apr 22, 09:40 UTC | Apr 22, 09:50 UTC | 10m |
| 2026-04-22 | N17XF | - | Apr 22, 05:55 UTC | Apr 22, 08:25 UTC | 2h 30m |
| 2026-04-20 | N17XF | - | Apr 20, 04:55 UTC | Apr 20, 11:55 UTC | 7h 0m |
| 2026-04-19 | N17XF | MEB → PER | Apr 19, 03:00 UTC | Apr 19, 06:40 UTC | 3h 40m |
| 2026-04-14 | N17XF | - | Apr 14, 09:10 UTC | Apr 14, 09:55 UTC | 45m |
| 2026-04-14 | N17XF | - | Apr 14, 08:50 UTC | Apr 14, 09:05 UTC | 15m |
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 N17XF page for operator, model, and routing details .