sensors Mode-S transponder
E48A10
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PP-SFY · CESSNA 560XL Citation XLS
- Hex
- E48A10
- Octal
- 71105020
- Decimal
- 14,977,552
- Country
- BR
- Tail
- PP-SFY
- Type
- C56X
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address E48A10 falls within the block assigned to Brazil (BR) by ICAO Annex 10, Volume III. Every aircraft registered in Brazil 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 |
|---|---|---|---|
| PPSFY | - | 56 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-09 | PPSFY | - | Jun 9, 18:00 UTC | Jun 9, 18:55 UTC | 55m |
| 2026-06-09 | PPSFY | - | Jun 9, 12:25 UTC | Jun 9, 13:20 UTC | 55m |
| 2026-06-09 | PPSFY | - | Jun 9, 08:55 UTC | Jun 9, 09:50 UTC | 55m |
| 2026-06-07 | PPSFY | - | Jun 7, 20:20 UTC | Jun 7, 20:45 UTC | 25m |
| 2026-06-07 | PPSFY | - | Jun 7, 19:05 UTC | Jun 7, 19:25 UTC | 20m |
| 2026-06-07 | PPSFY | - | Jun 7, 02:40 UTC | Jun 7, 03:30 UTC | 50m |
| 2026-06-06 | PPSFY | - | Jun 6, 20:19 UTC | Jun 6, 21:00 UTC | 40m |
| 2026-06-06 | PPSFY | - | Jun 6, 15:59 UTC | Jun 6, 16:20 UTC | 20m |
| 2026-06-04 | PPSFY | - | Jun 4, 13:25 UTC | Jun 4, 18:30 UTC | 5h 5m |
| 2026-06-01 | PPSFY | - | Jun 1, 22:05 UTC | Jun 2, 16:10 UTC | 18h 5m |
| 2026-06-01 | PPSFY | - | Jun 1, 13:55 UTC | Jun 1, 21:05 UTC | 7h 10m |
| 2026-05-31 | PPSFY | - | May 31, 22:30 UTC | May 31, 23:15 UTC | 45m |
| 2026-05-31 | PPSFY | - | May 31, 13:20 UTC | May 31, 21:50 UTC | 8h 30m |
| 2026-05-30 | PPSFY | - | May 30, 14:35 UTC | May 30, 15:35 UTC | 1h 0m |
| 2026-05-26 | PPSFY | - | May 26, 21:55 UTC | May 26, 22:09 UTC | 15m |
| 2026-05-25 | PPSFY | - | May 25, 16:15 UTC | May 25, 16:35 UTC | 20m |
| 2026-05-24 | PPSFY | - | May 24, 13:35 UTC | May 24, 14:25 UTC | 50m |
| 2026-05-24 | PPSFY | - | May 24, 10:50 UTC | May 24, 11:40 UTC | 50m |
| 2026-05-22 | PPSFY | - | May 22, 19:20 UTC | May 22, 20:05 UTC | 45m |
| 2026-05-22 | PPSFY | - | May 22, 00:25 UTC | May 22, 00:40 UTC | 15m |
| 2026-05-21 | PPSFY | - | May 21, 22:40 UTC | May 21, 23:30 UTC | 50m |
| 2026-05-17 | PPSFY | - | May 17, 21:55 UTC | May 17, 22:50 UTC | 55m |
| 2026-05-17 | PPSFY | - | May 17, 20:20 UTC | May 17, 21:15 UTC | 55m |
| 2026-05-13 | PPSFY | - | May 13, 19:20 UTC | May 13, 20:05 UTC | 45m |
| 2026-05-11 | PPSFY | - | May 11, 22:05 UTC | May 11, 22:15 UTC | 10m |
| 2026-05-11 | PPSFY | - | May 11, 02:05 UTC | May 11, 02:20 UTC | 15m |
| 2026-05-11 | PPSFY | - | May 11, 00:15 UTC | May 11, 00:34 UTC | 20m |
| 2026-05-09 | PPSFY | - | May 9, 03:35 UTC | May 9, 03:55 UTC | 20m |
| 2026-05-09 | PPSFY | - | May 9, 02:15 UTC | May 9, 02:25 UTC | 10m |
| 2026-05-03 | PPSFY | - | May 3, 21:14 UTC | May 3, 22:05 UTC | 50m |
| 2026-05-01 | PPSFY | - | May 1, 23:15 UTC | May 1, 23:55 UTC | 40m |
| 2026-05-01 | PPSFY | - | May 1, 14:55 UTC | May 1, 15:40 UTC | 45m |
| 2026-05-01 | PPSFY | - | May 1, 01:10 UTC | May 1, 01:45 UTC | 35m |
| 2026-04-30 | PPSFY | - | Apr 30, 23:00 UTC | Apr 30, 23:50 UTC | 50m |
| 2026-04-30 | PPSFY | - | Apr 30, 21:15 UTC | Apr 30, 21:35 UTC | 20m |
| 2026-04-30 | PPSFY | - | Apr 30, 13:35 UTC | Apr 30, 13:50 UTC | 15m |
| 2026-04-30 | PPSFY | - | Apr 30, 12:25 UTC | Apr 30, 12:45 UTC | 20m |
| 2026-04-26 | PPSFY | - | Apr 26, 16:40 UTC | Apr 26, 17:10 UTC | 30m |
| 2026-04-23 | PPSFY | - | Apr 23, 11:55 UTC | Apr 23, 15:50 UTC | 3h 55m |
| 2026-04-22 | PPSFY | - | Apr 22, 14:45 UTC | Apr 22, 23:25 UTC | 8h 40m |
| 2026-04-21 | PPSFY | - | Apr 21, 18:05 UTC | Apr 22, 14:00 UTC | 19h 55m |
| 2026-04-21 | PPSFY | - | Apr 21, 17:45 UTC | Apr 22, 14:00 UTC | 20h 15m |
| 2026-04-21 | PPSFY | - | Apr 21, 12:45 UTC | Apr 21, 18:20 UTC | 5h 35m |
| 2026-04-20 | PPSFY | - | Apr 20, 02:15 UTC | Apr 20, 03:05 UTC | 50m |
| 2026-04-17 | PPSFY | - | Apr 17, 20:10 UTC | Apr 17, 20:55 UTC | 45m |
| 2026-04-17 | PPSFY | - | Apr 17, 03:35 UTC | Apr 17, 04:30 UTC | 55m |
| 2026-04-16 | PPSFY | - | Apr 16, 23:45 UTC | Apr 17, 00:20 UTC | 35m |
| 2026-04-16 | PPSFY | - | Apr 16, 17:40 UTC | Apr 16, 18:15 UTC | 35m |
| 2026-04-16 | PPSFY | - | Apr 16, 13:15 UTC | Apr 16, 13:50 UTC | 35m |
| 2026-04-15 | PPSFY | - | Apr 15, 21:10 UTC | Apr 15, 21:45 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 PP-SFY page for operator, model, and routing details .