sensors Mode-S transponder
E49240
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PP-CGP · BELL 429 GlobalRanger
- Hex
- E49240
- Octal
- 71111100
- Decimal
- 14,979,648
- Country
- BR
- Tail
- PP-CGP
- Type
- B429
- Flights observed
- 63
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address E49240 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 |
|---|---|---|---|
| PPCGP | - | 63 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | PPCGP | - | Jul 13, 12:20 UTC | Jul 13, 12:40 UTC | 20m |
| 2026-07-12 | PPCGP | - | Jul 12, 17:10 UTC | Jul 12, 17:25 UTC | 15m |
| 2026-07-12 | PPCGP | - | Jul 12, 15:55 UTC | Jul 12, 16:40 UTC | 45m |
| 2026-07-11 | PPCGP | - | Jul 11, 21:25 UTC | Jul 11, 21:45 UTC | 20m |
| 2026-07-11 | PPCGP | - | Jul 11, 20:15 UTC | Jul 11, 20:40 UTC | 25m |
| 2026-07-08 | PPCGP | - | Jul 8, 19:50 UTC | Jul 8, 20:35 UTC | 45m |
| 2026-07-08 | PPCGP | - | Jul 8, 14:25 UTC | Jul 8, 14:50 UTC | 25m |
| 2026-07-07 | PPCGP | GIG → GIG | Jul 7, 14:10 UTC | Jul 7, 15:20 UTC | 1h 10m |
| 2026-07-06 | PPCGP | - | Jul 6, 15:50 UTC | Jul 6, 16:25 UTC | 35m |
| 2026-07-06 | PPCGP | - | Jul 6, 15:05 UTC | Jul 6, 15:15 UTC | 10m |
| 2026-07-04 | PPCGP | - | Jul 4, 17:45 UTC | Jul 4, 18:00 UTC | 15m |
| 2026-06-29 | PPCGP | - | Jun 29, 14:04 UTC | Jun 29, 14:25 UTC | 20m |
| 2026-06-29 | PPCGP | - | Jun 29, 13:24 UTC | Jun 29, 13:59 UTC | 35m |
| 2026-06-28 | PPCGP | - | Jun 28, 22:55 UTC | Jun 28, 23:04 UTC | 10m |
| 2026-06-28 | PPCGP | - | Jun 28, 21:40 UTC | Jun 28, 22:04 UTC | 25m |
| 2026-06-28 | PPCGP | - | Jun 28, 20:50 UTC | Jun 28, 20:59 UTC | 10m |
| 2026-06-28 | PPCGP | - | Jun 28, 14:39 UTC | Jun 28, 15:09 UTC | 30m |
| 2026-06-27 | PPCGP | - | Jun 27, 19:39 UTC | Jun 27, 20:09 UTC | 30m |
| 2026-06-27 | PPCGP | - | Jun 27, 19:05 UTC | Jun 27, 19:19 UTC | 15m |
| 2026-06-22 | PPCGP | - | Jun 22, 22:24 UTC | Jun 22, 22:34 UTC | 10m |
| 2026-06-22 | PPCGP | - | Jun 22, 21:14 UTC | Jun 22, 21:40 UTC | 25m |
| 2026-06-22 | PPCGP | - | Jun 22, 20:04 UTC | Jun 22, 20:34 UTC | 30m |
| 2026-06-19 | PPCGP | - | Jun 19, 16:04 UTC | Jun 19, 16:59 UTC | 55m |
| 2026-06-18 | PPCGP | - | Jun 18, 11:30 UTC | Jun 18, 11:45 UTC | 15m |
| 2026-06-17 | PPCGP | - | Jun 17, 19:40 UTC | Jun 17, 20:20 UTC | 40m |
| 2026-06-04 | PPCGP | - | Jun 4, 21:05 UTC | Jun 4, 21:45 UTC | 40m |
| 2026-06-04 | PPCGP | - | Jun 4, 18:45 UTC | Jun 4, 19:15 UTC | 30m |
| 2026-06-04 | PPCGP | - | Jun 4, 14:50 UTC | Jun 4, 15:25 UTC | 35m |
| 2026-06-04 | PPCGP | - | Jun 4, 13:55 UTC | Jun 4, 14:40 UTC | 45m |
| 2026-05-31 | PPCGP | - | May 31, 18:15 UTC | May 31, 19:25 UTC | 1h 10m |
| 2026-05-31 | PPCGP | GIG → GIG | May 31, 15:40 UTC | May 31, 16:30 UTC | 50m |
| 2026-05-30 | PPCGP | GIG → GIG | May 30, 16:20 UTC | May 30, 17:20 UTC | 1h 0m |
| 2026-05-29 | PPCGP | GIG → GIG | May 29, 22:05 UTC | May 29, 22:25 UTC | 20m |
| 2026-05-29 | PPCGP | - | May 29, 17:40 UTC | May 29, 17:55 UTC | 15m |
| 2026-05-29 | PPCGP | - | May 29, 16:15 UTC | May 29, 16:25 UTC | 10m |
| 2026-05-29 | PPCGP | - | May 29, 12:10 UTC | May 29, 12:20 UTC | 10m |
| 2026-05-26 | PPCGP | - | May 26, 14:00 UTC | May 26, 14:40 UTC | 40m |
| 2026-05-26 | PPCGP | - | May 26, 12:35 UTC | May 26, 13:04 UTC | 30m |
| 2026-05-26 | PPCGP | - | May 26, 11:34 UTC | May 26, 11:50 UTC | 15m |
| 2026-05-24 | PPCGP | - | May 24, 20:25 UTC | May 24, 20:40 UTC | 15m |
| 2026-05-23 | PPCGP | - | May 23, 20:00 UTC | May 23, 20:10 UTC | 10m |
| 2026-05-22 | PPCGP | GIG → GIG | May 22, 23:00 UTC | May 22, 23:30 UTC | 30m |
| 2026-05-19 | PPCGP | - | May 19, 13:20 UTC | May 19, 14:15 UTC | 55m |
| 2026-05-18 | PPCGP | - | May 18, 18:30 UTC | May 18, 19:00 UTC | 30m |
| 2026-05-11 | PPCGP | - | May 11, 21:50 UTC | May 11, 22:35 UTC | 44m |
| 2026-05-11 | PPCGP | - | May 11, 12:25 UTC | May 11, 12:50 UTC | 25m |
| 2026-05-03 | PPCGP | - | May 3, 22:05 UTC | May 3, 22:30 UTC | 25m |
| 2026-04-30 | PPCGP | - | Apr 30, 19:25 UTC | Apr 30, 19:50 UTC | 25m |
| 2026-04-29 | PPCGP | GIG → GIG | Apr 29, 21:25 UTC | Apr 29, 21:40 UTC | 15m |
| 2026-04-26 | PPCGP | - | Apr 26, 16:20 UTC | Apr 26, 16:40 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-CGP page for operator, model, and routing details .