sensors Mode-S transponder

E4962E

ICAO 24-bit transponder address · allocated to Brazil

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

Hex
E4962E
Octal
71113056
Decimal
14,980,654
Country
BR
Tail
PR-YJD
Type
A21N
No current signal · last broadcast 1h ago
Flights observed
131
Distinct callsigns
20
Country
BR
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S E4962E.

Country allocation

The ICAO 24-bit address E4962E 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-30 AZU4451 VCP → MAO May 30, 02:10 UTCMay 30, 04:35 UTC2h 25m
2026-05-29 AZU4345 REC → VCP May 29, 16:40 UTCMay 29, 23:15 UTC6h 35m
2026-05-29 AZU4451 VCP → MAO May 29, 02:10 UTCMay 29, 14:55 UTC12h 45m
2026-05-28 AZU4493 REC → VCP May 28, 17:40 UTCMay 29, 00:20 UTC6h 40m
2026-05-28 AZU2876 REC → VCP May 28, 09:10 UTCMay 28, 15:55 UTC6h 45m
2026-05-27 AZU2830 BSB → SDU May 27, 20:15 UTCMay 28, 00:15 UTC4h 0m
2026-05-27 AZU4669 FOR → VCP May 27, 15:50 UTCMay 27, 19:00 UTC3h 10m
2026-05-27 AZU4712 VCP → FOR May 27, 11:55 UTCMay 27, 14:50 UTC2h 55m
2026-05-27 AZU4451 VCP → MAO May 27, 02:04 UTCMay 27, 09:45 UTC7h 41m
2026-05-26 AZU4493 REC → VCP May 26, 17:39 UTCMay 27, 00:25 UTC6h 45m
2026-05-26 AZU2876 REC → VCP May 26, 09:15 UTCMay 26, 16:05 UTC6h 50m
2026-05-24 AZU2805 VCP → REC May 24, 16:55 UTCMay 24, 23:25 UTC6h 30m
2026-05-24 AZU4232 GRU → REC May 24, 08:20 UTCMay 24, 15:25 UTC7h 5m
2026-05-23 AZU5092 GRU → REC May 23, 20:20 UTCMay 24, 02:45 UTC6h 25m
2026-05-23 AZU2768 REC → GRU May 23, 12:00 UTCMay 23, 19:00 UTC7h 0m
2026-05-23 AZU4152 GRU → REC May 23, 02:55 UTCMay 23, 09:30 UTC6h 35m
2026-05-22 AZU2959 GRU → REC May 22, 16:45 UTCMay 23, 00:10 UTC7h 25m
2026-05-22 AZU4232 GRU → REC May 22, 08:05 UTCMay 22, 14:55 UTC6h 50m
2026-05-21 AZU5092 GRU → REC May 21, 20:10 UTCMay 22, 02:35 UTC6h 25m
2026-05-21 AZU2768 REC → GRU May 21, 11:40 UTCMay 21, 18:40 UTC7h 0m
2026-05-21 AZU4153 REC → GRU May 21, 02:35 UTCMay 21, 09:20 UTC6h 45m
2026-05-20 AZU2805 VCP → REC May 20, 16:35 UTCMay 20, 23:15 UTC6h 40m
2026-05-20 AZU4232 GRU → REC May 20, 08:05 UTCMay 20, 14:50 UTC6h 45m
2026-05-19 AZU4232 GRU → REC May 19, 08:15 UTCMay 19, 14:55 UTC6h 40m
2026-05-18 AZU5092 GRU → REC May 18, 20:35 UTCMay 19, 03:10 UTC6h 35m
2026-05-18 AZU2768 REC → GRU May 18, 12:20 UTCMay 18, 19:15 UTC6h 54m
2026-05-18 AZU4152 GRU → REC May 18, 03:20 UTCMay 18, 09:45 UTC6h 25m
2026-05-17 AZU4820 POA → CWB May 17, 17:05 UTCMay 18, 00:40 UTC7h 35m
2026-05-17 AZU4152 GRU → REC May 17, 01:55 UTCMay 17, 14:55 UTC13h 0m
2026-05-16 AZU4820 POA → CWB May 16, 17:35 UTCMay 17, 00:40 UTC7h 5m
2026-05-16 AZU2331 REC → VCP May 16, 09:16 UTCMay 16, 15:50 UTC6h 35m
2026-05-15 AZU4345 REC → VCP May 15, 16:35 UTCMay 15, 23:10 UTC6h 35m
2026-05-15 AZU4451 VCP → MAO May 15, 02:10 UTCMay 15, 14:50 UTC12h 39m
2026-05-14 AZU4840 VCP → BEL May 14, 11:40 UTCMay 14, 22:50 UTC11h 10m
2026-05-13 AZU4345 REC → VCP May 13, 16:45 UTCMay 13, 23:35 UTC6h 50m
2026-05-13 AZU4508 REC → VCP May 13, 08:05 UTCMay 13, 15:00 UTC6h 55m
2026-05-12 AZU5092 GRU → REC May 12, 19:55 UTCMay 13, 02:55 UTC7h 0m
2026-05-12 AZU2744 GRU → REC May 12, 11:35 UTCMay 12, 18:30 UTC6h 55m
2026-05-11 AZU2959 GRU → REC May 11, 16:55 UTCMay 12, 10:15 UTC17h 21m
2026-05-11 AZU4232 GRU → REC May 11, 08:15 UTCMay 11, 15:15 UTC7h 0m
2026-05-10 AZU5092 GRU → REC May 10, 19:54 UTCMay 11, 02:30 UTC6h 35m
2026-05-10 AZU2744 GRU → REC May 10, 11:30 UTCMay 10, 18:29 UTC7h 0m
2026-05-10 AZU4153 REC → GRU May 10, 02:30 UTCMay 10, 09:55 UTC7h 25m
2026-05-09 AZU4820 POA → CWB May 9, 17:30 UTCMay 10, 00:49 UTC7h 20m
2026-05-09 AZU4079 VCP → REC May 9, 09:20 UTCMay 9, 15:45 UTC6h 25m
2026-05-08 AZU2742 REC → AJU May 8, 21:20 UTCMay 9, 01:10 UTC3h 50m
2026-05-08 AZU4669 FOR → VCP May 8, 15:50 UTCMay 8, 19:10 UTC3h 20m
2026-05-08 AZU4712 VCP → FOR May 8, 12:04 UTCMay 8, 14:55 UTC2h 50m
2026-05-08 AZU4383 MAO → VCP May 8, 03:09 UTCMay 8, 09:54 UTC6h 45m
2026-05-07 AZU2648 REC → MAO May 7, 21:20 UTCMay 8, 02:59 UTC5h 39m

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

Mode-S E4962E frequently asked

What is Mode-S code E4962E?
E4962E is an ICAO 24-bit transponder address. Allocated to Brazil. Assigned to PR-YJD.
Where is Mode-S E4962E registered?
Mode-S code E4962E is allocated to Brazil (BR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is E4962E broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex E4962E, octal 71113056, decimal 14,980,654.
What flights does E4962E operate?
Mode-S E4962E has broadcast 20 distinct callsigns, including AZU4232, AZU4345, AZU4820, AZU4451, AZU5092.