sensors Mode-S transponder
A6CF20
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N538LA · BOEING 767-300 · operated by QUETRO AIRCRAFT LEASING TRUST
- Hex
- A6CF20
- Octal
- 51547440
- Decimal
- 10,932,000
- Country
- US
- Tail
- N538LA
- Type
- B763
- Flights observed
- 175
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 21m ago
Last known position
Country allocation
The ICAO 24-bit address A6CF20 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 |
|---|---|---|---|
| LAE1803 | - | 9 | 2026-07-12 |
| LCO1514 | LAN Cargo | 8 | 2026-05-22 |
| LAE1804 | - | 7 | 2026-07-13 |
| LCO1771 | LAN Cargo | 6 | 2026-05-25 |
| LCO1517 | LAN Cargo | 6 | 2026-06-01 |
| LAE2530 | - | 6 | 2026-07-14 |
| LAE2502 | LATAM Cargo Colombia | 6 | 2026-04-18 |
| LCO3611 | LAN Cargo | 5 | 2026-05-13 |
| LCO1614 | - | 5 | 2026-04-16 |
| LCO1513 | - | 4 | 2026-07-09 |
| LCO1402 | LAN Cargo | 4 | 2026-05-11 |
| LCO1731 | LAN Cargo | 3 | 2026-05-28 |
| LCO1507 | LAN Cargo | 3 | 2026-05-31 |
| LAE2838 | - | 3 | 2026-07-05 |
| LAE2833 | LATAM Cargo Colombia | 3 | 2026-04-15 |
| LAE2505 | LATAM Cargo Colombia | 3 | 2026-05-12 |
| LAE1820 | LATAM Cargo Colombia | 3 | 2026-05-27 |
| LNE519 | LATAM Airlines Ecuador | 2 | 2026-05-08 |
| LCO3607 | LAN Cargo | 2 | 2026-05-23 |
| LCO1902 | - | 2 | 2026-07-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | LAE2530 | - | Jul 14, 00:15 UTC | Jul 14, 08:00 UTC | 7h 45m |
| 2026-07-13 | LAE1804 | - | Jul 13, 02:35 UTC | Jul 13, 04:45 UTC | 2h 10m |
| 2026-07-12 | LAE1803 | SJO → GUA | Jul 12, 22:35 UTC | Jul 13, 00:01 UTC | 1h 25m |
| 2026-07-12 | LAE1803 | - | Jul 12, 18:45 UTC | Jul 12, 21:10 UTC | 2h 25m |
| 2026-07-12 | LNE620 | - | Jul 12, 09:50 UTC | Jul 12, 11:50 UTC | 2h 0m |
| 2026-07-12 | LNE619 | - | Jul 12, 00:45 UTC | Jul 12, 03:35 UTC | 2h 50m |
| 2026-07-11 | LNE618 | - | Jul 11, 11:05 UTC | Jul 11, 22:20 UTC | 11h 15m |
| 2026-07-11 | LAE1834 | - | Jul 11, 05:05 UTC | Jul 11, 08:20 UTC | 3h 15m |
| 2026-07-11 | LAE1833 | - | Jul 11, 00:10 UTC | Jul 11, 02:50 UTC | 2h 40m |
| 2026-07-10 | LNE513 | - | Jul 10, 07:00 UTC | Jul 10, 19:15 UTC | 12h 15m |
| 2026-07-09 | LCO1602 | UIO → MIA | Jul 9, 15:40 UTC | Jul 9, 20:55 UTC | 5h 15m |
| 2026-07-09 | LCO1602 | UIO → MIA | Jul 9, 12:45 UTC | Jul 9, 12:55 UTC | 10m |
| 2026-07-09 | LCO1513 | - | Jul 9, 07:35 UTC | Jul 9, 09:00 UTC | 1h 25m |
| 2026-07-09 | LCO1513 | - | Jul 9, 04:25 UTC | Jul 9, 06:40 UTC | 2h 15m |
| 2026-07-08 | LCO1513 | - | Jul 8, 12:05 UTC | Jul 9, 02:45 UTC | 14h 40m |
| 2026-07-08 | LCO1513 | BRU → FRA | Jul 8, 10:00 UTC | Jul 8, 10:40 UTC | 40m |
| 2026-07-07 | LCO1503 | - | Jul 7, 23:35 UTC | Jul 8, 08:25 UTC | 8h 50m |
| 2026-07-07 | LNE226 | - | Jul 7, 08:50 UTC | Jul 7, 21:00 UTC | 12h 10m |
| 2026-07-06 | LAE1804 | - | Jul 6, 06:20 UTC | Jul 6, 11:25 UTC | 5h 5m |
| 2026-07-06 | LAE1803 | - | Jul 6, 02:35 UTC | Jul 6, 04:55 UTC | 2h 20m |
| 2026-07-05 | LAE2838 | - | Jul 5, 05:35 UTC | Jul 5, 16:15 UTC | 10h 40m |
| 2026-07-05 | LAE2838 | - | Jul 5, 03:40 UTC | Jul 5, 04:00 UTC | 20m |
| 2026-07-04 | LAE2838 | - | Jul 4, 17:20 UTC | Jul 4, 21:00 UTC | 3h 40m |
| 2026-07-04 | LAE1808 | - | Jul 4, 10:25 UTC | Jul 4, 11:00 UTC | 35m |
| 2026-07-04 | LAE1807 | - | Jul 4, 02:35 UTC | Jul 4, 03:00 UTC | 25m |
| 2026-07-03 | LCO1902 | - | Jul 3, 13:40 UTC | Jul 3, 15:40 UTC | 2h 0m |
| 2026-07-02 | LCO538 | - | Jul 2, 16:25 UTC | Jul 2, 16:40 UTC | 15m |
| 2026-06-01 | LCO1517 | MIA → AMS | Jun 1, 09:55 UTC | Jun 1, 11:40 UTC | 1h 45m |
| 2026-05-31 | LCO1517 | MIA → AMS | May 31, 18:15 UTC | Jun 1, 08:05 UTC | 13h 50m |
| 2026-05-31 | LCO1517 | MIA → AMS | May 31, 15:30 UTC | May 31, 16:15 UTC | 45m |
| 2026-05-31 | LCO1507 | MIA → AMS | May 31, 12:15 UTC | May 31, 13:55 UTC | 1h 40m |
| 2026-05-30 | LCO1507 | MIA → AMS | May 30, 14:55 UTC | May 31, 13:55 UTC | 23h 0m |
| 2026-05-30 | LNE625 | MIA → PTY | May 30, 13:20 UTC | May 30, 15:00 UTC | 1h 40m |
| 2026-05-29 | LAE1804 | SJO → MIA | May 29, 12:50 UTC | May 29, 18:05 UTC | 5h 15m |
| 2026-05-29 | LAE1803 | MIA → GUA | May 29, 08:30 UTC | May 29, 10:50 UTC | 2h 20m |
| 2026-05-28 | LCO1731 | MIA → CFB | May 28, 16:45 UTC | May 29, 04:15 UTC | 11h 30m |
| 2026-05-28 | LCO1731 | MIA → CFB | May 28, 13:10 UTC | May 28, 15:25 UTC | 2h 15m |
| 2026-05-28 | LCO1731 | MIA → CFB | May 28, 03:40 UTC | May 28, 11:35 UTC | 7h 55m |
| 2026-05-28 | LAE2538 | BOG → MIA | May 28, 00:10 UTC | May 28, 00:40 UTC | 30m |
| 2026-05-27 | LAE2538 | BOG → MIA | May 27, 21:30 UTC | May 27, 21:45 UTC | 15m |
| 2026-05-27 | LAE1820 | BOG → MIA | May 27, 19:30 UTC | May 27, 19:40 UTC | 10m |
| 2026-05-27 | LAE1820 | BOG → MIA | May 27, 13:00 UTC | May 27, 18:00 UTC | 5h 0m |
| 2026-05-27 | LAE1820 | BOG → MIA | May 27, 05:04 UTC | May 27, 10:55 UTC | 5h 50m |
| 2026-05-25 | LCO1771 | MIA → VCP | May 25, 08:35 UTC | May 25, 12:40 UTC | 4h 5m |
| 2026-05-25 | LCO1771 | MIA → VCP | May 25, 05:25 UTC | May 25, 06:50 UTC | 1h 25m |
| 2026-05-24 | LCO1771 | MIA → VCP | May 24, 18:15 UTC | May 25, 03:40 UTC | 9h 25m |
| 2026-05-24 | LAE2534 | MIA → GRU | May 24, 10:40 UTC | May 24, 11:15 UTC | 35m |
| 2026-05-24 | LAE2534 | MIA → GRU | May 24, 08:05 UTC | May 24, 08:15 UTC | 10m |
| 2026-05-24 | LAE2533 | MVD → SCL | May 24, 03:25 UTC | May 24, 06:05 UTC | 2h 40m |
| 2026-05-23 | LAE2533 | MVD → SCL | May 23, 20:10 UTC | May 24, 01:00 UTC | 4h 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 N538LA page for operator, model, and routing details .