sensors Mode-S transponder
780A5C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-KQL · BOEING 777-300ER
- Hex
- 780A5C
- Octal
- 36005134
- Decimal
- 7,866,972
- Country
- CN
- Tail
- B-KQL
- Type
- B77W
- Flights observed
- 213
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 9h ago
Current position
Country allocation
The ICAO 24-bit address 780A5C falls within the block assigned to China (CN) by ICAO Annex 10, Volume III. Every aircraft registered in China 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 |
|---|---|---|---|
| CPA289 | - | 20 | 2026-07-13 |
| CPA288 | Cathay Pacific | 18 | 2026-06-23 |
| CPA549 | - | 12 | 2026-07-11 |
| CPA178 | Cathay Pacific | 11 | 2026-06-25 |
| CPA872 | - | 10 | 2026-07-11 |
| CPA865 | Cathay Pacific | 10 | 2026-07-07 |
| CPA233 | - | 10 | 2026-07-09 |
| CPA888 | Cathay Pacific | 9 | 2026-07-06 |
| CPA873 | - | 8 | 2026-07-12 |
| CPA548 | - | 8 | 2026-07-11 |
| CPA255 | Cathay Pacific | 8 | 2026-06-04 |
| CPA885 | - | 7 | 2026-07-03 |
| CPA234 | - | 7 | 2026-07-10 |
| CPA884 | - | 6 | 2026-07-02 |
| CPA581 | Cathay Pacific | 6 | 2026-06-04 |
| CPA250 | Cathay Pacific | 6 | 2026-06-05 |
| CPA163 | - | 6 | 2026-06-25 |
| CPA253 | Cathay Pacific | 4 | 2026-06-09 |
| CPA100 | - | 4 | 2026-07-04 |
| CPA595 | Cathay Pacific | 3 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | CPA289 | HKG → FRA | Jul 13, 16:20 UTC | Jul 14, 05:05 UTC | 12h 45m |
| 2026-07-13 | CPA583 | CTS → HKG | Jul 13, 08:45 UTC | Jul 13, 13:05 UTC | 4h 20m |
| 2026-07-13 | CPA582 | - | Jul 13, 02:25 UTC | Jul 13, 07:01 UTC | 4h 35m |
| 2026-07-12 | CPA873 | - | Jul 12, 08:45 UTC | Jul 12, 21:55 UTC | 13h 10m |
| 2026-07-11 | CPA872 | - | Jul 11, 18:15 UTC | Jul 12, 05:50 UTC | 11h 35m |
| 2026-07-11 | CPA872 | - | Jul 11, 17:30 UTC | Jul 11, 17:45 UTC | 15m |
| 2026-07-11 | CPA549 | - | Jul 11, 07:45 UTC | Jul 11, 11:20 UTC | 3h 35m |
| 2026-07-11 | CPA548 | HKG → HND | Jul 11, 01:10 UTC | Jul 11, 04:55 UTC | 3h 45m |
| 2026-07-10 | CPA234 | - | Jul 10, 21:25 UTC | Jul 10, 22:00 UTC | 35m |
| 2026-07-10 | CPA234 | - | Jul 10, 11:15 UTC | Jul 10, 14:40 UTC | 3h 25m |
| 2026-07-09 | CPA233 | - | Jul 9, 17:20 UTC | Jul 10, 03:00 UTC | 9h 40m |
| 2026-07-09 | CPA704 | - | Jul 9, 14:40 UTC | Jul 9, 14:45 UTC | 5m |
| 2026-07-09 | CPA704 | - | Jul 9, 12:30 UTC | Jul 9, 14:05 UTC | 1h 35m |
| 2026-07-09 | CPA701 | HKG → BKK | Jul 9, 08:20 UTC | Jul 9, 10:40 UTC | 2h 20m |
| 2026-07-09 | CPA431 | KHH → HKG | Jul 9, 03:50 UTC | Jul 9, 04:55 UTC | 1h 5m |
| 2026-07-09 | CPA432 | HKG → KHH | Jul 9, 01:00 UTC | Jul 9, 02:10 UTC | 1h 10m |
| 2026-07-07 | CPA865 | YVR → HKG | Jul 7, 08:40 UTC | Jul 7, 20:50 UTC | 12h 10m |
| 2026-07-06 | CPA888 | HKG → YVR | Jul 6, 17:00 UTC | Jul 7, 04:35 UTC | 11h 35m |
| 2026-07-06 | CPA549 | HND → HKG | Jul 6, 07:40 UTC | Jul 6, 11:40 UTC | 4h 0m |
| 2026-07-06 | CPA548 | HKG → HND | Jul 6, 01:20 UTC | Jul 6, 05:00 UTC | 3h 40m |
| 2026-07-05 | CPA865 | YVR → HKG | Jul 5, 08:45 UTC | Jul 5, 21:00 UTC | 12h 15m |
| 2026-07-04 | CPA888 | HKG → YVR | Jul 4, 17:05 UTC | Jul 5, 04:20 UTC | 11h 15m |
| 2026-07-04 | CPA100 | - | Jul 4, 12:45 UTC | Jul 4, 13:00 UTC | 15m |
| 2026-07-04 | CPA100 | - | Jul 4, 04:20 UTC | Jul 4, 11:50 UTC | 7h 30m |
| 2026-07-03 | CPA181 | HKG → SYD | Jul 3, 18:30 UTC | Jul 4, 01:40 UTC | 7h 10m |
| 2026-07-03 | CPA181 | HKG → SYD | Jul 3, 17:25 UTC | Jul 3, 17:35 UTC | 10m |
| 2026-07-03 | CPA885 | - | Jul 3, 10:30 UTC | Jul 3, 10:45 UTC | 15m |
| 2026-07-02 | CPA885 | - | Jul 2, 21:00 UTC | Jul 3, 10:00 UTC | 13h 0m |
| 2026-07-02 | CPA884 | - | Jul 2, 06:00 UTC | Jul 2, 17:30 UTC | 11h 30m |
| 2026-07-02 | CPA884 | - | Jul 2, 05:15 UTC | Jul 2, 05:30 UTC | 15m |
| 2026-06-30 | CPA865 | YVR → HKG | Jun 30, 21:15 UTC | Jun 30, 21:30 UTC | 15m |
| 2026-06-30 | CPA865 | YVR → HKG | Jun 30, 08:50 UTC | Jun 30, 20:40 UTC | 11h 50m |
| 2026-06-29 | CPA888 | HKG → YVR | Jun 29, 17:24 UTC | Jun 30, 04:25 UTC | 11h 1m |
| 2026-06-28 | CPA885 | - | Jun 28, 21:34 UTC | Jun 29, 11:50 UTC | 14h 15m |
| 2026-06-28 | CPA884 | - | Jun 28, 06:49 UTC | Jun 28, 19:04 UTC | 12h 15m |
| 2026-06-27 | CPA865 | YVR → HKG | Jun 27, 09:09 UTC | Jun 27, 21:40 UTC | 12h 30m |
| 2026-06-26 | CPA888 | HKG → YVR | Jun 26, 17:19 UTC | Jun 27, 04:29 UTC | 11h 10m |
| 2026-06-25 | CPA178 | MEL → HKG | Jun 25, 22:49 UTC | Jun 25, 23:14 UTC | 25m |
| 2026-06-25 | CPA178 | MEL → HKG | Jun 25, 14:39 UTC | Jun 25, 22:04 UTC | 7h 25m |
| 2026-06-25 | CPA163 | HKG → MEL | Jun 25, 03:34 UTC | Jun 25, 11:50 UTC | 8h 15m |
| 2026-06-24 | CPA178 | MEL → HKG | Jun 24, 22:19 UTC | Jun 24, 22:45 UTC | 25m |
| 2026-06-24 | CPA178 | MEL → HKG | Jun 24, 13:54 UTC | Jun 24, 21:29 UTC | 7h 35m |
| 2026-06-24 | CPA163 | HKG → MEL | Jun 24, 03:44 UTC | Jun 24, 11:59 UTC | 8h 15m |
| 2026-06-23 | CPA288 | FRA → HKG | Jun 23, 23:10 UTC | Jun 23, 23:39 UTC | 30m |
| 2026-06-23 | CPA288 | FRA → HKG | Jun 23, 12:40 UTC | Jun 23, 16:54 UTC | 4h 15m |
| 2026-06-23 | CPA289 | HKG → FRA | Jun 23, 01:30 UTC | Jun 23, 05:15 UTC | 3h 45m |
| 2026-06-22 | CPA289 | HKG → FRA | Jun 22, 16:14 UTC | Jun 22, 16:29 UTC | 15m |
| 2026-06-22 | CPA885 | - | Jun 22, 10:40 UTC | Jun 22, 11:00 UTC | 20m |
| 2026-06-21 | CPA885 | - | Jun 21, 21:05 UTC | Jun 22, 10:10 UTC | 13h 5m |
| 2026-06-21 | CPA884 | - | Jun 21, 05:10 UTC | Jun 21, 16:59 UTC | 11h 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 B-KQL page for operator, model, and routing details .