Not currently tracked · last seen Jul 24, 14:10 UTC
- Flights observed
- 199 showing last 50
- Avg flight time
- 14h 8m
- Typical route
- CGP → MCT
- Last seen
- Jul 24, 14:10 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-24 | CGP → MCT | Jul 24, 03:05 UTC | Jul 24, 14:10 UTC | 11h 5m |
| 2026-07-23 | MCT → CGP | Jul 23, 22:35 UTC | Jul 24, 01:50 UTC | 3h 15m |
| 2026-07-23 | - | Jul 23, 12:45 UTC | Jul 23, 14:05 UTC | 1h 20m |
| 2026-07-23 | CGP → MCT | Jul 23, 05:40 UTC | Jul 23, 10:05 UTC | 4h 25m |
| 2026-07-23 | CGP → MCT | Jul 23, 03:35 UTC | Jul 23, 04:30 UTC | 55m |
| 2026-07-22 | MCT → CGP | Jul 22, 12:05 UTC | Jul 23, 02:00 UTC | 13h 55m |
| 2026-07-22 | MCT → CGP | Jul 22, 01:05 UTC | Jul 23, 01:00 UTC | 23h 55m |
| 2026-07-21 | CGP → MCT | Jul 21, 04:10 UTC | Jul 21, 22:40 UTC | 18h 30m |
| 2026-07-20 | MCT → CGP | Jul 20, 12:25 UTC | Jul 21, 01:55 UTC | 13h 30m |
| 2026-07-19 | PZU → MCT | Jul 19, 23:35 UTC | Jul 20, 23:00 UTC | 23h 25m |
| 2026-07-19 | PZU → MCT | Jul 19, 21:05 UTC | Jul 20, 18:20 UTC | 21h 15m |
| 2026-07-19 | MCT → HYD | Jul 19, 19:55 UTC | Jul 20, 18:20 UTC | 22h 25m |
| 2026-07-19 | - | Jul 19, 15:15 UTC | Jul 19, 16:15 UTC | 1h 0m |
| 2026-07-19 | - | Jul 19, 13:35 UTC | Jul 19, 13:45 UTC | 10m |
| 2026-07-18 | - | Jul 18, 21:00 UTC | Jul 19, 09:40 UTC | 12h 40m |
| 2026-07-18 | - | Jul 18, 11:05 UTC | Jul 19, 09:40 UTC | 22h 35m |
| 2026-07-17 | - | Jul 17, 23:45 UTC | Jul 18, 21:05 UTC | 21h 21m |
| 2026-07-17 | - | Jul 17, 21:05 UTC | Jul 18, 21:00 UTC | 23h 56m |
| 2026-07-17 | - | Jul 17, 20:04 UTC | Jul 18, 11:20 UTC | 15h 16m |
| 2026-07-17 | - | Jul 17, 15:05 UTC | Jul 18, 11:20 UTC | 20h 16m |
| 2026-07-17 | - | Jul 17, 00:35 UTC | Jul 17, 21:15 UTC | 20h 40m |
| 2026-07-16 | - | Jul 16, 22:35 UTC | Jul 16, 23:20 UTC | 45m |
| 2026-07-15 | - | Jul 15, 11:20 UTC | Jul 15, 16:35 UTC | 5h 15m |
| 2026-07-15 | - | Jul 15, 10:55 UTC | Jul 15, 11:15 UTC | 20m |
| 2026-07-14 | - | Jul 14, 13:05 UTC | Jul 15, 11:15 UTC | 22h 9m |
| 2026-07-14 | - | Jul 14, 12:50 UTC | Jul 15, 11:00 UTC | 22h 9m |
| 2026-07-13 | - | Jul 13, 22:10 UTC | Jul 14, 13:45 UTC | 15h 35m |
| 2026-07-13 | - | Jul 13, 16:40 UTC | Jul 14, 13:45 UTC | 21h 5m |
| 2026-07-13 | - | Jul 13, 11:25 UTC | Jul 14, 00:20 UTC | 12h 55m |
| 2026-07-12 | - | Jul 12, 23:30 UTC | Jul 13, 22:15 UTC | 22h 45m |
| 2026-07-12 | - | Jul 12, 03:05 UTC | Jul 12, 22:00 UTC | 18h 55m |
| 2026-07-12 | - | Jul 12, 01:05 UTC | Jul 12, 22:00 UTC | 20h 55m |
| 2026-07-12 | - | Jul 12, 00:45 UTC | Jul 12, 22:00 UTC | 21h 15m |
| 2026-07-11 | - | Jul 11, 10:25 UTC | Jul 11, 22:40 UTC | 12h 15m |
| 2026-07-10 | - | Jul 10, 15:30 UTC | Jul 11, 11:15 UTC | 19h 45m |
| 2026-07-10 | - | Jul 10, 04:05 UTC | Jul 10, 16:15 UTC | 12h 10m |
| 2026-07-09 | - | Jul 9, 17:45 UTC | Jul 10, 02:45 UTC | 9h 0m |
| 2026-07-09 | - | Jul 9, 00:00 UTC | Jul 9, 16:05 UTC | 16h 5m |
| 2026-07-08 | - | Jul 8, 19:35 UTC | Jul 8, 22:55 UTC | 3h 20m |
| 2026-07-07 | - | Jul 7, 21:05 UTC | Jul 8, 16:30 UTC | 19h 25m |
| 2026-07-07 | - | Jul 7, 20:30 UTC | Jul 8, 16:30 UTC | 20h 0m |
| 2026-07-07 | - | Jul 7, 07:05 UTC | Jul 8, 01:05 UTC | 18h 0m |
| 2026-07-07 | - | Jul 7, 05:05 UTC | Jul 8, 01:05 UTC | 20h 0m |
| 2026-07-07 | - | Jul 7, 04:10 UTC | Jul 8, 01:05 UTC | 20h 55m |
| 2026-07-06 | - | Jul 6, 22:30 UTC | Jul 7, 01:40 UTC | 3h 10m |
| 2026-07-06 | - | Jul 6, 09:05 UTC | Jul 6, 13:45 UTC | 4h 40m |
| 2026-07-04 | - | Jul 4, 00:20 UTC | Jul 4, 01:50 UTC | 1h 30m |
| 2026-07-03 | - | Jul 3, 21:25 UTC | Jul 3, 23:05 UTC | 1h 40m |
| 2026-07-03 | - | Jul 3, 01:30 UTC | Jul 3, 23:05 UTC | 21h 35m |
| 2026-07-03 | - | Jul 3, 00:00 UTC | Jul 3, 23:00 UTC | 23h 0m |
Specifications
| Registration | A4O-OVG |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 70C10C · 34140414 (octal) |
Looking for transponder-level data? View the Mode-S 70C10C page for country allocation, callsign history, and ADS-B signal details.
A4O-OVG frequently asked
What type of aircraft is A4O-OVG?
A4O-OVG is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for A4O-OVG?
A4O-OVG broadcasts on Mode-S (ICAO 24-bit) address 70C10C (octal 34140414). View the transponder page.
What route does A4O-OVG typically fly?
A4O-OVG most frequently flies between CGP and MCT based on observed flights.
Where is A4O-OVG right now?
A4O-OVG is not currently being tracked; last seen Jul 24, 14:10 UTC.