sensors Mode-S transponder
A57E0E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N453JE · RAYTHEON 4000 Hawker Horizon · operated by HAWKER ACQUISITION LLC
- Hex
- A57E0E
- Octal
- 51277016
- Decimal
- 10,845,710
- Country
- US
- Tail
- N453JE
- Type
- HA4T
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address A57E0E 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 |
|---|---|---|---|
| TFF903 | - | 56 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | TFF903 | - | Jul 17, 20:15 UTC | Jul 17, 22:40 UTC | 2h 25m |
| 2026-07-16 | TFF903 | - | Jul 16, 15:25 UTC | Jul 16, 15:45 UTC | 20m |
| 2026-07-15 | TFF903 | - | Jul 15, 17:20 UTC | Jul 15, 20:10 UTC | 2h 50m |
| 2026-07-15 | TFF903 | - | Jul 15, 15:20 UTC | Jul 15, 15:55 UTC | 35m |
| 2026-07-13 | TFF903 | - | Jul 13, 21:05 UTC | Jul 13, 21:40 UTC | 35m |
| 2026-07-09 | TFF903 | - | Jul 9, 22:00 UTC | Jul 9, 22:35 UTC | 35m |
| 2026-07-08 | TFF903 | - | Jul 8, 19:50 UTC | Jul 8, 20:30 UTC | 40m |
| 2026-07-08 | TFF903 | - | Jul 8, 03:35 UTC | Jul 8, 05:05 UTC | 1h 30m |
| 2026-07-07 | TFF903 | - | Jul 7, 14:35 UTC | Jul 7, 16:25 UTC | 1h 50m |
| 2026-07-06 | TFF903 | SLC → BLM | Jul 6, 23:45 UTC | Jul 7, 04:45 UTC | 5h 0m |
| 2026-07-05 | TFF903 | - | Jul 5, 17:30 UTC | Jul 5, 21:45 UTC | 4h 15m |
| 2026-07-02 | TFF903 | FOK → TEB | Jul 2, 15:05 UTC | Jul 2, 15:30 UTC | 25m |
| 2026-07-01 | TFF903 | - | Jul 1, 15:05 UTC | Jul 1, 17:25 UTC | 2h 20m |
| 2026-06-28 | TFF903 | - | Jun 28, 20:29 UTC | Jun 28, 21:10 UTC | 40m |
| 2026-06-27 | TFF903 | - | Jun 27, 13:09 UTC | Jun 27, 13:40 UTC | 30m |
| 2026-06-25 | TFF903 | - | Jun 25, 15:04 UTC | Jun 25, 17:30 UTC | 2h 25m |
| 2026-06-23 | TFF903 | - | Jun 23, 16:14 UTC | Jun 23, 16:44 UTC | 30m |
| 2026-06-21 | TFF903 | - | Jun 21, 15:49 UTC | Jun 21, 16:10 UTC | 20m |
| 2026-06-19 | TFF903 | - | Jun 19, 19:04 UTC | Jun 19, 19:59 UTC | 55m |
| 2026-06-18 | TFF903 | - | Jun 18, 13:25 UTC | Jun 18, 14:30 UTC | 1h 5m |
| 2026-06-16 | TFF903 | XNA → TEB | Jun 16, 21:05 UTC | Jun 16, 23:25 UTC | 2h 20m |
| 2026-06-15 | TFF903 | - | Jun 15, 17:34 UTC | Jun 15, 20:30 UTC | 2h 55m |
| 2026-06-14 | TFF903 | - | Jun 14, 18:10 UTC | Jun 14, 21:35 UTC | 3h 25m |
| 2026-06-13 | TFF903 | - | Jun 13, 18:35 UTC | Jun 13, 22:00 UTC | 3h 25m |
| 2026-06-13 | TFF903 | - | Jun 13, 15:35 UTC | Jun 13, 15:55 UTC | 20m |
| 2026-06-11 | TFF903 | - | Jun 11, 17:40 UTC | Jun 11, 20:15 UTC | 2h 35m |
| 2026-06-11 | TFF903 | - | Jun 11, 15:30 UTC | Jun 11, 15:55 UTC | 25m |
| 2026-06-08 | TFF903 | - | Jun 8, 17:45 UTC | Jun 8, 18:40 UTC | 55m |
| 2026-06-05 | TFF903 | - | Jun 5, 15:55 UTC | Jun 5, 16:40 UTC | 45m |
| 2026-06-04 | TFF903 | - | Jun 4, 21:10 UTC | Jun 4, 23:35 UTC | 2h 25m |
| 2026-06-04 | TFF903 | - | Jun 4, 19:50 UTC | Jun 4, 20:20 UTC | 30m |
| 2026-06-04 | TFF903 | - | Jun 4, 10:45 UTC | Jun 4, 11:35 UTC | 50m |
| 2026-06-03 | TFF903 | - | Jun 3, 16:40 UTC | Jun 3, 17:10 UTC | 30m |
| 2026-06-03 | TFF903 | - | Jun 3, 15:10 UTC | Jun 3, 15:45 UTC | 35m |
| 2026-06-03 | TFF903 | - | Jun 3, 13:45 UTC | Jun 3, 14:15 UTC | 30m |
| 2026-06-03 | TFF903 | - | Jun 3, 00:35 UTC | Jun 3, 03:00 UTC | 2h 25m |
| 2026-06-01 | TFF903 | - | Jun 1, 22:35 UTC | Jun 1, 23:25 UTC | 50m |
| 2026-06-01 | TFF903 | - | Jun 1, 13:50 UTC | Jun 1, 16:50 UTC | 3h 0m |
| 2026-05-30 | TFF903 | - | May 30, 20:45 UTC | May 30, 21:35 UTC | 50m |
| 2026-05-30 | TFF903 | - | May 30, 16:30 UTC | May 30, 17:15 UTC | 45m |
| 2026-05-30 | TFF903 | FRG → TEB | May 30, 13:30 UTC | May 30, 14:00 UTC | 30m |
| 2026-05-16 | TFF903 | TEB → FRG | May 16, 04:50 UTC | May 16, 05:05 UTC | 15m |
| 2026-05-16 | TFF903 | - | May 16, 02:20 UTC | May 16, 04:05 UTC | 1h 45m |
| 2026-05-15 | TFF903 | - | May 15, 01:10 UTC | May 15, 02:50 UTC | 1h 40m |
| 2026-05-09 | TFF903 | - | May 9, 22:49 UTC | May 10, 00:55 UTC | 2h 5m |
| 2026-05-07 | TFF903 | - | May 7, 14:00 UTC | May 7, 15:50 UTC | 1h 50m |
| 2026-05-07 | TFF903 | - | May 7, 13:45 UTC | May 7, 13:55 UTC | 10m |
| 2026-04-23 | TFF903 | - | Apr 23, 21:25 UTC | Apr 23, 23:55 UTC | 2h 30m |
| 2026-04-21 | TFF903 | - | Apr 21, 17:25 UTC | Apr 21, 20:00 UTC | 2h 35m |
| 2026-04-18 | TFF903 | - | Apr 18, 20:45 UTC | Apr 18, 21:45 UTC | 1h 0m |
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 N453JE page for operator, model, and routing details .