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