sensors Mode-S transponder
780BFD
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1926 · BOEING 737-800
- Hex
- 780BFD
- Octal
- 36005775
- Decimal
- 7,867,389
- Country
- CN
- Tail
- B-1926
- Type
- B738
- Flights observed
- 51
- Distinct callsigns
- 14
- Country
- CN
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 780BFD 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| KNA8369 | Knight Air | 10 | 2026-05-27 |
| KNA8370 | Knight Air | 6 | 2026-05-27 |
| KNA8272 | Knight Air | 6 | 2026-04-30 |
| KNA8269 | Knight Air | 6 | 2026-05-22 |
| KNA8270 | Knight Air | 5 | 2026-05-08 |
| KNA8249 | Knight Air | 5 | 2026-05-28 |
| KNA8271 | Knight Air | 4 | 2026-04-29 |
| KNA8368 | - | 2 | 2026-04-14 |
| KNA8367 | Knight Air | 2 | 2026-04-14 |
| KNA8286 | Knight Air | 1 | 2026-04-16 |
| KNA8280 | Knight Air | 1 | 2026-05-08 |
| KNA8278 | Knight Air | 1 | 2026-05-18 |
| KNA8250 | Knight Air | 1 | 2026-05-29 |
| KNA8245 | Knight Air | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | KNA8250 | HRB → KHN | May 29, 01:25 UTC | May 29, 13:20 UTC | 11h 55m |
| 2026-05-28 | KNA8249 | KHN → HRB | May 28, 13:25 UTC | May 29, 13:15 UTC | 23h 50m |
| 2026-05-28 | KNA8249 | KHN → HRB | May 28, 02:55 UTC | May 28, 13:40 UTC | 10h 45m |
| 2026-05-27 | KNA8370 | BKK → KMG | May 27, 13:20 UTC | May 27, 14:10 UTC | 50m |
| 2026-05-27 | KNA8369 | KMG → BKK | May 27, 01:59 UTC | May 27, 11:35 UTC | 9h 36m |
| 2026-05-26 | KNA8369 | KMG → BKK | May 26, 13:19 UTC | May 27, 11:35 UTC | 22h 16m |
| 2026-05-26 | KNA8369 | KMG → BKK | May 26, 13:10 UTC | May 27, 11:15 UTC | 22h 6m |
| 2026-05-23 | KNA8370 | BKK → KMG | May 23, 13:05 UTC | May 23, 14:00 UTC | 55m |
| 2026-05-23 | KNA8369 | KMG → BKK | May 23, 10:30 UTC | May 23, 11:30 UTC | 1h 0m |
| 2026-05-22 | KNA8269 | KMG → PEK | May 22, 03:00 UTC | May 22, 03:30 UTC | 30m |
| 2026-05-19 | KNA8249 | KHN → HRB | May 19, 13:50 UTC | May 20, 02:05 UTC | 12h 15m |
| 2026-05-19 | KNA8249 | KHN → HRB | May 19, 01:50 UTC | May 19, 14:05 UTC | 12h 15m |
| 2026-05-18 | KNA8249 | KHN → HRB | May 18, 13:10 UTC | May 19, 02:00 UTC | 12h 49m |
| 2026-05-18 | KNA8278 | WUH → KMG | May 18, 02:20 UTC | May 18, 02:35 UTC | 15m |
| 2026-05-13 | KNA8370 | BKK → KMG | May 13, 13:15 UTC | May 13, 14:05 UTC | 50m |
| 2026-05-13 | KNA8369 | KMG → BKK | May 13, 10:50 UTC | May 13, 11:45 UTC | 55m |
| 2026-05-11 | KNA8370 | BKK → KMG | May 11, 13:20 UTC | May 11, 14:20 UTC | 1h 0m |
| 2026-05-11 | KNA8369 | KMG → BKK | May 11, 10:40 UTC | May 11, 11:45 UTC | 1h 5m |
| 2026-05-10 | KNA8369 | KMG → BKK | May 10, 13:30 UTC | May 11, 11:45 UTC | 22h 15m |
| 2026-05-10 | KNA8369 | KMG → BKK | May 10, 10:35 UTC | May 10, 11:35 UTC | 1h 0m |
| 2026-05-08 | KNA8280 | CAN → KMG | May 8, 14:35 UTC | May 9, 05:05 UTC | 14h 30m |
| 2026-05-08 | KNA8270 | PEK → KMG | May 8, 05:59 UTC | May 8, 06:25 UTC | 25m |
| 2026-05-08 | KNA8269 | KMG → PEK | May 8, 03:30 UTC | May 8, 03:49 UTC | 20m |
| 2026-05-07 | KNA8270 | PEK → KMG | May 7, 05:50 UTC | May 7, 06:05 UTC | 15m |
| 2026-05-07 | KNA8269 | KMG → PEK | May 7, 03:30 UTC | May 7, 03:50 UTC | 20m |
| 2026-05-06 | KNA8270 | PEK → KMG | May 6, 05:45 UTC | May 6, 06:15 UTC | 30m |
| 2026-05-06 | KNA8269 | KMG → PEK | May 6, 03:20 UTC | May 6, 03:40 UTC | 20m |
| 2026-05-05 | KNA8270 | PEK → KMG | May 5, 05:50 UTC | May 5, 06:20 UTC | 30m |
| 2026-05-05 | KNA8269 | KMG → PEK | May 5, 03:40 UTC | May 5, 04:00 UTC | 20m |
| 2026-05-03 | KNA8245 | TFU → HRB | May 3, 15:30 UTC | May 4, 04:44 UTC | 13h 15m |
| 2026-04-30 | KNA8272 | SZX → KMG | Apr 30, 00:45 UTC | Apr 30, 00:55 UTC | 10m |
| 2026-04-29 | KNA8271 | KMG → SZX | Apr 29, 17:15 UTC | Apr 29, 17:25 UTC | 10m |
| 2026-04-29 | KNA8272 | SZX → KMG | Apr 29, 03:49 UTC | Apr 29, 04:10 UTC | 20m |
| 2026-04-27 | KNA8270 | PEK → KMG | Apr 27, 05:40 UTC | Apr 27, 06:10 UTC | 30m |
| 2026-04-27 | KNA8269 | KMG → PEK | Apr 27, 03:25 UTC | Apr 27, 03:40 UTC | 15m |
| 2026-04-26 | KNA8272 | SZX → KMG | Apr 26, 00:55 UTC | Apr 26, 08:35 UTC | 7h 40m |
| 2026-04-25 | KNA8272 | SZX → KMG | Apr 25, 00:55 UTC | Apr 25, 01:10 UTC | 15m |
| 2026-04-24 | KNA8271 | KMG → SZX | Apr 24, 17:20 UTC | Apr 24, 17:30 UTC | 10m |
| 2026-04-24 | KNA8272 | SZX → KMG | Apr 24, 01:15 UTC | Apr 24, 01:30 UTC | 15m |
| 2026-04-23 | KNA8271 | KMG → SZX | Apr 23, 20:50 UTC | Apr 23, 21:00 UTC | 10m |
| 2026-04-23 | KNA8272 | SZX → KMG | Apr 23, 02:10 UTC | Apr 23, 02:25 UTC | 15m |
| 2026-04-22 | KNA8271 | KMG → SZX | Apr 22, 14:35 UTC | Apr 22, 14:45 UTC | 10m |
| 2026-04-21 | KNA8370 | BKK → KMG | Apr 21, 13:20 UTC | Apr 21, 14:05 UTC | 45m |
| 2026-04-21 | KNA8369 | KMG → BKK | Apr 21, 10:35 UTC | Apr 21, 11:30 UTC | 55m |
| 2026-04-20 | KNA8370 | BKK → KMG | Apr 20, 16:10 UTC | Apr 21, 11:30 UTC | 19h 20m |
| 2026-04-20 | KNA8369 | KMG → BKK | Apr 20, 13:50 UTC | Apr 20, 14:45 UTC | 55m |
| 2026-04-16 | KNA8286 | HUZ → KMG | Apr 16, 15:30 UTC | Apr 16, 15:55 UTC | 25m |
| 2026-04-14 | KNA8368 | - | Apr 14, 11:50 UTC | Apr 14, 12:10 UTC | 20m |
| 2026-04-14 | KNA8367 | KMG → BKK | Apr 14, 09:40 UTC | Apr 14, 10:10 UTC | 30m |
| 2026-04-13 | KNA8368 | - | Apr 13, 12:00 UTC | Apr 13, 12:10 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-1926 page for operator, model, and routing details .