sensors Mode-S transponder
78138B
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1281 · BOEING 737-800
- Hex
- 78138B
- Octal
- 36011613
- Decimal
- 7,869,323
- Country
- CN
- Tail
- B-1281
- Type
- B738
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 78138B 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 |
|---|---|---|---|
| CUA5251 | - | 6 | 2026-07-09 |
| CUA5252 | - | 4 | 2026-05-27 |
| CUA5651 | - | 3 | 2026-06-06 |
| CUA5569 | - | 3 | 2026-07-20 |
| CUA5570 | - | 2 | 2026-07-20 |
| CUA5509 | China United Airlines | 2 | 2026-06-19 |
| CUA5290 | - | 2 | 2026-07-13 |
| CUA5890 | - | 1 | 2026-07-22 |
| CUA5889 | China United Airlines | 1 | 2026-06-20 |
| CUA5876 | China United Airlines | 1 | 2026-05-02 |
| CUA5812 | China United Airlines | 1 | 2026-07-06 |
| CUA5686 | China United Airlines | 1 | 2026-04-24 |
| CUA5652 | - | 1 | 2026-06-06 |
| CUA5597 | - | 1 | 2026-07-14 |
| CUA5596 | China United Airlines | 1 | 2026-04-28 |
| CUA5582 | - | 1 | 2026-07-20 |
| CUA5581 | - | 1 | 2026-07-20 |
| CUA5535 | - | 1 | 2026-05-03 |
| CUA5531 | - | 1 | 2026-07-04 |
| CUA5529 | - | 1 | 2026-07-03 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | CUA5890 | - | Jul 22, 14:50 UTC | Jul 22, 15:10 UTC | 20m |
| 2026-07-20 | CUA5582 | - | Jul 20, 15:00 UTC | Jul 20, 15:30 UTC | 30m |
| 2026-07-20 | CUA5581 | - | Jul 20, 09:20 UTC | Jul 20, 09:30 UTC | 10m |
| 2026-07-20 | CUA5570 | - | Jul 20, 06:00 UTC | Jul 20, 06:30 UTC | 30m |
| 2026-07-20 | CUA5570 | - | Jul 20, 05:15 UTC | Jul 20, 05:30 UTC | 15m |
| 2026-07-20 | CUA5569 | - | Jul 20, 01:05 UTC | Jul 20, 01:15 UTC | 10m |
| 2026-07-17 | CUA2867 | - | Jul 17, 12:35 UTC | Jul 18, 06:35 UTC | 18h 1m |
| 2026-07-16 | CUA5005 | - | Jul 16, 11:50 UTC | Jul 16, 12:30 UTC | 40m |
| 2026-07-14 | CUA5597 | - | Jul 14, 08:40 UTC | Jul 14, 08:55 UTC | 15m |
| 2026-07-14 | CUA5569 | - | Jul 14, 01:50 UTC | Jul 14, 02:05 UTC | 15m |
| 2026-07-13 | CUA5290 | - | Jul 13, 03:45 UTC | Jul 13, 04:30 UTC | 45m |
| 2026-07-09 | CUA5251 | - | Jul 9, 09:55 UTC | Jul 9, 10:40 UTC | 45m |
| 2026-07-06 | CUA5812 | HAK → PKX | Jul 6, 13:50 UTC | Jul 6, 14:10 UTC | 20m |
| 2026-07-04 | CUA5531 | - | Jul 4, 10:30 UTC | Jul 4, 10:45 UTC | 15m |
| 2026-07-03 | CUA5529 | - | Jul 3, 10:25 UTC | Jul 3, 10:45 UTC | 20m |
| 2026-06-30 | CUA5569 | - | Jun 30, 05:15 UTC | Jun 30, 05:25 UTC | 10m |
| 2026-06-24 | - | - | Jun 24, 08:20 UTC | Jun 24, 08:30 UTC | 10m |
| 2026-06-20 | CUA5889 | PKX → ZHA | Jun 20, 08:59 UTC | Jun 20, 09:09 UTC | 10m |
| 2026-06-19 | CUA5509 | PKX → JXA | Jun 19, 23:19 UTC | Jun 19, 23:29 UTC | 10m |
| 2026-06-06 | CUA5652 | - | Jun 6, 13:44 UTC | Jun 6, 13:54 UTC | 10m |
| 2026-06-06 | CUA5651 | - | Jun 6, 06:15 UTC | Jun 6, 06:25 UTC | 10m |
| 2026-06-05 | CUA5509 | PKX → JXA | Jun 5, 23:15 UTC | Jun 5, 23:25 UTC | 10m |
| 2026-05-31 | CUA5010 | - | May 31, 08:30 UTC | May 31, 08:40 UTC | 10m |
| 2026-05-27 | CUA5252 | - | May 27, 09:05 UTC | May 27, 09:15 UTC | 10m |
| 2026-05-27 | CUA5251 | - | May 27, 07:00 UTC | May 27, 07:20 UTC | 20m |
| 2026-05-24 | CUA5252 | - | May 24, 09:10 UTC | May 24, 09:25 UTC | 15m |
| 2026-05-24 | CUA5251 | - | May 24, 07:15 UTC | May 24, 07:40 UTC | 25m |
| 2026-05-22 | CUA5252 | - | May 22, 11:20 UTC | May 22, 11:35 UTC | 15m |
| 2026-05-22 | CUA5251 | - | May 22, 09:35 UTC | May 22, 10:00 UTC | 25m |
| 2026-05-12 | CUA5290 | - | May 12, 03:35 UTC | May 12, 04:05 UTC | 30m |
| 2026-05-11 | CUA5252 | - | May 11, 09:05 UTC | May 11, 09:15 UTC | 10m |
| 2026-05-11 | CUA5251 | - | May 11, 07:15 UTC | May 11, 07:35 UTC | 20m |
| 2026-05-04 | CUA5251 | - | May 4, 07:25 UTC | May 4, 07:45 UTC | 20m |
| 2026-05-03 | CUA5535 | - | May 3, 05:05 UTC | May 3, 05:15 UTC | 10m |
| 2026-05-02 | CUA5876 | ZUH → PKX | May 2, 07:30 UTC | May 2, 07:40 UTC | 10m |
| 2026-04-28 | CUA5596 | DBC → PKX | Apr 28, 03:10 UTC | Apr 28, 03:20 UTC | 10m |
| 2026-04-25 | CUA5651 | - | Apr 25, 06:10 UTC | Apr 25, 06:25 UTC | 15m |
| 2026-04-25 | CUA5525 | PKX → YSQ | Apr 25, 00:20 UTC | Apr 25, 00:30 UTC | 10m |
| 2026-04-24 | CUA5686 | HMI → PKX | Apr 24, 14:25 UTC | Apr 24, 14:40 UTC | 15m |
| 2026-04-23 | CUA5651 | - | Apr 23, 06:10 UTC | Apr 23, 06: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-1281 page for operator, model, and routing details .