sensors Mode-S transponder

E49512

ICAO 24-bit transponder address · allocated to Brazil

Currently assigned to PR-YJA · AIRBUS A-321neo

Hex
E49512
Octal
71112422
Decimal
14,980,370
Country
BR
Tail
PR-YJA
Type
A21N
No current signal · last broadcast 4h ago
Flights observed
140
Distinct callsigns
20
Country
BR
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S E49512.

Country allocation

The ICAO 24-bit address E49512 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 AZU2830 BSB → SDU May 29, 20:30 UTCMay 30, 00:00 UTC3h 30m
2026-05-29 AZU2744 GRU → REC May 29, 11:30 UTCMay 29, 19:05 UTC7h 35m
2026-05-29 AZU4153 REC → GRU May 29, 02:55 UTCMay 29, 09:50 UTC6h 55m
2026-05-28 AZU2959 GRU → REC May 28, 16:50 UTCMay 29, 00:30 UTC7h 40m
2026-05-28 AZU4451 VCP → MAO May 28, 02:10 UTCMay 28, 15:00 UTC12h 50m
2026-05-27 AZU4345 REC → VCP May 27, 16:35 UTCMay 27, 23:30 UTC6h 55m
2026-05-27 AZU4232 GRU → REC May 27, 08:05 UTCMay 27, 14:55 UTC6h 50m
2026-05-26 AZU5092 GRU → REC May 26, 20:34 UTCMay 27, 03:24 UTC6h 50m
2026-05-26 AZU2768 REC → GRU May 26, 12:05 UTCMay 26, 18:45 UTC6h 40m
2026-05-26 AZU4335 REC → VCP May 26, 02:15 UTCMay 26, 09:29 UTC7h 15m
2026-05-25 AZU4820 POA → CWB May 25, 17:25 UTCMay 26, 00:39 UTC7h 14m
2026-05-25 AZU2876 REC → VCP May 25, 09:10 UTCMay 25, 16:00 UTC6h 50m
2026-05-24 AZU2660 VCP → POA May 24, 20:30 UTCMay 24, 23:46 UTC3h 16m
2026-05-24 AZU4669 FOR → VCP May 24, 15:50 UTCMay 24, 18:55 UTC3h 5m
2026-05-24 AZU4712 VCP → FOR May 24, 11:50 UTCMay 24, 14:40 UTC2h 50m
2026-05-23 AZU2830 BSB → SDU May 23, 20:35 UTCMay 24, 00:20 UTC3h 45m
2026-05-23 AZU4669 FOR → VCP May 23, 16:05 UTCMay 23, 19:05 UTC3h 0m
2026-05-23 AZU4712 VCP → FOR May 23, 12:05 UTCMay 23, 15:00 UTC2h 55m
2026-05-22 AZU2648 REC → MAO May 22, 21:30 UTCMay 23, 09:45 UTC12h 14m
2026-05-22 AZU2823 MCZ → SDU May 22, 12:00 UTCMay 22, 18:55 UTC6h 55m
2026-05-22 AZU4335 REC → VCP May 22, 02:55 UTCMay 22, 09:50 UTC6h 55m
2026-05-21 AZU2959 GRU → REC May 21, 16:55 UTCMay 22, 00:10 UTC7h 15m
2026-05-21 AZU4232 GRU → REC May 21, 08:05 UTCMay 21, 15:10 UTC7h 5m
2026-05-20 AZU5092 GRU → REC May 20, 20:00 UTCMay 21, 02:35 UTC6h 35m
2026-05-20 AZU2768 REC → GRU May 20, 11:35 UTCMay 20, 18:35 UTC7h 0m
2026-05-20 AZU4153 REC → GRU May 20, 08:35 UTCMay 20, 09:20 UTC45m
2026-05-20 AZU4092 VCP → REC May 20, 02:25 UTCMay 20, 03:00 UTC35m
2026-05-19 AZU4345 REC → VCP May 19, 16:35 UTCMay 19, 23:35 UTC7h 0m
2026-05-19 AZU4451 VCP → MAO May 19, 02:10 UTCMay 19, 14:40 UTC12h 30m
2026-05-18 AZU2959 GRU → REC May 18, 17:00 UTCMay 19, 00:15 UTC7h 14m
2026-05-18 AZU4674 REC → GRU May 18, 08:10 UTCMay 18, 15:05 UTC6h 55m
2026-05-17 AZU5092 GRU → REC May 17, 19:55 UTCMay 18, 02:30 UTC6h 35m
2026-05-17 AZU2744 GRU → REC May 17, 12:10 UTCMay 17, 18:40 UTC6h 30m
2026-05-16 AZU4153 REC → GRU May 16, 21:05 UTCMay 17, 10:45 UTC13h 40m
2026-05-16 AZU4669 FOR → VCP May 16, 15:55 UTCMay 16, 19:00 UTC3h 5m
2026-05-16 AZU4712 VCP → FOR May 16, 11:51 UTCMay 16, 14:51 UTC3h 0m
2026-05-16 AZU4152 GRU → REC May 16, 03:05 UTCMay 16, 09:45 UTC6h 41m
2026-05-15 AZU2810 VCP → REC May 15, 18:00 UTCMay 16, 00:45 UTC6h 45m
2026-05-15 AZU2876 REC → VCP May 15, 09:15 UTCMay 15, 16:00 UTC6h 44m
2026-05-14 AZU2660 VCP → POA May 14, 20:45 UTCMay 15, 00:35 UTC3h 50m
2026-05-14 AZU2531 VCP → REC May 14, 11:40 UTCMay 14, 18:50 UTC7h 10m
2026-05-14 AZU4152 GRU → REC May 14, 02:45 UTCMay 14, 09:15 UTC6h 30m
2026-05-13 AZU2959 GRU → REC May 13, 16:50 UTCMay 14, 00:20 UTC7h 30m
2026-05-12 AZU4400 VCP → REC May 12, 21:20 UTCMay 13, 14:55 UTC17h 35m
2026-05-12 AZU2823 MCZ → SDU May 12, 12:00 UTCMay 12, 18:45 UTC6h 45m
2026-05-11 AZU4383 MAO → VCP May 11, 21:15 UTCMay 12, 09:45 UTC12h 30m
2026-05-11 AZU2823 MCZ → SDU May 11, 12:00 UTCMay 11, 19:00 UTC7h 0m
2026-05-11 AZU4383 MAO → VCP May 11, 03:20 UTCMay 11, 09:45 UTC6h 25m
2026-05-10 AZU2648 REC → MAO May 10, 21:19 UTCMay 11, 03:10 UTC5h 50m
2026-05-10 AZU4669 FOR → VCP May 10, 16:00 UTCMay 10, 19:00 UTC3h 0m

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-YJA page for operator, model, and routing details .

Mode-S E49512 frequently asked

What is Mode-S code E49512?
E49512 is an ICAO 24-bit transponder address. Allocated to Brazil. Assigned to PR-YJA.
Where is Mode-S E49512 registered?
Mode-S code E49512 is allocated to Brazil (BR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is E49512 broadcasting right now?
No active broadcast right now. Last signal was 4h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex E49512, octal 71112422, decimal 14,980,370.
What flights does E49512 operate?
Mode-S E49512 has broadcast 20 distinct callsigns, including AZU4669, AZU4153, AZU4712, AZU2823, AZU2959.