sensors Mode-S transponder
4CC1E9
ICAO 24-bit transponder address · allocated to Iceland
Currently assigned to TF-SPY · CESSNA 172 Skyhawk
- Hex
- 4CC1E9
- Octal
- 23140751
- Decimal
- 5,030,377
- Country
- IS
- Tail
- TF-SPY
- Type
- C172
- Flights observed
- 53
- Distinct callsigns
- 1
- Country
- IS
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 4CC1E9 falls within the block assigned to Iceland (IS) by ICAO Annex 10, Volume III. Every aircraft registered in Iceland 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 |
|---|---|---|---|
| TFSPY | - | 53 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TFSPY | RKV → RKV | May 29, 15:45 UTC | May 29, 16:15 UTC | 30m |
| 2026-05-28 | TFSPY | RKV → RKV | May 28, 21:30 UTC | May 28, 22:45 UTC | 1h 15m |
| 2026-05-21 | TFSPY | - | May 21, 15:30 UTC | May 21, 15:40 UTC | 10m |
| 2026-05-21 | TFSPY | - | May 21, 13:30 UTC | May 21, 13:45 UTC | 15m |
| 2026-05-20 | TFSPY | - | May 20, 20:55 UTC | May 20, 21:10 UTC | 15m |
| 2026-05-20 | TFSPY | - | May 20, 19:55 UTC | May 20, 20:15 UTC | 20m |
| 2026-05-20 | TFSPY | - | May 20, 15:25 UTC | May 20, 16:15 UTC | 50m |
| 2026-05-20 | TFSPY | - | May 20, 13:15 UTC | May 20, 13:40 UTC | 25m |
| 2026-05-20 | TFSPY | - | May 20, 11:25 UTC | May 20, 11:55 UTC | 30m |
| 2026-05-19 | TFSPY | RKV → RKV | May 19, 21:00 UTC | May 19, 22:15 UTC | 1h 15m |
| 2026-05-19 | TFSPY | RKV → RKV | May 19, 15:35 UTC | May 19, 16:10 UTC | 35m |
| 2026-05-18 | TFSPY | - | May 18, 16:45 UTC | May 18, 17:15 UTC | 30m |
| 2026-05-18 | TFSPY | - | May 18, 15:10 UTC | May 18, 15:30 UTC | 20m |
| 2026-05-18 | TFSPY | - | May 18, 11:45 UTC | May 18, 12:25 UTC | 40m |
| 2026-05-18 | TFSPY | RKV → RKV | May 18, 10:10 UTC | May 18, 10:40 UTC | 30m |
| 2026-05-17 | TFSPY | RKV → RKV | May 17, 17:20 UTC | May 17, 18:25 UTC | 1h 5m |
| 2026-05-17 | TFSPY | - | May 17, 15:25 UTC | May 17, 15:40 UTC | 15m |
| 2026-05-17 | TFSPY | - | May 17, 09:35 UTC | May 17, 09:55 UTC | 20m |
| 2026-05-16 | TFSPY | RKV → RKV | May 16, 14:51 UTC | May 16, 15:05 UTC | 15m |
| 2026-05-13 | TFSPY | - | May 13, 21:30 UTC | May 13, 22:35 UTC | 1h 5m |
| 2026-05-13 | TFSPY | RKV → RKV | May 13, 18:35 UTC | May 13, 19:45 UTC | 1h 10m |
| 2026-05-13 | TFSPY | RKV → RKV | May 13, 12:35 UTC | May 13, 13:31 UTC | 55m |
| 2026-05-08 | TFSPY | RKV → RKV | May 8, 16:20 UTC | May 8, 17:10 UTC | 50m |
| 2026-05-08 | TFSPY | - | May 8, 14:45 UTC | May 8, 15:35 UTC | 50m |
| 2026-05-08 | TFSPY | RKV → RKV | May 8, 10:29 UTC | May 8, 11:14 UTC | 45m |
| 2026-05-07 | TFSPY | - | May 7, 22:10 UTC | May 7, 22:20 UTC | 10m |
| 2026-05-07 | TFSPY | - | May 7, 20:30 UTC | May 7, 21:05 UTC | 35m |
| 2026-05-07 | TFSPY | RKV → RKV | May 7, 12:00 UTC | May 7, 12:25 UTC | 25m |
| 2026-05-03 | TFSPY | - | May 3, 20:25 UTC | May 3, 20:45 UTC | 20m |
| 2026-05-03 | TFSPY | - | May 3, 19:25 UTC | May 3, 19:40 UTC | 15m |
| 2026-05-03 | TFSPY | - | May 3, 17:35 UTC | May 3, 18:34 UTC | 1h 0m |
| 2026-05-03 | TFSPY | - | May 3, 12:40 UTC | May 3, 13:10 UTC | 30m |
| 2026-05-03 | TFSPY | RKV → RKV | May 3, 10:35 UTC | May 3, 11:25 UTC | 50m |
| 2026-05-02 | TFSPY | - | May 2, 12:15 UTC | May 2, 12:25 UTC | 10m |
| 2026-05-02 | TFSPY | - | May 2, 10:30 UTC | May 2, 10:55 UTC | 25m |
| 2026-05-01 | TFSPY | - | May 1, 21:35 UTC | May 1, 21:45 UTC | 10m |
| 2026-05-01 | TFSPY | - | May 1, 20:15 UTC | May 1, 20:30 UTC | 15m |
| 2026-05-01 | TFSPY | - | May 1, 17:40 UTC | May 1, 17:55 UTC | 15m |
| 2026-05-01 | TFSPY | - | May 1, 15:25 UTC | May 1, 16:35 UTC | 1h 10m |
| 2026-05-01 | TFSPY | - | May 1, 13:55 UTC | May 1, 14:15 UTC | 20m |
| 2026-04-24 | TFSPY | - | Apr 24, 19:50 UTC | Apr 24, 20:15 UTC | 25m |
| 2026-04-24 | TFSPY | - | Apr 24, 18:55 UTC | Apr 24, 19:15 UTC | 20m |
| 2026-04-20 | TFSPY | - | Apr 20, 21:35 UTC | Apr 20, 22:05 UTC | 30m |
| 2026-04-20 | TFSPY | - | Apr 20, 20:45 UTC | Apr 20, 21:00 UTC | 15m |
| 2026-04-20 | TFSPY | RKV → RKV | Apr 20, 15:25 UTC | Apr 20, 16:20 UTC | 55m |
| 2026-04-18 | TFSPY | - | Apr 18, 15:50 UTC | Apr 18, 16:10 UTC | 20m |
| 2026-04-18 | TFSPY | - | Apr 18, 12:50 UTC | Apr 18, 13:10 UTC | 20m |
| 2026-04-17 | TFSPY | - | Apr 17, 11:50 UTC | Apr 17, 12:15 UTC | 25m |
| 2026-04-17 | TFSPY | RKV → RKV | Apr 17, 10:55 UTC | Apr 17, 11:15 UTC | 20m |
| 2026-04-16 | TFSPY | - | Apr 16, 16:25 UTC | Apr 16, 17:10 UTC | 45m |
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 TF-SPY page for operator, model, and routing details .