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