sensors Mode-S transponder
406D7A
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-ZBKD · BOEING 787-9 Dreamliner
- Hex
- 406D7A
- Octal
- 20066572
- Decimal
- 4,222,330
- Country
- GB
- Tail
- G-ZBKD
- Type
- B789
- Flights observed
- 199
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 406D7A falls within the block assigned to United Kingdom (GB) by ICAO Annex 10, Volume III. Every aircraft registered in United Kingdom 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 |
|---|---|---|---|
| BAW168 | - | 31 | 2026-07-13 |
| BAW169 | - | 21 | 2026-07-12 |
| BAW16 | British Airways | 21 | 2026-07-06 |
| BAW15 | British Airways | 17 | 2026-07-05 |
| BAW33 | - | 15 | 2026-07-13 |
| BAW34 | - | 12 | 2026-06-21 |
| BAW81V | - | 6 | 2026-07-02 |
| BAW37J | British Airways | 6 | 2026-06-07 |
| BAW26E | - | 6 | 2026-07-02 |
| BAW18A | British Airways | 6 | 2026-06-08 |
| BAW70Q | - | 5 | 2026-06-17 |
| BAW243 | British Airways | 5 | 2026-06-19 |
| BAW171 | British Airways | 5 | 2026-06-16 |
| BAW6 | - | 4 | 2026-07-08 |
| BAW5 | British Airways | 4 | 2026-07-07 |
| BAW242 | - | 4 | 2026-06-20 |
| BAW36 | British Airways | 3 | 2026-06-03 |
| BAW250 | British Airways | 3 | 2026-05-23 |
| BAW49N | British Airways | 2 | 2026-05-29 |
| BAW276 | British Airways | 2 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | BAW33 | - | Jul 13, 21:00 UTC | Jul 14, 08:25 UTC | 11h 25m |
| 2026-07-13 | BAW168 | - | Jul 13, 05:05 UTC | Jul 13, 17:30 UTC | 12h 25m |
| 2026-07-12 | BAW168 | - | Jul 12, 15:35 UTC | Jul 13, 13:45 UTC | 22h 10m |
| 2026-07-12 | BAW169 | - | Jul 12, 12:35 UTC | Jul 13, 12:30 UTC | 23h 55m |
| 2026-07-12 | BAW169 | - | Jul 12, 11:35 UTC | Jul 13, 09:15 UTC | 21h 40m |
| 2026-07-09 | BAW138 | - | Jul 9, 21:40 UTC | Jul 10, 06:55 UTC | 9h 15m |
| 2026-07-09 | BAW139 | LHR → BOM | Jul 9, 09:20 UTC | Jul 9, 18:05 UTC | 8h 45m |
| 2026-07-08 | BAW6 | HND → LHR | Jul 8, 04:20 UTC | Jul 8, 18:20 UTC | 14h 0m |
| 2026-07-07 | BAW5 | LHR → NRT | Jul 7, 13:05 UTC | Jul 8, 01:55 UTC | 12h 50m |
| 2026-07-06 | BAW16 | SIN → LHR | Jul 6, 15:15 UTC | Jul 7, 04:25 UTC | 13h 10m |
| 2026-07-06 | BAW16 | SIN → LHR | Jul 6, 12:30 UTC | Jul 6, 12:40 UTC | 10m |
| 2026-07-06 | BAW16 | SIN → LHR | Jul 6, 04:55 UTC | Jul 6, 05:25 UTC | 30m |
| 2026-07-05 | BAW15 | SIN → SYD | Jul 5, 12:50 UTC | Jul 5, 20:05 UTC | 7h 15m |
| 2026-07-04 | BAW15 | SIN → SYD | Jul 4, 21:20 UTC | Jul 5, 10:20 UTC | 13h 0m |
| 2026-07-04 | BAW168 | - | Jul 4, 05:35 UTC | Jul 4, 17:50 UTC | 12h 15m |
| 2026-07-03 | BAW168 | - | Jul 3, 18:35 UTC | Jul 4, 17:50 UTC | 23h 15m |
| 2026-07-03 | BAW168 | - | Jul 3, 15:10 UTC | Jul 4, 13:55 UTC | 22h 45m |
| 2026-07-03 | BAW169 | - | Jul 3, 11:35 UTC | Jul 4, 06:00 UTC | 18h 25m |
| 2026-07-02 | BAW81V | - | Jul 2, 22:00 UTC | Jul 3, 06:30 UTC | 8h 30m |
| 2026-07-02 | BAW26E | - | Jul 2, 08:45 UTC | Jul 2, 18:50 UTC | 10h 5m |
| 2026-07-01 | BAW168 | - | Jul 1, 05:15 UTC | Jul 1, 17:20 UTC | 12h 5m |
| 2026-06-30 | BAW168 | - | Jun 30, 14:35 UTC | Jul 1, 13:45 UTC | 23h 10m |
| 2026-06-30 | BAW169 | - | Jun 30, 11:35 UTC | Jul 1, 05:35 UTC | 18h 0m |
| 2026-06-29 | BAW16 | SIN → LHR | Jun 29, 14:54 UTC | Jun 30, 03:50 UTC | 12h 56m |
| 2026-06-29 | BAW16 | SIN → LHR | Jun 29, 12:39 UTC | Jun 29, 12:49 UTC | 10m |
| 2026-06-29 | BAW16 | SIN → LHR | Jun 29, 05:00 UTC | Jun 29, 05:34 UTC | 35m |
| 2026-06-28 | BAW15 | SIN → SYD | Jun 28, 19:04 UTC | Jun 28, 19:44 UTC | 40m |
| 2026-06-28 | BAW15 | SIN → SYD | Jun 28, 12:55 UTC | Jun 28, 13:04 UTC | 10m |
| 2026-06-27 | BAW15 | SIN → SYD | Jun 27, 22:15 UTC | Jun 28, 11:00 UTC | 12h 45m |
| 2026-06-27 | BAW168 | - | Jun 27, 04:39 UTC | Jun 27, 17:09 UTC | 12h 30m |
| 2026-06-26 | BAW168 | - | Jun 26, 18:44 UTC | Jun 27, 17:09 UTC | 22h 25m |
| 2026-06-26 | BAW168 | - | Jun 26, 14:35 UTC | Jun 27, 14:29 UTC | 23h 55m |
| 2026-06-26 | BAW169 | - | Jun 26, 12:34 UTC | Jun 27, 12:29 UTC | 23h 55m |
| 2026-06-26 | BAW169 | - | Jun 26, 11:34 UTC | Jun 27, 08:44 UTC | 21h 10m |
| 2026-06-25 | BAW16 | SIN → LHR | Jun 25, 14:59 UTC | Jun 26, 04:10 UTC | 13h 10m |
| 2026-06-25 | BAW16 | SIN → LHR | Jun 25, 04:45 UTC | Jun 25, 05:20 UTC | 35m |
| 2026-06-24 | BAW15 | SIN → SYD | Jun 24, 19:20 UTC | Jun 24, 20:20 UTC | 1h 0m |
| 2026-06-24 | BAW15 | SIN → SYD | Jun 24, 13:05 UTC | Jun 24, 13:14 UTC | 10m |
| 2026-06-23 | BAW15 | SIN → SYD | Jun 23, 21:20 UTC | Jun 24, 10:14 UTC | 12h 55m |
| 2026-06-23 | BAW168 | - | Jun 23, 04:55 UTC | Jun 23, 17:15 UTC | 12h 20m |
| 2026-06-22 | BAW168 | - | Jun 22, 19:00 UTC | Jun 23, 17:15 UTC | 22h 15m |
| 2026-06-22 | BAW168 | - | Jun 22, 14:34 UTC | Jun 23, 14:29 UTC | 23h 55m |
| 2026-06-22 | BAW169 | - | Jun 22, 12:34 UTC | Jun 23, 12:29 UTC | 23h 55m |
| 2026-06-22 | BAW169 | - | Jun 22, 11:44 UTC | Jun 23, 08:59 UTC | 21h 15m |
| 2026-06-21 | BAW34 | - | Jun 21, 15:19 UTC | Jun 22, 04:15 UTC | 12h 55m |
| 2026-06-20 | BAW33 | LHR → KUL | Jun 20, 21:14 UTC | Jun 21, 09:24 UTC | 12h 10m |
| 2026-06-20 | BAW242 | - | Jun 20, 04:24 UTC | Jun 20, 14:09 UTC | 9h 45m |
| 2026-06-19 | BAW243 | LHR → MEX | Jun 19, 14:54 UTC | Jun 20, 01:55 UTC | 11h 0m |
| 2026-06-18 | BAW6 | HND → LHR | Jun 18, 05:35 UTC | Jun 18, 19:35 UTC | 14h 0m |
| 2026-06-17 | BAW5 | LHR → NRT | Jun 17, 12:25 UTC | Jun 18, 01:20 UTC | 12h 55m |
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 G-ZBKD page for operator, model, and routing details .