Not currently tracked · last seen 4h ago
- Flights observed
- 250 showing last 50
- Avg flight time
- 1h 26m
- Typical route
- TLS → ORY
- Last seen
- 4h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | VCE → ORY | May 29, 19:25 UTC | May 29, 20:45 UTC | 1h 20m |
| 2026-05-29 | ORY → VCE | May 29, 17:10 UTC | May 29, 18:25 UTC | 1h 15m |
| 2026-05-29 | TLS → ORY | May 29, 14:40 UTC | May 29, 15:40 UTC | 1h 0m |
| 2026-05-29 | ORY → TLS | May 29, 13:05 UTC | May 29, 14:00 UTC | 55m |
| 2026-05-29 | TLS → ORY | May 29, 11:05 UTC | May 29, 12:10 UTC | 1h 5m |
| 2026-05-29 | - | May 29, 09:20 UTC | May 29, 10:20 UTC | 1h 0m |
| 2026-05-29 | LIN → ORY | May 29, 07:20 UTC | May 29, 08:20 UTC | 1h 0m |
| 2026-05-29 | ORY → LIN | May 29, 04:50 UTC | May 29, 05:55 UTC | 1h 5m |
| 2026-05-28 | NCE → ORY | May 28, 19:20 UTC | May 28, 20:35 UTC | 1h 15m |
| 2026-05-28 | ORY → NCE | May 28, 17:10 UTC | May 28, 18:20 UTC | 1h 10m |
| 2026-05-28 | TLS → ORY | May 28, 15:25 UTC | May 28, 16:20 UTC | 55m |
| 2026-05-28 | ORY → TLS | May 28, 13:45 UTC | May 28, 14:40 UTC | 55m |
| 2026-05-28 | TLS → ORY | May 28, 11:35 UTC | May 28, 12:25 UTC | 50m |
| 2026-05-28 | ORY → TLS | May 28, 09:50 UTC | May 28, 10:50 UTC | 1h 0m |
| 2026-05-28 | VCE → ORY | May 28, 07:25 UTC | May 28, 08:55 UTC | 1h 30m |
| 2026-05-28 | ORY → VCE | May 28, 05:05 UTC | May 28, 06:20 UTC | 1h 15m |
| 2026-05-27 | FCO → ORY | May 27, 17:40 UTC | May 27, 19:25 UTC | 1h 45m |
| 2026-05-27 | ORY → FCO | May 27, 14:55 UTC | May 27, 16:25 UTC | 1h 30m |
| 2026-05-27 | VCE → ORY | May 27, 11:55 UTC | May 27, 13:20 UTC | 1h 25m |
| 2026-05-27 | ORY → VCE | May 27, 09:30 UTC | May 27, 10:45 UTC | 1h 15m |
| 2026-05-27 | TLS → ORY | May 27, 05:49 UTC | May 27, 06:44 UTC | 55m |
| 2026-05-27 | ORY → TLS | May 27, 04:04 UTC | May 27, 05:04 UTC | 1h 0m |
| 2026-05-26 | LIN → ORY | May 26, 19:15 UTC | May 26, 20:24 UTC | 1h 10m |
| 2026-05-26 | CDG → LIN | May 26, 17:04 UTC | May 26, 18:14 UTC | 1h 10m |
| 2026-05-26 | - | May 26, 13:00 UTC | May 26, 15:54 UTC | 2h 55m |
| 2026-05-26 | CDG → HER | May 26, 08:50 UTC | May 26, 11:54 UTC | 3h 5m |
| 2026-05-26 | MXP → CDG | May 26, 06:14 UTC | May 26, 07:19 UTC | 1h 5m |
| 2026-05-26 | CDG → MXP | May 26, 04:00 UTC | May 26, 05:05 UTC | 1h 5m |
| 2026-05-25 | NCE → CDG | May 25, 20:45 UTC | May 25, 22:00 UTC | 1h 15m |
| 2026-05-25 | CDG → NCE | May 25, 18:35 UTC | May 25, 19:54 UTC | 1h 19m |
| 2026-05-25 | LBA → CDG | May 25, 16:25 UTC | May 25, 17:30 UTC | 1h 5m |
| 2026-05-25 | CDG → EDI | May 25, 14:15 UTC | May 25, 15:20 UTC | 1h 5m |
| 2026-05-25 | LTN → CDG | May 25, 12:25 UTC | May 25, 13:15 UTC | 50m |
| 2026-05-25 | CDG → BRS | May 25, 10:35 UTC | May 25, 11:30 UTC | 55m |
| 2026-05-25 | VCE → CDG | May 25, 07:40 UTC | May 25, 09:05 UTC | 1h 25m |
| 2026-05-25 | CDG → VCE | May 25, 05:10 UTC | May 25, 06:30 UTC | 1h 20m |
| 2026-05-24 | VCE → CDG | May 24, 20:15 UTC | May 24, 21:35 UTC | 1h 20m |
| 2026-05-24 | CDG → VCE | May 24, 18:10 UTC | May 24, 19:30 UTC | 1h 20m |
| 2026-05-24 | FSC → CDG | May 24, 15:25 UTC | May 24, 16:50 UTC | 1h 25m |
| 2026-05-24 | CDG → FSC | May 24, 14:10 UTC | May 24, 14:20 UTC | 10m |
| 2026-05-24 | CDG → FSC | May 24, 11:05 UTC | May 24, 13:05 UTC | 2h 0m |
| 2026-05-24 | - | May 24, 07:40 UTC | May 24, 08:15 UTC | 35m |
| 2026-05-24 | LYS → LGW | May 24, 05:05 UTC | May 24, 06:15 UTC | 1h 10m |
| 2026-05-23 | GLA → AMS | May 23, 12:55 UTC | May 23, 23:00 UTC | 10h 6m |
| 2026-05-23 | - | May 23, 08:40 UTC | May 23, 10:35 UTC | 1h 55m |
| 2026-05-23 | LYS → TNG | May 23, 05:30 UTC | May 23, 07:35 UTC | 2h 5m |
| 2026-05-22 | LGW → LYS | May 22, 19:05 UTC | May 22, 20:15 UTC | 1h 10m |
| 2026-05-22 | LYS → LGW | May 22, 16:45 UTC | May 22, 18:05 UTC | 1h 20m |
| 2026-05-22 | BIQ → LYS | May 22, 14:45 UTC | May 22, 15:45 UTC | 1h 0m |
| 2026-05-22 | LYS → BIQ | May 22, 12:55 UTC | May 22, 13:55 UTC | 1h 0m |
Specifications
| Registration | OE-IVI |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 440080 · 21000200 (octal) |
Looking for transponder-level data? View the Mode-S 440080 page for country allocation, callsign history, and ADS-B signal details.
OE-IVI frequently asked
What type of aircraft is OE-IVI?
OE-IVI is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for OE-IVI?
OE-IVI broadcasts on Mode-S (ICAO 24-bit) address 440080 (octal 21000200). View the transponder page.
What route does OE-IVI typically fly?
OE-IVI most frequently flies between TLS and ORY based on observed flights.
Where is OE-IVI right now?
OE-IVI is not currently being tracked; last seen 4h ago.