sensors Mode-S transponder

E4A1D8

ICAO 24-bit transponder address · allocated to Brazil

Currently assigned to PR-MLD · AIRBUS A-320

Hex
E4A1D8
Octal
71120730
Decimal
14,983,640
Country
BR
Tail
PR-MLD
Type
A320
No current signal · last broadcast 6d ago
Flights observed
84
Distinct callsigns
5
Country
BR
Last broadcast
6d ago

Last known position

Most recent position reported by Mode-S E4A1D8.

Country allocation

The ICAO 24-bit address E4A1D8 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 5 distinct

Callsign Airline Flights Last seen
FBZ5901 Flybondi 23 2026-05-23
FBZ5900 Flybondi 23 2026-05-23
FBZ5903 Flybondi 20 2026-05-21
FBZ5902 Flybondi 17 2026-05-21
FBZ5052 Flybondi 1 2026-05-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-23 FBZ5900 EZE → GIG May 23, 14:35 UTCMay 23, 17:00 UTC2h 25m
2026-05-23 FBZ5901 GIG → EZE May 23, 10:20 UTCMay 23, 13:20 UTC3h 0m
2026-05-22 FBZ5900 EZE → GIG May 22, 22:30 UTCMay 23, 01:00 UTC2h 30m
2026-05-22 FBZ5052 AEP → MDZ May 22, 16:40 UTCMay 22, 20:35 UTC3h 55m
2026-05-22 FBZ5901 GIG → EZE May 22, 11:55 UTCMay 22, 14:55 UTC3h 0m
2026-05-21 FBZ5902 AEP → GIG May 21, 23:00 UTCMay 22, 01:25 UTC2h 25m
2026-05-21 FBZ5903 GIG → EZE May 21, 18:20 UTCMay 21, 21:35 UTC3h 15m
2026-05-21 FBZ5900 EZE → GIG May 21, 14:35 UTCMay 21, 17:00 UTC2h 25m
2026-05-21 FBZ5901 GIG → EZE May 21, 10:05 UTCMay 21, 13:10 UTC3h 5m
2026-05-20 FBZ5900 EZE → GIG May 20, 14:30 UTCMay 20, 17:00 UTC2h 30m
2026-05-20 FBZ5901 GIG → EZE May 20, 10:10 UTCMay 20, 13:05 UTC2h 55m
2026-05-19 FBZ5902 AEP → GIG May 19, 22:40 UTCMay 20, 01:15 UTC2h 35m
2026-05-19 FBZ5903 GIG → EZE May 19, 18:35 UTCMay 19, 21:30 UTC2h 55m
2026-05-19 FBZ5900 EZE → GIG May 19, 14:45 UTCMay 19, 17:25 UTC2h 40m
2026-05-19 FBZ5901 GIG → EZE May 19, 10:10 UTCMay 19, 13:15 UTC3h 5m
2026-05-18 FBZ5900 EZE → GIG May 18, 14:30 UTCMay 18, 17:05 UTC2h 35m
2026-05-18 FBZ5901 GIG → EZE May 18, 10:10 UTCMay 18, 13:10 UTC3h 0m
2026-05-17 FBZ5900 EZE → GIG May 17, 14:30 UTCMay 17, 17:01 UTC2h 30m
2026-05-17 FBZ5901 GIG → EZE May 17, 10:20 UTCMay 17, 13:20 UTC3h 0m
2026-05-16 FBZ5902 AEP → GIG May 16, 22:30 UTCMay 17, 00:55 UTC2h 25m
2026-05-16 FBZ5903 GIG → EZE May 16, 18:25 UTCMay 16, 21:20 UTC2h 54m
2026-05-16 FBZ5900 EZE → GIG May 16, 14:31 UTCMay 16, 17:01 UTC2h 30m
2026-05-16 FBZ5901 GIG → EZE May 16, 10:16 UTCMay 16, 13:15 UTC3h 0m
2026-04-22 FBZ5902 AEP → GIG Apr 22, 23:25 UTCApr 23, 01:50 UTC2h 25m
2026-04-22 FBZ5903 GIG → EZE Apr 22, 19:00 UTCApr 22, 22:05 UTC3h 5m
2026-04-22 FBZ5900 EZE → GIG Apr 22, 14:30 UTCApr 22, 16:50 UTC2h 20m
2026-04-22 FBZ5901 GIG → EZE Apr 22, 10:10 UTCApr 22, 13:25 UTC3h 15m
2026-04-21 FBZ5902 AEP → GIG Apr 21, 23:15 UTCApr 22, 01:35 UTC2h 20m
2026-04-21 FBZ5903 GIG → EZE Apr 21, 18:55 UTCApr 21, 21:55 UTC3h 0m
2026-04-21 FBZ5900 EZE → GIG Apr 21, 14:45 UTCApr 21, 17:10 UTC2h 25m
2026-04-21 FBZ5901 GIG → EZE Apr 21, 10:15 UTCApr 21, 13:20 UTC3h 5m
2026-04-20 FBZ5902 AEP → GIG Apr 20, 23:20 UTCApr 21, 01:45 UTC2h 25m
2026-04-20 FBZ5903 GIG → EZE Apr 20, 19:05 UTCApr 20, 22:05 UTC3h 0m
2026-04-20 FBZ5900 EZE → GIG Apr 20, 14:25 UTCApr 20, 16:55 UTC2h 30m
2026-04-20 FBZ5901 GIG → EZE Apr 20, 10:10 UTCApr 20, 13:15 UTC3h 5m
2026-04-20 FBZ5902 AEP → GIG Apr 20, 02:50 UTCApr 20, 05:10 UTC2h 20m
2026-04-19 FBZ5903 GIG → EZE Apr 19, 22:35 UTCApr 20, 01:30 UTC2h 55m
2026-04-19 FBZ5900 EZE → GIG Apr 19, 18:10 UTCApr 19, 20:55 UTC2h 45m
2026-04-18 FBZ5901 GIG → EZE Apr 18, 10:20 UTCApr 18, 13:20 UTC3h 0m
2026-04-18 FBZ5902 AEP → GIG Apr 18, 01:25 UTCApr 18, 01:55 UTC30m
2026-04-17 FBZ5902 AEP → GIG Apr 17, 23:30 UTCApr 18, 01:20 UTC1h 50m
2026-04-17 FBZ5903 GIG → EZE Apr 17, 21:25 UTCApr 17, 21:45 UTC20m
2026-04-17 FBZ5903 GIG → EZE Apr 17, 19:25 UTCApr 17, 21:20 UTC1h 55m
2026-04-17 FBZ5903 GIG → EZE Apr 17, 19:00 UTCApr 17, 19:20 UTC20m
2026-04-17 FBZ5900 - Apr 17, 16:05 UTCApr 17, 17:05 UTC1h 0m
2026-04-17 FBZ5900 - Apr 17, 14:40 UTCApr 17, 15:05 UTC24m
2026-04-17 FBZ5901 GIG → EZE Apr 17, 11:25 UTCApr 17, 13:10 UTC1h 45m
2026-04-17 FBZ5901 GIG → EZE Apr 17, 10:20 UTCApr 17, 11:10 UTC50m
2026-04-17 FBZ5902 AEP → GIG Apr 17, 01:20 UTCApr 17, 01:50 UTC30m
2026-04-16 FBZ5902 AEP → GIG Apr 16, 23:20 UTCApr 17, 01:15 UTC1h 55m

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

Mode-S E4A1D8 frequently asked

What is Mode-S code E4A1D8?
E4A1D8 is an ICAO 24-bit transponder address. Allocated to Brazil. Assigned to PR-MLD.
Where is Mode-S E4A1D8 registered?
Mode-S code E4A1D8 is allocated to Brazil (BR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is E4A1D8 broadcasting right now?
No active broadcast right now. Last signal was 6d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex E4A1D8, octal 71120730, decimal 14,983,640.
What flights does E4A1D8 operate?
Mode-S E4A1D8 has broadcast 5 distinct callsigns, including FBZ5901, FBZ5900, FBZ5903, FBZ5902, FBZ5052.