sensors Mode-S transponder
78174F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-20CQ · BOEING 737 MAX 8
- Hex
- 78174F
- Octal
- 36013517
- Decimal
- 7,870,287
- Country
- CN
- Tail
- B-20CQ
- Type
- B38M
- Flights observed
- 97
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 78174F 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 |
|---|---|---|---|
| CXA8673 | - | 19 | 2026-07-03 |
| CXA8674 | - | 15 | 2026-07-04 |
| CXA8684 | - | 9 | 2026-06-30 |
| CXA8694 | - | 8 | 2026-07-04 |
| CXA8783 | - | 5 | 2026-07-09 |
| CXA8683 | - | 5 | 2026-07-01 |
| CXA864 | Xiamen Airlines | 3 | 2026-06-05 |
| CXA8359 | Xiamen Airlines | 3 | 2026-05-30 |
| CXA8688 | Xiamen Airlines | 2 | 2026-04-28 |
| CXA8687 | Xiamen Airlines | 2 | 2026-04-28 |
| CXA863 | Xiamen Airlines | 2 | 2026-06-05 |
| CXA8429 | - | 2 | 2026-06-18 |
| CXA8370 | - | 2 | 2026-06-23 |
| CXA8369 | - | 2 | 2026-06-23 |
| CXA8230 | Xiamen Airlines | 2 | 2026-05-09 |
| CXA8229 | Xiamen Airlines | 2 | 2026-05-09 |
| CXA878 | - | 1 | 2026-06-19 |
| CXA877 | - | 1 | 2026-06-19 |
| CXA8693 | - | 1 | 2026-07-04 |
| CXA8628 | Xiamen Airlines | 1 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | CXA8783 | - | Jul 9, 11:40 UTC | Jul 9, 15:55 UTC | 4h 15m |
| 2026-07-08 | CXA8783 | - | Jul 8, 11:45 UTC | Jul 8, 16:20 UTC | 4h 35m |
| 2026-07-07 | CXA8783 | - | Jul 7, 11:50 UTC | Jul 7, 15:20 UTC | 3h 30m |
| 2026-07-06 | CXA8783 | - | Jul 6, 14:40 UTC | Jul 7, 12:30 UTC | 21h 50m |
| 2026-07-06 | CXA8783 | - | Jul 6, 11:30 UTC | Jul 6, 14:40 UTC | 3h 10m |
| 2026-07-04 | CXA8674 | - | Jul 4, 16:40 UTC | Jul 4, 20:55 UTC | 4h 15m |
| 2026-07-04 | CXA8693 | - | Jul 4, 14:10 UTC | Jul 4, 14:20 UTC | 10m |
| 2026-07-04 | CXA8694 | - | Jul 4, 00:10 UTC | Jul 4, 12:40 UTC | 12h 30m |
| 2026-07-03 | CXA8673 | - | Jul 3, 21:10 UTC | Jul 3, 21:25 UTC | 15m |
| 2026-07-03 | CXA8673 | - | Jul 3, 17:15 UTC | Jul 3, 20:35 UTC | 3h 20m |
| 2026-07-01 | CXA8674 | - | Jul 1, 16:35 UTC | Jul 1, 20:50 UTC | 4h 15m |
| 2026-07-01 | CXA8683 | - | Jul 1, 14:15 UTC | Jul 1, 14:30 UTC | 15m |
| 2026-06-30 | CXA8684 | - | Jun 30, 23:45 UTC | Jul 1, 10:25 UTC | 10h 40m |
| 2026-06-30 | CXA8673 | - | Jun 30, 17:35 UTC | Jun 30, 21:55 UTC | 4h 20m |
| 2026-06-28 | CXA8674 | - | Jun 28, 16:35 UTC | Jun 28, 20:39 UTC | 4h 5m |
| 2026-06-28 | CXA8683 | - | Jun 28, 14:14 UTC | Jun 28, 14:30 UTC | 15m |
| 2026-06-28 | CXA8684 | - | Jun 28, 00:09 UTC | Jun 28, 10:19 UTC | 10h 10m |
| 2026-06-27 | CXA8673 | - | Jun 27, 12:34 UTC | Jun 27, 21:40 UTC | 9h 5m |
| 2026-06-23 | CXA8370 | - | Jun 23, 02:34 UTC | Jun 23, 02:49 UTC | 15m |
| 2026-06-23 | CXA8369 | - | Jun 23, 00:54 UTC | Jun 23, 01:20 UTC | 25m |
| 2026-06-21 | CXA8324 | CAN → FOC | Jun 21, 05:30 UTC | Jun 21, 05:44 UTC | 15m |
| 2026-06-21 | CXA8323 | - | Jun 21, 03:30 UTC | Jun 21, 03:40 UTC | 10m |
| 2026-06-19 | CXA878 | - | Jun 19, 11:54 UTC | Jun 19, 12:34 UTC | 40m |
| 2026-06-19 | CXA877 | - | Jun 19, 08:54 UTC | Jun 19, 09:34 UTC | 40m |
| 2026-06-18 | CXA8429 | - | Jun 18, 00:50 UTC | Jun 18, 14:05 UTC | 13h 15m |
| 2026-06-15 | CXA8628 | CSX → FOC | Jun 15, 06:10 UTC | Jun 15, 06:49 UTC | 40m |
| 2026-06-14 | CXA8405 | - | Jun 14, 00:40 UTC | Jun 14, 01:40 UTC | 1h 0m |
| 2026-06-05 | CXA864 | SIN → HGH | Jun 5, 16:20 UTC | Jun 6, 00:25 UTC | 8h 5m |
| 2026-06-05 | CXA863 | HGH → SIN | Jun 5, 12:45 UTC | Jun 5, 15:05 UTC | 2h 20m |
| 2026-06-03 | CXA8674 | CGK → CKG | Jun 3, 16:35 UTC | Jun 3, 20:45 UTC | 4h 10m |
| 2026-06-03 | CXA8683 | WUH → CGK | Jun 3, 14:15 UTC | Jun 3, 14:30 UTC | 15m |
| 2026-06-03 | CXA8684 | CGK → WUH | Jun 3, 00:10 UTC | Jun 3, 10:20 UTC | 10h 10m |
| 2026-06-02 | CXA8673 | CKG → CGK | Jun 2, 17:25 UTC | Jun 2, 21:30 UTC | 4h 5m |
| 2026-06-01 | CXA864 | SIN → HGH | Jun 1, 13:10 UTC | Jun 1, 15:35 UTC | 2h 25m |
| 2026-06-01 | CXA863 | HGH → SIN | Jun 1, 08:45 UTC | Jun 1, 11:35 UTC | 2h 50m |
| 2026-05-31 | CXA8307 | XMN → SYX | May 31, 08:55 UTC | May 31, 13:10 UTC | 4h 15m |
| 2026-05-30 | CXA8359 | XMN → NNG | May 30, 10:00 UTC | May 30, 11:00 UTC | 1h 0m |
| 2026-05-29 | CXA864 | SIN → HGH | May 29, 13:20 UTC | May 29, 15:55 UTC | 2h 35m |
| 2026-05-28 | CXA8674 | CGK → CKG | May 28, 16:35 UTC | May 29, 11:35 UTC | 19h 0m |
| 2026-05-27 | CXA8694 | CGK → NKG | May 27, 23:55 UTC | May 28, 12:35 UTC | 12h 40m |
| 2026-05-27 | CXA8673 | CKG → CGK | May 27, 17:45 UTC | May 27, 21:00 UTC | 3h 15m |
| 2026-05-25 | CXA8674 | CGK → CKG | May 25, 16:40 UTC | May 25, 18:10 UTC | 1h 30m |
| 2026-05-25 | CXA8684 | CGK → WUH | May 25, 04:05 UTC | May 25, 09:55 UTC | 5h 50m |
| 2026-05-24 | CXA8673 | CKG → CGK | May 24, 21:10 UTC | May 24, 21:20 UTC | 10m |
| 2026-05-24 | CXA8673 | CKG → CGK | May 24, 19:45 UTC | May 24, 20:35 UTC | 50m |
| 2026-05-20 | CXA8674 | CGK → CKG | May 20, 16:35 UTC | May 20, 18:15 UTC | 1h 40m |
| 2026-05-20 | CXA8684 | CGK → WUH | May 20, 00:10 UTC | May 20, 10:10 UTC | 10h 1m |
| 2026-05-19 | CXA8673 | CKG → CGK | May 19, 20:10 UTC | May 19, 20:55 UTC | 45m |
| 2026-05-16 | CXA8359 | XMN → NNG | May 16, 10:05 UTC | May 16, 10:25 UTC | 20m |
| 2026-05-16 | CXA8370 | ZUH → HGH | May 16, 02:45 UTC | May 16, 02:55 UTC | 10m |
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-20CQ page for operator, model, and routing details .