sensors Mode-S transponder
E48DA8
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PT-JCB · BEECH 58 Baron
- Hex
- E48DA8
- Octal
- 71106650
- Decimal
- 14,978,472
- Country
- BR
- Tail
- PT-JCB
- Type
- BE58
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- Jul 26, 15:00 UTC
Last known position
Country allocation
The ICAO 24-bit address E48DA8 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 |
|---|---|---|---|
| PTJCB | - | 51 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | PTJCB | - | Jul 26, 14:05 UTC | Jul 26, 15:00 UTC | 55m |
| 2026-07-21 | PTJCB | - | Jul 21, 10:25 UTC | Jul 21, 11:10 UTC | 45m |
| 2026-07-20 | PTJCB | - | Jul 20, 20:00 UTC | Jul 20, 20:40 UTC | 40m |
| 2026-07-20 | PTJCB | - | Jul 20, 18:15 UTC | Jul 20, 19:10 UTC | 55m |
| 2026-07-20 | PTJCB | - | Jul 20, 15:20 UTC | Jul 20, 16:10 UTC | 50m |
| 2026-07-20 | PTJCB | - | Jul 20, 13:25 UTC | Jul 20, 14:10 UTC | 45m |
| 2026-07-17 | PTJCB | - | Jul 17, 15:35 UTC | Jul 17, 16:19 UTC | 45m |
| 2026-07-17 | PTJCB | - | Jul 17, 14:00 UTC | Jul 17, 14:44 UTC | 45m |
| 2026-07-17 | PTJCB | - | Jul 17, 12:40 UTC | Jul 17, 13:29 UTC | 50m |
| 2026-07-15 | PTJCB | - | Jul 15, 16:10 UTC | Jul 15, 17:10 UTC | 1h 0m |
| 2026-07-15 | PTJCB | - | Jul 15, 14:10 UTC | Jul 15, 14:40 UTC | 30m |
| 2026-07-15 | PTJCB | - | Jul 15, 12:30 UTC | Jul 15, 12:50 UTC | 20m |
| 2026-07-14 | PTJCB | - | Jul 14, 13:30 UTC | Jul 14, 13:45 UTC | 15m |
| 2026-07-14 | PTJCB | - | Jul 14, 11:50 UTC | Jul 14, 12:00 UTC | 10m |
| 2026-07-14 | PTJCB | - | Jul 14, 08:50 UTC | Jul 14, 09:40 UTC | 50m |
| 2026-07-12 | PTJCB | - | Jul 12, 14:40 UTC | Jul 12, 16:10 UTC | 1h 30m |
| 2026-07-11 | PTJCB | - | Jul 11, 12:30 UTC | Jul 11, 14:35 UTC | 2h 5m |
| 2026-07-11 | PTJCB | - | Jul 11, 10:55 UTC | Jul 11, 11:40 UTC | 45m |
| 2026-07-10 | PTJCB | - | Jul 10, 14:00 UTC | Jul 10, 14:45 UTC | 45m |
| 2026-07-09 | PTJCB | - | Jul 9, 12:20 UTC | Jul 9, 13:45 UTC | 1h 25m |
| 2026-07-08 | PTJCB | - | Jul 8, 18:25 UTC | Jul 8, 19:10 UTC | 45m |
| 2026-07-08 | PTJCB | - | Jul 8, 13:45 UTC | Jul 8, 14:50 UTC | 1h 5m |
| 2026-07-06 | PTJCB | - | Jul 6, 11:45 UTC | Jul 6, 12:30 UTC | 45m |
| 2026-07-04 | PTJCB | - | Jul 4, 11:20 UTC | Jul 4, 12:25 UTC | 1h 5m |
| 2026-07-02 | PTJCB | - | Jul 2, 19:55 UTC | Jul 2, 20:15 UTC | 20m |
| 2026-07-01 | PTJCB | - | Jul 1, 18:00 UTC | Jul 1, 18:30 UTC | 30m |
| 2026-06-25 | PTJCB | - | Jun 25, 14:44 UTC | Jun 25, 15:15 UTC | 30m |
| 2026-06-25 | PTJCB | - | Jun 25, 13:35 UTC | Jun 25, 13:55 UTC | 20m |
| 2026-06-21 | PTJCB | - | Jun 21, 14:10 UTC | Jun 21, 14:30 UTC | 20m |
| 2026-06-21 | PTJCB | - | Jun 21, 12:40 UTC | Jun 21, 13:09 UTC | 30m |
| 2026-06-10 | PTJCB | - | Jun 10, 10:45 UTC | Jun 10, 10:55 UTC | 10m |
| 2026-06-06 | PTJCB | - | Jun 6, 18:50 UTC | Jun 6, 19:34 UTC | 45m |
| 2026-06-03 | PTJCB | - | Jun 3, 12:20 UTC | Jun 3, 13:10 UTC | 50m |
| 2026-05-22 | PTJCB | - | May 22, 14:15 UTC | May 22, 14:40 UTC | 25m |
| 2026-05-21 | PTJCB | - | May 21, 14:30 UTC | May 21, 14:45 UTC | 15m |
| 2026-05-20 | PTJCB | - | May 20, 17:35 UTC | May 20, 18:05 UTC | 30m |
| 2026-05-13 | PTJCB | - | May 13, 19:30 UTC | May 13, 20:20 UTC | 50m |
| 2026-05-12 | PTJCB | - | May 12, 13:05 UTC | May 12, 14:00 UTC | 55m |
| 2026-05-03 | PTJCB | - | May 3, 16:09 UTC | May 3, 17:00 UTC | 50m |
| 2026-05-03 | PTJCB | - | May 3, 12:30 UTC | May 3, 13:20 UTC | 50m |
| 2026-05-02 | PTJCB | - | May 2, 20:35 UTC | May 2, 21:05 UTC | 30m |
| 2026-05-01 | PTJCB | - | May 1, 12:40 UTC | May 1, 13:10 UTC | 30m |
| 2026-04-30 | PTJCB | - | Apr 30, 20:00 UTC | Apr 30, 20:45 UTC | 45m |
| 2026-04-30 | PTJCB | - | Apr 30, 16:35 UTC | Apr 30, 17:30 UTC | 55m |
| 2026-04-28 | PTJCB | - | Apr 28, 18:00 UTC | Apr 28, 18:35 UTC | 35m |
| 2026-04-28 | PTJCB | - | Apr 28, 10:10 UTC | Apr 28, 10:40 UTC | 30m |
| 2026-04-24 | PTJCB | - | Apr 24, 15:55 UTC | Apr 24, 16:55 UTC | 1h 0m |
| 2026-04-24 | PTJCB | - | Apr 24, 10:25 UTC | Apr 24, 11:30 UTC | 1h 5m |
| 2026-04-15 | PTJCB | - | Apr 15, 12:10 UTC | Apr 15, 12:55 UTC | 45m |
| 2026-04-14 | PTJCB | - | Apr 14, 12:50 UTC | Apr 14, 13:15 UTC | 25m |
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 PT-JCB page for operator, model, and routing details .