Not currently tracked · last seen 7d ago
- Flights observed
- 126 showing last 50
- Avg flight time
- 3h 16m
- Typical route
- RHO → FMO
- Last seen
- 7d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-25 | FMO → FUE | Jul 25, 11:55 UTC | Jul 25, 22:25 UTC | 10h 30m |
| 2026-07-25 | HER → FMO | Jul 25, 07:30 UTC | Jul 25, 10:40 UTC | 3h 10m |
| 2026-07-25 | FMO → HER | Jul 25, 03:10 UTC | Jul 25, 05:45 UTC | 2h 35m |
| 2026-07-24 | RHO → FMO | Jul 24, 10:25 UTC | Jul 24, 13:40 UTC | 3h 15m |
| 2026-07-24 | FMO → RHO | Jul 24, 05:10 UTC | Jul 24, 08:05 UTC | 2h 55m |
| 2026-07-23 | HER → FMO | Jul 23, 17:20 UTC | Jul 23, 20:25 UTC | 3h 5m |
| 2026-07-23 | FMO → HER | Jul 23, 13:20 UTC | Jul 23, 15:55 UTC | 2h 35m |
| 2026-07-22 | FUE → FMO | Jul 22, 12:50 UTC | Jul 22, 16:35 UTC | 3h 45m |
| 2026-07-22 | FMO → FUE | Jul 22, 10:20 UTC | Jul 22, 11:30 UTC | 1h 10m |
| 2026-07-21 | RHO → FMO | Jul 21, 09:45 UTC | Jul 21, 13:00 UTC | 3h 15m |
| 2026-07-21 | FMO → RHO | Jul 21, 05:20 UTC | Jul 21, 08:15 UTC | 2h 55m |
| 2026-07-20 | BRU → RTM | Jul 20, 20:45 UTC | Jul 20, 23:50 UTC | 3h 5m |
| 2026-07-20 | - | Jul 20, 16:30 UTC | Jul 20, 19:30 UTC | 3h 0m |
| 2026-07-20 | AMS → LIS | Jul 20, 14:05 UTC | Jul 20, 14:40 UTC | 35m |
| 2026-07-20 | HER → FMO | Jul 20, 10:30 UTC | Jul 20, 13:20 UTC | 2h 50m |
| 2026-07-20 | FMO → HER | Jul 20, 06:10 UTC | Jul 20, 08:50 UTC | 2h 40m |
| 2026-07-18 | FUE → FMO | Jul 18, 17:55 UTC | Jul 18, 21:35 UTC | 3h 40m |
| 2026-07-18 | - | Jul 18, 11:55 UTC | Jul 18, 16:15 UTC | 4h 20m |
| 2026-07-18 | HER → FMO | Jul 18, 07:25 UTC | Jul 18, 10:30 UTC | 3h 5m |
| 2026-07-18 | FMO → HER | Jul 18, 03:05 UTC | Jul 18, 05:50 UTC | 2h 45m |
| 2026-07-17 | RHO → FMO | Jul 17, 10:05 UTC | Jul 17, 13:25 UTC | 3h 20m |
| 2026-07-17 | FMO → RHO | Jul 17, 05:10 UTC | Jul 17, 08:15 UTC | 3h 5m |
| 2026-07-16 | - | Jul 16, 14:05 UTC | Jul 16, 17:14 UTC | 3h 10m |
| 2026-07-16 | - | Jul 16, 09:40 UTC | Jul 16, 12:14 UTC | 2h 35m |
| 2026-07-15 | - | Jul 15, 13:05 UTC | Jul 15, 16:50 UTC | 3h 45m |
| 2026-07-15 | - | Jul 15, 07:20 UTC | Jul 15, 11:55 UTC | 4h 35m |
| 2026-07-14 | RHO → FMO | Jul 14, 09:50 UTC | Jul 14, 13:20 UTC | 3h 30m |
| 2026-07-14 | - | Jul 14, 05:15 UTC | Jul 14, 08:10 UTC | 2h 55m |
| 2026-07-13 | - | Jul 13, 09:35 UTC | Jul 13, 12:35 UTC | 3h 0m |
| 2026-07-13 | - | Jul 13, 05:15 UTC | Jul 13, 08:15 UTC | 3h 0m |
| 2026-07-11 | - | Jul 11, 11:50 UTC | Jul 11, 21:10 UTC | 9h 20m |
| 2026-07-11 | - | Jul 11, 07:25 UTC | Jul 11, 10:25 UTC | 3h 0m |
| 2026-07-11 | - | Jul 11, 03:10 UTC | Jul 11, 05:55 UTC | 2h 45m |
| 2026-07-10 | RHO → FMO | Jul 10, 09:45 UTC | Jul 10, 13:10 UTC | 3h 25m |
| 2026-07-10 | FMO → RHO | Jul 10, 05:10 UTC | Jul 10, 08:05 UTC | 2h 55m |
| 2026-07-09 | - | Jul 9, 14:05 UTC | Jul 9, 17:15 UTC | 3h 10m |
| 2026-07-09 | - | Jul 9, 09:35 UTC | Jul 9, 12:20 UTC | 2h 45m |
| 2026-07-08 | FUE → FMO | Jul 8, 12:35 UTC | Jul 8, 16:35 UTC | 4h 0m |
| 2026-07-08 | - | Jul 8, 07:15 UTC | Jul 8, 11:20 UTC | 4h 5m |
| 2026-07-07 | RHO → FMO | Jul 7, 10:05 UTC | Jul 7, 13:30 UTC | 3h 25m |
| 2026-07-07 | FMO → RHO | Jul 7, 05:05 UTC | Jul 7, 08:05 UTC | 3h 0m |
| 2026-07-06 | - | Jul 6, 09:20 UTC | Jul 6, 12:35 UTC | 3h 15m |
| 2026-07-06 | - | Jul 6, 05:05 UTC | Jul 6, 07:50 UTC | 2h 45m |
| 2026-07-05 | DUB → FMO | Jul 5, 16:55 UTC | Jul 5, 18:15 UTC | 1h 20m |
| 2026-07-05 | - | Jul 5, 15:15 UTC | Jul 5, 15:50 UTC | 35m |
| 2026-07-05 | - | Jul 5, 11:35 UTC | Jul 5, 13:05 UTC | 1h 30m |
| 2026-07-04 | FUE → FMO | Jul 4, 17:25 UTC | Jul 4, 21:25 UTC | 4h 0m |
| 2026-07-04 | - | Jul 4, 11:50 UTC | Jul 4, 16:00 UTC | 4h 10m |
| 2026-07-04 | - | Jul 4, 07:30 UTC | Jul 4, 10:40 UTC | 3h 10m |
| 2026-07-04 | - | Jul 4, 03:10 UTC | Jul 4, 05:50 UTC | 2h 40m |
Specifications
| Registration | D-ADDY |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 3C5099 · 17050231 (octal) |
Looking for transponder-level data? View the Mode-S 3C5099 page for country allocation, callsign history, and ADS-B signal details.
D-ADDY frequently asked
What type of aircraft is D-ADDY?
D-ADDY is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for D-ADDY?
D-ADDY broadcasts on Mode-S (ICAO 24-bit) address 3C5099 (octal 17050231). View the transponder page.
What route does D-ADDY typically fly?
D-ADDY most frequently flies between RHO and FMO based on observed flights.
Where is D-ADDY right now?
D-ADDY is not currently being tracked; last seen 7d ago.