sensors Mode-S transponder
78067F
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-6707 · AIRBUS A-320
- Hex
- 78067F
- Octal
- 36003177
- Decimal
- 7,865,983
- Country
- CN
- Tail
- B-6707
- Type
- A320
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 78067F 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 |
|---|---|---|---|
| CQH6825 | - | 5 | 2026-07-07 |
| CQH8933 | Spring Airlines | 3 | 2026-05-10 |
| CQH6826 | - | 3 | 2026-07-07 |
| CQH8755 | Spring Airlines | 2 | 2026-06-08 |
| CQH7420 | Spring Airlines | 2 | 2026-06-10 |
| CQH7419 | Spring Airlines | 2 | 2026-04-18 |
| CQH7286 | Spring Airlines | 2 | 2026-04-18 |
| CQH7285 | - | 2 | 2026-06-10 |
| CQH7278 | - | 2 | 2026-06-21 |
| CQH7277 | - | 2 | 2026-06-21 |
| CQH7206 | - | 2 | 2026-07-12 |
| CQH6836 | - | 2 | 2026-06-28 |
| CQH6538 | Spring Airlines | 2 | 2026-05-30 |
| CQH6537 | Spring Airlines | 2 | 2026-05-30 |
| CQH8934 | - | 1 | 2026-04-15 |
| CQH8892 | Spring Airlines | 1 | 2026-05-13 |
| CQH8891 | Spring Airlines | 1 | 2026-05-12 |
| CQH8878 | Spring Airlines | 1 | 2026-05-10 |
| CQH8877 | Spring Airlines | 1 | 2026-05-10 |
| CQH8810 | Spring Airlines | 1 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | CQH7206 | - | Jul 12, 13:55 UTC | Jul 12, 14:15 UTC | 20m |
| 2026-07-12 | CQH720U | - | Jul 12, 11:01 UTC | Jul 12, 11:35 UTC | 35m |
| 2026-07-12 | CQH7518 | - | Jul 12, 07:31 UTC | Jul 12, 07:40 UTC | 10m |
| 2026-07-10 | CQH7256 | - | Jul 10, 13:40 UTC | Jul 10, 13:55 UTC | 15m |
| 2026-07-10 | CQH7255 | - | Jul 10, 08:55 UTC | Jul 10, 09:15 UTC | 20m |
| 2026-07-07 | CQH6826 | - | Jul 7, 10:35 UTC | Jul 7, 12:55 UTC | 2h 20m |
| 2026-07-07 | CQH6825 | - | Jul 7, 06:50 UTC | Jul 7, 09:10 UTC | 2h 20m |
| 2026-07-05 | CQH7462 | - | Jul 5, 13:25 UTC | Jul 5, 13:35 UTC | 10m |
| 2026-07-05 | CQH7461 | - | Jul 5, 10:20 UTC | Jul 5, 10:35 UTC | 15m |
| 2026-06-28 | CQH6628 | - | Jun 28, 14:39 UTC | Jun 28, 15:29 UTC | 50m |
| 2026-06-28 | CQH6627 | - | Jun 28, 12:15 UTC | Jun 28, 13:04 UTC | 50m |
| 2026-06-28 | CQH6836 | - | Jun 28, 03:35 UTC | Jun 28, 03:45 UTC | 10m |
| 2026-06-23 | CQH7609 | - | Jun 23, 02:29 UTC | Jun 23, 02:49 UTC | 20m |
| 2026-06-21 | CQH7278 | - | Jun 21, 06:44 UTC | Jun 21, 07:04 UTC | 20m |
| 2026-06-21 | CQH7277 | - | Jun 21, 02:24 UTC | Jun 21, 02:40 UTC | 15m |
| 2026-06-16 | CQH6190 | - | Jun 16, 16:05 UTC | Jun 16, 16:50 UTC | 45m |
| 2026-06-15 | CQH7206 | - | Jun 15, 13:34 UTC | Jun 15, 14:05 UTC | 30m |
| 2026-06-15 | CQH7205 | - | Jun 15, 11:10 UTC | Jun 15, 11:30 UTC | 20m |
| 2026-06-12 | CQH7135 | LHW → TSN | Jun 12, 04:15 UTC | Jun 12, 04:40 UTC | 25m |
| 2026-06-10 | CQH7420 | BKK → CAN | Jun 10, 17:10 UTC | Jun 10, 18:50 UTC | 1h 40m |
| 2026-06-10 | CQH7285 | - | Jun 10, 13:30 UTC | Jun 10, 15:50 UTC | 2h 20m |
| 2026-06-09 | CQH7282 | BKK → PVG | Jun 9, 10:35 UTC | Jun 9, 12:55 UTC | 2h 20m |
| 2026-06-08 | CQH7281 | PVG → BKK | Jun 8, 19:55 UTC | Jun 9, 08:55 UTC | 13h 0m |
| 2026-06-08 | CQH8755 | PVG → BKK | Jun 8, 17:30 UTC | Jun 8, 18:05 UTC | 35m |
| 2026-06-08 | CQH6610 | FUK → PVG | Jun 8, 03:00 UTC | Jun 8, 03:10 UTC | 10m |
| 2026-06-07 | CQH8810 | CGQ → PVG | Jun 7, 03:35 UTC | Jun 7, 04:05 UTC | 30m |
| 2026-05-31 | CQH8779 | SHA → SYX | May 31, 00:30 UTC | May 31, 00:55 UTC | 25m |
| 2026-05-30 | CQH6538 | FUK → PVG | May 30, 09:15 UTC | May 30, 09:25 UTC | 10m |
| 2026-05-30 | CQH6537 | PVG → FUK | May 30, 07:10 UTC | May 30, 07:20 UTC | 10m |
| 2026-05-29 | CQH6826 | - | May 29, 10:45 UTC | May 29, 13:05 UTC | 2h 20m |
| 2026-05-29 | CQH6825 | - | May 29, 06:35 UTC | May 29, 09:05 UTC | 2h 30m |
| 2026-05-28 | CQH6825 | - | May 28, 08:50 UTC | May 29, 07:25 UTC | 22h 35m |
| 2026-05-27 | CQH7278 | HLD → SJW | May 27, 06:49 UTC | May 27, 07:05 UTC | 16m |
| 2026-05-27 | CQH7277 | SHA → SJW | May 27, 02:34 UTC | May 27, 02:49 UTC | 15m |
| 2026-05-20 | CQH6954 | SHE → SJW | May 20, 14:45 UTC | May 20, 14:55 UTC | 10m |
| 2026-05-17 | CQH7587 | SHE → CJU | May 17, 10:30 UTC | May 18, 03:40 UTC | 17h 10m |
| 2026-05-17 | CQH7502 | BKK → TFU | May 17, 04:20 UTC | May 18, 03:40 UTC | 23h 20m |
| 2026-05-16 | CQH7501 | TFU → BKK | May 16, 10:20 UTC | May 17, 03:05 UTC | 16h 45m |
| 2026-05-14 | CQH6826 | - | May 14, 10:55 UTC | May 14, 13:10 UTC | 2h 15m |
| 2026-05-14 | CQH6825 | - | May 14, 07:20 UTC | May 14, 09:55 UTC | 2h 35m |
| 2026-05-13 | CQH6825 | - | May 13, 08:05 UTC | May 14, 07:45 UTC | 23h 40m |
| 2026-05-13 | CQH8892 | BKK → PVG | May 13, 06:05 UTC | May 13, 08:15 UTC | 2h 10m |
| 2026-05-12 | CQH8891 | PVG → BKK | May 12, 13:35 UTC | May 13, 04:35 UTC | 15h 0m |
| 2026-05-11 | CQH6538 | FUK → PVG | May 11, 09:15 UTC | May 11, 09:25 UTC | 10m |
| 2026-05-11 | CQH6537 | PVG → FUK | May 11, 07:05 UTC | May 11, 07:20 UTC | 15m |
| 2026-05-10 | CQH8878 | KHH → PVG | May 10, 10:19 UTC | May 11, 03:25 UTC | 17h 5m |
| 2026-05-10 | CQH8877 | PVG → KHH | May 10, 01:55 UTC | May 10, 08:54 UTC | 7h 0m |
| 2026-05-10 | CQH8933 | CAN → CNX | May 10, 00:20 UTC | May 10, 00:49 UTC | 30m |
| 2026-05-09 | CQH7420 | BKK → CAN | May 9, 15:10 UTC | May 9, 15:55 UTC | 45m |
| 2026-05-09 | CQH7285 | - | May 9, 04:15 UTC | May 9, 13:15 UTC | 9h 0m |
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-6707 page for operator, model, and routing details .