sensors Mode-S transponder
3C48A9
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-ABEI · DASSAULT Falcon 6X
- Hex
- 3C48A9
- Octal
- 17044251
- Decimal
- 3,950,761
- Country
- DE
- Tail
- D-ABEI
- Type
- FA6X
- Flights observed
- 55
- Distinct callsigns
- 2
- Country
- DE
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 3C48A9 falls within the block assigned to Germany (DE) by ICAO Annex 10, Volume III. Every aircraft registered in Germany 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-07-17 | JBD1 | - | Jul 17, 14:44 UTC | Jul 17, 15:05 UTC | 20m |
| 2026-07-17 | JBD1 | - | Jul 17, 12:19 UTC | Jul 17, 13:45 UTC | 1h 25m |
| 2026-07-17 | JBD1 | NUQ → CGN | Jul 17, 00:14 UTC | Jul 17, 10:40 UTC | 10h 25m |
| 2026-07-14 | JBD1 | BFI → NUQ | Jul 14, 02:55 UTC | Jul 14, 04:45 UTC | 1h 50m |
| 2026-07-12 | JBD1 | - | Jul 12, 10:10 UTC | Jul 12, 20:20 UTC | 10h 10m |
| 2026-07-10 | JBD1 | - | Jul 10, 10:50 UTC | Jul 10, 13:05 UTC | 2h 15m |
| 2026-07-10 | JBD1 | - | Jul 10, 06:20 UTC | Jul 10, 08:50 UTC | 2h 30m |
| 2026-07-09 | JBD1 | - | Jul 9, 12:10 UTC | Jul 9, 14:15 UTC | 2h 5m |
| 2026-07-08 | JBD1 | CGN → BBU | Jul 8, 13:10 UTC | Jul 8, 15:05 UTC | 1h 55m |
| 2026-07-08 | JBD1 | - | Jul 8, 10:10 UTC | Jul 8, 12:25 UTC | 2h 15m |
| 2026-07-08 | JBD1 | - | Jul 8, 06:40 UTC | Jul 8, 08:50 UTC | 2h 10m |
| 2026-07-06 | JBD2 | - | Jul 6, 08:10 UTC | Jul 6, 10:05 UTC | 1h 55m |
| 2026-07-05 | JBD2 | - | Jul 5, 23:30 UTC | Jul 6, 07:05 UTC | 7h 35m |
| 2026-07-04 | JBD2 | CTO → BLM | Jul 4, 16:15 UTC | Jul 4, 16:45 UTC | 30m |
| 2026-07-03 | JBD2 | - | Jul 3, 17:00 UTC | Jul 4, 00:00 UTC | 7h 0m |
| 2026-07-03 | JBD2 | CGN → FAB | Jul 3, 12:25 UTC | Jul 3, 13:35 UTC | 1h 10m |
| 2026-07-02 | JBD1 | ATH → CGN | Jul 2, 15:30 UTC | Jul 2, 18:00 UTC | 2h 30m |
| 2026-07-01 | JBD1 | CGN → ATH | Jul 1, 14:30 UTC | Jul 1, 17:20 UTC | 2h 50m |
| 2026-06-21 | JBD2 | - | Jun 21, 10:14 UTC | Jun 21, 11:24 UTC | 1h 10m |
| 2026-06-21 | JBD2 | - | Jun 21, 00:49 UTC | Jun 21, 09:35 UTC | 8h 45m |
| 2026-06-19 | JBD2 | - | Jun 19, 17:39 UTC | Jun 19, 18:20 UTC | 40m |
| 2026-06-17 | JBD2 | - | Jun 17, 12:45 UTC | Jun 17, 22:00 UTC | 9h 15m |
| 2026-06-17 | JBD2 | CGN → LBG | Jun 17, 10:25 UTC | Jun 17, 11:10 UTC | 45m |
| 2026-06-16 | JBD1 | - | Jun 16, 20:35 UTC | Jun 17, 05:40 UTC | 9h 5m |
| 2026-06-13 | JBD1 | CGN → BFI | Jun 13, 09:20 UTC | Jun 13, 18:50 UTC | 9h 30m |
| 2026-06-08 | JBD1 | - | Jun 8, 19:05 UTC | Jun 8, 19:50 UTC | 45m |
| 2026-06-08 | JBD1 | CGN → BER | Jun 8, 06:25 UTC | Jun 8, 07:15 UTC | 50m |
| 2026-06-05 | JBD1 | - | Jun 5, 09:10 UTC | Jun 5, 09:45 UTC | 35m |
| 2026-06-01 | JBD1 | CGN → NUE | Jun 1, 05:45 UTC | Jun 1, 06:25 UTC | 40m |
| 2026-05-30 | JBD1 | - | May 30, 11:30 UTC | May 30, 13:20 UTC | 1h 50m |
| 2026-05-29 | JBD1 | - | May 29, 09:15 UTC | May 29, 10:30 UTC | 1h 15m |
| 2026-05-29 | JBD1 | - | May 29, 07:10 UTC | May 29, 07:45 UTC | 35m |
| 2026-05-28 | JBD1 | BRU → CGN | May 28, 15:15 UTC | May 28, 15:40 UTC | 25m |
| 2026-05-28 | JBD1 | CGN → BRU | May 28, 11:45 UTC | May 28, 12:15 UTC | 30m |
| 2026-05-27 | JBD1 | - | May 27, 14:20 UTC | May 27, 15:00 UTC | 40m |
| 2026-05-26 | JBD1 | CGN → MUC | May 26, 14:50 UTC | May 26, 15:35 UTC | 45m |
| 2026-05-24 | JBD1 | - | May 24, 12:20 UTC | May 24, 14:55 UTC | 2h 35m |
| 2026-05-24 | JBD1 | - | May 24, 08:55 UTC | May 24, 11:20 UTC | 2h 25m |
| 2026-05-13 | JBD1 | - | May 13, 14:55 UTC | May 13, 16:55 UTC | 2h 0m |
| 2026-05-12 | JBD1 | - | May 12, 15:01 UTC | May 12, 16:30 UTC | 1h 30m |
| 2026-05-12 | JBD2 | REG → CGN | May 12, 10:15 UTC | May 12, 12:25 UTC | 2h 10m |
| 2026-05-11 | JBD2 | - | May 11, 16:30 UTC | May 11, 17:35 UTC | 1h 6m |
| 2026-05-11 | JBD2 | - | May 11, 07:20 UTC | May 11, 08:40 UTC | 1h 20m |
| 2026-05-10 | JBD2 | CGN → REG | May 10, 16:04 UTC | May 10, 18:09 UTC | 2h 5m |
| 2026-05-06 | JBD1 | NUE → CGN | May 6, 23:00 UTC | May 6, 23:35 UTC | 35m |
| 2026-05-06 | JBD1 | - | May 6, 17:40 UTC | May 6, 18:00 UTC | 20m |
| 2026-05-06 | JBD1 | - | May 6, 15:10 UTC | May 6, 16:50 UTC | 1h 40m |
| 2026-05-04 | JBD1 | - | May 4, 07:15 UTC | May 4, 09:05 UTC | 1h 50m |
| 2026-04-24 | JBD1 | - | Apr 24, 13:10 UTC | Apr 24, 13:50 UTC | 40m |
| 2026-04-22 | JBD1 | CGN → MUC | Apr 22, 08:10 UTC | Apr 22, 08:55 UTC | 45m |
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 D-ABEI page for operator, model, and routing details .