sensors Mode-S transponder
3C6562
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIKB · AIRBUS A-330-300
- Hex
- 3C6562
- Octal
- 17062542
- Decimal
- 3,958,114
- Country
- DE
- Tail
- D-AIKB
- Type
- A333
- Flights observed
- 130
- Distinct callsigns
- 20
- Country
- DE
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 3C6562 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 |
|---|---|---|---|
| OCN135K | O Air | 14 | 2026-06-05 |
| OCN69 | - | 12 | 2026-07-07 |
| OCN68 | - | 12 | 2026-07-06 |
| OCN659 | - | 7 | 2026-07-10 |
| OCN642 | - | 7 | 2026-07-10 |
| OCN77 | O Air | 5 | 2026-06-10 |
| OCN76 | O Air | 5 | 2026-06-10 |
| OCN51 | - | 5 | 2026-07-02 |
| OCN50 | O Air | 5 | 2026-07-02 |
| OCN131 | - | 5 | 2026-07-13 |
| OCN12 | O Air | 5 | 2026-06-04 |
| OCN11 | O Air | 5 | 2026-06-03 |
| OCN975 | O Air | 4 | 2026-04-13 |
| OCN74 | - | 4 | 2026-07-07 |
| OCN3 | O Air | 4 | 2026-05-17 |
| OCN143Y | - | 3 | 2026-05-11 |
| OCN137 | - | 3 | 2026-07-12 |
| OCN133 | - | 3 | 2026-06-22 |
| OCN132W | O Air | 3 | 2026-06-20 |
| OCN75 | - | 2 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | OCN131 | FRA → FRA | Jul 13, 10:40 UTC | Jul 14, 06:05 UTC | 19h 25m |
| 2026-07-12 | OCN137 | - | Jul 12, 13:20 UTC | Jul 12, 17:10 UTC | 3h 50m |
| 2026-07-11 | OCN137 | - | Jul 11, 20:35 UTC | Jul 12, 17:10 UTC | 20h 35m |
| 2026-07-11 | OCN137 | - | Jul 11, 18:35 UTC | Jul 12, 17:10 UTC | 22h 35m |
| 2026-07-10 | OCN659 | - | Jul 10, 22:05 UTC | Jul 11, 06:45 UTC | 8h 40m |
| 2026-07-10 | OCN642 | FRA → TPA | Jul 10, 10:10 UTC | Jul 10, 19:50 UTC | 9h 40m |
| 2026-07-07 | OCN75 | - | Jul 7, 22:45 UTC | Jul 8, 04:55 UTC | 6h 10m |
| 2026-07-07 | OCN74 | - | Jul 7, 14:00 UTC | Jul 7, 20:15 UTC | 6h 15m |
| 2026-07-07 | OCN69 | MCO → FRA | Jul 7, 01:25 UTC | Jul 7, 10:00 UTC | 8h 35m |
| 2026-07-06 | OCN68 | FRA → MCO | Jul 6, 12:20 UTC | Jul 6, 21:55 UTC | 9h 35m |
| 2026-07-06 | OCN69 | MCO → FRA | Jul 6, 00:45 UTC | Jul 6, 09:15 UTC | 8h 30m |
| 2026-07-05 | OCN68 | FRA → MCO | Jul 5, 12:50 UTC | Jul 5, 22:25 UTC | 9h 35m |
| 2026-07-05 | OCN69 | - | Jul 5, 00:40 UTC | Jul 5, 09:15 UTC | 8h 35m |
| 2026-07-04 | OCN68 | - | Jul 4, 12:05 UTC | Jul 4, 21:50 UTC | 9h 45m |
| 2026-07-03 | OCN659 | TPA → FRA | Jul 3, 22:10 UTC | Jul 4, 06:50 UTC | 8h 40m |
| 2026-07-03 | OCN642 | FRA → TPA | Jul 3, 10:05 UTC | Jul 3, 19:55 UTC | 9h 50m |
| 2026-07-02 | OCN51 | PHL → FRA | Jul 2, 23:35 UTC | Jul 3, 06:30 UTC | 6h 55m |
| 2026-07-02 | OCN50 | FRA → PHL | Jul 2, 12:40 UTC | Jul 2, 21:15 UTC | 8h 35m |
| 2026-07-01 | OCN157 | - | Jul 1, 23:10 UTC | Jul 2, 03:10 UTC | 4h 0m |
| 2026-06-30 | OCN156 | - | Jun 30, 20:50 UTC | Jul 1, 00:30 UTC | 3h 40m |
| 2026-06-29 | OCN659 | TPA → FRA | Jun 29, 22:15 UTC | Jun 30, 06:50 UTC | 8h 36m |
| 2026-06-29 | OCN642 | FRA → TPA | Jun 29, 09:54 UTC | Jun 29, 20:09 UTC | 10h 15m |
| 2026-06-28 | OCN51 | - | Jun 28, 22:04 UTC | Jun 29, 05:00 UTC | 6h 55m |
| 2026-06-28 | OCN50 | FRA → PHL | Jun 28, 12:05 UTC | Jun 28, 20:04 UTC | 8h 0m |
| 2026-06-27 | OCN659 | TPA → FRA | Jun 27, 22:35 UTC | Jun 28, 07:05 UTC | 8h 30m |
| 2026-06-27 | OCN642 | FRA → TPA | Jun 27, 10:40 UTC | Jun 27, 20:34 UTC | 9h 55m |
| 2026-06-26 | OCN659 | - | Jun 26, 22:14 UTC | Jun 27, 06:54 UTC | 8h 40m |
| 2026-06-26 | OCN642 | FRA → TPA | Jun 26, 10:05 UTC | Jun 26, 20:10 UTC | 10h 5m |
| 2026-06-25 | OCN51 | - | Jun 25, 22:20 UTC | Jun 26, 05:10 UTC | 6h 50m |
| 2026-06-25 | OCN50 | FRA → PHL | Jun 25, 11:59 UTC | Jun 25, 20:25 UTC | 8h 25m |
| 2026-06-25 | OCN731 | - | Jun 25, 01:50 UTC | Jun 25, 07:34 UTC | 5h 45m |
| 2026-06-24 | OCN74 | - | Jun 24, 16:54 UTC | Jun 24, 23:34 UTC | 6h 40m |
| 2026-06-23 | OCN131 | MBA → FRA | Jun 23, 19:15 UTC | Jun 24, 14:29 UTC | 19h 15m |
| 2026-06-22 | OCN133 | - | Jun 22, 01:00 UTC | Jun 22, 03:05 UTC | 2h 5m |
| 2026-06-20 | OCN132W | FRA → WDH | Jun 20, 20:45 UTC | Jun 20, 22:30 UTC | 1h 45m |
| 2026-06-19 | OCN131 | MBA → FRA | Jun 19, 18:59 UTC | Jun 20, 16:00 UTC | 21h 0m |
| 2026-06-19 | OCN69 | MCO → FRA | Jun 19, 00:29 UTC | Jun 19, 09:09 UTC | 8h 40m |
| 2026-06-18 | OCN68 | FRA → MCO | Jun 18, 11:55 UTC | Jun 18, 21:35 UTC | 9h 40m |
| 2026-06-18 | OCN69 | MCO → FRA | Jun 18, 01:00 UTC | Jun 18, 09:15 UTC | 8h 15m |
| 2026-06-17 | OCN68 | FRA → MCO | Jun 17, 12:10 UTC | Jun 17, 21:50 UTC | 9h 40m |
| 2026-06-16 | OCN69 | MCO → FRA | Jun 16, 01:35 UTC | Jun 16, 09:55 UTC | 8h 20m |
| 2026-06-15 | OCN68 | FRA → MCO | Jun 15, 12:35 UTC | Jun 15, 22:35 UTC | 10h 0m |
| 2026-06-15 | OCN133 | - | Jun 15, 01:04 UTC | Jun 15, 03:10 UTC | 2h 5m |
| 2026-06-13 | OCN132W | FRA → WDH | Jun 13, 20:15 UTC | Jun 13, 21:55 UTC | 1h 40m |
| 2026-06-12 | OCN131 | MBA → FRA | Jun 12, 20:35 UTC | Jun 13, 16:15 UTC | 19h 39m |
| 2026-06-12 | OCN131 | MBA → FRA | Jun 12, 19:10 UTC | Jun 13, 16:15 UTC | 21h 4m |
| 2026-06-11 | OCN617 | RSW → FRA | Jun 11, 23:40 UTC | Jun 12, 08:40 UTC | 9h 1m |
| 2026-06-11 | OCN601 | FRA → RSW | Jun 11, 11:25 UTC | Jun 11, 21:50 UTC | 10h 25m |
| 2026-06-10 | OCN77 | YYC → FRA | Jun 10, 23:10 UTC | Jun 11, 07:40 UTC | 8h 30m |
| 2026-06-10 | OCN76 | FRA → YYC | Jun 10, 12:10 UTC | Jun 10, 21:00 UTC | 8h 50m |
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-AIKB page for operator, model, and routing details .