sensors Mode-S transponder
71C366
ICAO 24-bit transponder address · allocated to Korea, South
Currently assigned to HL8366 · AIRBUS A-321neo
- Hex
- 71C366
- Octal
- 34341546
- Decimal
- 7,455,590
- Country
- KR
- Tail
- HL8366
- Type
- A21N
- Flights observed
- 120
- Distinct callsigns
- 20
- Country
- KR
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 71C366 falls within the block assigned to Korea, South (KR) by ICAO Annex 10, Volume III. Every aircraft registered in Korea, South 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 |
|---|---|---|---|
| ABL602 | Air Busan | 11 | 2026-05-25 |
| ABL601 | Air Busan | 11 | 2026-05-11 |
| ABL725 | Air Busan | 8 | 2026-05-15 |
| ABL181 | Air Busan | 8 | 2026-05-10 |
| ABL8803 | Air Busan | 6 | 2026-05-26 |
| ABL726 | Air Busan | 6 | 2026-05-15 |
| ABL1635 | Air Busan | 6 | 2026-05-11 |
| ABL8012 | Air Busan | 5 | 2026-05-26 |
| ABL793 | Air Busan | 5 | 2026-05-27 |
| ABL1645 | Air Busan | 5 | 2026-04-30 |
| ABL773 | Air Busan | 4 | 2026-05-07 |
| ABL795 | Air Busan | 3 | 2026-05-29 |
| ABL794 | Air Busan | 3 | 2026-05-27 |
| ABL711 | Air Busan | 3 | 2026-04-23 |
| ABL123 | Air Busan | 3 | 2026-05-23 |
| ABL782 | Air Busan | 2 | 2026-05-29 |
| ABL781 | Air Busan | 2 | 2026-05-24 |
| ABL7315 | - | 2 | 2026-04-13 |
| ABL712 | Air Busan | 2 | 2026-04-16 |
| ABL702F | - | 2 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ABL782 | CXR → PUS | May 29, 06:25 UTC | May 29, 19:30 UTC | 13h 5m |
| 2026-05-29 | ABL795 | PUS → KHH | May 29, 04:10 UTC | May 29, 05:00 UTC | 50m |
| 2026-05-29 | ABL8873 | GMP → PUS | May 29, 00:35 UTC | May 29, 01:00 UTC | 25m |
| 2026-05-28 | ABL8040 | CJU → GMP | May 28, 01:30 UTC | May 28, 02:05 UTC | 35m |
| 2026-05-27 | ABL794 | TPE → PUS | May 27, 05:49 UTC | May 27, 21:40 UTC | 15h 50m |
| 2026-05-27 | ABL793 | PUS → TPE | May 27, 03:34 UTC | May 27, 04:04 UTC | 30m |
| 2026-05-26 | ABL8803 | GMP → PUS | May 26, 22:39 UTC | May 26, 23:10 UTC | 30m |
| 2026-05-26 | ABL8012 | CJU → GMP | May 26, 11:24 UTC | May 26, 12:05 UTC | 40m |
| 2026-05-25 | ABL602 | DPS → PUS | May 25, 05:15 UTC | May 25, 21:30 UTC | 16h 14m |
| 2026-05-24 | ABL781 | PUS → CXR | May 24, 12:00 UTC | May 25, 03:55 UTC | 15h 55m |
| 2026-05-24 | ABL781 | PUS → CXR | May 24, 06:25 UTC | May 25, 03:55 UTC | 21h 30m |
| 2026-05-24 | ABL795 | PUS → KHH | May 24, 03:55 UTC | May 24, 04:55 UTC | 1h 0m |
| 2026-05-23 | ABL123 | KIX → PUS | May 23, 02:25 UTC | May 23, 03:00 UTC | 34m |
| 2026-05-22 | ABL782 | CXR → PUS | May 22, 06:30 UTC | May 23, 01:00 UTC | 18h 30m |
| 2026-05-22 | ABL795 | PUS → KHH | May 22, 03:10 UTC | May 22, 05:10 UTC | 2h 0m |
| 2026-05-21 | ABL803F | - | May 21, 20:55 UTC | May 21, 21:25 UTC | 30m |
| 2026-05-19 | ABL702F | - | May 19, 12:45 UTC | May 19, 13:10 UTC | 25m |
| 2026-05-19 | ABL702F | - | May 19, 10:50 UTC | May 19, 11:35 UTC | 45m |
| 2026-05-16 | ABL791 | PUS → TPE | May 16, 02:20 UTC | May 16, 08:16 UTC | 5h 56m |
| 2026-05-15 | ABL726 | BKK → PUS | May 15, 16:20 UTC | May 16, 00:55 UTC | 8h 35m |
| 2026-05-15 | ABL725 | PUS → BKK | May 15, 05:35 UTC | May 15, 14:20 UTC | 8h 45m |
| 2026-05-15 | ABL793 | PUS → TPE | May 15, 03:15 UTC | May 15, 04:00 UTC | 45m |
| 2026-05-14 | - | - | May 14, 18:25 UTC | May 14, 18:35 UTC | 10m |
| 2026-05-14 | ABL794 | TPE → PUS | May 14, 05:40 UTC | May 14, 06:05 UTC | 25m |
| 2026-05-14 | ABL793 | PUS → TPE | May 14, 03:20 UTC | May 14, 03:50 UTC | 30m |
| 2026-05-13 | ABL602 | DPS → PUS | May 13, 08:30 UTC | May 13, 21:35 UTC | 13h 5m |
| 2026-05-13 | ABL337 | PUS → YNJ | May 13, 01:00 UTC | May 13, 06:40 UTC | 5h 40m |
| 2026-05-12 | ABL8803 | GMP → PUS | May 12, 22:40 UTC | May 12, 23:10 UTC | 30m |
| 2026-05-12 | ABL8012 | CJU → GMP | May 12, 11:05 UTC | May 12, 11:50 UTC | 45m |
| 2026-05-11 | ABL601 | PUS → DPS | May 11, 08:25 UTC | May 11, 21:55 UTC | 13h 31m |
| 2026-05-11 | ABL1635 | FSZ → PUS | May 11, 03:05 UTC | May 11, 04:00 UTC | 55m |
| 2026-05-10 | ABL601 | PUS → DPS | May 10, 08:25 UTC | May 11, 01:25 UTC | 17h 0m |
| 2026-05-10 | ABL181 | CTS → PUS | May 10, 03:45 UTC | May 10, 05:34 UTC | 1h 50m |
| 2026-05-09 | ABL182 | PUS → CTS | May 9, 16:15 UTC | May 10, 02:30 UTC | 10h 15m |
| 2026-05-08 | ABL725 | PUS → BKK | May 8, 19:35 UTC | May 9, 14:40 UTC | 19h 5m |
| 2026-05-08 | ABL725 | PUS → BKK | May 8, 18:10 UTC | May 9, 14:40 UTC | 20h 30m |
| 2026-05-08 | ABL602 | DPS → PUS | May 8, 11:34 UTC | May 9, 11:30 UTC | 23h 55m |
| 2026-05-08 | ABL601 | PUS → DPS | May 8, 08:24 UTC | May 9, 00:50 UTC | 16h 25m |
| 2026-05-08 | ABL1635 | FSZ → PUS | May 8, 03:04 UTC | May 8, 04:04 UTC | 1h 0m |
| 2026-05-07 | ABL773 | PUS → DAD | May 7, 12:15 UTC | May 8, 01:24 UTC | 13h 9m |
| 2026-05-07 | ABL181 | CTS → PUS | May 7, 03:40 UTC | May 7, 05:30 UTC | 1h 50m |
| 2026-05-06 | ABL602 | DPS → PUS | May 6, 09:25 UTC | May 7, 02:10 UTC | 16h 44m |
| 2026-05-06 | ABL321 | PUS → TAO | May 6, 01:45 UTC | May 6, 06:00 UTC | 4h 15m |
| 2026-05-05 | ABL8803 | GMP → PUS | May 5, 22:35 UTC | May 5, 23:00 UTC | 25m |
| 2026-05-05 | ABL8012 | CJU → GMP | May 5, 11:00 UTC | May 5, 11:45 UTC | 45m |
| 2026-05-05 | ABL181 | CTS → PUS | May 5, 03:55 UTC | May 5, 05:40 UTC | 1h 45m |
| 2026-05-04 | ABL601 | PUS → DPS | May 4, 08:25 UTC | May 5, 02:15 UTC | 17h 51m |
| 2026-05-04 | ABL601 | PUS → DPS | May 4, 03:35 UTC | May 5, 02:15 UTC | 22h 41m |
| 2026-05-04 | ABL601 | PUS → DPS | May 4, 03:05 UTC | May 5, 01:25 UTC | 22h 21m |
| 2026-05-03 | ABL602 | DPS → PUS | May 3, 08:25 UTC | May 4, 01:24 UTC | 17h 0m |
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 HL8366 page for operator, model, and routing details .