sensors Mode-S transponder
E49A0A
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-BFB · BEECHCRAFT Super King Air 350
- Hex
- E49A0A
- Octal
- 71115012
- Decimal
- 14,981,642
- Country
- BR
- Tail
- PS-BFB
- Type
- B350
- Flights observed
- 63
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address E49A0A 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PSBFB | - | 63 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | PSBFB | - | Jul 26, 00:40 UTC | Jul 26, 01:05 UTC | 25m |
| 2026-07-25 | PSBFB | - | Jul 25, 16:50 UTC | Jul 25, 17:25 UTC | 35m |
| 2026-07-25 | PSBFB | - | Jul 25, 15:35 UTC | Jul 25, 16:40 UTC | 1h 5m |
| 2026-07-25 | PSBFB | - | Jul 25, 14:10 UTC | Jul 25, 14:30 UTC | 20m |
| 2026-07-24 | PSBFB | - | Jul 24, 10:20 UTC | Jul 24, 10:30 UTC | 10m |
| 2026-07-24 | PSBFB | - | Jul 24, 02:00 UTC | Jul 24, 02:10 UTC | 10m |
| 2026-07-17 | PSBFB | - | Jul 17, 12:45 UTC | Jul 17, 13:10 UTC | 25m |
| 2026-07-15 | PSBFB | - | Jul 15, 17:35 UTC | Jul 15, 17:55 UTC | 20m |
| 2026-07-15 | PSBFB | - | Jul 15, 13:55 UTC | Jul 15, 14:20 UTC | 25m |
| 2026-07-12 | PSBFB | - | Jul 12, 06:30 UTC | Jul 12, 07:01 UTC | 30m |
| 2026-07-11 | PSBFB | - | Jul 11, 13:55 UTC | Jul 11, 14:35 UTC | 40m |
| 2026-07-10 | PSBFB | - | Jul 10, 21:25 UTC | Jul 10, 22:00 UTC | 35m |
| 2026-07-01 | PSBFB | - | Jul 1, 21:50 UTC | Jul 1, 22:45 UTC | 55m |
| 2026-07-01 | PSBFB | - | Jul 1, 19:20 UTC | Jul 1, 20:00 UTC | 40m |
| 2026-07-01 | PSBFB | - | Jul 1, 17:35 UTC | Jul 1, 18:20 UTC | 45m |
| 2026-07-01 | PSBFB | - | Jul 1, 16:00 UTC | Jul 1, 16:45 UTC | 45m |
| 2026-07-01 | PSBFB | - | Jul 1, 14:45 UTC | Jul 1, 15:25 UTC | 40m |
| 2026-07-01 | PSBFB | - | Jul 1, 13:10 UTC | Jul 1, 13:55 UTC | 45m |
| 2026-07-01 | PSBFB | - | Jul 1, 11:50 UTC | Jul 1, 12:30 UTC | 40m |
| 2026-06-29 | PSBFB | - | Jun 29, 19:44 UTC | Jun 29, 20:49 UTC | 1h 5m |
| 2026-06-27 | PSBFB | - | Jun 27, 19:05 UTC | Jun 27, 19:24 UTC | 20m |
| 2026-06-27 | PSBFB | - | Jun 27, 11:25 UTC | Jun 27, 12:04 UTC | 40m |
| 2026-06-26 | PSBFB | - | Jun 26, 19:04 UTC | Jun 26, 23:04 UTC | 4h 0m |
| 2026-06-23 | PSBFB | - | Jun 23, 21:39 UTC | Jun 23, 21:59 UTC | 20m |
| 2026-06-23 | PSBFB | - | Jun 23, 20:04 UTC | Jun 23, 20:15 UTC | 10m |
| 2026-06-23 | PSBFB | - | Jun 23, 14:35 UTC | Jun 23, 14:59 UTC | 25m |
| 2026-06-17 | PSBFB | - | Jun 17, 14:35 UTC | Jun 17, 15:40 UTC | 1h 5m |
| 2026-06-16 | PSBFB | - | Jun 16, 10:30 UTC | Jun 16, 11:25 UTC | 55m |
| 2026-06-05 | PSBFB | - | Jun 5, 20:20 UTC | Jun 5, 20:45 UTC | 25m |
| 2026-06-04 | PSBFB | - | Jun 4, 18:45 UTC | Jun 4, 19:05 UTC | 20m |
| 2026-06-03 | PSBFB | - | Jun 3, 20:20 UTC | Jun 3, 20:40 UTC | 20m |
| 2026-06-03 | PSBFB | - | Jun 3, 18:40 UTC | Jun 3, 19:15 UTC | 35m |
| 2026-06-03 | PSBFB | - | Jun 3, 11:00 UTC | Jun 3, 12:00 UTC | 1h 0m |
| 2026-05-31 | PSBFB | - | May 31, 21:10 UTC | May 31, 21:30 UTC | 20m |
| 2026-05-31 | PSBFB | - | May 31, 13:35 UTC | May 31, 13:55 UTC | 20m |
| 2026-05-30 | PSBFB | - | May 30, 17:25 UTC | May 30, 17:45 UTC | 20m |
| 2026-05-30 | PSBFB | - | May 30, 13:35 UTC | May 30, 13:50 UTC | 15m |
| 2026-05-29 | PSBFB | - | May 29, 18:05 UTC | May 29, 19:00 UTC | 55m |
| 2026-05-29 | PSBFB | - | May 29, 14:15 UTC | May 29, 14:25 UTC | 10m |
| 2026-05-27 | PSBFB | - | May 27, 13:55 UTC | May 27, 14:55 UTC | 1h 0m |
| 2026-05-22 | PSBFB | - | May 22, 22:00 UTC | May 22, 22:15 UTC | 15m |
| 2026-05-22 | PSBFB | - | May 22, 20:35 UTC | May 22, 20:45 UTC | 10m |
| 2026-05-22 | PSBFB | - | May 22, 17:20 UTC | May 22, 17:45 UTC | 25m |
| 2026-05-20 | PSBFB | - | May 20, 21:40 UTC | May 20, 21:55 UTC | 15m |
| 2026-05-20 | PSBFB | - | May 20, 17:30 UTC | May 20, 17:50 UTC | 20m |
| 2026-05-19 | PSBFB | - | May 19, 21:55 UTC | May 19, 22:50 UTC | 55m |
| 2026-05-19 | PSBFB | - | May 19, 11:35 UTC | May 19, 12:45 UTC | 1h 10m |
| 2026-05-17 | PSBFB | - | May 17, 00:25 UTC | May 17, 00:50 UTC | 25m |
| 2026-05-16 | PSBFB | - | May 16, 18:15 UTC | May 16, 18:30 UTC | 15m |
| 2026-05-16 | PSBFB | - | May 16, 15:25 UTC | May 16, 15:35 UTC | 10m |
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 PS-BFB page for operator, model, and routing details .