sensors Mode-S transponder
780D73
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1627 · AIRBUS A-320
- Hex
- 780D73
- Octal
- 36006563
- Decimal
- 7,867,763
- Country
- CN
- Tail
- B-1627
- Type
- A320
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 780D73 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 |
|---|---|---|---|
| CQH6539 | Spring Airlines | 6 | 2026-05-06 |
| CQH7587 | Spring Airlines | 4 | 2026-05-24 |
| CQH6540 | Spring Airlines | 4 | 2026-05-06 |
| CQH8632 | Spring Airlines | 3 | 2026-05-28 |
| CQH8613 | Spring Airlines | 3 | 2026-05-05 |
| CQH8779 | Spring Airlines | 2 | 2026-06-04 |
| CQH8661 | Spring Airlines | 2 | 2026-05-03 |
| CQH8631 | Spring Airlines | 2 | 2026-05-28 |
| CQH7596 | Spring Airlines | 2 | 2026-06-10 |
| CQH7385 | Spring Airlines | 2 | 2026-05-30 |
| CQH6731 | - | 2 | 2026-06-30 |
| CQH6482 | - | 2 | 2026-06-16 |
| CQH6472 | Spring Airlines | 2 | 2026-04-27 |
| CQH6471 | Spring Airlines | 2 | 2026-04-27 |
| CQH8894 | Spring Airlines | 1 | 2026-05-09 |
| CQH8893 | Spring Airlines | 1 | 2026-05-09 |
| CQH8876 | Spring Airlines | 1 | 2026-06-04 |
| CQH8875 | Spring Airlines | 1 | 2026-06-04 |
| CQH8790 | - | 1 | 2026-07-14 |
| CQH8789 | - | 1 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | CQH8790 | - | Jul 14, 11:00 UTC | Jul 14, 11:25 UTC | 25m |
| 2026-07-14 | CQH8789 | - | Jul 14, 09:00 UTC | Jul 14, 09:45 UTC | 45m |
| 2026-07-12 | CQH7348 | - | Jul 12, 14:45 UTC | Jul 12, 15:05 UTC | 20m |
| 2026-07-12 | CQH7347 | - | Jul 12, 08:40 UTC | Jul 12, 08:55 UTC | 15m |
| 2026-07-11 | CQH8684 | - | Jul 11, 05:45 UTC | Jul 11, 06:25 UTC | 40m |
| 2026-07-07 | CQH7507 | - | Jul 7, 10:25 UTC | Jul 8, 07:25 UTC | 21h 0m |
| 2026-07-07 | CQH7502 | - | Jul 7, 04:20 UTC | Jul 7, 10:25 UTC | 6h 5m |
| 2026-07-07 | CQH7501 | - | Jul 7, 01:15 UTC | Jul 7, 02:40 UTC | 1h 25m |
| 2026-07-05 | CQH6155 | - | Jul 5, 03:35 UTC | Jul 5, 03:55 UTC | 20m |
| 2026-07-01 | CQH6732 | - | Jul 1, 13:05 UTC | Jul 2, 10:50 UTC | 21h 45m |
| 2026-06-30 | CQH6731 | - | Jun 30, 23:45 UTC | Jul 1, 10:55 UTC | 11h 10m |
| 2026-06-30 | - | - | Jun 30, 02:55 UTC | Jun 30, 03:05 UTC | 10m |
| 2026-06-28 | CQH6731 | - | Jun 28, 23:25 UTC | Jun 29, 13:49 UTC | 14h 25m |
| 2026-06-27 | CQH7302 | - | Jun 27, 08:44 UTC | Jun 27, 11:09 UTC | 2h 25m |
| 2026-06-27 | CQH7301 | - | Jun 27, 04:24 UTC | Jun 27, 06:54 UTC | 2h 30m |
| 2026-06-25 | CQH6760 | - | Jun 25, 11:04 UTC | Jun 25, 23:30 UTC | 12h 25m |
| 2026-06-23 | CQH7282 | - | Jun 23, 11:49 UTC | Jun 23, 14:04 UTC | 2h 15m |
| 2026-06-23 | CQH7281 | - | Jun 23, 08:04 UTC | Jun 23, 10:19 UTC | 2h 15m |
| 2026-06-16 | CQH6595 | - | Jun 16, 22:55 UTC | Jun 16, 23:10 UTC | 15m |
| 2026-06-16 | CQH6482 | - | Jun 16, 18:05 UTC | Jun 16, 18:20 UTC | 15m |
| 2026-06-14 | CQH7461 | - | Jun 14, 10:30 UTC | Jun 14, 14:00 UTC | 3h 30m |
| 2026-06-10 | CQH7596 | ZUH → YTY | Jun 10, 06:20 UTC | Jun 10, 06:40 UTC | 20m |
| 2026-06-10 | CQH7595 | YTY → ZUH | Jun 10, 04:00 UTC | Jun 10, 04:45 UTC | 45m |
| 2026-06-05 | CQH7420 | BKK → CAN | Jun 5, 14:40 UTC | Jun 5, 16:20 UTC | 1h 40m |
| 2026-06-05 | CQH7285 | - | Jun 5, 00:15 UTC | Jun 5, 13:05 UTC | 12h 50m |
| 2026-06-04 | CQH8779 | SHA → SYX | Jun 4, 05:00 UTC | Jun 5, 01:30 UTC | 20h 30m |
| 2026-06-04 | CQH8779 | SHA → SYX | Jun 4, 04:45 UTC | Jun 5, 01:30 UTC | 20h 45m |
| 2026-06-04 | CQH8876 | MFM → PVG | Jun 4, 03:55 UTC | Jun 4, 04:10 UTC | 15m |
| 2026-06-04 | CQH8875 | PVG → MFM | Jun 4, 00:55 UTC | Jun 4, 02:10 UTC | 1h 15m |
| 2026-05-30 | CQH7385 | NGB → SYX | May 30, 10:30 UTC | May 30, 14:40 UTC | 4h 10m |
| 2026-05-29 | CQH8762 | HRB → SJW | May 29, 08:10 UTC | May 29, 08:20 UTC | 10m |
| 2026-05-29 | CQH8761 | SJW → HRB | May 29, 04:10 UTC | May 29, 04:25 UTC | 15m |
| 2026-05-28 | CQH8632 | ZUH → NGB | May 28, 12:05 UTC | May 28, 12:20 UTC | 15m |
| 2026-05-28 | CQH8631 | NGB → ZUH | May 28, 09:35 UTC | May 28, 10:20 UTC | 45m |
| 2026-05-26 | CQH7385 | NGB → SYX | May 26, 10:14 UTC | May 26, 13:54 UTC | 3h 40m |
| 2026-05-24 | CQH7587 | SHE → CJU | May 24, 00:15 UTC | May 24, 07:40 UTC | 7h 25m |
| 2026-05-23 | CQH7587 | SHE → CJU | May 23, 03:15 UTC | May 24, 01:00 UTC | 21h 46m |
| 2026-05-23 | CQH7587 | SHE → CJU | May 23, 00:50 UTC | May 24, 00:45 UTC | 23h 55m |
| 2026-05-22 | CQH7587 | SHE → CJU | May 22, 09:55 UTC | May 23, 03:30 UTC | 17h 34m |
| 2026-05-16 | CQH7252 | - | May 16, 12:35 UTC | May 16, 12:50 UTC | 15m |
| 2026-05-15 | CQH7596 | ZUH → YTY | May 15, 08:55 UTC | May 15, 09:05 UTC | 10m |
| 2026-05-09 | CQH8894 | BKK → CAN | May 9, 13:00 UTC | May 9, 13:45 UTC | 45m |
| 2026-05-09 | CQH8893 | CAN → BKK | May 9, 08:40 UTC | May 9, 10:55 UTC | 2h 15m |
| 2026-05-07 | CQH6873 | SZX → NGB | May 7, 06:40 UTC | May 7, 06:50 UTC | 10m |
| 2026-05-06 | CQH8753 | SZX → XIY | May 6, 22:45 UTC | May 6, 23:05 UTC | 20m |
| 2026-05-06 | CQH6540 | SJW → SZX | May 6, 16:20 UTC | May 6, 16:35 UTC | 15m |
| 2026-05-06 | CQH6540 | SJW → SZX | May 6, 12:05 UTC | May 6, 12:20 UTC | 15m |
| 2026-05-06 | CQH6539 | SZX → SJW | May 6, 09:10 UTC | May 6, 09:20 UTC | 10m |
| 2026-05-06 | CQH6539 | SZX → SJW | May 6, 05:10 UTC | May 6, 05:25 UTC | 15m |
| 2026-05-06 | - | - | May 6, 03:30 UTC | May 6, 03:40 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-1627 page for operator, model, and routing details .