Not currently tracked · last seen 7h ago
- Flights observed
- 526 showing last 50
- Avg flight time
- 1h 45m
- Typical route
- LGW → OPO
- Last seen
- 7h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | FNC → OPO | Jul 13, 20:30 UTC | Jul 13, 22:05 UTC | 1h 35m |
| 2026-07-13 | - | Jul 13, 19:35 UTC | Jul 13, 19:40 UTC | 5m |
| 2026-07-13 | - | Jul 13, 17:55 UTC | Jul 13, 19:00 UTC | 1h 5m |
| 2026-07-13 | ORY → OPO | Jul 13, 14:35 UTC | Jul 13, 16:30 UTC | 1h 55m |
| 2026-07-13 | OPO → ORY | Jul 13, 11:45 UTC | Jul 13, 13:25 UTC | 1h 40m |
| 2026-07-13 | - | Jul 13, 08:15 UTC | Jul 13, 10:25 UTC | 2h 10m |
| 2026-07-13 | OPO → GVA | Jul 13, 05:31 UTC | Jul 13, 07:10 UTC | 1h 40m |
| 2026-07-12 | GVA → OPO | Jul 12, 19:15 UTC | Jul 12, 21:25 UTC | 2h 10m |
| 2026-07-12 | OPO → GVA | Jul 12, 16:20 UTC | Jul 12, 18:05 UTC | 1h 45m |
| 2026-07-12 | NTE → OPO | Jul 12, 14:05 UTC | Jul 12, 15:30 UTC | 1h 25m |
| 2026-07-12 | - | Jul 12, 11:55 UTC | Jul 12, 13:10 UTC | 1h 15m |
| 2026-07-12 | LGW → OPO | Jul 12, 08:50 UTC | Jul 12, 10:45 UTC | 1h 55m |
| 2026-07-12 | OPO → LGW | Jul 12, 05:50 UTC | Jul 12, 07:40 UTC | 1h 50m |
| 2026-07-11 | GVA → OPO | Jul 11, 17:35 UTC | Jul 11, 19:40 UTC | 2h 5m |
| 2026-07-11 | OPO → GVA | Jul 11, 12:30 UTC | Jul 11, 14:35 UTC | 2h 5m |
| 2026-07-11 | - | Jul 11, 09:00 UTC | Jul 11, 11:05 UTC | 2h 5m |
| 2026-07-11 | - | Jul 11, 05:15 UTC | Jul 11, 07:25 UTC | 2h 10m |
| 2026-07-10 | - | Jul 10, 20:05 UTC | Jul 10, 22:15 UTC | 2h 10m |
| 2026-07-10 | OPO → LUX | Jul 10, 17:05 UTC | Jul 10, 19:05 UTC | 2h 0m |
| 2026-07-10 | BOD → OPO | Jul 10, 14:50 UTC | Jul 10, 16:05 UTC | 1h 15m |
| 2026-07-10 | OPO → BOD | Jul 10, 12:35 UTC | Jul 10, 13:55 UTC | 1h 20m |
| 2026-07-10 | - | Jul 10, 09:20 UTC | Jul 10, 11:30 UTC | 2h 10m |
| 2026-07-10 | OPO → LUX | Jul 10, 05:25 UTC | Jul 10, 07:35 UTC | 2h 10m |
| 2026-07-09 | - | Jul 9, 19:00 UTC | Jul 9, 20:20 UTC | 1h 20m |
| 2026-07-09 | - | Jul 9, 16:55 UTC | Jul 9, 18:05 UTC | 1h 10m |
| 2026-07-09 | BOD → OPO | Jul 9, 14:15 UTC | Jul 9, 15:35 UTC | 1h 20m |
| 2026-07-09 | OPO → BOD | Jul 9, 12:00 UTC | Jul 9, 13:30 UTC | 1h 30m |
| 2026-07-09 | LGW → OPO | Jul 9, 09:20 UTC | Jul 9, 11:05 UTC | 1h 45m |
| 2026-07-09 | - | Jul 9, 05:55 UTC | Jul 9, 07:55 UTC | 2h 0m |
| 2026-07-08 | LGW → OPO | Jul 8, 19:25 UTC | Jul 8, 21:20 UTC | 1h 55m |
| 2026-07-08 | OPO → LGW | Jul 8, 16:35 UTC | Jul 8, 18:20 UTC | 1h 45m |
| 2026-07-08 | IBZ → OPO | Jul 8, 14:05 UTC | Jul 8, 15:40 UTC | 1h 35m |
| 2026-07-08 | OPO → IBZ | Jul 8, 11:35 UTC | Jul 8, 13:00 UTC | 1h 25m |
| 2026-07-08 | MAH → OPO | Jul 8, 08:15 UTC | Jul 8, 10:05 UTC | 1h 50m |
| 2026-07-08 | OPO → MAH | Jul 8, 05:20 UTC | Jul 8, 06:55 UTC | 1h 35m |
| 2026-07-07 | FNC → OPO | Jul 7, 20:45 UTC | Jul 7, 22:15 UTC | 1h 30m |
| 2026-07-07 | OPO → FNC | Jul 7, 18:15 UTC | Jul 7, 20:00 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 15:15 UTC | Jul 7, 17:20 UTC | 2h 5m |
| 2026-07-07 | OPO → BSL | Jul 7, 11:50 UTC | Jul 7, 14:00 UTC | 2h 10m |
| 2026-07-07 | LGW → OPO | Jul 7, 08:40 UTC | Jul 7, 10:30 UTC | 1h 50m |
| 2026-07-07 | OPO → LGW | Jul 7, 05:25 UTC | Jul 7, 07:20 UTC | 1h 55m |
| 2026-07-06 | GVA → OPO | Jul 6, 16:50 UTC | Jul 6, 18:45 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 13:40 UTC | Jul 6, 15:35 UTC | 1h 55m |
| 2026-07-06 | ZRH → OPO | Jul 6, 09:30 UTC | Jul 6, 11:40 UTC | 2h 10m |
| 2026-07-06 | OPO → ZRH | Jul 6, 06:10 UTC | Jul 6, 08:25 UTC | 2h 15m |
| 2026-07-05 | LGW → OPO | Jul 5, 20:35 UTC | Jul 5, 22:25 UTC | 1h 50m |
| 2026-07-05 | OPO → LGW | Jul 5, 16:45 UTC | Jul 5, 18:45 UTC | 2h 0m |
| 2026-07-05 | GVA → OPO | Jul 5, 13:25 UTC | Jul 5, 15:20 UTC | 1h 55m |
| 2026-07-05 | OPO → GVA | Jul 5, 10:40 UTC | Jul 5, 12:35 UTC | 1h 55m |
| 2026-07-05 | - | Jul 5, 07:55 UTC | Jul 5, 09:30 UTC | 1h 35m |
Specifications
| Registration | OE-IJV |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 440352 · 21001522 (octal) |
Looking for transponder-level data? View the Mode-S 440352 page for country allocation, callsign history, and ADS-B signal details.
OE-IJV frequently asked
What type of aircraft is OE-IJV?
OE-IJV is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for OE-IJV?
OE-IJV broadcasts on Mode-S (ICAO 24-bit) address 440352 (octal 21001522). View the transponder page.
What route does OE-IJV typically fly?
OE-IJV most frequently flies between LGW and OPO based on observed flights.
Where is OE-IJV right now?
OE-IJV is not currently being tracked; last seen 7h ago.