sensors Mode-S transponder
E491D9
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PR-SDV · BOEING 737-400
- Hex
- E491D9
- Octal
- 71110731
- Decimal
- 14,979,545
- Country
- BR
- Tail
- PR-SDV
- Type
- B734
- Flights observed
- 58
- Distinct callsigns
- 6
- Country
- BR
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address E491D9 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | SID9409 | - | Jun 10, 01:00 UTC | Jun 10, 02:00 UTC | 1h 0m |
| 2026-06-09 | SID9409 | - | Jun 9, 09:55 UTC | Jun 9, 13:00 UTC | 3h 5m |
| 2026-06-09 | SID9408 | - | Jun 9, 01:15 UTC | Jun 9, 04:30 UTC | 3h 15m |
| 2026-06-06 | SID9409 | - | Jun 6, 07:45 UTC | Jun 6, 10:34 UTC | 2h 50m |
| 2026-06-06 | SID9408 | - | Jun 6, 01:10 UTC | Jun 6, 04:30 UTC | 3h 20m |
| 2026-06-04 | SID9409 | - | Jun 4, 07:30 UTC | Jun 4, 10:30 UTC | 3h 0m |
| 2026-06-04 | SID9409 | - | Jun 4, 01:45 UTC | Jun 4, 04:55 UTC | 3h 10m |
| 2026-06-03 | SID9409 | - | Jun 3, 08:40 UTC | Jun 3, 11:45 UTC | 3h 5m |
| 2026-06-03 | SID9409 | - | Jun 3, 01:20 UTC | Jun 3, 04:40 UTC | 3h 20m |
| 2026-06-02 | SID9409 | - | Jun 2, 07:25 UTC | Jun 2, 09:55 UTC | 2h 30m |
| 2026-06-02 | SID9408 | - | Jun 2, 01:50 UTC | Jun 2, 04:30 UTC | 2h 40m |
| 2026-05-30 | SID9409 | - | May 30, 07:10 UTC | May 30, 10:15 UTC | 3h 5m |
| 2026-05-30 | SID9408 | - | May 30, 01:15 UTC | May 30, 04:30 UTC | 3h 15m |
| 2026-05-29 | SID9408 | - | May 29, 07:25 UTC | May 29, 10:25 UTC | 3h 0m |
| 2026-05-29 | SID9408 | - | May 29, 00:55 UTC | May 29, 04:10 UTC | 3h 15m |
| 2026-05-28 | SID9304 | - | May 28, 07:00 UTC | May 28, 10:00 UTC | 3h 0m |
| 2026-05-28 | SID9304 | - | May 28, 04:00 UTC | May 28, 04:50 UTC | 50m |
| 2026-05-27 | SID9305 | - | May 27, 09:05 UTC | May 28, 04:50 UTC | 19h 45m |
| 2026-05-27 | SID9304 | - | May 27, 03:34 UTC | May 27, 04:19 UTC | 45m |
| 2026-05-26 | SID9305 | - | May 26, 09:04 UTC | May 27, 04:19 UTC | 19h 15m |
| 2026-05-26 | SID9304 | - | May 26, 00:49 UTC | May 26, 04:54 UTC | 4h 5m |
| 2026-05-23 | SID9305 | - | May 23, 08:45 UTC | May 23, 09:30 UTC | 45m |
| 2026-05-23 | SID9304 | - | May 23, 00:55 UTC | May 23, 04:45 UTC | 3h 49m |
| 2026-05-22 | SID9304 | - | May 22, 08:50 UTC | May 23, 04:45 UTC | 19h 54m |
| 2026-05-22 | SID9304 | - | May 22, 00:55 UTC | May 22, 04:30 UTC | 3h 35m |
| 2026-05-21 | SID9304 | - | May 21, 09:05 UTC | May 22, 04:30 UTC | 19h 25m |
| 2026-05-21 | SID9304 | - | May 21, 00:40 UTC | May 21, 04:30 UTC | 3h 50m |
| 2026-05-20 | SID9305 | - | May 20, 08:55 UTC | May 21, 04:30 UTC | 19h 35m |
| 2026-05-20 | SID9304 | - | May 20, 03:45 UTC | May 20, 04:30 UTC | 45m |
| 2026-05-19 | SID9305 | - | May 19, 09:10 UTC | May 19, 10:00 UTC | 50m |
| 2026-05-19 | SID9304 | - | May 19, 03:50 UTC | May 19, 04:35 UTC | 45m |
| 2026-05-16 | SID9305 | - | May 16, 08:51 UTC | May 16, 09:35 UTC | 45m |
| 2026-05-16 | SID9408 | - | May 16, 01:00 UTC | May 16, 04:05 UTC | 3h 5m |
| 2026-05-15 | 00000000 | - | May 15, 07:25 UTC | May 15, 10:35 UTC | 3h 10m |
| 2026-05-15 | 00000000 | - | May 15, 00:50 UTC | May 15, 03:55 UTC | 3h 5m |
| 2026-05-14 | SID9409 | - | May 14, 07:25 UTC | May 14, 10:25 UTC | 3h 0m |
| 2026-05-13 | SID9304 | - | May 13, 10:20 UTC | May 14, 04:30 UTC | 18h 10m |
| 2026-05-13 | SID9304 | - | May 13, 09:55 UTC | May 14, 04:30 UTC | 18h 35m |
| 2026-05-13 | SID9408 | - | May 13, 01:00 UTC | May 13, 04:15 UTC | 3h 15m |
| 2026-05-12 | 00000000 | - | May 12, 07:35 UTC | May 12, 10:35 UTC | 3h 0m |
| 2026-05-12 | 00000000 | - | May 12, 02:45 UTC | May 12, 04:10 UTC | 1h 25m |
| 2026-05-09 | SID9409 | - | May 9, 08:05 UTC | May 9, 11:00 UTC | 2h 55m |
| 2026-05-09 | SID9408 | - | May 9, 01:05 UTC | May 9, 04:15 UTC | 3h 10m |
| 2026-05-08 | SID9409 | - | May 8, 07:59 UTC | May 8, 10:49 UTC | 2h 50m |
| 2026-05-08 | SID9409 | - | May 8, 00:54 UTC | May 8, 04:14 UTC | 3h 20m |
| 2026-05-07 | SID9408 | - | May 7, 08:40 UTC | May 7, 11:25 UTC | 2h 45m |
| 2026-05-07 | SID9408 | - | May 7, 01:00 UTC | May 7, 04:30 UTC | 3h 30m |
| 2026-05-06 | SID9409 | - | May 6, 08:25 UTC | May 6, 11:30 UTC | 3h 5m |
| 2026-05-06 | SID9304 | - | May 6, 04:00 UTC | May 6, 04:40 UTC | 40m |
| 2026-05-05 | SID9304 | - | May 5, 09:00 UTC | May 6, 04:40 UTC | 19h 40m |
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-SDV page for operator, model, and routing details .