sensors Mode-S transponder
A6C044
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N534LA · BOEING 767-300 · operated by CHIRIHUE LEASING TRUST
- Hex
- A6C044
- Octal
- 51540104
- Decimal
- 10,928,196
- Country
- US
- Tail
- N534LA
- Type
- B763
- Flights observed
- 238
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address A6C044 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 |
|---|---|---|---|
| LAE1828 | LATAM Cargo Colombia | 12 | 2026-06-05 |
| LAE1820 | LATAM Cargo Colombia | 7 | 2026-06-12 |
| LAE1801 | - | 7 | 2026-07-09 |
| LNE327 | LATAM Airlines Ecuador | 5 | 2026-05-07 |
| LAE2874 | LATAM Cargo Colombia | 5 | 2026-06-23 |
| LAE2538 | LATAM Cargo Colombia | 5 | 2026-06-10 |
| LAE2504 | - | 5 | 2026-06-24 |
| LAE1814 | LATAM Cargo Colombia | 5 | 2026-05-02 |
| LAE1812 | LATAM Cargo Colombia | 5 | 2026-05-30 |
| LAE1808 | LATAM Cargo Colombia | 5 | 2026-06-20 |
| LAE1802 | - | 5 | 2026-07-09 |
| LCO3617 | LAN Cargo | 4 | 2026-04-13 |
| LCO3614 | - | 4 | 2026-07-03 |
| LCO1517 | LAN Cargo | 4 | 2026-04-20 |
| LCO1513 | LAN Cargo | 4 | 2026-05-21 |
| LAE2873 | LATAM Cargo Colombia | 4 | 2026-06-09 |
| LAE2510 | - | 4 | 2026-06-27 |
| LAE2503 | LATAM Cargo Colombia | 4 | 2026-06-08 |
| LAE1817 | LATAM Cargo Colombia | 4 | 2026-06-19 |
| LNE518 | LATAM Airlines Ecuador | 3 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | LNE119 | - | Jul 13, 07:30 UTC | Jul 13, 09:05 UTC | 1h 35m |
| 2026-07-12 | LCO1501 | - | Jul 12, 13:20 UTC | Jul 12, 18:30 UTC | 5h 10m |
| 2026-07-12 | LCO1516 | - | Jul 12, 04:20 UTC | Jul 12, 07:25 UTC | 3h 5m |
| 2026-07-11 | LCO1516 | - | Jul 11, 11:50 UTC | Jul 12, 02:55 UTC | 15h 5m |
| 2026-07-11 | LCO1516 | BRU → FRA | Jul 11, 09:30 UTC | Jul 11, 10:05 UTC | 35m |
| 2026-07-10 | LCO1506 | MIA → BRU | Jul 10, 23:00 UTC | Jul 11, 07:50 UTC | 8h 50m |
| 2026-07-09 | LAE1802 | - | Jul 9, 17:20 UTC | Jul 9, 22:45 UTC | 5h 25m |
| 2026-07-09 | LAE1801 | - | Jul 9, 13:40 UTC | Jul 9, 15:55 UTC | 2h 15m |
| 2026-07-09 | LNE319 | MIA → UIO | Jul 9, 01:30 UTC | Jul 9, 08:35 UTC | 7h 5m |
| 2026-07-08 | LNE319 | MIA → UIO | Jul 8, 18:10 UTC | Jul 8, 23:05 UTC | 4h 55m |
| 2026-07-07 | LCO3611 | - | Jul 7, 10:00 UTC | Jul 8, 00:35 UTC | 14h 35m |
| 2026-07-07 | LCO3611 | - | Jul 7, 07:10 UTC | Jul 7, 07:35 UTC | 25m |
| 2026-07-06 | LCO3611 | - | Jul 6, 14:45 UTC | Jul 7, 04:35 UTC | 13h 50m |
| 2026-07-06 | LCO3601 | - | Jul 6, 04:30 UTC | Jul 6, 12:55 UTC | 8h 25m |
| 2026-07-05 | LCO1612 | - | Jul 5, 14:00 UTC | Jul 6, 00:50 UTC | 10h 50m |
| 2026-07-05 | LCO1611 | - | Jul 5, 09:30 UTC | Jul 5, 11:00 UTC | 1h 30m |
| 2026-07-04 | LCO1611 | - | Jul 4, 23:00 UTC | Jul 5, 06:15 UTC | 7h 15m |
| 2026-07-04 | LNE617 | - | Jul 4, 07:05 UTC | Jul 4, 19:55 UTC | 12h 50m |
| 2026-07-03 | LCO3614 | - | Jul 3, 07:40 UTC | Jul 4, 01:00 UTC | 17h 20m |
| 2026-07-03 | LCO3614 | - | Jul 3, 03:20 UTC | Jul 3, 05:55 UTC | 2h 35m |
| 2026-07-02 | LCO3614 | - | Jul 2, 11:20 UTC | Jul 3, 00:40 UTC | 13h 20m |
| 2026-07-02 | LCO3614 | BRU → BRU | Jul 2, 11:00 UTC | Jul 2, 11:05 UTC | 5m |
| 2026-07-02 | LCO3604 | - | Jul 2, 00:20 UTC | Jul 2, 08:50 UTC | 8h 30m |
| 2026-07-01 | LCO3604 | - | Jul 1, 19:00 UTC | Jul 1, 19:30 UTC | 30m |
| 2026-06-30 | LNE518 | GYE → MIA | Jun 30, 21:30 UTC | Jul 1, 19:30 UTC | 22h 0m |
| 2026-06-30 | LNE518 | GYE → MIA | Jun 30, 19:10 UTC | Jul 1, 19:00 UTC | 23h 50m |
| 2026-06-30 | LNE518 | GYE → MIA | Jun 30, 17:45 UTC | Jun 30, 22:20 UTC | 4h 35m |
| 2026-06-30 | LAE2518 | - | Jun 30, 15:10 UTC | Jun 30, 15:30 UTC | 20m |
| 2026-06-30 | LAE2518 | - | Jun 30, 11:40 UTC | Jun 30, 13:45 UTC | 2h 5m |
| 2026-06-30 | LAE2518 | - | Jun 30, 01:40 UTC | Jun 30, 10:10 UTC | 8h 30m |
| 2026-06-29 | LAE2851 | - | Jun 29, 18:05 UTC | Jun 29, 18:34 UTC | 30m |
| 2026-06-29 | LAE2851 | - | Jun 29, 08:04 UTC | Jun 29, 12:39 UTC | 4h 35m |
| 2026-06-28 | LAE2851 | - | Jun 28, 22:34 UTC | Jun 29, 05:59 UTC | 7h 25m |
| 2026-06-28 | LAE1804 | - | Jun 28, 16:49 UTC | Jun 28, 19:04 UTC | 2h 15m |
| 2026-06-28 | LAE1803 | - | Jun 28, 10:04 UTC | Jun 28, 15:24 UTC | 5h 20m |
| 2026-06-27 | LAE2510 | - | Jun 27, 12:34 UTC | Jun 28, 02:05 UTC | 13h 30m |
| 2026-06-26 | LAE2510 | - | Jun 26, 18:20 UTC | Jun 27, 09:09 UTC | 14h 50m |
| 2026-06-26 | LAE1810 | MIA → UIO | Jun 26, 05:19 UTC | Jun 26, 13:55 UTC | 8h 35m |
| 2026-06-25 | LAE1802 | GUA → MIA | Jun 25, 17:05 UTC | Jun 25, 19:20 UTC | 2h 15m |
| 2026-06-25 | LAE1801 | - | Jun 25, 10:04 UTC | Jun 25, 15:44 UTC | 5h 40m |
| 2026-06-24 | LAE2504 | - | Jun 24, 18:39 UTC | Jun 24, 19:15 UTC | 35m |
| 2026-06-24 | LAE2549 | - | Jun 24, 08:14 UTC | Jun 24, 13:05 UTC | 4h 50m |
| 2026-06-23 | LAE2874 | BOG → MIA | Jun 23, 23:50 UTC | Jun 24, 00:15 UTC | 25m |
| 2026-06-23 | LAE2874 | BOG → MIA | Jun 23, 13:15 UTC | Jun 23, 21:10 UTC | 7h 55m |
| 2026-06-22 | LNE119 | MIA → GYE | Jun 22, 15:50 UTC | Jun 23, 04:05 UTC | 12h 15m |
| 2026-06-22 | LCO3603 | MIA → BRU | Jun 22, 02:34 UTC | Jun 22, 12:49 UTC | 10h 15m |
| 2026-06-21 | LAE2536 | - | Jun 21, 14:10 UTC | Jun 21, 14:30 UTC | 20m |
| 2026-06-20 | LAE2533 | MVD → SCL | Jun 20, 18:24 UTC | Jun 21, 09:55 UTC | 15h 30m |
| 2026-06-20 | LAE1808 | BOG → MIA | Jun 20, 14:39 UTC | Jun 20, 15:19 UTC | 40m |
| 2026-06-20 | LAE1807 | MIA → BOG | Jun 20, 06:39 UTC | Jun 20, 07:04 UTC | 25m |
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 N534LA page for operator, model, and routing details .