sensors Mode-S transponder
71C078
ICAO 24-bit transponder address · allocated to Korea, South
Currently assigned to HL8078 · AIRBUS A-350-900
- Hex
- 71C078
- Octal
- 34340170
- Decimal
- 7,454,840
- Country
- KR
- Tail
- HL8078
- Type
- A359
- Flights observed
- 232
- Distinct callsigns
- 20
- Country
- KR
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 71C078 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 |
|---|---|---|---|
| AAR546 | - | 15 | 2026-06-19 |
| AAR512 | Asiana Airlines | 14 | 2026-07-05 |
| AAR545 | - | 12 | 2026-06-18 |
| AAR521 | Asiana Airlines | 11 | 2026-06-20 |
| AAR511 | - | 10 | 2026-07-04 |
| AAR548 | - | 9 | 2026-07-13 |
| AAR547 | - | 9 | 2026-07-12 |
| AAR522 | - | 9 | 2026-06-21 |
| AAR742 | - | 7 | 2026-07-05 |
| AAR741 | - | 7 | 2026-07-05 |
| AAR211 | Asiana Airlines | 7 | 2026-05-16 |
| AAR761 | Asiana Airlines | 6 | 2026-05-10 |
| AAR752 | - | 6 | 2026-07-13 |
| AAR751 | - | 6 | 2026-07-13 |
| AAR212 | Asiana Airlines | 6 | 2026-05-15 |
| AAR133 | - | 6 | 2026-06-21 |
| AAR111 | - | 6 | 2026-07-09 |
| AAR733 | - | 5 | 2026-06-26 |
| AAR204 | - | 5 | 2026-07-10 |
| AAR203 | - | 5 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AAR561 | - | Jul 14, 06:00 UTC | Jul 14, 06:20 UTC | 20m |
| 2026-07-14 | AAR561 | - | Jul 14, 04:50 UTC | Jul 14, 05:10 UTC | 20m |
| 2026-07-13 | AAR752 | - | Jul 13, 18:15 UTC | Jul 13, 21:20 UTC | 3h 5m |
| 2026-07-13 | AAR752 | - | Jul 13, 15:05 UTC | Jul 13, 15:15 UTC | 10m |
| 2026-07-13 | AAR751 | - | Jul 13, 07:35 UTC | Jul 13, 13:05 UTC | 5h 30m |
| 2026-07-13 | AAR548 | - | Jul 13, 03:50 UTC | Jul 13, 04:15 UTC | 25m |
| 2026-07-12 | AAR548 | - | Jul 12, 18:15 UTC | Jul 13, 02:55 UTC | 8h 40m |
| 2026-07-12 | AAR547 | - | Jul 12, 05:10 UTC | Jul 12, 15:55 UTC | 10h 45m |
| 2026-07-12 | AAR547 | - | Jul 12, 04:01 UTC | Jul 12, 04:20 UTC | 20m |
| 2026-07-11 | AAR203 | - | Jul 11, 06:30 UTC | Jul 11, 18:35 UTC | 12h 5m |
| 2026-07-10 | AAR204 | - | Jul 10, 13:10 UTC | Jul 11, 00:10 UTC | 11h 0m |
| 2026-07-10 | AAR582 | - | Jul 10, 06:35 UTC | Jul 10, 07:00 UTC | 25m |
| 2026-07-09 | AAR582 | - | Jul 9, 20:35 UTC | Jul 10, 05:45 UTC | 9h 10m |
| 2026-07-09 | AAR581 | - | Jul 9, 06:50 UTC | Jul 9, 18:35 UTC | 11h 45m |
| 2026-07-09 | AAR581 | - | Jul 9, 05:35 UTC | Jul 9, 05:50 UTC | 15m |
| 2026-07-09 | AAR111 | KIX → ICN | Jul 9, 01:55 UTC | Jul 9, 03:15 UTC | 1h 20m |
| 2026-07-08 | AAR112 | ICN → KIX | Jul 8, 22:15 UTC | Jul 8, 23:35 UTC | 1h 20m |
| 2026-07-08 | AAR203 | - | Jul 8, 06:50 UTC | Jul 8, 19:05 UTC | 12h 15m |
| 2026-07-07 | AAR204 | - | Jul 7, 13:15 UTC | Jul 8, 00:10 UTC | 10h 55m |
| 2026-07-07 | AAR101 | - | Jul 7, 04:10 UTC | Jul 7, 06:05 UTC | 1h 55m |
| 2026-07-06 | AAR102 | ICN → NRT | Jul 6, 23:50 UTC | Jul 7, 01:55 UTC | 2h 5m |
| 2026-07-06 | AAR752 | SIN → ICN | Jul 6, 18:10 UTC | Jul 6, 21:20 UTC | 3h 10m |
| 2026-07-06 | AAR751 | - | Jul 6, 12:50 UTC | Jul 6, 13:10 UTC | 20m |
| 2026-07-06 | AAR751 | - | Jul 6, 07:45 UTC | Jul 6, 10:25 UTC | 2h 40m |
| 2026-07-05 | AAR742 | - | Jul 5, 19:00 UTC | Jul 6, 00:00 UTC | 5h 0m |
| 2026-07-05 | AAR741 | ICN → BKK | Jul 5, 11:00 UTC | Jul 5, 15:55 UTC | 4h 55m |
| 2026-07-05 | AAR512 | BCN → ICN | Jul 5, 06:10 UTC | Jul 5, 06:35 UTC | 25m |
| 2026-07-04 | AAR512 | BCN → ICN | Jul 4, 19:20 UTC | Jul 5, 05:20 UTC | 10h 0m |
| 2026-07-04 | AAR511 | - | Jul 4, 03:35 UTC | Jul 4, 16:50 UTC | 13h 15m |
| 2026-07-03 | AAR203 | - | Jul 3, 06:30 UTC | Jul 3, 19:05 UTC | 12h 35m |
| 2026-07-02 | AAR204 | - | Jul 2, 13:00 UTC | Jul 2, 23:15 UTC | 10h 15m |
| 2026-07-02 | AAR548 | - | Jul 2, 04:05 UTC | Jul 2, 04:25 UTC | 20m |
| 2026-07-01 | AAR548 | - | Jul 1, 18:20 UTC | Jul 1, 21:10 UTC | 2h 50m |
| 2026-07-01 | AAR547 | - | Jul 1, 04:20 UTC | Jul 1, 16:15 UTC | 11h 55m |
| 2026-06-30 | AAR742 | - | Jun 30, 18:45 UTC | Jun 30, 23:55 UTC | 5h 10m |
| 2026-06-30 | AAR741 | ICN → BKK | Jun 30, 11:25 UTC | Jun 30, 16:25 UTC | 5h 0m |
| 2026-06-30 | AAR512 | BCN → ICN | Jun 30, 06:40 UTC | Jun 30, 07:05 UTC | 25m |
| 2026-06-29 | AAR512 | BCN → ICN | Jun 29, 19:29 UTC | Jun 30, 05:50 UTC | 10h 21m |
| 2026-06-29 | AAR511 | - | Jun 29, 04:39 UTC | Jun 29, 16:55 UTC | 12h 15m |
| 2026-06-29 | AAR511 | - | Jun 29, 03:29 UTC | Jun 29, 03:44 UTC | 15m |
| 2026-06-28 | AAR742 | - | Jun 28, 18:44 UTC | Jun 28, 23:44 UTC | 5h 0m |
| 2026-06-28 | AAR741 | ICN → BKK | Jun 28, 11:04 UTC | Jun 28, 16:00 UTC | 4h 55m |
| 2026-06-27 | AAR502 | - | Jun 27, 17:44 UTC | Jun 28, 05:09 UTC | 11h 25m |
| 2026-06-27 | AAR501 | - | Jun 27, 02:45 UTC | Jun 27, 15:10 UTC | 12h 25m |
| 2026-06-27 | AAR501 | - | Jun 27, 01:35 UTC | Jun 27, 01:49 UTC | 15m |
| 2026-06-26 | AAR734 | - | Jun 26, 16:49 UTC | Jun 26, 20:29 UTC | 3h 40m |
| 2026-06-26 | AAR733 | - | Jun 26, 11:00 UTC | Jun 26, 14:39 UTC | 3h 40m |
| 2026-06-23 | AAR512 | BCN → ICN | Jun 23, 07:19 UTC | Jun 23, 07:45 UTC | 25m |
| 2026-06-22 | AAR512 | BCN → ICN | Jun 22, 20:19 UTC | Jun 23, 06:34 UTC | 10h 15m |
| 2026-06-22 | AAR511 | - | Jun 22, 05:49 UTC | Jun 22, 18:15 UTC | 12h 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 HL8078 page for operator, model, and routing details .