sensors Mode-S transponder
3CCD44
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-CFAQ · LEARJET 60
- Hex
- 3CCD44
- Octal
- 17146504
- Decimal
- 3,984,708
- Country
- DE
- Tail
- D-CFAQ
- Type
- LJ60
- Flights observed
- 42
- Distinct callsigns
- 14
- Country
- DE
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 3CCD44 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IFA6245 | - | 5 | 2026-04-19 |
| IFA6363 | - | 4 | 2026-05-29 |
| IFA6328 | - | 4 | 2026-05-23 |
| IFA6322 | - | 4 | 2026-05-19 |
| IFA6317 | - | 4 | 2026-05-27 |
| IFA6224 | - | 4 | 2026-04-13 |
| IFA6293 | - | 3 | 2026-05-06 |
| IFA6258 | - | 3 | 2026-05-24 |
| IFA6304 | - | 2 | 2026-05-23 |
| IFA6301 | - | 2 | 2026-05-07 |
| IFA6200 | - | 2 | 2026-04-29 |
| IFA6198 | - | 2 | 2026-05-03 |
| IFA110 | - | 2 | 2026-04-26 |
| IFA6279 | - | 1 | 2026-05-24 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | IFA6363 | - | May 29, 17:40 UTC | May 29, 19:10 UTC | 1h 30m |
| 2026-05-29 | IFA6363 | - | May 29, 14:15 UTC | May 29, 16:50 UTC | 2h 35m |
| 2026-05-29 | IFA6363 | - | May 29, 08:00 UTC | May 29, 09:10 UTC | 1h 10m |
| 2026-05-29 | IFA6363 | NUE → WAW | May 29, 05:05 UTC | May 29, 06:15 UTC | 1h 10m |
| 2026-05-27 | IFA6317 | EMA → NUE | May 27, 16:35 UTC | May 27, 17:50 UTC | 1h 15m |
| 2026-05-27 | IFA6317 | BCN → EMA | May 27, 13:35 UTC | May 27, 15:25 UTC | 1h 50m |
| 2026-05-25 | IFA6317 | EMA → BCN | May 25, 15:00 UTC | May 25, 17:00 UTC | 2h 0m |
| 2026-05-25 | IFA6317 | IBZ → EMA | May 25, 11:30 UTC | May 25, 13:35 UTC | 2h 5m |
| 2026-05-24 | IFA6279 | MUC → IBZ | May 24, 17:45 UTC | May 24, 19:35 UTC | 1h 50m |
| 2026-05-24 | IFA6258 | PRG → MUC | May 24, 16:05 UTC | May 24, 16:40 UTC | 35m |
| 2026-05-24 | IFA6258 | - | May 24, 08:25 UTC | May 24, 08:50 UTC | 25m |
| 2026-05-24 | IFA6258 | BER → BRQ | May 24, 06:20 UTC | May 24, 07:05 UTC | 45m |
| 2026-05-23 | IFA6304 | - | May 23, 14:05 UTC | May 23, 15:50 UTC | 1h 45m |
| 2026-05-23 | IFA6304 | AMS → CIA | May 23, 11:15 UTC | May 23, 13:00 UTC | 1h 45m |
| 2026-05-23 | IFA6328 | - | May 23, 07:45 UTC | May 23, 08:25 UTC | 40m |
| 2026-05-22 | IFA6328 | BER → FRA | May 22, 12:30 UTC | May 22, 13:20 UTC | 50m |
| 2026-05-22 | IFA6328 | STR → BER | May 22, 08:55 UTC | May 22, 09:50 UTC | 55m |
| 2026-05-22 | IFA6328 | NUE → STR | May 22, 07:10 UTC | May 22, 07:40 UTC | 30m |
| 2026-05-19 | IFA6322 | - | May 19, 13:10 UTC | May 19, 14:10 UTC | 1h 0m |
| 2026-05-19 | IFA6322 | - | May 19, 10:00 UTC | May 19, 12:05 UTC | 2h 5m |
| 2026-05-18 | IFA6322 | - | May 18, 08:10 UTC | May 18, 10:10 UTC | 2h 0m |
| 2026-05-18 | IFA6322 | NUE → LBG | May 18, 05:50 UTC | May 18, 06:50 UTC | 1h 0m |
| 2026-05-07 | IFA6301 | - | May 7, 13:05 UTC | May 7, 14:20 UTC | 1h 15m |
| 2026-05-06 | IFA6301 | - | May 6, 16:15 UTC | May 6, 19:00 UTC | 2h 45m |
| 2026-05-06 | IFA6293 | TLL → VNO | May 6, 12:10 UTC | May 6, 13:00 UTC | 50m |
| 2026-05-05 | IFA6293 | - | May 5, 09:10 UTC | May 5, 11:00 UTC | 1h 50m |
| 2026-05-05 | IFA6293 | NUE → AMS | May 5, 06:20 UTC | May 5, 07:25 UTC | 1h 5m |
| 2026-05-03 | IFA6198 | - | May 3, 09:30 UTC | May 3, 11:30 UTC | 2h 0m |
| 2026-04-29 | IFA6198 | - | Apr 29, 14:10 UTC | Apr 29, 16:00 UTC | 1h 50m |
| 2026-04-29 | IFA6200 | BUD → NUE | Apr 29, 10:15 UTC | Apr 29, 11:20 UTC | 1h 5m |
| 2026-04-27 | IFA6200 | NUE → BUD | Apr 27, 07:15 UTC | Apr 27, 08:05 UTC | 50m |
| 2026-04-26 | IFA110 | FDH → NUE | Apr 26, 15:20 UTC | Apr 26, 15:50 UTC | 30m |
| 2026-04-21 | IFA110 | NUE → FDH | Apr 21, 05:20 UTC | Apr 21, 05:50 UTC | 30m |
| 2026-04-19 | IFA6245 | - | Apr 19, 18:45 UTC | Apr 19, 19:15 UTC | 30m |
| 2026-04-19 | IFA6245 | - | Apr 19, 16:15 UTC | Apr 19, 17:55 UTC | 1h 40m |
| 2026-04-17 | IFA6245 | - | Apr 17, 14:40 UTC | Apr 17, 14:50 UTC | 10m |
| 2026-04-17 | IFA6245 | - | Apr 17, 12:00 UTC | Apr 17, 13:15 UTC | 1h 15m |
| 2026-04-17 | IFA6245 | - | Apr 17, 10:10 UTC | Apr 17, 10:40 UTC | 30m |
| 2026-04-13 | IFA6224 | - | Apr 13, 12:20 UTC | Apr 13, 12:25 UTC | 5m |
| 2026-04-13 | IFA6224 | - | Apr 13, 12:00 UTC | Apr 13, 12:15 UTC | 15m |
| 2026-04-13 | IFA6224 | BER → MUC | Apr 13, 10:05 UTC | Apr 13, 10:55 UTC | 50m |
| 2026-04-13 | IFA6224 | NUE → BER | Apr 13, 08:30 UTC | Apr 13, 09:05 UTC | 35m |
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-CFAQ page for operator, model, and routing details .