sensors Mode-S transponder
780B89
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-9976 · AIRBUS A-320
- Hex
- 780B89
- Octal
- 36005611
- Decimal
- 7,867,273
- Country
- CN
- Tail
- B-9976
- Type
- A320
- Flights observed
- 43
- Distinct callsigns
- 13
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 780B89 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CQN2361 | Chongqing Airlines | 8 | 2026-07-21 |
| CQN2103 | - | 7 | 2026-07-02 |
| CQN2362 | Chongqing Airlines | 6 | 2026-07-21 |
| CQN2025 | - | 5 | 2026-07-15 |
| CQN2105 | - | 4 | 2026-07-18 |
| CQN2386 | - | 3 | 2026-06-18 |
| CQN2111 | - | 3 | 2026-04-28 |
| CQN2131 | - | 2 | 2026-06-02 |
| CQN2350 | - | 1 | 2026-06-28 |
| CQN2343 | - | 1 | 2026-04-20 |
| CQN2132 | - | 1 | 2026-04-23 |
| CQN2106 | - | 1 | 2026-07-08 |
| CQN2039 | - | 1 | 2026-07-04 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | CQN2362 | BKK → CKG | Jul 21, 18:30 UTC | Jul 21, 19:55 UTC | 1h 25m |
| 2026-07-21 | CQN2361 | CKG → BKK | Jul 21, 15:25 UTC | Jul 21, 16:40 UTC | 1h 15m |
| 2026-07-18 | CQN2105 | - | Jul 18, 23:40 UTC | Jul 19, 08:40 UTC | 9h 0m |
| 2026-07-16 | CQN2362 | - | Jul 16, 18:29 UTC | Jul 16, 19:50 UTC | 1h 20m |
| 2026-07-16 | CQN2361 | - | Jul 16, 15:19 UTC | Jul 16, 16:40 UTC | 1h 20m |
| 2026-07-15 | CQN2025 | - | Jul 15, 00:05 UTC | Jul 15, 00:50 UTC | 45m |
| 2026-07-08 | CQN2106 | - | Jul 8, 11:35 UTC | Jul 8, 11:45 UTC | 10m |
| 2026-07-07 | CQN2105 | - | Jul 7, 23:50 UTC | Jul 8, 09:00 UTC | 9h 10m |
| 2026-07-04 | CQN2039 | - | Jul 4, 00:45 UTC | Jul 4, 00:55 UTC | 10m |
| 2026-07-02 | CQN2103 | - | Jul 2, 15:05 UTC | Jul 3, 01:55 UTC | 10h 50m |
| 2026-06-28 | CQN2350 | - | Jun 28, 15:09 UTC | Jun 28, 15:24 UTC | 15m |
| 2026-06-26 | CQN2362 | - | Jun 26, 18:24 UTC | Jun 26, 18:49 UTC | 25m |
| 2026-06-26 | CQN2361 | - | Jun 26, 16:14 UTC | Jun 26, 16:39 UTC | 25m |
| 2026-06-23 | CQN2025 | - | Jun 23, 23:39 UTC | Jun 24, 00:34 UTC | 55m |
| 2026-06-20 | CQN2103 | - | Jun 20, 01:29 UTC | Jun 20, 02:24 UTC | 55m |
| 2026-06-18 | CQN2386 | - | Jun 18, 17:21 UTC | Jun 18, 17:35 UTC | 14m |
| 2026-06-17 | CQN2103 | - | Jun 17, 01:10 UTC | Jun 17, 05:20 UTC | 4h 10m |
| 2026-06-16 | CQN2103 | - | Jun 16, 02:15 UTC | Jun 16, 06:15 UTC | 4h 0m |
| 2026-06-10 | CQN2362 | BKK → CKG | Jun 10, 18:10 UTC | Jun 10, 18:40 UTC | 30m |
| 2026-06-10 | CQN2361 | CKG → BKK | Jun 10, 15:45 UTC | Jun 10, 16:50 UTC | 1h 5m |
| 2026-06-08 | CQN2386 | - | Jun 8, 15:30 UTC | Jun 8, 15:40 UTC | 10m |
| 2026-06-04 | CQN2386 | - | Jun 4, 12:35 UTC | Jun 4, 12:45 UTC | 10m |
| 2026-06-03 | CQN2105 | - | Jun 3, 07:00 UTC | Jun 3, 07:40 UTC | 40m |
| 2026-06-02 | CQN2131 | - | Jun 2, 10:40 UTC | Jun 2, 10:50 UTC | 10m |
| 2026-05-29 | CQN2103 | - | May 29, 01:10 UTC | May 29, 01:25 UTC | 15m |
| 2026-05-28 | CQN2103 | - | May 28, 01:10 UTC | May 28, 02:00 UTC | 50m |
| 2026-05-21 | CQN2105 | - | May 21, 07:10 UTC | May 21, 07:25 UTC | 15m |
| 2026-05-14 | CQN2131 | - | May 14, 12:30 UTC | May 14, 12:40 UTC | 10m |
| 2026-05-08 | CQN2362 | BKK → CKG | May 8, 18:25 UTC | May 8, 19:15 UTC | 50m |
| 2026-05-08 | CQN2361 | CKG → BKK | May 8, 15:50 UTC | May 8, 16:50 UTC | 1h 0m |
| 2026-05-07 | CQN2361 | CKG → BKK | May 7, 18:25 UTC | May 8, 16:50 UTC | 22h 25m |
| 2026-05-07 | CQN2361 | CKG → BKK | May 7, 15:45 UTC | May 7, 16:40 UTC | 55m |
| 2026-05-06 | CQN2362 | BKK → CKG | May 6, 18:25 UTC | May 7, 16:40 UTC | 22h 16m |
| 2026-05-06 | CQN2361 | CKG → BKK | May 6, 15:55 UTC | May 6, 16:50 UTC | 55m |
| 2026-05-02 | CQN2103 | - | May 2, 01:05 UTC | May 2, 01:15 UTC | 10m |
| 2026-04-30 | CQN2025 | - | Apr 30, 23:45 UTC | Apr 30, 23:55 UTC | 10m |
| 2026-04-30 | CQN2025 | - | Apr 30, 00:30 UTC | Apr 30, 00:40 UTC | 10m |
| 2026-04-28 | CQN2111 | - | Apr 28, 12:00 UTC | Apr 28, 12:10 UTC | 10m |
| 2026-04-25 | CQN2025 | - | Apr 25, 23:40 UTC | Apr 25, 23:55 UTC | 15m |
| 2026-04-23 | CQN2132 | - | Apr 23, 17:15 UTC | Apr 23, 17:35 UTC | 20m |
| 2026-04-22 | CQN2111 | - | Apr 22, 10:50 UTC | Apr 22, 11:05 UTC | 15m |
| 2026-04-20 | CQN2343 | - | Apr 20, 00:40 UTC | Apr 20, 00:50 UTC | 10m |
| 2026-04-16 | CQN2111 | - | Apr 16, 10:40 UTC | Apr 16, 10:54 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-9976 page for operator, model, and routing details .