sensors Mode-S transponder
407990
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-SADB · DIAMOND DA-42 Guardian
- Hex
- 407990
- Octal
- 20074620
- Decimal
- 4,225,424
- Country
- GB
- Tail
- G-SADB
- Type
- DA42
- Flights observed
- 85
- Distinct callsigns
- 2
- Country
- GB
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 407990 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SFY3DB | - | May 29, 15:00 UTC | May 29, 16:25 UTC | 1h 25m |
| 2026-05-29 | SFY3DB | - | May 29, 12:15 UTC | May 29, 13:35 UTC | 1h 20m |
| 2026-05-29 | SFY3DB | - | May 29, 08:00 UTC | May 29, 09:35 UTC | 1h 35m |
| 2026-05-24 | SFY3DB | - | May 24, 12:40 UTC | May 24, 14:40 UTC | 2h 0m |
| 2026-05-24 | SFY3DB | - | May 24, 09:20 UTC | May 24, 11:15 UTC | 1h 55m |
| 2026-05-22 | SFY3DB | - | May 22, 12:35 UTC | May 22, 13:35 UTC | 1h 0m |
| 2026-05-21 | SFY3DB | GLO → GLO | May 21, 16:10 UTC | May 21, 17:50 UTC | 1h 40m |
| 2026-05-21 | SFY3DB | - | May 21, 14:05 UTC | May 21, 15:15 UTC | 1h 10m |
| 2026-05-21 | SFY3DB | - | May 21, 11:55 UTC | May 21, 13:05 UTC | 1h 10m |
| 2026-05-20 | SFY3DB | - | May 20, 15:10 UTC | May 20, 15:50 UTC | 40m |
| 2026-05-12 | SFY3DB | - | May 12, 13:20 UTC | May 12, 14:45 UTC | 1h 25m |
| 2026-05-12 | SFY3DB | - | May 12, 09:15 UTC | May 12, 10:25 UTC | 1h 10m |
| 2026-05-11 | SFY3DB | - | May 11, 14:10 UTC | May 11, 15:00 UTC | 50m |
| 2026-05-11 | SFY3DB | - | May 11, 12:20 UTC | May 11, 13:20 UTC | 1h 0m |
| 2026-05-10 | SFY3DB | - | May 10, 15:35 UTC | May 10, 17:20 UTC | 1h 45m |
| 2026-05-09 | SFY3DB | - | May 9, 09:20 UTC | May 9, 11:20 UTC | 2h 0m |
| 2026-05-08 | SFY3DB | - | May 8, 16:15 UTC | May 8, 17:30 UTC | 1h 15m |
| 2026-05-08 | SFY3DB | - | May 8, 13:10 UTC | May 8, 14:15 UTC | 1h 5m |
| 2026-05-08 | SFY3DB | - | May 8, 08:55 UTC | May 8, 10:39 UTC | 1h 45m |
| 2026-05-07 | SFY3DB | - | May 7, 15:10 UTC | May 7, 16:25 UTC | 1h 15m |
| 2026-05-07 | SFY3DB | - | May 7, 12:35 UTC | May 7, 14:00 UTC | 1h 25m |
| 2026-05-07 | SFY3DB | GLO → GLO | May 7, 08:35 UTC | May 7, 10:15 UTC | 1h 40m |
| 2026-05-06 | SFY3DB | - | May 6, 14:50 UTC | May 6, 16:00 UTC | 1h 10m |
| 2026-05-06 | SFY3DB | - | May 6, 10:35 UTC | May 6, 11:55 UTC | 1h 20m |
| 2026-05-06 | SFY3DB | - | May 6, 08:10 UTC | May 6, 09:40 UTC | 1h 30m |
| 2026-05-04 | SFY3DB | GLO → GLO | May 4, 16:20 UTC | May 4, 17:40 UTC | 1h 20m |
| 2026-05-04 | SFY3DB | - | May 4, 08:05 UTC | May 4, 09:55 UTC | 1h 50m |
| 2026-05-02 | SFY3DB | - | May 2, 10:20 UTC | May 2, 11:35 UTC | 1h 15m |
| 2026-05-02 | EXM94 | - | May 2, 08:40 UTC | May 2, 09:10 UTC | 30m |
| 2026-05-01 | SFY3DB | - | May 1, 16:00 UTC | May 1, 17:40 UTC | 1h 40m |
| 2026-05-01 | SFY3DB | - | May 1, 13:20 UTC | May 1, 14:45 UTC | 1h 25m |
| 2026-05-01 | SFY3DB | - | May 1, 10:10 UTC | May 1, 11:50 UTC | 1h 40m |
| 2026-05-01 | SFY3DB | - | May 1, 08:30 UTC | May 1, 09:35 UTC | 1h 5m |
| 2026-04-30 | SFY3DB | GLO → GLO | Apr 30, 16:25 UTC | Apr 30, 17:55 UTC | 1h 30m |
| 2026-04-30 | SFY3DB | - | Apr 30, 13:45 UTC | Apr 30, 15:35 UTC | 1h 50m |
| 2026-04-30 | SFY3DB | - | Apr 30, 11:15 UTC | Apr 30, 12:50 UTC | 1h 35m |
| 2026-04-30 | SFY3DB | - | Apr 30, 08:10 UTC | Apr 30, 09:50 UTC | 1h 40m |
| 2026-04-29 | SFY3DB | - | Apr 29, 13:55 UTC | Apr 29, 15:30 UTC | 1h 35m |
| 2026-04-29 | SFY3DB | - | Apr 29, 10:30 UTC | Apr 29, 12:15 UTC | 1h 45m |
| 2026-04-29 | SFY3DB | - | Apr 29, 08:05 UTC | Apr 29, 09:45 UTC | 1h 41m |
| 2026-04-28 | SFY3DB | - | Apr 28, 17:15 UTC | Apr 28, 18:25 UTC | 1h 10m |
| 2026-04-28 | SFY3DB | - | Apr 28, 15:35 UTC | Apr 28, 16:20 UTC | 45m |
| 2026-04-28 | SFY3DB | - | Apr 28, 15:10 UTC | Apr 28, 15:30 UTC | 20m |
| 2026-04-27 | SFY3DB | - | Apr 27, 17:40 UTC | Apr 27, 18:30 UTC | 50m |
| 2026-04-27 | SFY3DB | - | Apr 27, 14:55 UTC | Apr 27, 16:45 UTC | 1h 50m |
| 2026-04-27 | SFY3DB | - | Apr 27, 12:10 UTC | Apr 27, 13:50 UTC | 1h 40m |
| 2026-04-27 | SFY3DB | CWL → GLO | Apr 27, 10:05 UTC | Apr 27, 11:20 UTC | 1h 15m |
| 2026-04-27 | SFY3DB | - | Apr 27, 09:30 UTC | Apr 27, 10:00 UTC | 30m |
| 2026-04-25 | SFY3DB | - | Apr 25, 11:20 UTC | Apr 25, 13:10 UTC | 1h 50m |
| 2026-04-25 | SFY3DB | - | Apr 25, 07:25 UTC | Apr 25, 09:30 UTC | 2h 5m |
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-SADB page for operator, model, and routing details .