sensors Mode-S transponder
0D0F89
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-MBE · LEARJET 45
- Hex
- 0D0F89
- Octal
- 03207611
- Decimal
- 855,945
- Country
- MX
- Tail
- XA-MBE
- Type
- LJ45
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 1d ago
Current position
Country allocation
The ICAO 24-bit address 0D0F89 falls within the block assigned to Mexico (MX) by ICAO Annex 10, Volume III. Every aircraft registered in Mexico 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LET7892 | - | 2 | 2026-06-04 |
| LET7295 | - | 2 | 2026-05-03 |
| LET7291 | - | 2 | 2026-05-03 |
| LET7290 | - | 2 | 2026-05-03 |
| LET7192 | - | 2 | 2026-06-07 |
| LET7190 | - | 2 | 2026-05-04 |
| XAMBE | - | 1 | 2026-04-12 |
| LET7912 | - | 1 | 2026-04-23 |
| LET7893 | - | 1 | 2026-06-05 |
| LET7689 | - | 1 | 2026-05-06 |
| LET7645 | - | 1 | 2026-04-24 |
| LET7549 | - | 1 | 2026-06-02 |
| LET7452 | - | 1 | 2026-06-03 |
| LET7451 | - | 1 | 2026-06-03 |
| LET7450 | - | 1 | 2026-06-03 |
| LET7385 | - | 1 | 2026-04-30 |
| LET7384 | - | 1 | 2026-04-30 |
| LET7296 | - | 1 | 2026-05-03 |
| LET7294 | - | 1 | 2026-05-02 |
| LET7292 | - | 1 | 2026-05-01 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | LET7194 | - | Jun 7, 18:35 UTC | Jun 7, 19:55 UTC | 1h 20m |
| 2026-06-07 | LET7192 | - | Jun 7, 15:30 UTC | Jun 7, 16:45 UTC | 1h 15m |
| 2026-06-06 | LET7192 | - | Jun 6, 20:00 UTC | Jun 7, 16:45 UTC | 20h 45m |
| 2026-06-05 | LET7893 | - | Jun 5, 19:55 UTC | Jun 5, 21:30 UTC | 1h 35m |
| 2026-06-04 | LET7892 | - | Jun 4, 16:45 UTC | Jun 4, 18:10 UTC | 1h 25m |
| 2026-06-03 | LET7452 | - | Jun 3, 22:45 UTC | Jun 3, 23:15 UTC | 30m |
| 2026-06-03 | LET7451 | BFM → VER | Jun 3, 19:20 UTC | Jun 3, 21:30 UTC | 2h 10m |
| 2026-06-03 | LET7450 | - | Jun 3, 16:10 UTC | Jun 3, 18:30 UTC | 2h 20m |
| 2026-06-02 | LET7549 | - | Jun 2, 20:20 UTC | Jun 2, 22:55 UTC | 2h 35m |
| 2026-06-01 | LET7253 | - | Jun 1, 18:25 UTC | Jun 1, 21:20 UTC | 2h 55m |
| 2026-06-01 | LET7248 | - | Jun 1, 14:50 UTC | Jun 1, 15:20 UTC | 30m |
| 2026-05-06 | LET7892 | NTR → NTR | May 6, 19:20 UTC | May 6, 23:50 UTC | 4h 30m |
| 2026-05-06 | LET7689 | - | May 6, 13:20 UTC | May 6, 17:25 UTC | 4h 5m |
| 2026-05-05 | LET7170 | - | May 5, 01:10 UTC | May 5, 03:55 UTC | 2h 45m |
| 2026-05-04 | LET7244 | - | May 4, 22:20 UTC | May 4, 22:55 UTC | 35m |
| 2026-05-04 | LET7243 | - | May 4, 19:30 UTC | May 4, 20:30 UTC | 1h 0m |
| 2026-05-04 | LET7190 | - | May 4, 15:15 UTC | May 4, 15:40 UTC | 25m |
| 2026-05-04 | LET7190 | - | May 4, 13:10 UTC | May 4, 13:35 UTC | 25m |
| 2026-05-03 | LET7291 | - | May 3, 23:04 UTC | May 3, 23:25 UTC | 20m |
| 2026-05-03 | LET7290 | - | May 3, 21:24 UTC | May 3, 21:44 UTC | 20m |
| 2026-05-03 | LET7296 | - | May 3, 18:20 UTC | May 3, 18:55 UTC | 35m |
| 2026-05-03 | LET7295 | - | May 3, 16:09 UTC | May 3, 16:45 UTC | 35m |
| 2026-05-02 | LET7295 | - | May 2, 18:20 UTC | May 3, 16:45 UTC | 22h 24m |
| 2026-05-02 | LET7294 | - | May 2, 17:55 UTC | May 3, 16:15 UTC | 22h 19m |
| 2026-05-01 | LET7292 | - | May 1, 21:55 UTC | May 1, 22:20 UTC | 25m |
| 2026-05-01 | LET7291 | - | May 1, 18:00 UTC | May 1, 18:35 UTC | 35m |
| 2026-05-01 | LET7290 | - | May 1, 15:50 UTC | May 1, 16:20 UTC | 30m |
| 2026-04-30 | LET7385 | - | Apr 30, 18:45 UTC | Apr 30, 20:35 UTC | 1h 50m |
| 2026-04-30 | LET7384 | - | Apr 30, 15:50 UTC | Apr 30, 17:30 UTC | 1h 40m |
| 2026-04-24 | LET7645 | - | Apr 24, 16:40 UTC | Apr 24, 16:50 UTC | 10m |
| 2026-04-23 | LET7912 | - | Apr 23, 01:40 UTC | Apr 23, 01:50 UTC | 10m |
| 2026-04-21 | LET7217 | - | Apr 21, 18:30 UTC | Apr 21, 19:55 UTC | 1h 25m |
| 2026-04-16 | LET7216 | - | Apr 16, 19:15 UTC | Apr 16, 20:25 UTC | 1h 10m |
| 2026-04-12 | XAMBE | - | Apr 12, 18:30 UTC | Apr 12, 19:20 UTC | 50m |
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 XA-MBE page for operator, model, and routing details .