sensors Mode-S transponder
A217E2
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N234FJ · DASSAULT Falcon 2000 · operated by HHI HOLDINGS LLC
- Hex
- A217E2
- Octal
- 50413742
- Decimal
- 10,622,946
- Country
- US
- Tail
- N234FJ
- Type
- F2TH
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address A217E2 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 |
|---|---|---|---|
| N234FJ | - | 48 | 2026-07-11 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | N234FJ | - | Jul 11, 15:45 UTC | Jul 11, 18:10 UTC | 2h 25m |
| 2026-07-10 | N234FJ | - | Jul 10, 16:10 UTC | Jul 10, 16:45 UTC | 35m |
| 2026-07-09 | N234FJ | AMS → IBZ | Jul 9, 15:25 UTC | Jul 9, 17:35 UTC | 2h 10m |
| 2026-07-05 | N234FJ | LIN → AMS | Jul 5, 13:40 UTC | Jul 5, 15:10 UTC | 1h 30m |
| 2026-07-04 | N234FJ | - | Jul 4, 02:45 UTC | Jul 4, 14:00 UTC | 11h 15m |
| 2026-07-03 | N234FJ | - | Jul 3, 03:00 UTC | Jul 3, 05:45 UTC | 2h 45m |
| 2026-07-02 | N234FJ | - | Jul 2, 22:20 UTC | Jul 3, 01:10 UTC | 2h 50m |
| 2026-07-01 | N234FJ | - | Jul 1, 16:45 UTC | Jul 2, 00:35 UTC | 7h 50m |
| 2026-06-26 | N234FJ | - | Jun 26, 03:50 UTC | Jun 26, 07:10 UTC | 3h 20m |
| 2026-06-25 | N234FJ | - | Jun 25, 12:50 UTC | Jun 25, 15:34 UTC | 2h 45m |
| 2026-06-25 | N234FJ | - | Jun 25, 10:55 UTC | Jun 25, 11:04 UTC | 10m |
| 2026-06-24 | N234FJ | - | Jun 24, 18:05 UTC | Jun 24, 21:00 UTC | 2h 55m |
| 2026-06-24 | N234FJ | - | Jun 24, 12:54 UTC | Jun 24, 15:39 UTC | 2h 45m |
| 2026-06-20 | N234FJ | - | Jun 20, 04:20 UTC | Jun 20, 04:29 UTC | 10m |
| 2026-06-20 | N234FJ | - | Jun 20, 00:34 UTC | Jun 20, 03:34 UTC | 3h 0m |
| 2026-06-17 | N234FJ | - | Jun 17, 15:46 UTC | Jun 17, 18:30 UTC | 2h 45m |
| 2026-06-14 | N234FJ | - | Jun 14, 09:45 UTC | Jun 14, 10:00 UTC | 15m |
| 2026-06-14 | N234FJ | MTY → MIA | Jun 14, 06:20 UTC | Jun 14, 09:00 UTC | 2h 40m |
| 2026-06-11 | N234FJ | - | Jun 11, 16:25 UTC | Jun 11, 19:00 UTC | 2h 35m |
| 2026-06-07 | N234FJ | - | Jun 7, 19:50 UTC | Jun 7, 20:30 UTC | 40m |
| 2026-06-07 | N234FJ | - | Jun 7, 16:50 UTC | Jun 7, 17:05 UTC | 15m |
| 2026-06-05 | N234FJ | - | Jun 5, 01:45 UTC | Jun 5, 02:20 UTC | 35m |
| 2026-06-03 | N234FJ | - | Jun 3, 18:10 UTC | Jun 3, 19:10 UTC | 1h 0m |
| 2026-06-03 | N234FJ | - | Jun 3, 14:35 UTC | Jun 3, 14:55 UTC | 20m |
| 2026-05-27 | N234FJ | - | May 27, 20:25 UTC | May 27, 21:25 UTC | 1h 0m |
| 2026-05-27 | N234FJ | - | May 27, 19:05 UTC | May 27, 19:45 UTC | 40m |
| 2026-05-23 | N234FJ | - | May 23, 08:20 UTC | May 23, 08:30 UTC | 10m |
| 2026-05-23 | N234FJ | - | May 23, 05:20 UTC | May 23, 07:40 UTC | 2h 20m |
| 2026-05-21 | N234FJ | - | May 21, 17:25 UTC | May 21, 19:45 UTC | 2h 20m |
| 2026-05-20 | N234FJ | - | May 20, 21:10 UTC | May 20, 21:45 UTC | 35m |
| 2026-05-20 | N234FJ | - | May 20, 19:20 UTC | May 20, 19:30 UTC | 10m |
| 2026-05-20 | N234FJ | - | May 20, 17:55 UTC | May 20, 18:05 UTC | 10m |
| 2026-05-20 | N234FJ | - | May 20, 15:55 UTC | May 20, 16:10 UTC | 15m |
| 2026-05-17 | N234FJ | - | May 17, 09:25 UTC | May 17, 09:40 UTC | 15m |
| 2026-05-17 | N234FJ | - | May 17, 06:10 UTC | May 17, 08:35 UTC | 2h 25m |
| 2026-05-13 | N234FJ | - | May 13, 06:30 UTC | May 13, 07:05 UTC | 35m |
| 2026-05-02 | N234FJ | - | May 2, 15:25 UTC | May 2, 18:25 UTC | 3h 0m |
| 2026-05-01 | N234FJ | - | May 1, 22:35 UTC | May 1, 23:30 UTC | 55m |
| 2026-05-01 | N234FJ | - | May 1, 21:30 UTC | May 1, 22:05 UTC | 35m |
| 2026-05-01 | N234FJ | HMO → OPF | May 1, 07:00 UTC | May 1, 13:30 UTC | 6h 30m |
| 2026-04-29 | N234FJ | - | Apr 29, 06:19 UTC | Apr 29, 07:20 UTC | 1h 0m |
| 2026-04-27 | N234FJ | - | Apr 27, 21:05 UTC | Apr 27, 22:30 UTC | 1h 25m |
| 2026-04-24 | N234FJ | - | Apr 24, 21:10 UTC | Apr 24, 21:25 UTC | 15m |
| 2026-04-24 | N234FJ | - | Apr 24, 15:05 UTC | Apr 24, 18:05 UTC | 3h 0m |
| 2026-04-23 | N234FJ | - | Apr 23, 12:45 UTC | Apr 23, 13:20 UTC | 35m |
| 2026-04-21 | N234FJ | - | Apr 21, 19:30 UTC | Apr 21, 19:40 UTC | 10m |
| 2026-04-19 | N234FJ | - | Apr 19, 23:25 UTC | Apr 19, 23:45 UTC | 20m |
| 2026-04-18 | N234FJ | - | Apr 18, 22:15 UTC | Apr 18, 23:05 UTC | 50m |
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 N234FJ page for operator, model, and routing details .