sensors Mode-S transponder
A80D47
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N618JJ · BOMBARDIER CL-600 Challenger · operated by JJ CHALLENGER 620TM LLC
- Hex
- A80D47
- Octal
- 52006507
- Decimal
- 11,013,447
- Country
- US
- Tail
- N618JJ
- Type
- CL60
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 17:30 UTC
Last known position
Country allocation
The ICAO 24-bit address A80D47 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 |
|---|---|---|---|
| TFF925 | - | 54 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TFF925 | - | Jul 26, 15:15 UTC | Jul 26, 17:30 UTC | 2h 15m |
| 2026-07-25 | TFF925 | - | Jul 25, 13:25 UTC | Jul 25, 17:40 UTC | 4h 15m |
| 2026-07-25 | TFF925 | - | Jul 25, 11:25 UTC | Jul 25, 11:35 UTC | 10m |
| 2026-07-17 | TFF925 | TEB → FRG | Jul 17, 19:35 UTC | Jul 17, 20:04 UTC | 30m |
| 2026-07-17 | TFF925 | - | Jul 17, 16:10 UTC | Jul 17, 17:55 UTC | 1h 45m |
| 2026-07-17 | TFF925 | - | Jul 17, 13:15 UTC | Jul 17, 14:30 UTC | 1h 15m |
| 2026-07-12 | TFF925 | - | Jul 12, 15:10 UTC | Jul 12, 20:20 UTC | 5h 10m |
| 2026-07-09 | TFF925 | - | Jul 9, 14:00 UTC | Jul 9, 19:35 UTC | 5h 35m |
| 2026-07-05 | TFF925 | - | Jul 5, 16:10 UTC | Jul 5, 16:35 UTC | 25m |
| 2026-07-03 | TFF925 | - | Jul 3, 13:25 UTC | Jul 3, 13:55 UTC | 30m |
| 2026-07-02 | TFF925 | - | Jul 2, 18:45 UTC | Jul 2, 21:15 UTC | 2h 30m |
| 2026-07-02 | TFF925 | - | Jul 2, 15:10 UTC | Jul 2, 17:35 UTC | 2h 25m |
| 2026-07-02 | TFF925 | - | Jul 2, 12:05 UTC | Jul 2, 14:15 UTC | 2h 10m |
| 2026-07-01 | TFF925 | - | Jul 1, 19:25 UTC | Jul 1, 21:50 UTC | 2h 25m |
| 2026-06-28 | TFF925 | - | Jun 28, 16:39 UTC | Jun 28, 19:20 UTC | 2h 40m |
| 2026-06-28 | TFF925 | - | Jun 28, 13:00 UTC | Jun 28, 14:45 UTC | 1h 45m |
| 2026-06-22 | TFF925 | - | Jun 22, 22:49 UTC | Jun 22, 23:14 UTC | 25m |
| 2026-06-21 | TFF925 | - | Jun 21, 14:10 UTC | Jun 21, 16:39 UTC | 2h 30m |
| 2026-06-21 | TFF925 | - | Jun 21, 12:10 UTC | Jun 21, 12:40 UTC | 30m |
| 2026-06-20 | TFF925 | - | Jun 20, 19:49 UTC | Jun 20, 20:29 UTC | 40m |
| 2026-06-20 | TFF925 | - | Jun 20, 16:24 UTC | Jun 20, 17:14 UTC | 50m |
| 2026-06-19 | TFF925 | YYZ → TPA | Jun 19, 17:24 UTC | Jun 19, 19:54 UTC | 2h 30m |
| 2026-06-19 | TFF925 | - | Jun 19, 14:09 UTC | Jun 19, 15:09 UTC | 1h 0m |
| 2026-06-16 | TFF925 | YYZ → TEB | Jun 16, 01:45 UTC | Jun 16, 02:45 UTC | 1h 0m |
| 2026-06-15 | TFF925 | CDW → YYZ | Jun 15, 12:45 UTC | Jun 15, 13:45 UTC | 1h 0m |
| 2026-06-14 | TFF925 | - | Jun 14, 18:35 UTC | Jun 14, 19:50 UTC | 1h 15m |
| 2026-06-12 | TFF925 | - | Jun 12, 19:05 UTC | Jun 12, 20:10 UTC | 1h 5m |
| 2026-06-11 | TFF925 | - | Jun 11, 21:05 UTC | Jun 11, 22:50 UTC | 1h 45m |
| 2026-06-11 | TFF925 | - | Jun 11, 17:20 UTC | Jun 11, 19:15 UTC | 1h 55m |
| 2026-06-07 | TFF925 | - | Jun 7, 16:00 UTC | Jun 7, 16:20 UTC | 20m |
| 2026-06-04 | TFF925 | - | Jun 4, 04:40 UTC | Jun 4, 08:10 UTC | 3h 30m |
| 2026-06-03 | TFF925 | - | Jun 3, 20:30 UTC | Jun 3, 23:50 UTC | 3h 20m |
| 2026-06-03 | TFF925 | - | Jun 3, 00:40 UTC | Jun 3, 03:10 UTC | 2h 30m |
| 2026-06-01 | TFF925 | - | Jun 1, 14:55 UTC | Jun 1, 17:25 UTC | 2h 30m |
| 2026-05-31 | TFF925 | - | May 31, 20:25 UTC | May 31, 23:30 UTC | 3h 5m |
| 2026-05-28 | TFF925 | - | May 28, 17:50 UTC | May 28, 21:05 UTC | 3h 15m |
| 2026-05-28 | TFF925 | TEB → HPN | May 28, 16:20 UTC | May 28, 16:35 UTC | 15m |
| 2026-05-25 | TFF925 | - | May 25, 18:50 UTC | May 26, 00:29 UTC | 5h 39m |
| 2026-05-22 | TFF925 | - | May 22, 02:20 UTC | May 22, 07:25 UTC | 5h 5m |
| 2026-05-22 | TFF925 | - | May 22, 00:10 UTC | May 22, 00:45 UTC | 35m |
| 2026-05-08 | TFF925 | - | May 8, 20:40 UTC | May 8, 21:10 UTC | 30m |
| 2026-05-08 | TFF925 | - | May 8, 18:05 UTC | May 8, 19:30 UTC | 1h 25m |
| 2026-05-07 | TFF925 | - | May 7, 16:40 UTC | May 7, 17:10 UTC | 30m |
| 2026-05-04 | TFF925 | - | May 4, 16:05 UTC | May 4, 16:40 UTC | 35m |
| 2026-05-03 | TFF925 | - | May 3, 12:50 UTC | May 3, 14:50 UTC | 2h 0m |
| 2026-04-30 | TFF925 | - | Apr 30, 17:45 UTC | Apr 30, 19:05 UTC | 1h 20m |
| 2026-04-29 | TFF925 | - | Apr 29, 19:05 UTC | Apr 29, 20:40 UTC | 1h 35m |
| 2026-04-28 | TFF925 | - | Apr 28, 18:20 UTC | Apr 28, 18:55 UTC | 35m |
| 2026-04-22 | TFF925 | - | Apr 22, 14:05 UTC | Apr 22, 14:35 UTC | 30m |
| 2026-04-20 | TFF925 | - | Apr 20, 21:15 UTC | Apr 20, 21:45 UTC | 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 N618JJ page for operator, model, and routing details .