sensors Mode-S transponder
AB7E33
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N84HD · DASSAULT Falcon 900 · operated by HOMERLEASE CO INC
- Hex
- AB7E33
- Octal
- 52677063
- Decimal
- 11,238,963
- Country
- US
- Tail
- N84HD
- Type
- F900
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 25, 20:25 UTC
Last known position
Country allocation
The ICAO 24-bit address AB7E33 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 |
|---|---|---|---|
| N84HD | - | 66 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | N84HD | YVR → FTY | Jul 25, 16:15 UTC | Jul 25, 20:25 UTC | 4h 10m |
| 2026-07-22 | N84HD | - | Jul 22, 12:20 UTC | Jul 22, 17:05 UTC | 4h 45m |
| 2026-07-21 | N84HD | - | Jul 21, 18:40 UTC | Jul 21, 20:05 UTC | 1h 25m |
| 2026-07-21 | N84HD | - | Jul 21, 16:30 UTC | Jul 21, 18:00 UTC | 1h 30m |
| 2026-07-16 | N84HD | - | Jul 16, 19:25 UTC | Jul 16, 20:49 UTC | 1h 25m |
| 2026-07-16 | N84HD | FTY → PWK | Jul 16, 12:00 UTC | Jul 16, 13:30 UTC | 1h 30m |
| 2026-07-02 | N84HD | - | Jul 2, 20:40 UTC | Jul 2, 21:35 UTC | 55m |
| 2026-07-02 | N84HD | - | Jul 2, 12:05 UTC | Jul 2, 13:00 UTC | 55m |
| 2026-07-01 | N84HD | - | Jul 1, 21:05 UTC | Jul 1, 23:00 UTC | 1h 55m |
| 2026-07-01 | N84HD | - | Jul 1, 12:10 UTC | Jul 1, 13:40 UTC | 1h 30m |
| 2026-06-24 | N84HD | - | Jun 24, 17:25 UTC | Jun 24, 18:09 UTC | 45m |
| 2026-06-22 | N84HD | - | Jun 22, 22:44 UTC | Jun 22, 23:35 UTC | 50m |
| 2026-06-19 | N84HD | MSY → FTY | Jun 19, 21:44 UTC | Jun 19, 22:55 UTC | 1h 10m |
| 2026-06-17 | N84HD | FTY → MSY | Jun 17, 13:05 UTC | Jun 17, 14:10 UTC | 1h 5m |
| 2026-06-15 | N84HD | - | Jun 15, 20:59 UTC | Jun 15, 22:15 UTC | 1h 15m |
| 2026-06-15 | N84HD | FTY → MDW | Jun 15, 12:05 UTC | Jun 15, 13:34 UTC | 1h 30m |
| 2026-06-12 | N84HD | - | Jun 12, 20:25 UTC | Jun 12, 22:25 UTC | 2h 0m |
| 2026-06-11 | N84HD | - | Jun 11, 19:55 UTC | Jun 11, 20:35 UTC | 40m |
| 2026-06-11 | N84HD | FTY → EWR | Jun 11, 11:50 UTC | Jun 11, 13:35 UTC | 1h 45m |
| 2026-06-04 | N84HD | - | Jun 4, 15:00 UTC | Jun 4, 19:15 UTC | 4h 15m |
| 2026-06-02 | N84HD | FTY → BFI | Jun 2, 19:30 UTC | Jun 3, 00:25 UTC | 4h 55m |
| 2026-05-30 | N84HD | - | May 30, 15:10 UTC | May 30, 18:50 UTC | 3h 40m |
| 2026-05-28 | N84HD | - | May 28, 19:25 UTC | May 28, 19:50 UTC | 25m |
| 2026-05-28 | N84HD | - | May 28, 12:50 UTC | May 28, 17:05 UTC | 4h 15m |
| 2026-05-27 | N84HD | - | May 27, 19:30 UTC | May 27, 21:00 UTC | 1h 30m |
| 2026-05-27 | N84HD | - | May 27, 12:05 UTC | May 27, 13:25 UTC | 1h 20m |
| 2026-05-22 | N84HD | - | May 22, 00:15 UTC | May 22, 02:10 UTC | 1h 55m |
| 2026-05-21 | N84HD | - | May 21, 23:25 UTC | May 21, 23:40 UTC | 15m |
| 2026-05-21 | N84HD | FTY → TEB | May 21, 19:20 UTC | May 21, 21:05 UTC | 1h 45m |
| 2026-05-20 | N84HD | TEB → FTY | May 20, 13:40 UTC | May 20, 15:20 UTC | 1h 40m |
| 2026-05-19 | N84HD | - | May 19, 14:45 UTC | May 19, 16:40 UTC | 1h 55m |
| 2026-05-14 | N84HD | - | May 14, 17:55 UTC | May 14, 19:00 UTC | 1h 5m |
| 2026-05-14 | N84HD | - | May 14, 12:05 UTC | May 14, 13:15 UTC | 1h 10m |
| 2026-05-07 | N84HD | TEB → FTY | May 7, 19:30 UTC | May 7, 21:35 UTC | 2h 5m |
| 2026-05-05 | N84HD | - | May 5, 20:10 UTC | May 5, 21:55 UTC | 1h 45m |
| 2026-05-04 | N84HD | FTY → FTY | May 4, 19:35 UTC | May 4, 23:05 UTC | 3h 30m |
| 2026-05-01 | N84HD | FTY → FTY | May 1, 18:30 UTC | May 1, 19:10 UTC | 40m |
| 2026-04-30 | N84HD | PSQ → FTY | Apr 30, 20:25 UTC | Apr 30, 22:10 UTC | 1h 45m |
| 2026-04-30 | N84HD | - | Apr 30, 12:30 UTC | Apr 30, 14:00 UTC | 1h 30m |
| 2026-04-29 | N84HD | STL → FTY | Apr 29, 18:40 UTC | Apr 29, 19:40 UTC | 1h 0m |
| 2026-04-29 | N84HD | - | Apr 29, 11:55 UTC | Apr 29, 13:15 UTC | 1h 20m |
| 2026-04-28 | N84HD | - | Apr 28, 20:10 UTC | Apr 28, 21:35 UTC | 1h 25m |
| 2026-04-28 | N84HD | FTY → DTW | Apr 28, 11:50 UTC | Apr 28, 13:40 UTC | 1h 50m |
| 2026-04-27 | N84HD | IAD → FTY | Apr 27, 18:35 UTC | Apr 27, 19:50 UTC | 1h 15m |
| 2026-04-26 | N84HD | FTY → IAD | Apr 26, 23:15 UTC | Apr 27, 00:40 UTC | 1h 25m |
| 2026-04-23 | N84HD | - | Apr 23, 19:25 UTC | Apr 24, 01:25 UTC | 6h 0m |
| 2026-04-22 | N84HD | - | Apr 22, 14:20 UTC | Apr 22, 15:15 UTC | 55m |
| 2026-04-21 | N84HD | - | Apr 21, 15:20 UTC | Apr 21, 17:20 UTC | 2h 0m |
| 2026-04-20 | N84HD | FTY → SNA | Apr 20, 17:45 UTC | Apr 20, 22:00 UTC | 4h 15m |
| 2026-04-18 | N84HD | BNA → FTY | Apr 18, 19:35 UTC | Apr 18, 20:10 UTC | 35m |
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 N84HD page for operator, model, and routing details .