sensors Mode-S transponder
E49AEA
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PR-YXA · ATR-72-600
- Hex
- E49AEA
- Octal
- 71115352
- Decimal
- 14,981,866
- Country
- BR
- Tail
- PR-YXA
- Type
- AT76
- Flights observed
- 245
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address E49AEA 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AZU4334 | Azul Brazilian Airlines | 8 | 2026-06-13 |
| AZU4333 | Azul Brazilian Airlines | 8 | 2026-06-13 |
| AZU4907 | Azul Brazilian Airlines | 7 | 2026-06-14 |
| AZU4876 | Azul Brazilian Airlines | 7 | 2026-06-14 |
| AZU4268 | - | 7 | 2026-06-14 |
| AZU5033 | - | 6 | 2026-07-03 |
| AZU5023 | - | 6 | 2026-07-03 |
| AZU4650 | Azul Brazilian Airlines | 6 | 2026-06-10 |
| AZU4611 | Azul Brazilian Airlines | 6 | 2026-06-09 |
| AZU4270 | Azul Brazilian Airlines | 6 | 2026-06-11 |
| AZU2654 | Azul Brazilian Airlines | 6 | 2026-06-09 |
| AZU6210 | Azul Brazilian Airlines | 5 | 2026-07-01 |
| AZU6176 | - | 5 | 2026-07-01 |
| AZU4825 | Azul Brazilian Airlines | 5 | 2026-06-11 |
| AZU4766 | Azul Brazilian Airlines | 5 | 2026-06-09 |
| AZU4590 | Azul Brazilian Airlines | 5 | 2026-06-09 |
| AZU4316 | Azul Brazilian Airlines | 5 | 2026-06-13 |
| AZU4265 | - | 5 | 2026-06-13 |
| AZU4119 | Azul Brazilian Airlines | 5 | 2026-06-11 |
| AZU2676 | Azul Brazilian Airlines | 5 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-03 | AZU5023 | - | Jul 3, 14:50 UTC | Jul 3, 15:25 UTC | 35m |
| 2026-07-03 | AZU5033 | - | Jul 3, 12:50 UTC | Jul 3, 13:30 UTC | 40m |
| 2026-07-03 | AZU4376 | - | Jul 3, 02:20 UTC | Jul 3, 02:45 UTC | 25m |
| 2026-07-01 | AZU6210 | SJP → CNF | Jul 1, 19:30 UTC | Jul 1, 20:10 UTC | 40m |
| 2026-07-01 | AZU6176 | - | Jul 1, 17:35 UTC | Jul 1, 18:30 UTC | 55m |
| 2026-07-01 | AZU5023 | - | Jul 1, 14:40 UTC | Jul 1, 15:15 UTC | 35m |
| 2026-07-01 | AZU5033 | - | Jul 1, 12:50 UTC | Jul 1, 13:25 UTC | 35m |
| 2026-06-30 | AZU6210 | SJP → CNF | Jun 30, 22:55 UTC | Jun 30, 23:40 UTC | 45m |
| 2026-06-30 | AZU6176 | - | Jun 30, 20:50 UTC | Jun 30, 21:45 UTC | 55m |
| 2026-06-29 | AZU4264 | - | Jun 29, 21:14 UTC | Jun 29, 21:34 UTC | 20m |
| 2026-06-27 | AZU5023 | - | Jun 27, 14:29 UTC | Jun 27, 15:05 UTC | 35m |
| 2026-06-27 | AZU5033 | - | Jun 27, 12:39 UTC | Jun 27, 13:15 UTC | 35m |
| 2026-06-26 | AZU6210 | SJP → CNF | Jun 26, 20:15 UTC | Jun 26, 20:55 UTC | 40m |
| 2026-06-26 | AZU6176 | - | Jun 26, 18:20 UTC | Jun 26, 19:04 UTC | 45m |
| 2026-06-24 | AZU6175 | - | Jun 24, 19:04 UTC | Jun 24, 19:39 UTC | 35m |
| 2026-06-24 | AZU6174 | - | Jun 24, 17:45 UTC | Jun 24, 18:20 UTC | 35m |
| 2026-06-22 | AZU6175 | - | Jun 22, 19:14 UTC | Jun 22, 19:49 UTC | 35m |
| 2026-06-22 | AZU6174 | - | Jun 22, 17:55 UTC | Jun 22, 18:24 UTC | 30m |
| 2026-06-22 | AZU5023 | - | Jun 22, 14:40 UTC | Jun 22, 15:14 UTC | 35m |
| 2026-06-22 | AZU5033 | - | Jun 22, 12:49 UTC | Jun 22, 13:29 UTC | 40m |
| 2026-06-21 | AZU6122 | - | Jun 21, 12:40 UTC | Jun 21, 13:09 UTC | 30m |
| 2026-06-20 | AZU4670 | - | Jun 20, 02:04 UTC | Jun 20, 03:14 UTC | 1h 10m |
| 2026-06-19 | AZU4927 | PMG → VCP | Jun 19, 16:49 UTC | Jun 19, 17:39 UTC | 50m |
| 2026-06-19 | AZU4927 | PMG → VCP | Jun 19, 15:24 UTC | Jun 19, 15:59 UTC | 35m |
| 2026-06-19 | AZU4926 | VCP → PMG | Jun 19, 13:20 UTC | Jun 19, 14:15 UTC | 55m |
| 2026-06-19 | AZU4926 | VCP → PMG | Jun 19, 11:39 UTC | Jun 19, 12:09 UTC | 30m |
| 2026-06-19 | AZU9032 | - | Jun 19, 02:14 UTC | Jun 19, 02:29 UTC | 15m |
| 2026-06-18 | AZU9800 | CGB → GYN | Jun 18, 11:20 UTC | Jun 18, 12:15 UTC | 55m |
| 2026-06-18 | AZU4393 | - | Jun 18, 08:45 UTC | Jun 18, 09:45 UTC | 1h 0m |
| 2026-06-15 | AZU5023 | BRA → CNF | Jun 15, 16:24 UTC | Jun 15, 17:10 UTC | 45m |
| 2026-06-15 | AZU5033 | - | Jun 15, 14:45 UTC | Jun 15, 15:19 UTC | 35m |
| 2026-06-14 | AZU6175 | - | Jun 14, 20:00 UTC | Jun 14, 20:35 UTC | 35m |
| 2026-06-14 | AZU4268 | - | Jun 14, 18:25 UTC | Jun 14, 19:10 UTC | 45m |
| 2026-06-14 | AZU4876 | SJP → VCP | Jun 14, 16:35 UTC | Jun 14, 17:15 UTC | 40m |
| 2026-06-14 | AZU4907 | VCP → SJP | Jun 14, 12:25 UTC | Jun 14, 13:15 UTC | 50m |
| 2026-06-13 | AZU4265 | - | Jun 13, 19:35 UTC | Jun 13, 20:25 UTC | 50m |
| 2026-06-13 | AZU4316 | VCP → UDI | Jun 13, 17:00 UTC | Jun 13, 17:45 UTC | 45m |
| 2026-06-13 | AZU4334 | JOI → VCP | Jun 13, 15:00 UTC | Jun 13, 15:35 UTC | 35m |
| 2026-06-13 | AZU4333 | VCP → JOI | Jun 13, 12:40 UTC | Jun 13, 13:20 UTC | 40m |
| 2026-06-12 | AZU2710 | NVT → VCP | Jun 12, 18:30 UTC | Jun 12, 19:00 UTC | 30m |
| 2026-06-12 | AZU2707 | VCP → JOI | Jun 12, 16:10 UTC | Jun 12, 16:50 UTC | 40m |
| 2026-06-12 | AZU4540 | JTC → VCP | Jun 12, 14:10 UTC | Jun 12, 14:30 UTC | 20m |
| 2026-06-12 | AZU4530 | VCP → JTC | Jun 12, 12:35 UTC | Jun 12, 13:05 UTC | 30m |
| 2026-06-11 | AZU4119 | RAO → VCP | Jun 11, 23:30 UTC | Jun 12, 00:05 UTC | 35m |
| 2026-06-11 | AZU4825 | VCP → RAO | Jun 11, 21:55 UTC | Jun 11, 22:40 UTC | 45m |
| 2026-06-11 | AZU4270 | RAO → VCP | Jun 11, 20:10 UTC | Jun 11, 20:50 UTC | 40m |
| 2026-06-11 | AZU4268 | VCP → RAO | Jun 11, 18:40 UTC | Jun 11, 19:25 UTC | 45m |
| 2026-06-11 | AZU4876 | SJP → VCP | Jun 11, 14:20 UTC | Jun 11, 15:05 UTC | 45m |
| 2026-06-11 | AZU4907 | VCP → SJP | Jun 11, 12:35 UTC | Jun 11, 13:05 UTC | 30m |
| 2026-06-11 | AZU4474 | PPB → VCP | Jun 11, 09:40 UTC | Jun 11, 10:05 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 PR-YXA page for operator, model, and routing details .