sensors Mode-S transponder
E4A247
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-IJC · CESSNA 680 Citation Latitude
- Hex
- E4A247
- Octal
- 71121107
- Decimal
- 14,983,751
- Country
- BR
- Tail
- PS-IJC
- Type
- C68A
- Flights observed
- 59
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- Jul 25, 01:10 UTC
Last known position
Country allocation
The ICAO 24-bit address E4A247 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 |
|---|---|---|---|
| PSIJC | - | 59 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | PSIJC | - | Jul 25, 00:30 UTC | Jul 25, 01:10 UTC | 40m |
| 2026-07-24 | PSIJC | - | Jul 24, 22:15 UTC | Jul 24, 22:45 UTC | 30m |
| 2026-07-24 | PSIJC | - | Jul 24, 00:05 UTC | Jul 24, 01:15 UTC | 1h 10m |
| 2026-07-23 | PSIJC | - | Jul 23, 19:15 UTC | Jul 23, 19:55 UTC | 40m |
| 2026-07-22 | PSIJC | - | Jul 22, 20:30 UTC | Jul 22, 20:55 UTC | 25m |
| 2026-07-21 | PSIJC | - | Jul 21, 12:15 UTC | Jul 21, 12:40 UTC | 25m |
| 2026-07-21 | PSIJC | - | Jul 21, 00:35 UTC | Jul 21, 01:00 UTC | 25m |
| 2026-07-20 | PSIJC | - | Jul 20, 22:20 UTC | Jul 20, 23:10 UTC | 50m |
| 2026-07-14 | PSIJC | - | Jul 14, 13:50 UTC | Jul 14, 14:20 UTC | 30m |
| 2026-07-13 | PSIJC | - | Jul 13, 12:05 UTC | Jul 13, 12:40 UTC | 35m |
| 2026-07-06 | PSIJC | - | Jul 6, 10:20 UTC | Jul 6, 16:40 UTC | 6h 20m |
| 2026-07-05 | PSIJC | - | Jul 5, 13:10 UTC | Jul 5, 18:00 UTC | 4h 50m |
| 2026-07-01 | PSIJC | - | Jul 1, 09:05 UTC | Jul 1, 13:30 UTC | 4h 25m |
| 2026-06-25 | PSIJC | - | Jun 25, 20:05 UTC | Jun 25, 21:50 UTC | 1h 45m |
| 2026-06-25 | PSIJC | - | Jun 25, 13:55 UTC | Jun 25, 15:54 UTC | 2h 0m |
| 2026-06-23 | PSIJC | - | Jun 23, 19:55 UTC | Jun 23, 20:15 UTC | 20m |
| 2026-06-22 | PSIJC | - | Jun 22, 12:44 UTC | Jun 22, 13:10 UTC | 25m |
| 2026-06-16 | PSIJC | - | Jun 16, 18:35 UTC | Jun 16, 19:00 UTC | 25m |
| 2026-06-16 | PSIJC | - | Jun 16, 17:35 UTC | Jun 16, 17:59 UTC | 25m |
| 2026-06-14 | PSIJC | - | Jun 14, 15:10 UTC | Jun 14, 15:45 UTC | 35m |
| 2026-06-14 | PSIJC | - | Jun 14, 12:45 UTC | Jun 14, 13:05 UTC | 20m |
| 2026-06-12 | PSIJC | - | Jun 12, 22:35 UTC | Jun 12, 23:00 UTC | 25m |
| 2026-06-12 | PSIJC | - | Jun 12, 10:20 UTC | Jun 12, 10:55 UTC | 35m |
| 2026-06-11 | PSIJC | - | Jun 11, 16:55 UTC | Jun 11, 17:20 UTC | 25m |
| 2026-06-11 | PSIJC | - | Jun 11, 14:35 UTC | Jun 11, 15:15 UTC | 40m |
| 2026-06-08 | PSIJC | - | Jun 8, 21:50 UTC | Jun 9, 17:25 UTC | 19h 35m |
| 2026-06-08 | PSIJC | - | Jun 8, 21:25 UTC | Jun 9, 17:25 UTC | 20h 0m |
| 2026-06-08 | PSIJC | - | Jun 8, 18:45 UTC | Jun 9, 17:25 UTC | 22h 40m |
| 2026-06-02 | PSIJC | - | Jun 2, 14:00 UTC | Jun 2, 14:30 UTC | 30m |
| 2026-06-01 | PSIJC | - | Jun 1, 13:10 UTC | Jun 1, 13:35 UTC | 25m |
| 2026-05-29 | PSIJC | - | May 29, 20:00 UTC | May 29, 20:10 UTC | 10m |
| 2026-05-29 | PSIJC | - | May 29, 18:40 UTC | May 29, 19:05 UTC | 25m |
| 2026-05-27 | PSIJC | FOR → CGH | May 27, 12:30 UTC | May 27, 16:00 UTC | 3h 30m |
| 2026-05-26 | PSIJC | - | May 26, 13:19 UTC | May 26, 16:24 UTC | 3h 5m |
| 2026-05-25 | PSIJC | - | May 25, 13:50 UTC | May 25, 21:04 UTC | 7h 14m |
| 2026-05-25 | PSIJC | - | May 25, 12:05 UTC | May 25, 12:45 UTC | 40m |
| 2026-05-24 | PSIJC | - | May 24, 15:20 UTC | May 24, 17:05 UTC | 1h 45m |
| 2026-05-24 | PSIJC | - | May 24, 11:55 UTC | May 24, 13:15 UTC | 1h 20m |
| 2026-05-21 | PSIJC | - | May 21, 19:50 UTC | May 21, 22:10 UTC | 2h 20m |
| 2026-05-21 | PSIJC | - | May 21, 17:45 UTC | May 21, 18:50 UTC | 1h 5m |
| 2026-05-20 | PSIJC | - | May 20, 14:25 UTC | May 20, 15:55 UTC | 1h 30m |
| 2026-05-16 | PSIJC | - | May 16, 23:10 UTC | May 17, 00:00 UTC | 50m |
| 2026-05-16 | PSIJC | - | May 16, 21:20 UTC | May 16, 21:45 UTC | 25m |
| 2026-05-16 | PSIJC | - | May 16, 19:50 UTC | May 16, 20:20 UTC | 30m |
| 2026-05-16 | PSIJC | - | May 16, 15:25 UTC | May 16, 16:05 UTC | 40m |
| 2026-05-14 | PSIJC | - | May 14, 17:10 UTC | May 14, 17:45 UTC | 35m |
| 2026-05-13 | PSIJC | - | May 13, 18:20 UTC | May 13, 18:35 UTC | 15m |
| 2026-05-12 | PSIJC | - | May 12, 15:20 UTC | May 12, 21:01 UTC | 5h 40m |
| 2026-05-11 | PSIJC | - | May 11, 13:35 UTC | May 11, 14:00 UTC | 25m |
| 2026-05-11 | PSIJC | - | May 11, 01:45 UTC | May 11, 02:10 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 PS-IJC page for operator, model, and routing details .