sensors Mode-S transponder
0D09C8
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-PFL · EMBRAER ERJ-145
- Hex
- 0D09C8
- Octal
- 03204710
- Decimal
- 854,472
- Country
- MX
- Tail
- XA-PFL
- Type
- E145
- Flights observed
- 65
- Distinct callsigns
- 14
- Country
- MX
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 0D09C8 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LCT803 | Compania De Actividades Y Servicios De Aviacion | 12 | 2026-05-21 |
| LCT802 | - | 11 | 2026-05-21 |
| LCT824 | Compania De Actividades Y Servicios De Aviacion | 7 | 2026-05-20 |
| LCT815 | Compania De Actividades Y Servicios De Aviacion | 6 | 2026-05-19 |
| LCT814 | Compania De Actividades Y Servicios De Aviacion | 6 | 2026-05-21 |
| LCT839 | Compania De Actividades Y Servicios De Aviacion | 5 | 2026-05-20 |
| LCT825 | - | 4 | 2026-05-18 |
| LCT407 | Compania De Actividades Y Servicios De Aviacion | 4 | 2026-05-22 |
| LCT840 | Compania De Actividades Y Servicios De Aviacion | 2 | 2026-05-08 |
| LCT836 | Compania De Actividades Y Servicios De Aviacion | 2 | 2026-06-02 |
| LCT807 | Compania De Actividades Y Servicios De Aviacion | 2 | 2026-05-13 |
| LCT806 | Compania De Actividades Y Servicios De Aviacion | 2 | 2026-05-13 |
| LCT9110 | - | 1 | 2026-05-10 |
| LCT6901 | - | 1 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | LCT836 | HMO → CUU | Jun 2, 15:45 UTC | Jun 2, 15:55 UTC | 10m |
| 2026-05-22 | LCT407 | ACA → QRO | May 22, 03:40 UTC | May 22, 03:55 UTC | 15m |
| 2026-05-21 | LCT803 | LAP → HMO | May 21, 21:25 UTC | May 22, 02:45 UTC | 5h 20m |
| 2026-05-21 | LCT803 | LAP → HMO | May 21, 18:15 UTC | May 21, 20:50 UTC | 2h 35m |
| 2026-05-21 | LCT802 | - | May 21, 16:45 UTC | May 21, 17:40 UTC | 55m |
| 2026-05-21 | LCT814 | TRC → CJS | May 21, 03:05 UTC | May 21, 16:10 UTC | 13h 5m |
| 2026-05-20 | LCT824 | TRC → QRO | May 20, 23:50 UTC | May 21, 00:00 UTC | 10m |
| 2026-05-20 | LCT839 | CUL → CUU | May 20, 18:15 UTC | May 20, 23:20 UTC | 5h 5m |
| 2026-05-19 | LCT815 | CJS → TRC | May 19, 22:40 UTC | May 19, 23:10 UTC | 30m |
| 2026-05-19 | LCT803 | LAP → HMO | May 19, 21:15 UTC | May 19, 22:00 UTC | 45m |
| 2026-05-19 | LCT803 | LAP → HMO | May 19, 18:05 UTC | May 19, 20:35 UTC | 2h 30m |
| 2026-05-19 | LCT802 | - | May 19, 16:40 UTC | May 19, 17:30 UTC | 50m |
| 2026-05-19 | LCT814 | TRC → CJS | May 19, 02:40 UTC | May 19, 15:50 UTC | 13h 10m |
| 2026-05-18 | LCT824 | TRC → QRO | May 18, 23:45 UTC | May 18, 23:55 UTC | 10m |
| 2026-05-18 | LCT839 | CUL → CUU | May 18, 17:50 UTC | May 18, 23:05 UTC | 5h 14m |
| 2026-05-18 | LCT825 | - | May 18, 17:00 UTC | May 18, 17:10 UTC | 10m |
| 2026-05-16 | LCT815 | CJS → TRC | May 16, 22:40 UTC | May 17, 00:40 UTC | 2h 0m |
| 2026-05-16 | LCT802 | - | May 16, 21:15 UTC | May 16, 22:05 UTC | 50m |
| 2026-05-16 | LCT802 | - | May 16, 16:35 UTC | May 16, 17:25 UTC | 50m |
| 2026-05-15 | LCT814 | TRC → CJS | May 15, 18:10 UTC | May 16, 15:55 UTC | 21h 46m |
| 2026-05-14 | LCT836 | HMO → CUU | May 14, 23:25 UTC | May 14, 23:35 UTC | 10m |
| 2026-05-13 | LCT806 | HMO → LAP | May 13, 17:25 UTC | May 13, 17:45 UTC | 20m |
| 2026-05-13 | LCT807 | LAP → HMO | May 13, 16:25 UTC | May 13, 16:50 UTC | 25m |
| 2026-05-11 | LCT806 | HMO → LAP | May 11, 19:50 UTC | May 11, 20:20 UTC | 30m |
| 2026-05-11 | LCT807 | LAP → HMO | May 11, 18:45 UTC | May 11, 19:15 UTC | 30m |
| 2026-05-10 | LCT824 | TRC → QRO | May 10, 22:15 UTC | May 10, 22:25 UTC | 10m |
| 2026-05-10 | LCT825 | - | May 10, 19:35 UTC | May 10, 19:45 UTC | 10m |
| 2026-05-10 | LCT9110 | - | May 10, 14:34 UTC | May 10, 14:49 UTC | 15m |
| 2026-05-09 | LCT6901 | - | May 9, 16:00 UTC | May 9, 16:15 UTC | 15m |
| 2026-05-08 | LCT824 | TRC → QRO | May 8, 23:45 UTC | May 9, 00:00 UTC | 15m |
| 2026-05-08 | LCT840 | CUL → HMO | May 8, 22:45 UTC | May 8, 23:05 UTC | 20m |
| 2026-05-08 | LCT839 | CUL → CUU | May 8, 17:50 UTC | May 8, 18:10 UTC | 20m |
| 2026-05-08 | LCT825 | - | May 8, 17:00 UTC | May 8, 17:10 UTC | 10m |
| 2026-05-08 | LCT407 | ACA → QRO | May 8, 03:24 UTC | May 8, 03:39 UTC | 15m |
| 2026-05-07 | LCT815 | CJS → TRC | May 7, 22:25 UTC | May 8, 02:35 UTC | 4h 9m |
| 2026-05-07 | LCT803 | LAP → HMO | May 7, 21:05 UTC | May 7, 21:50 UTC | 45m |
| 2026-05-07 | LCT802 | - | May 7, 18:10 UTC | May 7, 20:30 UTC | 2h 20m |
| 2026-05-07 | LCT802 | - | May 7, 16:40 UTC | May 7, 17:35 UTC | 55m |
| 2026-05-07 | LCT814 | TRC → CJS | May 7, 02:50 UTC | May 7, 15:50 UTC | 13h 0m |
| 2026-05-06 | LCT824 | TRC → QRO | May 6, 23:40 UTC | May 6, 23:55 UTC | 15m |
| 2026-05-06 | LCT839 | CUL → CUU | May 6, 17:50 UTC | May 6, 23:10 UTC | 5h 20m |
| 2026-05-06 | LCT815 | CJS → TRC | May 6, 01:40 UTC | May 6, 02:15 UTC | 35m |
| 2026-05-06 | LCT803 | LAP → HMO | May 6, 00:40 UTC | May 6, 01:01 UTC | 20m |
| 2026-05-05 | LCT803 | LAP → HMO | May 5, 03:00 UTC | May 6, 01:01 UTC | 22h 0m |
| 2026-05-04 | LCT824 | TRC → QRO | May 4, 23:55 UTC | May 5, 00:10 UTC | 15m |
| 2026-05-04 | LCT840 | CUL → HMO | May 4, 23:05 UTC | May 4, 23:20 UTC | 15m |
| 2026-05-04 | LCT839 | CUL → CUU | May 4, 17:55 UTC | May 4, 18:25 UTC | 30m |
| 2026-05-03 | LCT802 | - | May 3, 20:15 UTC | May 3, 20:35 UTC | 20m |
| 2026-05-03 | LCT802 | - | May 3, 18:34 UTC | May 3, 19:34 UTC | 1h 0m |
| 2026-05-03 | LCT803 | LAP → HMO | May 3, 17:10 UTC | May 3, 17:54 UTC | 45m |
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-PFL page for operator, model, and routing details .