sensors Mode-S transponder
78206D
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-32G6 · AIRBUS A-350-900
- Hex
- 78206D
- Octal
- 36020155
- Decimal
- 7,872,621
- Country
- CN
- Tail
- B-32G6
- Type
- A359
- Flights observed
- 95
- Distinct callsigns
- 15
- Country
- CN
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 78206D 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CSC3887 | Sichuan Airlines | 14 | 2026-06-03 |
| CSC3838 | Sichuan Airlines | 13 | 2026-06-10 |
| CSC3837 | Sichuan Airlines | 11 | 2026-06-09 |
| CSC3815 | Sichuan Airlines | 11 | 2026-06-07 |
| CSC3896 | Sichuan Airlines | 10 | 2026-05-24 |
| CSC3860 | Sichuan Airlines | 7 | 2026-06-02 |
| CSC3895 | Sichuan Airlines | 6 | 2026-05-24 |
| CSC3888 | Sichuan Airlines | 6 | 2026-06-08 |
| CSC3803 | Sichuan Airlines | 4 | 2026-04-17 |
| CSC3859 | Sichuan Airlines | 3 | 2026-06-02 |
| CSC3816 | Sichuan Airlines | 3 | 2026-06-07 |
| CSC3804 | Sichuan Airlines | 3 | 2026-04-17 |
| CSC8894 | Sichuan Airlines | 2 | 2026-05-22 |
| CSC6872 | Sichuan Airlines | 1 | 2026-05-25 |
| CSC381A | - | 1 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | CSC3838 | LAX → TFU | Jun 10, 06:45 UTC | Jun 10, 19:25 UTC | 12h 40m |
| 2026-06-09 | CSC3837 | TFU → LAX | Jun 9, 17:10 UTC | Jun 10, 02:55 UTC | 9h 45m |
| 2026-06-08 | CSC3837 | TFU → LAX | Jun 8, 20:40 UTC | Jun 9, 18:25 UTC | 21h 45m |
| 2026-06-08 | CSC3888 | SVO → TFU | Jun 8, 19:35 UTC | Jun 8, 19:55 UTC | 20m |
| 2026-06-07 | CSC3816 | LED → TFU | Jun 7, 23:25 UTC | Jun 8, 13:05 UTC | 13h 40m |
| 2026-06-07 | CSC3816 | LED → TFU | Jun 7, 16:00 UTC | Jun 8, 13:05 UTC | 21h 5m |
| 2026-06-07 | CSC3815 | TFU → LED | Jun 7, 13:20 UTC | Jun 8, 13:05 UTC | 23h 45m |
| 2026-06-07 | CSC3815 | TFU → LED | Jun 7, 13:10 UTC | Jun 7, 23:55 UTC | 10h 45m |
| 2026-06-06 | CSC3838 | LAX → TFU | Jun 6, 17:19 UTC | Jun 7, 16:05 UTC | 22h 45m |
| 2026-06-06 | CSC3838 | LAX → TFU | Jun 6, 16:50 UTC | Jun 7, 13:45 UTC | 20h 55m |
| 2026-06-06 | CSC3838 | LAX → TFU | Jun 6, 06:25 UTC | Jun 6, 18:55 UTC | 12h 30m |
| 2026-06-05 | CSC3837 | TFU → LAX | Jun 5, 17:00 UTC | Jun 6, 03:00 UTC | 10h 0m |
| 2026-06-04 | CSC3837 | TFU → LAX | Jun 4, 22:40 UTC | Jun 5, 18:20 UTC | 19h 40m |
| 2026-06-04 | CSC3888 | SVO → TFU | Jun 4, 19:30 UTC | Jun 4, 19:50 UTC | 20m |
| 2026-06-03 | CSC3887 | TFU → SVO | Jun 3, 23:10 UTC | Jun 4, 15:30 UTC | 16h 20m |
| 2026-06-03 | CSC3887 | TFU → SVO | Jun 3, 15:55 UTC | Jun 4, 15:15 UTC | 23h 20m |
| 2026-06-03 | CSC3816 | LED → TFU | Jun 3, 13:20 UTC | Jun 4, 13:05 UTC | 23h 45m |
| 2026-06-03 | CSC3815 | TFU → LED | Jun 3, 13:05 UTC | Jun 3, 23:45 UTC | 10h 40m |
| 2026-06-02 | CSC3815 | TFU → LED | Jun 2, 17:40 UTC | Jun 3, 16:00 UTC | 22h 20m |
| 2026-06-02 | CSC3860 | YVR → TFU | Jun 2, 07:40 UTC | Jun 2, 18:05 UTC | 10h 25m |
| 2026-06-02 | CSC3859 | TFU → YVR | Jun 2, 01:05 UTC | Jun 2, 05:00 UTC | 3h 55m |
| 2026-05-31 | CSC3888 | SVO → TFU | May 31, 23:20 UTC | May 31, 23:40 UTC | 20m |
| 2026-05-31 | CSC3888 | SVO → TFU | May 31, 20:00 UTC | May 31, 20:30 UTC | 30m |
| 2026-05-30 | CSC3887 | TFU → SVO | May 30, 23:05 UTC | May 31, 15:45 UTC | 16h 40m |
| 2026-05-30 | CSC3888 | SVO → TFU | May 30, 19:35 UTC | May 30, 19:50 UTC | 15m |
| 2026-05-30 | CSC3887 | TFU → SVO | May 30, 12:45 UTC | May 30, 15:45 UTC | 3h 0m |
| 2026-05-29 | CSC3887 | TFU → SVO | May 29, 18:00 UTC | May 30, 15:45 UTC | 21h 45m |
| 2026-05-29 | CSC3860 | YVR → TFU | May 29, 16:40 UTC | May 30, 15:15 UTC | 22h 35m |
| 2026-05-29 | CSC3860 | YVR → TFU | May 29, 08:00 UTC | May 29, 18:50 UTC | 10h 50m |
| 2026-05-28 | CSC3859 | TFU → YVR | May 28, 20:05 UTC | May 29, 05:15 UTC | 9h 10m |
| 2026-05-27 | CSC3887 | TFU → SVO | May 27, 12:35 UTC | May 27, 21:00 UTC | 8h 25m |
| 2026-05-26 | CSC3887 | TFU → SVO | May 26, 20:50 UTC | May 27, 15:45 UTC | 18h 55m |
| 2026-05-26 | CSC3887 | TFU → SVO | May 26, 15:35 UTC | May 27, 13:05 UTC | 21h 31m |
| 2026-05-26 | CSC3887 | TFU → SVO | May 26, 13:19 UTC | May 27, 13:05 UTC | 23h 46m |
| 2026-05-26 | CSC3887 | TFU → SVO | May 26, 13:00 UTC | May 26, 21:00 UTC | 8h 0m |
| 2026-05-25 | CSC6872 | PEK → TFU | May 25, 12:30 UTC | May 25, 12:45 UTC | 15m |
| 2026-05-24 | CSC3896 | FCO → TFU | May 24, 11:40 UTC | May 24, 18:10 UTC | 6h 30m |
| 2026-05-24 | CSC3895 | TFU → FCO | May 24, 01:10 UTC | May 24, 04:30 UTC | 3h 20m |
| 2026-05-22 | CSC8894 | PEK → CTU | May 22, 04:20 UTC | May 22, 04:40 UTC | 20m |
| 2026-05-17 | CSC3896 | FCO → TFU | May 17, 12:55 UTC | May 17, 19:15 UTC | 6h 20m |
| 2026-05-17 | CSC3895 | TFU → FCO | May 17, 00:15 UTC | May 17, 05:05 UTC | 4h 50m |
| 2026-05-15 | CSC381A | - | May 15, 01:25 UTC | May 15, 01:50 UTC | 25m |
| 2026-05-13 | CSC3815 | TFU → LED | May 13, 12:45 UTC | May 13, 15:35 UTC | 2h 50m |
| 2026-05-12 | CSC3860 | YVR → TFU | May 12, 07:50 UTC | May 12, 11:25 UTC | 3h 35m |
| 2026-05-12 | CSC3859 | TFU → YVR | May 12, 02:45 UTC | May 12, 05:25 UTC | 2h 40m |
| 2026-05-10 | CSC3815 | TFU → LED | May 10, 13:10 UTC | May 10, 23:50 UTC | 10h 40m |
| 2026-05-09 | CSC3815 | TFU → LED | May 9, 17:49 UTC | May 10, 16:40 UTC | 22h 50m |
| 2026-05-09 | CSC3815 | TFU → LED | May 9, 15:35 UTC | May 10, 13:44 UTC | 22h 10m |
| 2026-05-09 | CSC3896 | FCO → TFU | May 9, 13:20 UTC | May 10, 13:14 UTC | 23h 55m |
| 2026-05-09 | CSC3896 | FCO → TFU | May 9, 11:40 UTC | May 9, 18:00 UTC | 6h 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-32G6 page for operator, model, and routing details .