sensors Mode-S transponder
3C66C5
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIVE · AIRBUS A-350-900
- Hex
- 3C66C5
- Octal
- 17063305
- Decimal
- 3,958,469
- Country
- DE
- Tail
- D-AIVE
- Type
- A359
- Flights observed
- 81
- Distinct callsigns
- 18
- Country
- DE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 3C66C5 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DLH726 | Lufthansa | 10 | 2026-05-29 |
| DLH727 | Lufthansa | 8 | 2026-05-30 |
| DLH411 | Lufthansa | 7 | 2026-05-12 |
| DLH410 | Lufthansa | 7 | 2026-05-12 |
| DLH715 | Lufthansa | 6 | 2026-05-29 |
| DLH714 | Lufthansa | 6 | 2026-05-28 |
| DLH765 | Lufthansa | 5 | 2026-05-14 |
| DLH764 | Lufthansa | 5 | 2026-05-14 |
| DLH5Y | Lufthansa | 4 | 2026-05-31 |
| DLH412 | Lufthansa | 4 | 2026-05-24 |
| DLH2P | Lufthansa | 4 | 2026-06-01 |
| DLH437 | Lufthansa | 3 | 2026-05-11 |
| DLH436 | Lufthansa | 3 | 2026-05-11 |
| DLH413 | Lufthansa | 3 | 2026-05-24 |
| DLH4C | Lufthansa | 2 | 2026-06-04 |
| DLH2C | Lufthansa | 2 | 2026-06-03 |
| DLH4W | Lufthansa | 1 | 2026-05-13 |
| DLH428 | Lufthansa | 1 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | DLH4C | FRA → PMI | Jun 4, 03:15 UTC | Jun 4, 05:15 UTC | 2h 0m |
| 2026-06-03 | DLH2C | MUC → ORD | Jun 3, 14:20 UTC | Jun 3, 23:15 UTC | 8h 55m |
| 2026-06-02 | DLH4C | FRA → PMI | Jun 2, 03:20 UTC | Jun 2, 11:30 UTC | 8h 10m |
| 2026-06-01 | DLH2C | MUC → ORD | Jun 1, 14:20 UTC | Jun 1, 22:45 UTC | 8h 25m |
| 2026-06-01 | DLH2P | SAN → MUC | Jun 1, 00:35 UTC | Jun 1, 11:30 UTC | 10h 55m |
| 2026-05-31 | DLH5Y | MUC → SAN | May 31, 11:10 UTC | May 31, 22:15 UTC | 11h 5m |
| 2026-05-30 | DLH727 | PVG → MUC | May 30, 16:55 UTC | May 31, 01:11 UTC | 8h 16m |
| 2026-05-30 | DLH727 | PVG → MUC | May 30, 02:35 UTC | May 31, 01:11 UTC | 22h 36m |
| 2026-05-29 | DLH726 | MUC → PVG | May 29, 23:40 UTC | May 30, 17:20 UTC | 17h 40m |
| 2026-05-29 | DLH726 | MUC → PVG | May 29, 21:20 UTC | May 30, 17:20 UTC | 20h 0m |
| 2026-05-29 | DLH726 | MUC → PVG | May 29, 20:35 UTC | May 30, 17:20 UTC | 20h 45m |
| 2026-05-29 | DLH715 | HND → MUC | May 29, 00:50 UTC | May 29, 14:35 UTC | 13h 45m |
| 2026-05-28 | DLH714 | MUC → HND | May 28, 10:50 UTC | May 28, 22:10 UTC | 11h 20m |
| 2026-05-27 | DLH727 | PVG → MUC | May 27, 17:00 UTC | May 28, 04:25 UTC | 11h 25m |
| 2026-05-27 | DLH727 | PVG → MUC | May 27, 05:24 UTC | May 28, 04:25 UTC | 23h 0m |
| 2026-05-26 | DLH726 | MUC → PVG | May 26, 21:20 UTC | May 27, 17:15 UTC | 19h 56m |
| 2026-05-26 | DLH726 | MUC → PVG | May 26, 20:20 UTC | May 27, 17:15 UTC | 20h 56m |
| 2026-05-26 | DLH715 | HND → MUC | May 26, 00:49 UTC | May 26, 14:40 UTC | 13h 50m |
| 2026-05-25 | DLH714 | MUC → HND | May 25, 10:55 UTC | May 25, 22:34 UTC | 11h 40m |
| 2026-05-24 | DLH412 | MUC → EWR | May 24, 14:25 UTC | May 25, 08:20 UTC | 17h 55m |
| 2026-05-24 | DLH413 | EWR → MUC | May 24, 01:05 UTC | May 24, 08:25 UTC | 7h 20m |
| 2026-05-23 | DLH412 | MUC → EWR | May 23, 14:35 UTC | May 23, 22:40 UTC | 8h 6m |
| 2026-05-23 | DLH2P | SAN → MUC | May 23, 00:35 UTC | May 23, 11:10 UTC | 10h 35m |
| 2026-05-22 | DLH5Y | MUC → SAN | May 22, 11:00 UTC | May 22, 22:15 UTC | 11h 15m |
| 2026-05-22 | DLH413 | EWR → MUC | May 22, 00:55 UTC | May 22, 07:45 UTC | 6h 50m |
| 2026-05-21 | DLH412 | MUC → EWR | May 21, 14:20 UTC | May 21, 22:40 UTC | 8h 20m |
| 2026-05-21 | DLH2P | SAN → MUC | May 21, 00:35 UTC | May 21, 11:00 UTC | 10h 25m |
| 2026-05-20 | DLH5Y | MUC → SAN | May 20, 11:00 UTC | May 20, 22:05 UTC | 11h 5m |
| 2026-05-18 | DLH727 | PVG → MUC | May 18, 16:40 UTC | May 19, 03:45 UTC | 11h 4m |
| 2026-05-18 | DLH727 | PVG → MUC | May 18, 05:35 UTC | May 19, 03:45 UTC | 22h 9m |
| 2026-05-17 | DLH726 | MUC → PVG | May 17, 21:20 UTC | May 18, 16:55 UTC | 19h 35m |
| 2026-05-17 | DLH726 | MUC → PVG | May 17, 20:30 UTC | May 18, 16:55 UTC | 20h 25m |
| 2026-05-17 | DLH715 | HND → MUC | May 17, 01:20 UTC | May 17, 14:45 UTC | 13h 25m |
| 2026-05-16 | DLH714 | MUC → HND | May 16, 10:50 UTC | May 16, 22:55 UTC | 12h 5m |
| 2026-05-14 | DLH765 | BOM → MUC | May 14, 22:20 UTC | May 15, 05:55 UTC | 7h 35m |
| 2026-05-14 | DLH765 | BOM → MUC | May 14, 21:00 UTC | May 14, 21:10 UTC | 10m |
| 2026-05-14 | DLH764 | MUC → BOM | May 14, 10:25 UTC | May 14, 18:55 UTC | 8h 30m |
| 2026-05-13 | DLH4W | BRU → FRA | May 13, 23:15 UTC | May 14, 07:20 UTC | 8h 5m |
| 2026-05-13 | DLH428 | MUC → CLT | May 13, 11:30 UTC | May 13, 20:35 UTC | 9h 5m |
| 2026-05-12 | DLH411 | JFK → MUC | May 12, 22:15 UTC | May 13, 05:30 UTC | 7h 15m |
| 2026-05-12 | DLH410 | MUC → JFK | May 12, 10:30 UTC | May 12, 18:45 UTC | 8h 15m |
| 2026-05-11 | DLH437 | ORD → MUC | May 11, 21:00 UTC | May 12, 04:50 UTC | 7h 50m |
| 2026-05-11 | DLH436 | MUC → ORD | May 11, 08:25 UTC | May 11, 17:25 UTC | 9h 1m |
| 2026-05-10 | DLH411 | JFK → MUC | May 10, 21:49 UTC | May 11, 05:05 UTC | 7h 15m |
| 2026-05-10 | DLH410 | MUC → JFK | May 10, 10:45 UTC | May 10, 18:45 UTC | 8h 0m |
| 2026-05-09 | DLH437 | ORD → MUC | May 9, 21:30 UTC | May 10, 05:25 UTC | 7h 55m |
| 2026-05-09 | DLH436 | MUC → ORD | May 9, 08:15 UTC | May 9, 17:20 UTC | 9h 5m |
| 2026-05-06 | DLH715 | HND → MUC | May 6, 00:55 UTC | May 6, 14:35 UTC | 13h 40m |
| 2026-05-05 | DLH714 | MUC → HND | May 5, 10:50 UTC | May 5, 22:35 UTC | 11h 45m |
| 2026-05-04 | DLH437 | ORD → MUC | May 4, 21:15 UTC | May 5, 05:25 UTC | 8h 10m |
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-AIVE page for operator, model, and routing details .