sensors Mode-S transponder
3C6566
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIKF · AIRBUS A-330-300
- Hex
- 3C6566
- Octal
- 17062546
- Decimal
- 3,958,118
- Country
- DE
- Tail
- D-AIKF
- Type
- A333
- Flights observed
- 136
- Distinct callsigns
- 20
- Country
- DE
- Last broadcast
- Jul 26, 20:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 3C6566 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OCN642 | O Air | 12 | 2026-07-26 |
| OCN51 | - | 12 | 2026-07-16 |
| OCN69 | - | 11 | 2026-07-15 |
| OCN68 | - | 11 | 2026-07-14 |
| OCN75 | O Air | 9 | 2026-05-29 |
| OCN659 | O Air | 9 | 2026-07-19 |
| OCN50 | - | 9 | 2026-07-16 |
| OCN74 | - | 8 | 2026-07-15 |
| OCN12 | O Air | 6 | 2026-07-23 |
| OCN11 | O Air | 6 | 2026-07-22 |
| OCN77 | O Air | 4 | 2026-05-30 |
| OCN76 | O Air | 4 | 2026-05-30 |
| OCN539 | O Air | 4 | 2026-06-10 |
| OCN52 | O Air | 4 | 2026-06-10 |
| OCN133 | O Air | 4 | 2026-07-26 |
| OCN132W | O Air | 4 | 2026-07-24 |
| OCN2 | O Air | 3 | 2026-05-28 |
| OCN135K | - | 3 | 2026-07-24 |
| OCN3 | O Air | 2 | 2026-05-28 |
| OCN137 | - | 2 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | OCN642 | FRA → TPA | Jul 26, 10:10 UTC | Jul 26, 20:00 UTC | 9h 50m |
| 2026-07-26 | OCN133 | WDH → FRA | Jul 26, 00:40 UTC | Jul 26, 03:10 UTC | 2h 30m |
| 2026-07-24 | OCN132W | FRA → WDH | Jul 24, 20:25 UTC | Jul 24, 22:05 UTC | 1h 40m |
| 2026-07-24 | OCN135K | - | Jul 24, 13:10 UTC | Jul 24, 16:50 UTC | 3h 40m |
| 2026-07-23 | OCN135K | - | Jul 23, 19:35 UTC | Jul 24, 16:50 UTC | 21h 15m |
| 2026-07-23 | OCN135K | FRA → FRA | Jul 23, 18:10 UTC | Jul 24, 16:50 UTC | 22h 40m |
| 2026-07-23 | OCN12 | LAS → FRA | Jul 23, 04:25 UTC | Jul 23, 14:25 UTC | 10h 0m |
| 2026-07-22 | OCN11 | CUN → FRA | Jul 22, 12:00 UTC | Jul 22, 23:05 UTC | 11h 5m |
| 2026-07-21 | OCN12 | - | Jul 21, 04:30 UTC | Jul 21, 14:40 UTC | 10h 10m |
| 2026-07-20 | OCN11 | FRA → LAS | Jul 20, 12:20 UTC | Jul 20, 23:35 UTC | 11h 15m |
| 2026-07-19 | OCN659 | TPA → FRA | Jul 19, 22:10 UTC | Jul 20, 07:25 UTC | 9h 15m |
| 2026-07-19 | OCN642 | FRA → TPA | Jul 19, 09:55 UTC | Jul 19, 19:30 UTC | 9h 35m |
| 2026-07-16 | OCN51 | - | Jul 16, 22:25 UTC | Jul 17, 05:55 UTC | 7h 30m |
| 2026-07-16 | OCN51 | PHL → PHL | Jul 16, 22:10 UTC | Jul 16, 22:15 UTC | 5m |
| 2026-07-16 | OCN50 | FRA → PHL | Jul 16, 11:45 UTC | Jul 16, 20:05 UTC | 8h 20m |
| 2026-07-16 | OCN731 | - | Jul 16, 01:15 UTC | Jul 16, 07:15 UTC | 6h 0m |
| 2026-07-15 | OCN74 | - | Jul 15, 16:45 UTC | Jul 15, 23:25 UTC | 6h 40m |
| 2026-07-15 | OCN69 | MCO → FRA | Jul 15, 02:45 UTC | Jul 15, 11:45 UTC | 9h 0m |
| 2026-07-14 | OCN068 | TPA → MCO | Jul 14, 23:45 UTC | Jul 15, 00:15 UTC | 30m |
| 2026-07-14 | OCN68 | FRA → TPA | Jul 14, 12:05 UTC | Jul 14, 22:30 UTC | 10h 25m |
| 2026-07-13 | OCN12 | LAS → FRA | Jul 13, 04:25 UTC | Jul 13, 14:50 UTC | 10h 25m |
| 2026-07-12 | OCN11 | FRA → LAS | Jul 12, 12:10 UTC | Jul 12, 23:10 UTC | 11h 0m |
| 2026-07-11 | OCN659 | TPA → FRA | Jul 11, 22:25 UTC | Jul 12, 07:05 UTC | 8h 40m |
| 2026-07-11 | OCN642 | FRA → TPA | Jul 11, 09:50 UTC | Jul 11, 19:30 UTC | 9h 40m |
| 2026-07-10 | OCN51 | PHL → FRA | Jul 10, 22:55 UTC | Jul 11, 05:55 UTC | 7h 0m |
| 2026-07-10 | OCN50 | FRA → PHL | Jul 10, 11:45 UTC | Jul 10, 20:15 UTC | 8h 30m |
| 2026-07-10 | OCN133 | - | Jul 10, 00:35 UTC | Jul 10, 03:05 UTC | 2h 30m |
| 2026-07-08 | OCN132W | - | Jul 8, 20:25 UTC | Jul 8, 22:30 UTC | 2h 5m |
| 2026-07-08 | OCN137 | - | Jul 8, 13:10 UTC | Jul 8, 16:55 UTC | 3h 45m |
| 2026-07-07 | OCN137 | FRA → FRA | Jul 7, 18:00 UTC | Jul 8, 16:55 UTC | 22h 55m |
| 2026-06-25 | OCN4087 | - | Jun 25, 15:20 UTC | Jun 25, 16:20 UTC | 1h 0m |
| 2026-06-11 | OCN4086 | - | Jun 11, 13:40 UTC | Jun 11, 14:35 UTC | 55m |
| 2026-06-10 | OCN539 | MSP → FRA | Jun 10, 22:50 UTC | Jun 11, 06:50 UTC | 8h 0m |
| 2026-06-10 | OCN52 | FRA → MSP | Jun 10, 11:00 UTC | Jun 10, 19:45 UTC | 8h 45m |
| 2026-06-08 | OCN659 | TPA → FRA | Jun 8, 22:05 UTC | Jun 9, 06:55 UTC | 8h 50m |
| 2026-06-08 | OCN642 | FRA → TPA | Jun 8, 09:50 UTC | Jun 8, 19:15 UTC | 9h 25m |
| 2026-06-06 | OCN659 | TPA → FRA | Jun 6, 22:00 UTC | Jun 7, 06:50 UTC | 8h 50m |
| 2026-06-06 | OCN642 | FRA → TPA | Jun 6, 09:50 UTC | Jun 6, 19:30 UTC | 9h 40m |
| 2026-06-05 | OCN539 | MSP → FRA | Jun 5, 21:25 UTC | Jun 6, 05:25 UTC | 8h 0m |
| 2026-06-05 | OCN52 | FRA → MSP | Jun 5, 09:50 UTC | Jun 5, 18:40 UTC | 8h 50m |
| 2026-06-05 | OCN51 | YHZ → FRA | Jun 5, 03:05 UTC | Jun 5, 05:05 UTC | 2h 0m |
| 2026-06-04 | OCN51 | YHZ → FRA | Jun 4, 21:55 UTC | Jun 4, 23:40 UTC | 1h 45m |
| 2026-06-04 | OCN50 | FRA → PHL | Jun 4, 11:45 UTC | Jun 4, 20:00 UTC | 8h 15m |
| 2026-06-03 | OCN69 | MCO → FRA | Jun 3, 00:00 UTC | Jun 3, 07:55 UTC | 7h 55m |
| 2026-06-02 | OCN68 | FRA → MCO | Jun 2, 12:25 UTC | Jun 2, 21:35 UTC | 9h 10m |
| 2026-06-01 | OCN539 | MSP → FRA | Jun 1, 21:20 UTC | Jun 2, 05:55 UTC | 8h 35m |
| 2026-06-01 | OCN52 | FRA → MSP | Jun 1, 10:15 UTC | Jun 1, 18:30 UTC | 8h 15m |
| 2026-05-30 | OCN77 | YYC → FRA | May 30, 23:25 UTC | May 30, 23:55 UTC | 30m |
| 2026-05-30 | OCN76 | FRA → YYC | May 30, 12:30 UTC | May 30, 21:20 UTC | 8h 50m |
| 2026-05-29 | OCN75 | YHZ → FRA | May 29, 23:15 UTC | May 30, 05:15 UTC | 6h 0m |
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-AIKF page for operator, model, and routing details .