sensors Mode-S transponder
781404
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-300A · AIRBUS A-321
- Hex
- 781404
- Octal
- 36012004
- Decimal
- 7,869,444
- Country
- CN
- Tail
- B-300A
- Type
- A321
- Flights observed
- 37
- Distinct callsigns
- 17
- Country
- CN
- Last broadcast
- 12d ago
Last known position
Country allocation
The ICAO 24-bit address 781404 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSC3935 | Sichuan Airlines | 7 | 2026-05-16 |
| CSC8702 | Sichuan Airlines | 4 | 2026-05-27 |
| CSC3936 | Sichuan Airlines | 4 | 2026-05-16 |
| CSC3931 | Sichuan Airlines | 4 | 2026-05-12 |
| CSC8898 | Sichuan Airlines | 2 | 2026-06-19 |
| CSC8706 | - | 2 | 2026-07-02 |
| CSC8705 | - | 2 | 2026-07-02 |
| CSC8701 | Sichuan Airlines | 2 | 2026-04-23 |
| CSC6872 | Sichuan Airlines | 2 | 2026-05-03 |
| CSC8894 | Sichuan Airlines | 1 | 2026-05-03 |
| CSC8890 | Sichuan Airlines | 1 | 2026-05-27 |
| CSC8888 | Sichuan Airlines | 1 | 2026-05-27 |
| CSC8887 | Sichuan Airlines | 1 | 2026-05-27 |
| CSC8778 | Sichuan Airlines | 1 | 2026-06-15 |
| CSC8777 | Sichuan Airlines | 1 | 2026-06-15 |
| CSC8764 | Sichuan Airlines | 1 | 2026-05-31 |
| CSC3932 | Sichuan Airlines | 1 | 2026-05-11 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-02 | CSC8706 | - | Jul 2, 08:55 UTC | Jul 2, 09:10 UTC | 15m |
| 2026-07-02 | CSC8705 | - | Jul 2, 07:25 UTC | Jul 2, 07:35 UTC | 10m |
| 2026-06-19 | CSC8898 | PEK → CTU | Jun 19, 14:15 UTC | Jun 19, 14:34 UTC | 20m |
| 2026-06-15 | CSC8778 | HAK → CTU | Jun 15, 13:00 UTC | Jun 15, 13:10 UTC | 10m |
| 2026-06-15 | CSC8777 | CTU → HAK | Jun 15, 10:24 UTC | Jun 15, 10:45 UTC | 20m |
| 2026-05-31 | CSC8764 | ZUH → CTU | May 31, 13:45 UTC | May 31, 14:00 UTC | 15m |
| 2026-05-28 | CSC8898 | PEK → CTU | May 28, 12:10 UTC | May 28, 12:30 UTC | 20m |
| 2026-05-27 | CSC8890 | PEK → CTU | May 27, 23:05 UTC | May 27, 23:25 UTC | 20m |
| 2026-05-27 | CSC8888 | PEK → CTU | May 27, 09:45 UTC | May 27, 10:05 UTC | 20m |
| 2026-05-27 | CSC8887 | CTU → PEK | May 27, 07:40 UTC | May 27, 08:00 UTC | 20m |
| 2026-05-27 | CSC8702 | SZX → CTU | May 27, 02:34 UTC | May 27, 02:44 UTC | 10m |
| 2026-05-16 | CSC3936 | BKK → TFU | May 16, 11:05 UTC | May 16, 12:01 UTC | 55m |
| 2026-05-16 | CSC3935 | TFU → BKK | May 16, 08:31 UTC | May 16, 09:31 UTC | 1h 0m |
| 2026-05-15 | CSC3935 | TFU → BKK | May 15, 11:10 UTC | May 16, 09:31 UTC | 22h 20m |
| 2026-05-15 | CSC3935 | TFU → BKK | May 15, 08:35 UTC | May 15, 09:35 UTC | 1h 0m |
| 2026-05-12 | CSC3931 | TFU → HKT | May 12, 09:15 UTC | May 12, 14:10 UTC | 4h 55m |
| 2026-05-11 | CSC3931 | TFU → HKT | May 11, 13:05 UTC | May 12, 13:00 UTC | 23h 56m |
| 2026-05-11 | CSC3932 | HKT → TFU | May 11, 12:35 UTC | May 12, 10:35 UTC | 22h 1m |
| 2026-05-11 | CSC3931 | TFU → HKT | May 11, 09:15 UTC | May 11, 13:55 UTC | 4h 40m |
| 2026-05-10 | CSC3931 | TFU → HKT | May 10, 11:10 UTC | May 11, 10:35 UTC | 23h 25m |
| 2026-05-10 | CSC3935 | TFU → BKK | May 10, 00:34 UTC | May 10, 09:45 UTC | 9h 10m |
| 2026-05-08 | CSC3936 | BKK → TFU | May 8, 11:40 UTC | May 8, 12:30 UTC | 50m |
| 2026-05-08 | CSC3935 | TFU → BKK | May 8, 08:40 UTC | May 8, 09:49 UTC | 1h 10m |
| 2026-05-05 | CSC3936 | BKK → TFU | May 5, 11:20 UTC | May 5, 11:45 UTC | 25m |
| 2026-05-05 | CSC3935 | TFU → BKK | May 5, 09:15 UTC | May 5, 09:40 UTC | 25m |
| 2026-05-03 | CSC6872 | PEK → TFU | May 3, 12:20 UTC | May 3, 12:40 UTC | 20m |
| 2026-05-03 | CSC8894 | PEK → CTU | May 3, 03:50 UTC | May 3, 04:05 UTC | 15m |
| 2026-05-01 | CSC3936 | BKK → TFU | May 1, 11:25 UTC | May 1, 11:55 UTC | 30m |
| 2026-05-01 | CSC3935 | TFU → BKK | May 1, 08:35 UTC | May 1, 09:40 UTC | 1h 5m |
| 2026-04-29 | CSC6872 | PEK → TFU | Apr 29, 12:40 UTC | Apr 29, 12:50 UTC | 10m |
| 2026-04-23 | CSC8702 | SZX → CTU | Apr 23, 05:15 UTC | Apr 23, 05:30 UTC | 15m |
| 2026-04-23 | CSC8701 | CTU → SZX | Apr 23, 00:45 UTC | Apr 23, 00:55 UTC | 10m |
| 2026-04-16 | CSC8702 | SZX → CTU | Apr 16, 02:15 UTC | Apr 16, 02:30 UTC | 15m |
| 2026-04-15 | CSC8702 | SZX → CTU | Apr 15, 02:15 UTC | Apr 15, 02:25 UTC | 10m |
| 2026-04-15 | CSC8701 | CTU → SZX | Apr 15, 00:25 UTC | Apr 15, 00:40 UTC | 15m |
| 2026-04-13 | CSC8706 | - | Apr 13, 08:50 UTC | Apr 13, 09:05 UTC | 15m |
| 2026-04-13 | CSC8705 | CTU → SZX | Apr 13, 07:10 UTC | Apr 13, 07:25 UTC | 15m |
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-300A page for operator, model, and routing details .