sensors Mode-S transponder
A1E289
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N220RS · PILATUS PC-24 · operated by BERGMANTWO LLC, PILATUS HLD 2 LLC
- Hex
- A1E289
- Octal
- 50361211
- Decimal
- 10,609,289
- Country
- US
- Tail
- N220RS
- Type
- PC24
- Flights observed
- 52
- Distinct callsigns
- 4
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A1E289 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | N220RS | - | Jul 18, 15:05 UTC | Jul 18, 18:15 UTC | 3h 10m |
| 2026-07-15 | N220RS | - | Jul 15, 22:00 UTC | Jul 15, 22:35 UTC | 35m |
| 2026-07-15 | FFL1054 | - | Jul 15, 00:20 UTC | Jul 15, 22:35 UTC | 22h 15m |
| 2026-07-14 | FFL1054 | - | Jul 14, 23:55 UTC | Jul 15, 22:15 UTC | 22h 20m |
| 2026-07-14 | FFL1054 | - | Jul 14, 14:00 UTC | Jul 14, 16:15 UTC | 2h 15m |
| 2026-07-12 | FFL1054 | TMB → DAY | Jul 12, 13:01 UTC | Jul 12, 15:25 UTC | 2h 25m |
| 2026-07-10 | FFL1054 | - | Jul 10, 16:25 UTC | Jul 10, 18:55 UTC | 2h 30m |
| 2026-07-07 | FFL1054 | - | Jul 7, 22:05 UTC | Jul 7, 23:50 UTC | 1h 45m |
| 2026-07-06 | FFL1054 | - | Jul 6, 19:40 UTC | Jul 6, 21:40 UTC | 2h 0m |
| 2026-07-06 | FFL1054 | - | Jul 6, 18:35 UTC | Jul 6, 19:10 UTC | 35m |
| 2026-06-29 | FFL1054 | - | Jun 29, 12:00 UTC | Jun 29, 12:39 UTC | 40m |
| 2026-06-25 | FFL1054 | - | Jun 25, 19:59 UTC | Jun 25, 22:59 UTC | 3h 0m |
| 2026-06-23 | FFL1279 | - | Jun 23, 17:25 UTC | Jun 23, 18:14 UTC | 50m |
| 2026-06-23 | FFL1279 | - | Jun 23, 14:04 UTC | Jun 23, 14:59 UTC | 55m |
| 2026-06-19 | FFL1279 | - | Jun 19, 20:44 UTC | Jun 19, 22:45 UTC | 2h 0m |
| 2026-06-19 | FFL1279 | BOS → BOS | Jun 19, 20:09 UTC | Jun 19, 20:14 UTC | 5m |
| 2026-06-18 | FFL1279 | - | Jun 18, 14:40 UTC | Jun 18, 16:35 UTC | 1h 55m |
| 2026-06-16 | FFL1279 | - | Jun 16, 14:09 UTC | Jun 16, 18:39 UTC | 4h 30m |
| 2026-06-14 | FFL1279 | OMA → APC | Jun 14, 19:25 UTC | Jun 14, 23:15 UTC | 3h 49m |
| 2026-06-14 | FFL1279 | - | Jun 14, 16:55 UTC | Jun 14, 18:45 UTC | 1h 50m |
| 2026-05-31 | FFL1279 | - | May 31, 13:25 UTC | May 31, 15:30 UTC | 2h 5m |
| 2026-05-28 | FFL1279 | - | May 28, 23:00 UTC | May 29, 01:55 UTC | 2h 55m |
| 2026-05-27 | FFL1279 | - | May 27, 18:50 UTC | May 27, 22:15 UTC | 3h 25m |
| 2026-05-22 | N220RS | - | May 22, 15:40 UTC | May 22, 18:55 UTC | 3h 15m |
| 2026-05-22 | N220RS | - | May 22, 14:55 UTC | May 22, 15:00 UTC | 5m |
| 2026-05-21 | N220RS | - | May 21, 09:10 UTC | May 21, 13:25 UTC | 4h 15m |
| 2026-05-21 | FFL1054 | - | May 21, 00:20 UTC | May 21, 02:30 UTC | 2h 10m |
| 2026-05-19 | FFL1279 | - | May 19, 13:45 UTC | May 19, 16:00 UTC | 2h 15m |
| 2026-05-17 | FFL1279 | - | May 17, 16:05 UTC | May 17, 20:25 UTC | 4h 20m |
| 2026-05-16 | FFL1279 | - | May 16, 15:31 UTC | May 16, 18:50 UTC | 3h 20m |
| 2026-05-16 | FFL1279 | - | May 16, 13:01 UTC | May 16, 14:55 UTC | 1h 55m |
| 2026-05-16 | FL1054 | ADS → DAY | May 16, 02:30 UTC | May 16, 04:30 UTC | 2h 0m |
| 2026-05-12 | N220RS | - | May 12, 17:35 UTC | May 12, 19:30 UTC | 1h 55m |
| 2026-05-12 | N220RS | - | May 12, 12:45 UTC | May 12, 15:01 UTC | 2h 15m |
| 2026-05-10 | N220RS | - | May 10, 00:34 UTC | May 10, 01:14 UTC | 40m |
| 2026-05-09 | N220RS | - | May 9, 11:35 UTC | May 9, 12:20 UTC | 45m |
| 2026-05-07 | N220RS | - | May 7, 22:00 UTC | May 7, 23:34 UTC | 1h 35m |
| 2026-05-07 | N220RS | - | May 7, 20:10 UTC | May 7, 21:30 UTC | 1h 20m |
| 2026-05-07 | N220RS | - | May 7, 17:55 UTC | May 7, 18:10 UTC | 15m |
| 2026-05-05 | N220RS | - | May 5, 19:25 UTC | May 5, 19:45 UTC | 20m |
| 2026-05-03 | N220RS | - | May 3, 15:35 UTC | May 3, 18:30 UTC | 2h 55m |
| 2026-05-03 | N220RS | - | May 3, 13:40 UTC | May 3, 15:00 UTC | 1h 20m |
| 2026-04-25 | N220RS | - | Apr 25, 18:30 UTC | Apr 25, 19:30 UTC | 1h 0m |
| 2026-04-25 | N220RS | - | Apr 25, 14:45 UTC | Apr 25, 15:10 UTC | 25m |
| 2026-04-25 | N220RS | - | Apr 25, 13:05 UTC | Apr 25, 14:00 UTC | 55m |
| 2026-04-23 | N220RS | - | Apr 23, 00:40 UTC | Apr 23, 02:45 UTC | 2h 5m |
| 2026-04-22 | N220RS | - | Apr 22, 23:50 UTC | Apr 23, 00:10 UTC | 20m |
| 2026-04-22 | N220RS | - | Apr 22, 22:10 UTC | Apr 22, 23:00 UTC | 51m |
| 2026-04-16 | N220RS | - | Apr 16, 19:15 UTC | Apr 16, 20:35 UTC | 1h 20m |
| 2026-04-16 | N220RS | - | Apr 16, 18:30 UTC | Apr 16, 19:10 UTC | 40m |
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 N220RS page for operator, model, and routing details .