sensors Mode-S transponder
0D09B6
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-LPZ · BOMBARDIER CL-600 Challenger
- Hex
- 0D09B6
- Octal
- 03204666
- Decimal
- 854,454
- Country
- MX
- Tail
- XA-LPZ
- Type
- CL60
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 0D09B6 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 |
|---|---|---|---|
| LET6550 | - | 2 | 2026-07-07 |
| LET6160 | - | 2 | 2026-06-14 |
| XALPZ | - | 1 | 2026-06-17 |
| LET6930 | - | 1 | 2026-06-01 |
| LET6831 | - | 1 | 2026-07-08 |
| LET6830 | - | 1 | 2026-07-08 |
| LET6780 | - | 1 | 2026-07-05 |
| LET6611 | - | 1 | 2026-07-06 |
| LET6551 | - | 1 | 2026-07-07 |
| LET6547 | - | 1 | 2026-07-06 |
| LET6546 | - | 1 | 2026-07-06 |
| LET6537 | - | 1 | 2026-06-04 |
| LET6536 | - | 1 | 2026-06-04 |
| LET6527 | - | 1 | 2026-07-05 |
| LET6523 | - | 1 | 2026-07-05 |
| LET6476 | - | 1 | 2026-05-28 |
| LET6422 | - | 1 | 2026-06-10 |
| LET6280 | - | 1 | 2026-06-11 |
| LET6251 | - | 1 | 2026-06-01 |
| LET6250 | - | 1 | 2026-06-01 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | LET6123 | - | Jul 13, 19:40 UTC | Jul 13, 21:10 UTC | 1h 30m |
| 2026-07-12 | LET6121 | - | Jul 12, 21:15 UTC | Jul 13, 02:05 UTC | 4h 50m |
| 2026-07-08 | LET6831 | - | Jul 8, 20:30 UTC | Jul 8, 23:10 UTC | 2h 40m |
| 2026-07-08 | LET6830 | - | Jul 8, 15:55 UTC | Jul 8, 18:40 UTC | 2h 45m |
| 2026-07-07 | LET6551 | - | Jul 7, 22:10 UTC | Jul 7, 22:40 UTC | 30m |
| 2026-07-07 | LET6550 | - | Jul 7, 17:35 UTC | Jul 7, 18:05 UTC | 30m |
| 2026-07-06 | LET6550 | - | Jul 6, 23:25 UTC | Jul 7, 18:05 UTC | 18h 40m |
| 2026-07-06 | LET6547 | - | Jul 6, 20:35 UTC | Jul 6, 20:55 UTC | 20m |
| 2026-07-06 | LET6546 | - | Jul 6, 19:25 UTC | Jul 6, 19:50 UTC | 25m |
| 2026-07-06 | LET6611 | - | Jul 6, 17:05 UTC | Jul 6, 17:50 UTC | 45m |
| 2026-07-05 | LET6780 | - | Jul 5, 20:50 UTC | Jul 5, 21:15 UTC | 25m |
| 2026-07-05 | LET6527 | - | Jul 5, 19:00 UTC | Jul 5, 19:25 UTC | 25m |
| 2026-07-05 | LET6523 | NTR → LRD | Jul 5, 16:30 UTC | Jul 5, 17:00 UTC | 30m |
| 2026-07-03 | LET6207 | - | Jul 3, 23:40 UTC | Jul 4, 01:45 UTC | 2h 5m |
| 2026-07-03 | LET6206 | - | Jul 3, 19:15 UTC | Jul 3, 22:10 UTC | 2h 55m |
| 2026-07-03 | LET6205 | - | Jul 3, 16:30 UTC | Jul 3, 17:45 UTC | 1h 15m |
| 2026-06-26 | LET6190 | - | Jun 26, 17:15 UTC | Jun 26, 17:50 UTC | 35m |
| 2026-06-19 | LET6110 | - | Jun 19, 17:19 UTC | Jun 19, 17:44 UTC | 25m |
| 2026-06-17 | XALPZ | NTR → MTY | Jun 17, 18:50 UTC | Jun 17, 19:20 UTC | 30m |
| 2026-06-15 | LET6183 | - | Jun 15, 19:39 UTC | Jun 15, 20:50 UTC | 1h 10m |
| 2026-06-15 | LET6181 | - | Jun 15, 14:50 UTC | Jun 15, 16:15 UTC | 1h 25m |
| 2026-06-14 | LET6160 | - | Jun 14, 18:35 UTC | Jun 14, 19:00 UTC | 25m |
| 2026-06-11 | LET6280 | - | Jun 11, 23:50 UTC | Jun 12, 01:05 UTC | 1h 16m |
| 2026-06-10 | LET6422 | - | Jun 10, 19:40 UTC | Jun 10, 20:05 UTC | 25m |
| 2026-06-07 | LET6216 | - | Jun 7, 22:25 UTC | Jun 7, 23:10 UTC | 45m |
| 2026-06-06 | LET6037 | - | Jun 6, 22:39 UTC | Jun 6, 23:15 UTC | 35m |
| 2026-06-06 | LET6036 | NTR → LRD | Jun 6, 21:40 UTC | Jun 6, 22:10 UTC | 30m |
| 2026-06-06 | LET6035 | - | Jun 6, 18:50 UTC | Jun 6, 19:14 UTC | 25m |
| 2026-06-06 | LET6034 | - | Jun 6, 17:15 UTC | Jun 6, 17:40 UTC | 25m |
| 2026-06-06 | LET6033 | - | Jun 6, 15:44 UTC | Jun 6, 16:14 UTC | 30m |
| 2026-06-05 | LET6032 | - | Jun 5, 22:45 UTC | Jun 5, 23:00 UTC | 15m |
| 2026-06-04 | LET6537 | - | Jun 4, 21:55 UTC | Jun 4, 22:35 UTC | 40m |
| 2026-06-04 | LET6536 | - | Jun 4, 16:45 UTC | Jun 4, 19:25 UTC | 2h 40m |
| 2026-06-01 | LET6251 | - | Jun 1, 15:50 UTC | Jun 1, 16:05 UTC | 15m |
| 2026-06-01 | LET6250 | - | Jun 1, 13:35 UTC | Jun 1, 13:50 UTC | 15m |
| 2026-06-01 | LET6930 | - | Jun 1, 00:15 UTC | Jun 1, 00:30 UTC | 15m |
| 2026-05-29 | LET6248 | - | May 29, 15:10 UTC | May 29, 15:20 UTC | 10m |
| 2026-05-29 | LE76477 | - | May 29, 00:20 UTC | May 29, 01:20 UTC | 1h 0m |
| 2026-05-28 | LET6476 | - | May 28, 20:40 UTC | May 28, 21:50 UTC | 1h 10m |
| 2026-05-27 | LET6075 | - | May 27, 15:55 UTC | May 27, 16:55 UTC | 1h 0m |
| 2026-05-27 | LET6074 | - | May 27, 14:00 UTC | May 27, 15:20 UTC | 1h 20m |
| 2026-05-26 | LET6160 | - | May 26, 16:15 UTC | May 26, 17:20 UTC | 1h 5m |
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-LPZ page for operator, model, and routing details .