sensors Mode-S transponder
780DD3
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1798 · BOEING 737-800
- Hex
- 780DD3
- Octal
- 36006723
- Decimal
- 7,867,859
- Country
- CN
- Tail
- B-1798
- Type
- B738
- Flights observed
- 41
- Distinct callsigns
- 18
- Country
- CN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 780DD3 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 |
|---|---|---|---|
| LKE9708 | - | 8 | 2026-07-15 |
| LKE9707 | - | 6 | 2026-06-23 |
| LKE9877 | - | 4 | 2026-07-08 |
| LKE9965 | - | 3 | 2026-06-27 |
| LKE9561 | - | 3 | 2026-07-13 |
| LKE9980 | Lucky Air | 2 | 2026-06-12 |
| LKE9890 | - | 2 | 2026-07-13 |
| LKE9843 | Lucky Air | 2 | 2026-06-05 |
| LKE9972 | Lucky Air | 1 | 2026-06-16 |
| LKE9884 | Lucky Air | 1 | 2026-06-01 |
| LKE9880 | Lucky Air | 1 | 2026-04-20 |
| LKE9879 | Lucky Air | 1 | 2026-05-30 |
| LKE9844 | Lucky Air | 1 | 2026-05-17 |
| LKE9691 | Lucky Air | 1 | 2026-05-28 |
| LKE9662 | Lucky Air | 1 | 2026-06-07 |
| LKE9556 | - | 1 | 2026-06-24 |
| LKE9555 | - | 1 | 2026-06-24 |
| LKE9545 | - | 1 | 2026-07-09 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | LKE9708 | - | Jul 15, 02:20 UTC | Jul 15, 02:40 UTC | 20m |
| 2026-07-13 | LKE9890 | - | Jul 13, 15:20 UTC | Jul 13, 15:35 UTC | 15m |
| 2026-07-13 | LKE9561 | - | Jul 13, 00:30 UTC | Jul 13, 00:40 UTC | 10m |
| 2026-07-09 | LKE9545 | - | Jul 9, 00:20 UTC | Jul 9, 09:15 UTC | 8h 55m |
| 2026-07-08 | LKE9877 | - | Jul 8, 13:35 UTC | Jul 9, 09:15 UTC | 19h 40m |
| 2026-06-27 | LKE9965 | - | Jun 27, 00:20 UTC | Jun 27, 14:14 UTC | 13h 55m |
| 2026-06-24 | LKE9556 | - | Jun 24, 09:05 UTC | Jun 24, 09:15 UTC | 10m |
| 2026-06-24 | LKE9555 | - | Jun 24, 04:39 UTC | Jun 24, 04:59 UTC | 20m |
| 2026-06-23 | LKE9708 | - | Jun 23, 02:45 UTC | Jun 23, 03:45 UTC | 1h 0m |
| 2026-06-23 | LKE9707 | - | Jun 23, 00:50 UTC | Jun 23, 01:00 UTC | 10m |
| 2026-06-21 | LKE9708 | - | Jun 21, 02:45 UTC | Jun 21, 07:49 UTC | 5h 5m |
| 2026-06-20 | LKE9707 | - | Jun 20, 23:50 UTC | Jun 21, 00:55 UTC | 1h 5m |
| 2026-06-17 | LKE9707 | - | Jun 17, 23:55 UTC | Jun 18, 03:10 UTC | 3h 15m |
| 2026-06-16 | LKE9972 | HAK → KMG | Jun 16, 00:29 UTC | Jun 16, 14:50 UTC | 14h 20m |
| 2026-06-14 | LKE9965 | KMG → SYX | Jun 14, 00:35 UTC | Jun 14, 03:30 UTC | 2h 55m |
| 2026-06-12 | LKE9980 | SZX → KMG | Jun 12, 13:35 UTC | Jun 12, 13:45 UTC | 10m |
| 2026-06-11 | LKE9965 | KMG → SYX | Jun 11, 00:30 UTC | Jun 11, 07:55 UTC | 7h 25m |
| 2026-06-10 | LKE9877 | - | Jun 10, 13:10 UTC | Jun 10, 13:20 UTC | 10m |
| 2026-06-07 | LKE9662 | ZUH → TFU | Jun 7, 02:50 UTC | Jun 7, 14:10 UTC | 11h 20m |
| 2026-06-05 | LKE9843 | KOW → HGH | Jun 5, 03:30 UTC | Jun 5, 11:15 UTC | 7h 45m |
| 2026-06-04 | LKE9843 | KOW → HGH | Jun 4, 13:50 UTC | Jun 5, 11:15 UTC | 21h 25m |
| 2026-06-04 | LKE9980 | SZX → KMG | Jun 4, 13:10 UTC | Jun 4, 13:20 UTC | 10m |
| 2026-06-01 | LKE9884 | ZUH → KMG | Jun 1, 03:30 UTC | Jun 1, 08:20 UTC | 4h 50m |
| 2026-05-31 | LKE9707 | - | May 31, 00:45 UTC | May 31, 01:11 UTC | 26m |
| 2026-05-30 | LKE9879 | KMG → FOC | May 30, 01:35 UTC | May 31, 00:45 UTC | 23h 10m |
| 2026-05-28 | LKE9691 | TFU → SYX | May 28, 03:30 UTC | May 28, 13:35 UTC | 10h 5m |
| 2026-05-17 | LKE9844 | KOW → HAK | May 17, 03:35 UTC | May 17, 11:05 UTC | 7h 30m |
| 2026-05-16 | LKE9877 | - | May 16, 13:01 UTC | May 16, 13:11 UTC | 10m |
| 2026-05-15 | LKE9890 | SZX → KMG | May 15, 17:55 UTC | May 16, 13:11 UTC | 19h 16m |
| 2026-05-15 | - | - | May 15, 16:20 UTC | May 15, 16:30 UTC | 10m |
| 2026-05-15 | LKE9561 | KMG → KOW | May 15, 00:00 UTC | May 15, 00:15 UTC | 15m |
| 2026-05-10 | LKE9708 | - | May 10, 02:50 UTC | May 11, 00:25 UTC | 21h 35m |
| 2026-05-10 | LKE9708 | - | May 10, 02:34 UTC | May 11, 00:25 UTC | 21h 50m |
| 2026-05-10 | LKE9707 | - | May 10, 00:34 UTC | May 10, 00:49 UTC | 15m |
| 2026-05-08 | LKE9708 | - | May 8, 00:29 UTC | May 8, 03:04 UTC | 2h 35m |
| 2026-05-06 | LKE9561 | KMG → KOW | May 6, 00:01 UTC | May 6, 00:10 UTC | 10m |
| 2026-04-20 | LKE9880 | FOC → KMG | Apr 20, 06:25 UTC | Apr 20, 06:50 UTC | 25m |
| 2026-04-18 | LKE9877 | - | Apr 18, 12:35 UTC | Apr 18, 12:50 UTC | 15m |
| 2026-04-17 | LKE9708 | - | Apr 17, 03:30 UTC | Apr 17, 04:00 UTC | 30m |
| 2026-04-17 | LKE9707 | - | Apr 17, 00:40 UTC | Apr 17, 00:55 UTC | 15m |
| 2026-04-15 | LKE9708 | - | Apr 15, 02:35 UTC | Apr 15, 02:50 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-1798 page for operator, model, and routing details .