sensors Mode-S transponder
4009D2
ICAO 24-bit transponder address · allocated to United Kingdom
Currently assigned to G-FRAR · DASSAULT Falcon 200
- Hex
- 4009D2
- Octal
- 20004722
- Decimal
- 4,196,818
- Country
- GB
- Tail
- G-FRAR
- Type
- FA20
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- GB
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4009D2 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 |
|---|---|---|---|
| AMBER2 | - | 19 | 2026-07-17 |
| AMBER1 | - | 12 | 2026-07-14 |
| CRIMSON1 | - | 11 | 2026-07-08 |
| BWY40 | - | 10 | 2026-07-09 |
| BLUE1 | - | 7 | 2026-06-05 |
| CRIMSON2 | - | 5 | 2026-07-14 |
| FRA84 | - | 2 | 2026-07-16 |
| AMBER4 | - | 2 | 2026-06-11 |
| WRTHOG82 | - | 1 | 2026-05-28 |
| WRTHOG13 | - | 1 | 2026-06-17 |
| MTHBAL93 | - | 1 | 2026-07-16 |
| FRA97 | - | 1 | 2026-05-28 |
| FRA96 | - | 1 | 2026-07-16 |
| FRA88 | - | 1 | 2026-06-09 |
| FRA75 | - | 1 | 2026-06-17 |
| CRMSON2 | - | 1 | 2026-06-01 |
| CRMSON1 | - | 1 | 2026-06-03 |
| BWY31 | - | 1 | 2026-07-13 |
| BWY21 | - | 1 | 2026-04-20 |
| AMBER3 | - | 1 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | AMBER2 | BOH → BOH | Jul 17, 08:30 UTC | Jul 17, 10:20 UTC | 1h 50m |
| 2026-07-16 | FRA96 | MME → BOH | Jul 16, 14:00 UTC | Jul 16, 14:50 UTC | 50m |
| 2026-07-16 | MTHBAL93 | MME → MME | Jul 16, 10:50 UTC | Jul 16, 12:14 UTC | 1h 25m |
| 2026-07-16 | FRA84 | BOH → MME | Jul 16, 06:35 UTC | Jul 16, 07:30 UTC | 55m |
| 2026-07-15 | FRA84 | NQY → BOH | Jul 15, 13:55 UTC | Jul 15, 14:25 UTC | 30m |
| 2026-07-15 | AMBER2 | BOH → NQY | Jul 15, 10:05 UTC | Jul 15, 12:20 UTC | 2h 15m |
| 2026-07-14 | AMBER1 | BOH → BOH | Jul 14, 13:40 UTC | Jul 14, 15:30 UTC | 1h 50m |
| 2026-07-14 | CRIMSON2 | BOH → BOH | Jul 14, 10:00 UTC | Jul 14, 11:20 UTC | 1h 20m |
| 2026-07-13 | AMBER2 | BOH → BOH | Jul 13, 18:55 UTC | Jul 13, 20:20 UTC | 1h 25m |
| 2026-07-13 | BWY31 | BOH → BOH | Jul 13, 12:45 UTC | Jul 13, 15:10 UTC | 2h 25m |
| 2026-07-09 | BWY40 | - | Jul 9, 07:35 UTC | Jul 9, 09:35 UTC | 2h 0m |
| 2026-07-08 | CRIMSON1 | BOH → BOH | Jul 8, 11:55 UTC | Jul 8, 13:45 UTC | 1h 50m |
| 2026-07-06 | AMBER2 | - | Jul 6, 10:30 UTC | Jul 6, 10:55 UTC | 25m |
| 2026-07-06 | AMBER2 | - | Jul 6, 09:35 UTC | Jul 6, 09:40 UTC | 5m |
| 2026-07-02 | AMBER3 | - | Jul 2, 07:35 UTC | Jul 2, 09:40 UTC | 2h 5m |
| 2026-06-30 | AMBER2 | BOH → BOH | Jun 30, 13:25 UTC | Jun 30, 15:15 UTC | 1h 50m |
| 2026-06-29 | AMBER2 | - | Jun 29, 18:30 UTC | Jun 29, 20:15 UTC | 1h 45m |
| 2026-06-25 | AMBER2 | NQY → BOH | Jun 25, 11:30 UTC | Jun 25, 13:29 UTC | 2h 0m |
| 2026-06-24 | CRIMSON1 | BOH → BOH | Jun 24, 08:49 UTC | Jun 24, 10:35 UTC | 1h 45m |
| 2026-06-23 | AMBER1 | BOH → BOH | Jun 23, 12:45 UTC | Jun 23, 14:04 UTC | 1h 20m |
| 2026-06-23 | CRIMSON1 | BOH → BOH | Jun 23, 07:40 UTC | Jun 23, 09:29 UTC | 1h 50m |
| 2026-06-22 | AMBER1 | BOH → BOH | Jun 22, 17:40 UTC | Jun 22, 19:24 UTC | 1h 45m |
| 2026-06-22 | AMBER1 | BOH → BOH | Jun 22, 11:24 UTC | Jun 22, 13:10 UTC | 1h 45m |
| 2026-06-19 | CRIMSON1 | BOH → BOH | Jun 19, 09:04 UTC | Jun 19, 10:35 UTC | 1h 30m |
| 2026-06-17 | WRTHOG13 | - | Jun 17, 10:40 UTC | Jun 17, 12:45 UTC | 2h 5m |
| 2026-06-17 | FRA75 | BOH → MME | Jun 17, 07:00 UTC | Jun 17, 07:45 UTC | 45m |
| 2026-06-16 | AMBER1 | BOH → BOH | Jun 16, 13:40 UTC | Jun 16, 15:30 UTC | 1h 50m |
| 2026-06-16 | AMBER1 | BOH → BOH | Jun 16, 08:00 UTC | Jun 16, 09:55 UTC | 1h 55m |
| 2026-06-15 | BWY40 | BOH → BOH | Jun 15, 11:00 UTC | Jun 15, 13:25 UTC | 2h 25m |
| 2026-06-11 | AMBER4 | BOH → BOH | Jun 11, 11:30 UTC | Jun 11, 13:25 UTC | 1h 55m |
| 2026-06-11 | AMBER4 | BOH → BOH | Jun 11, 07:50 UTC | Jun 11, 09:50 UTC | 2h 0m |
| 2026-06-09 | FRA88 | - | Jun 9, 16:45 UTC | Jun 9, 18:35 UTC | 1h 50m |
| 2026-06-08 | BWY40 | BOH → BOH | Jun 8, 12:10 UTC | Jun 8, 14:20 UTC | 2h 10m |
| 2026-06-08 | CRIMSON1 | BOH → BOH | Jun 8, 07:55 UTC | Jun 8, 09:30 UTC | 1h 35m |
| 2026-06-05 | BLUE1 | BOH → BOH | Jun 5, 07:45 UTC | Jun 5, 09:15 UTC | 1h 30m |
| 2026-06-04 | AMBER2 | NQY → BOH | Jun 4, 11:40 UTC | Jun 4, 13:30 UTC | 1h 50m |
| 2026-06-04 | AMBER2 | - | Jun 4, 08:00 UTC | Jun 4, 09:45 UTC | 1h 45m |
| 2026-06-03 | CRMSON1 | BOH → BOH | Jun 3, 13:30 UTC | Jun 3, 15:30 UTC | 2h 0m |
| 2026-06-03 | AMBER2 | BOH → BOH | Jun 3, 09:05 UTC | Jun 3, 10:00 UTC | 55m |
| 2026-06-02 | BLUE1 | BOH → BOH | Jun 2, 11:50 UTC | Jun 2, 13:55 UTC | 2h 5m |
| 2026-06-02 | BLUE1 | BOH → BOH | Jun 2, 07:35 UTC | Jun 2, 09:35 UTC | 2h 0m |
| 2026-06-01 | CRMSON2 | BOH → BOH | Jun 1, 12:05 UTC | Jun 1, 13:40 UTC | 1h 35m |
| 2026-06-01 | BWY40 | BOH → BOH | Jun 1, 07:15 UTC | Jun 1, 10:00 UTC | 2h 45m |
| 2026-05-29 | CRIMSON1 | BOH → BOH | May 29, 07:55 UTC | May 29, 09:50 UTC | 1h 55m |
| 2026-05-28 | WRTHOG82 | - | May 28, 10:50 UTC | May 28, 12:45 UTC | 1h 55m |
| 2026-05-28 | FRA97 | BOH → MME | May 28, 07:20 UTC | May 28, 08:15 UTC | 55m |
| 2026-05-27 | BLUE1 | BOH → BOH | May 27, 13:10 UTC | May 27, 14:55 UTC | 1h 45m |
| 2026-05-27 | CRIMSON1 | BOH → BOH | May 27, 07:35 UTC | May 27, 09:25 UTC | 1h 50m |
| 2026-05-26 | CRIMSON1 | BOH → BOH | May 26, 14:40 UTC | May 26, 16:30 UTC | 1h 50m |
| 2026-05-26 | CRIMSON2 | BOH → BOH | May 26, 09:40 UTC | May 26, 11:34 UTC | 1h 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-FRAR page for operator, model, and routing details .