sensors Mode-S transponder
78023D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-KPQ · BOEING 777-300ER
- Hex
- 78023D
- Octal
- 36001075
- Decimal
- 7,864,893
- Country
- CN
- Tail
- B-KPQ
- Type
- B77W
- Flights observed
- 182
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 78023D 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 |
|---|---|---|---|
| CPA830 | Cathay Pacific | 29 | 2026-07-07 |
| CPA831 | - | 23 | 2026-07-07 |
| CPA251 | - | 22 | 2026-07-12 |
| CPA881 | - | 18 | 2026-07-09 |
| CPA880 | - | 15 | 2026-07-08 |
| CPA252 | - | 14 | 2026-07-13 |
| CPA253 | Cathay Pacific | 12 | 2026-05-17 |
| CPA391 | - | 10 | 2026-07-10 |
| CPA254 | Cathay Pacific | 9 | 2026-05-18 |
| CPA390 | - | 8 | 2026-07-14 |
| CPA883 | Cathay Pacific | 4 | 2026-05-23 |
| CPA234 | Cathay Pacific | 4 | 2026-05-03 |
| CPA882 | Cathay Pacific | 3 | 2026-05-22 |
| CPA233 | Cathay Pacific | 3 | 2026-05-03 |
| CPA654 | - | 2 | 2026-07-05 |
| CPA421 | Cathay Pacific | 2 | 2026-04-30 |
| CPA653 | - | 1 | 2026-07-05 |
| CPA420 | Cathay Pacific | 1 | 2026-04-30 |
| CPA139 | - | 1 | 2026-07-01 |
| CPA138 | Cathay Pacific | 1 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CPA390 | - | Jul 14, 01:40 UTC | Jul 14, 01:55 UTC | 15m |
| 2026-07-13 | CPA252 | - | Jul 13, 23:15 UTC | Jul 13, 23:35 UTC | 20m |
| 2026-07-13 | CPA252 | - | Jul 13, 12:05 UTC | Jul 13, 15:00 UTC | 2h 55m |
| 2026-07-12 | CPA251 | - | Jul 12, 23:30 UTC | Jul 13, 04:35 UTC | 5h 5m |
| 2026-07-12 | CPA251 | - | Jul 12, 15:20 UTC | Jul 12, 15:35 UTC | 15m |
| 2026-07-11 | CPA252 | - | Jul 11, 22:50 UTC | Jul 11, 23:20 UTC | 30m |
| 2026-07-11 | CPA252 | - | Jul 11, 11:45 UTC | Jul 11, 14:40 UTC | 2h 55m |
| 2026-07-10 | CPA251 | - | Jul 10, 20:25 UTC | Jul 11, 04:50 UTC | 8h 25m |
| 2026-07-10 | CPA251 | - | Jul 10, 15:25 UTC | Jul 10, 15:45 UTC | 20m |
| 2026-07-10 | CPA391 | - | Jul 10, 06:30 UTC | Jul 10, 09:20 UTC | 2h 50m |
| 2026-07-10 | CPA390 | - | Jul 10, 01:30 UTC | Jul 10, 01:45 UTC | 15m |
| 2026-07-09 | CPA881 | - | Jul 9, 08:50 UTC | Jul 9, 22:55 UTC | 14h 5m |
| 2026-07-08 | CPA880 | - | Jul 8, 16:45 UTC | Jul 9, 05:35 UTC | 12h 50m |
| 2026-07-07 | CPA831 | JFK → HKG | Jul 7, 21:10 UTC | Jul 8, 12:20 UTC | 15h 10m |
| 2026-07-07 | CPA830 | HKG → JFK | Jul 7, 02:50 UTC | Jul 7, 18:35 UTC | 15h 45m |
| 2026-07-06 | CPA252 | LHR → HKG | Jul 6, 11:35 UTC | Jul 6, 23:15 UTC | 11h 40m |
| 2026-07-05 | CPA251 | HKG → LHR | Jul 5, 23:20 UTC | Jul 6, 04:35 UTC | 5h 15m |
| 2026-07-05 | CPA251 | HKG → LHR | Jul 5, 15:10 UTC | Jul 5, 15:25 UTC | 15m |
| 2026-07-05 | CPA654 | - | Jul 5, 10:25 UTC | Jul 5, 10:45 UTC | 20m |
| 2026-07-05 | CPA654 | - | Jul 5, 08:15 UTC | Jul 5, 09:05 UTC | 50m |
| 2026-07-05 | CPA653 | - | Jul 5, 04:15 UTC | Jul 5, 06:35 UTC | 2h 20m |
| 2026-07-04 | CPA881 | LAX → HKG | Jul 4, 08:45 UTC | Jul 4, 22:40 UTC | 13h 55m |
| 2026-07-03 | CPA880 | HKG → LAX | Jul 3, 16:30 UTC | Jul 4, 05:00 UTC | 12h 30m |
| 2026-07-02 | CPA831 | JFK → HKG | Jul 2, 19:35 UTC | Jul 3, 11:05 UTC | 15h 30m |
| 2026-07-02 | CPA830 | HKG → JFK | Jul 2, 02:20 UTC | Jul 2, 16:55 UTC | 14h 35m |
| 2026-07-02 | CPA830 | HKG → JFK | Jul 2, 01:30 UTC | Jul 2, 01:50 UTC | 20m |
| 2026-07-01 | CPA138 | SYD → HKG | Jul 1, 12:10 UTC | Jul 1, 21:15 UTC | 9h 5m |
| 2026-07-01 | CPA139 | - | Jul 1, 01:35 UTC | Jul 1, 09:45 UTC | 8h 10m |
| 2026-06-29 | CPA831 | - | Jun 29, 19:35 UTC | Jun 30, 11:20 UTC | 15h 46m |
| 2026-06-29 | CPA830 | HKG → JFK | Jun 29, 01:44 UTC | Jun 29, 17:10 UTC | 15h 25m |
| 2026-06-28 | CPA881 | LAX → HKG | Jun 28, 08:44 UTC | Jun 28, 22:34 UTC | 13h 50m |
| 2026-06-27 | CPA880 | HKG → LAX | Jun 27, 16:24 UTC | Jun 28, 04:44 UTC | 12h 20m |
| 2026-06-26 | CPA831 | JFK → HKG | Jun 26, 19:30 UTC | Jun 27, 10:25 UTC | 14h 55m |
| 2026-06-26 | CPA830 | HKG → JFK | Jun 26, 01:54 UTC | Jun 26, 17:04 UTC | 15h 10m |
| 2026-06-25 | CPA881 | LAX → HKG | Jun 25, 08:34 UTC | Jun 25, 22:29 UTC | 13h 55m |
| 2026-06-24 | CPA880 | HKG → LAX | Jun 24, 16:29 UTC | Jun 25, 04:45 UTC | 12h 15m |
| 2026-06-24 | CPA391 | - | Jun 24, 08:24 UTC | Jun 24, 09:05 UTC | 40m |
| 2026-06-24 | CPA391 | - | Jun 24, 06:10 UTC | Jun 24, 06:20 UTC | 10m |
| 2026-06-24 | CPA390 | - | Jun 24, 01:24 UTC | Jun 24, 01:34 UTC | 10m |
| 2026-06-23 | CPA252 | LHR → HKG | Jun 23, 11:54 UTC | Jun 23, 23:34 UTC | 11h 40m |
| 2026-06-22 | CPA251 | HKG → LHR | Jun 22, 20:04 UTC | Jun 23, 04:35 UTC | 8h 30m |
| 2026-06-22 | CPA251 | HKG → LHR | Jun 22, 15:14 UTC | Jun 22, 15:24 UTC | 10m |
| 2026-06-21 | CPA252 | LHR → HKG | Jun 21, 12:14 UTC | Jun 21, 23:55 UTC | 11h 40m |
| 2026-06-20 | CPA251 | HKG → LHR | Jun 20, 23:39 UTC | Jun 21, 04:39 UTC | 5h 0m |
| 2026-06-20 | CPA251 | HKG → LHR | Jun 20, 15:09 UTC | Jun 20, 15:24 UTC | 15m |
| 2026-06-19 | CPA831 | - | Jun 19, 19:29 UTC | Jun 20, 11:20 UTC | 15h 50m |
| 2026-06-19 | CPA830 | HKG → JFK | Jun 19, 01:45 UTC | Jun 19, 17:09 UTC | 15h 25m |
| 2026-06-18 | CPA831 | - | Jun 18, 13:50 UTC | Jun 18, 13:55 UTC | 5m |
| 2026-06-17 | CPA831 | - | Jun 17, 19:25 UTC | Jun 18, 10:10 UTC | 14h 45m |
| 2026-06-17 | CPA830 | HKG → JFK | Jun 17, 02:35 UTC | Jun 17, 16:55 UTC | 14h 20m |
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-KPQ page for operator, model, and routing details .