sensors Mode-S transponder
780739
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-5580 · BOEING 737-800
- Hex
- 780739
- Octal
- 36003471
- Decimal
- 7,866,169
- Country
- CN
- Tail
- B-5580
- Type
- B738
- Flights observed
- 36
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- Jul 25, 12:10 UTC
Last known position
Country allocation
The ICAO 24-bit address 780739 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| CGN8418 | Chang'an Airlines | 7 | 2026-07-23 |
| CGN8495 | - | 4 | 2026-07-15 |
| CGN8398 | Chang'an Airlines | 3 | 2026-06-28 |
| CGN8455 | - | 2 | 2026-07-14 |
| CGN8413 | Chang'an Airlines | 2 | 2026-07-25 |
| CGN8397 | Chang'an Airlines | 2 | 2026-06-28 |
| CGN6005 | Chang'an Airlines | 2 | 2026-06-24 |
| CGN6002 | - | 2 | 2026-07-07 |
| CGN6001 | - | 2 | 2026-07-07 |
| CGN8463 | - | 1 | 2026-05-31 |
| CGN8415 | - | 1 | 2026-04-29 |
| CGN8400 | - | 1 | 2026-06-22 |
| CGN8399 | Chang'an Airlines | 1 | 2026-04-30 |
| CGN8351 | - | 1 | 2026-07-21 |
| CGN8349 | Chang'an Airlines | 1 | 2026-05-08 |
| CGN8331 | - | 1 | 2026-06-25 |
| CGN6019 | - | 1 | 2026-07-24 |
| CGN6003 | Chang'an Airlines | 1 | 2026-06-25 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | CGN8413 | NNY → SYX | Jul 25, 03:45 UTC | Jul 25, 12:10 UTC | 8h 25m |
| 2026-07-24 | CGN6019 | - | Jul 24, 12:45 UTC | Jul 24, 13:20 UTC | 35m |
| 2026-07-23 | CGN8418 | ZUH → JGS | Jul 23, 11:00 UTC | Jul 23, 11:10 UTC | 10m |
| 2026-07-21 | CGN8351 | - | Jul 21, 03:55 UTC | Jul 21, 16:55 UTC | 13h 0m |
| 2026-07-18 | CGN8418 | - | Jul 18, 11:05 UTC | Jul 18, 11:15 UTC | 10m |
| 2026-07-15 | CGN8495 | - | Jul 15, 11:30 UTC | Jul 15, 11:45 UTC | 15m |
| 2026-07-14 | CGN8455 | - | Jul 14, 06:10 UTC | Jul 14, 10:35 UTC | 4h 25m |
| 2026-07-08 | CGN8495 | - | Jul 8, 14:25 UTC | Jul 9, 09:40 UTC | 19h 15m |
| 2026-07-08 | CGN8495 | - | Jul 8, 12:20 UTC | Jul 9, 09:40 UTC | 21h 20m |
| 2026-07-08 | CGN8495 | - | Jul 8, 12:00 UTC | Jul 9, 09:40 UTC | 21h 40m |
| 2026-07-07 | CGN6002 | - | Jul 7, 17:40 UTC | Jul 7, 17:55 UTC | 15m |
| 2026-07-07 | CGN6001 | - | Jul 7, 15:50 UTC | Jul 7, 16:00 UTC | 10m |
| 2026-07-04 | CGN8455 | CSX → HRB | Jul 4, 05:55 UTC | Jul 4, 10:25 UTC | 4h 30m |
| 2026-06-28 | CGN8398 | ZHA → XIY | Jun 28, 14:09 UTC | Jun 28, 14:19 UTC | 10m |
| 2026-06-28 | CGN8397 | XIY → ZHA | Jun 28, 12:25 UTC | Jun 28, 12:35 UTC | 10m |
| 2026-06-25 | CGN6003 | XIY → HJJ | Jun 25, 09:45 UTC | Jun 26, 03:10 UTC | 17h 25m |
| 2026-06-25 | CGN8331 | - | Jun 25, 03:40 UTC | Jun 25, 03:50 UTC | 10m |
| 2026-06-24 | CGN6005 | LLF → HAK | Jun 24, 08:39 UTC | Jun 24, 08:49 UTC | 10m |
| 2026-06-22 | CGN8398 | ZHA → XIY | Jun 22, 14:19 UTC | Jun 22, 14:34 UTC | 15m |
| 2026-06-22 | CGN8400 | - | Jun 22, 07:19 UTC | Jun 22, 12:40 UTC | 5h 20m |
| 2026-06-20 | CGN8418 | - | Jun 20, 10:59 UTC | Jun 20, 11:14 UTC | 15m |
| 2026-06-18 | CGN8418 | - | Jun 18, 13:15 UTC | Jun 18, 13:30 UTC | 15m |
| 2026-06-14 | CGN6005 | LLF → HAK | Jun 14, 08:40 UTC | Jun 14, 08:50 UTC | 10m |
| 2026-06-04 | CGN8418 | ZUH → JGS | Jun 4, 11:35 UTC | Jun 4, 11:45 UTC | 10m |
| 2026-06-03 | CGN8398 | ZHA → XIY | Jun 3, 14:10 UTC | Jun 3, 14:20 UTC | 10m |
| 2026-06-03 | CGN8397 | - | Jun 3, 12:10 UTC | Jun 3, 12:20 UTC | 10m |
| 2026-06-02 | CGN8413 | NNY → SYX | Jun 2, 02:50 UTC | Jun 2, 03:00 UTC | 10m |
| 2026-05-31 | CGN8463 | - | May 31, 09:00 UTC | May 31, 09:10 UTC | 10m |
| 2026-05-22 | - | - | May 22, 12:20 UTC | May 22, 12:30 UTC | 10m |
| 2026-05-08 | CGN8349 | XIY → CGQ | May 8, 09:34 UTC | May 8, 09:49 UTC | 15m |
| 2026-05-07 | CGN8418 | ZUH → JGS | May 7, 11:00 UTC | May 7, 11:10 UTC | 10m |
| 2026-04-30 | CGN8399 | XIY → TGO | Apr 30, 00:20 UTC | Apr 30, 00:40 UTC | 20m |
| 2026-04-29 | CGN8415 | - | Apr 29, 02:24 UTC | Apr 29, 02:35 UTC | 10m |
| 2026-04-16 | CGN6002 | - | Apr 16, 11:44 UTC | Apr 16, 11:54 UTC | 10m |
| 2026-04-16 | CGN6001 | XIY → SZX | Apr 16, 09:45 UTC | Apr 16, 09:54 UTC | 10m |
| 2026-04-14 | CGN8418 | ZUH → JGS | Apr 14, 12:25 UTC | Apr 14, 12:35 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-5580 page for operator, model, and routing details .