sensors Mode-S transponder
781D3C
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-221H · BOEING 767-300
- Hex
- 781D3C
- Octal
- 36016474
- Decimal
- 7,871,804
- Country
- CN
- Tail
- B-221H
- Type
- B763
- Flights observed
- 53
- Distinct callsigns
- 10
- Country
- CN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 781D3C 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 10 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | HYT9008 | - | Jun 1, 08:25 UTC | Jun 1, 09:10 UTC | 45m |
| 2026-06-01 | HYT9007 | - | Jun 1, 05:55 UTC | Jun 1, 06:55 UTC | 1h 0m |
| 2026-05-31 | HYT9007 | DAC → DAC | May 31, 09:10 UTC | Jun 1, 06:55 UTC | 21h 45m |
| 2026-05-29 | HYT9008 | - | May 29, 08:35 UTC | May 29, 09:30 UTC | 55m |
| 2026-05-29 | HYT9007 | - | May 29, 06:00 UTC | May 29, 07:00 UTC | 1h 0m |
| 2026-05-28 | HYT9007 | - | May 28, 09:10 UTC | May 29, 07:00 UTC | 21h 50m |
| 2026-05-28 | HYT9007 | DAC → DAC | May 28, 08:40 UTC | May 29, 07:00 UTC | 22h 20m |
| 2026-05-28 | HYT9007 | - | May 28, 06:25 UTC | May 28, 07:30 UTC | 1h 5m |
| 2026-05-23 | HYT9008 | - | May 23, 08:50 UTC | May 23, 09:05 UTC | 15m |
| 2026-05-23 | HYT9007 | - | May 23, 06:20 UTC | May 23, 07:05 UTC | 45m |
| 2026-05-21 | HYT9060 | - | May 21, 08:35 UTC | May 21, 09:30 UTC | 55m |
| 2026-05-21 | HYT9059 | - | May 21, 06:30 UTC | May 21, 07:10 UTC | 40m |
| 2026-05-16 | HYT9060 | - | May 16, 09:31 UTC | May 16, 10:01 UTC | 30m |
| 2026-05-16 | HYT9059 | - | May 16, 06:31 UTC | May 16, 07:05 UTC | 35m |
| 2026-05-14 | HYT9060 | - | May 14, 08:30 UTC | May 14, 09:15 UTC | 45m |
| 2026-05-14 | HYT9059 | - | May 14, 06:05 UTC | May 14, 07:00 UTC | 55m |
| 2026-05-12 | HYT9060 | - | May 12, 10:40 UTC | May 12, 11:25 UTC | 45m |
| 2026-05-12 | HYT9059 | - | May 12, 07:40 UTC | May 12, 08:45 UTC | 1h 5m |
| 2026-05-11 | HYT9059 | DAC → DAC | May 11, 09:05 UTC | May 12, 08:45 UTC | 23h 41m |
| 2026-05-11 | HYT9059 | - | May 11, 06:25 UTC | May 11, 07:15 UTC | 50m |
| 2026-05-09 | HYT9060 | - | May 9, 08:45 UTC | May 9, 09:15 UTC | 30m |
| 2026-05-09 | HYT9059 | - | May 9, 06:35 UTC | May 9, 07:20 UTC | 45m |
| 2026-05-07 | HYT9060 | - | May 7, 08:10 UTC | May 7, 08:40 UTC | 30m |
| 2026-05-07 | HYT9059 | - | May 7, 05:40 UTC | May 7, 06:50 UTC | 1h 10m |
| 2026-05-04 | HYT9060 | - | May 4, 09:00 UTC | May 4, 09:20 UTC | 20m |
| 2026-05-04 | HYT9059 | - | May 4, 06:40 UTC | May 4, 07:25 UTC | 45m |
| 2026-05-02 | HYT9060 | - | May 2, 12:50 UTC | May 2, 13:20 UTC | 30m |
| 2026-05-02 | HYT9059 | - | May 2, 09:20 UTC | May 2, 10:25 UTC | 1h 5m |
| 2026-04-30 | HYT9060 | - | Apr 30, 10:50 UTC | Apr 30, 11:25 UTC | 35m |
| 2026-04-30 | HYT9083 | - | Apr 30, 08:30 UTC | Apr 30, 09:15 UTC | 45m |
| 2026-04-29 | HYT9083 | - | Apr 29, 10:35 UTC | Apr 30, 09:00 UTC | 22h 25m |
| 2026-04-28 | HYT9087 | DAC → DAC | Apr 28, 21:10 UTC | Apr 29, 09:20 UTC | 12h 11m |
| 2026-04-28 | HYT9059 | - | Apr 28, 07:35 UTC | Apr 28, 19:30 UTC | 11h 55m |
| 2026-04-28 | HYT9087 | - | Apr 28, 03:50 UTC | Apr 28, 04:35 UTC | 45m |
| 2026-04-27 | HYT9087 | - | Apr 27, 07:55 UTC | Apr 28, 04:35 UTC | 20h 40m |
| 2026-04-27 | HYT9087 | - | Apr 27, 05:35 UTC | Apr 27, 06:35 UTC | 1h 0m |
| 2026-04-26 | HYT9088 | - | Apr 26, 05:15 UTC | Apr 26, 05:55 UTC | 40m |
| 2026-04-26 | HYT9059 | - | Apr 26, 00:50 UTC | Apr 26, 02:00 UTC | 1h 10m |
| 2026-04-23 | HYT9060 | - | Apr 23, 09:15 UTC | Apr 23, 10:05 UTC | 50m |
| 2026-04-23 | HYT9059 | - | Apr 23, 06:30 UTC | Apr 23, 07:45 UTC | 1h 15m |
| 2026-04-21 | HYT9060 | - | Apr 21, 09:10 UTC | Apr 21, 09:55 UTC | 45m |
| 2026-04-21 | HYT9059 | - | Apr 21, 06:45 UTC | Apr 21, 07:25 UTC | 40m |
| 2026-04-20 | HYT9059 | - | Apr 20, 09:05 UTC | Apr 21, 07:25 UTC | 22h 20m |
| 2026-04-20 | HYT9060 | - | Apr 20, 08:50 UTC | Apr 21, 07:00 UTC | 22h 11m |
| 2026-04-20 | HYT9059 | - | Apr 20, 06:30 UTC | Apr 20, 07:15 UTC | 45m |
| 2026-04-18 | HYT9058 | - | Apr 18, 07:45 UTC | Apr 18, 08:15 UTC | 30m |
| 2026-04-18 | HYT9083 | - | Apr 18, 05:25 UTC | Apr 18, 05:55 UTC | 30m |
| 2026-04-18 | HYT9083 | - | Apr 18, 05:10 UTC | Apr 18, 05:20 UTC | 10m |
| 2026-04-17 | HYT9084 | - | Apr 17, 08:35 UTC | Apr 17, 09:00 UTC | 25m |
| 2026-04-17 | HYT9057 | - | Apr 17, 06:20 UTC | Apr 17, 07:10 UTC | 50m |
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-221H page for operator, model, and routing details .