Not currently tracked · last seen 4h ago
- Flights observed
- 94 showing last 50
- Avg flight time
- 11h 52m
- Typical route
- CGP → MCT
- Last seen
- 4h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | MUX → MCT | Jun 2, 23:00 UTC | Jun 2, 23:05 UTC | 5m |
| 2026-06-02 | MCT → MUX | Jun 2, 21:50 UTC | Jun 2, 22:05 UTC | 15m |
| 2026-06-02 | CCJ → MCT | Jun 2, 00:05 UTC | Jun 2, 09:40 UTC | 9h 35m |
| 2026-06-01 | CGP → MCT | Jun 1, 05:15 UTC | Jun 2, 03:50 UTC | 22h 35m |
| 2026-06-01 | CGP → MCT | Jun 1, 03:05 UTC | Jun 2, 00:25 UTC | 21h 20m |
| 2026-05-31 | MCT → CGP | May 31, 16:25 UTC | Jun 1, 01:40 UTC | 9h 15m |
| 2026-05-31 | CCJ → MCT | May 31, 00:30 UTC | May 31, 15:00 UTC | 14h 30m |
| 2026-05-29 | DAC → MCT | May 29, 23:25 UTC | May 30, 02:40 UTC | 3h 15m |
| 2026-05-29 | MCT → DAC | May 29, 19:25 UTC | May 29, 22:20 UTC | 2h 55m |
| 2026-05-28 | MCT → DAC | May 28, 23:40 UTC | May 29, 22:20 UTC | 22h 40m |
| 2026-05-28 | MCT → HYD | May 28, 19:55 UTC | May 29, 00:40 UTC | 4h 45m |
| 2026-05-27 | MCT → HYD | May 27, 23:55 UTC | May 28, 21:00 UTC | 21h 5m |
| 2026-05-27 | MCT → HYD | May 27, 21:05 UTC | May 28, 21:00 UTC | 23h 55m |
| 2026-05-27 | MCT → HYD | May 27, 14:45 UTC | May 28, 00:50 UTC | 10h 5m |
| 2026-05-26 | MCT → HYD | May 26, 21:04 UTC | May 27, 21:00 UTC | 23h 55m |
| 2026-05-26 | CGP → MCT | May 26, 19:55 UTC | May 27, 15:10 UTC | 19h 15m |
| 2026-05-26 | CGP → MCT | May 26, 17:55 UTC | May 27, 15:00 UTC | 21h 5m |
| 2026-05-25 | MCT → CGP | May 25, 21:04 UTC | May 26, 16:40 UTC | 19h 35m |
| 2026-05-25 | MCT → CGP | May 25, 19:54 UTC | May 26, 16:40 UTC | 20h 45m |
| 2026-05-25 | MCT → HYD | May 25, 15:25 UTC | May 26, 14:40 UTC | 23h 14m |
| 2026-05-25 | MCT → DMM | May 25, 14:00 UTC | May 25, 14:10 UTC | 10m |
| 2026-05-25 | BOM → MCT | May 25, 08:05 UTC | May 25, 08:30 UTC | 25m |
| 2026-05-24 | MCT → BOM | May 24, 15:25 UTC | May 25, 06:25 UTC | 15h 0m |
| 2026-05-23 | MAA → MCT | May 23, 23:15 UTC | May 24, 00:55 UTC | 1h 40m |
| 2026-05-23 | MCT → MAA | May 23, 20:20 UTC | May 23, 22:00 UTC | 1h 40m |
| 2026-05-23 | MCT → MAA | May 23, 01:35 UTC | May 23, 22:00 UTC | 20h 25m |
| 2026-05-23 | BLR → MCT | May 23, 00:30 UTC | May 23, 22:00 UTC | 21h 30m |
| 2026-05-22 | MCT → BLR | May 22, 21:45 UTC | May 22, 23:15 UTC | 1h 30m |
| 2026-05-20 | CCJ → MCT | May 20, 19:15 UTC | May 20, 20:40 UTC | 1h 25m |
| 2026-05-20 | MCT → CCJ | May 20, 16:30 UTC | May 20, 16:55 UTC | 25m |
| 2026-05-19 | CGP → MCT | May 19, 19:15 UTC | May 20, 16:55 UTC | 21h 41m |
| 2026-05-19 | CGP → MCT | May 19, 17:20 UTC | May 20, 16:55 UTC | 23h 36m |
| 2026-05-18 | DAC → MCT | May 18, 23:35 UTC | May 19, 16:00 UTC | 16h 25m |
| 2026-05-18 | MCT → DAC | May 18, 19:40 UTC | May 18, 22:30 UTC | 2h 50m |
| 2026-05-18 | MCT → DAC | May 18, 01:05 UTC | May 18, 22:30 UTC | 21h 24m |
| 2026-05-18 | MCT → DAC | May 18, 00:30 UTC | May 18, 22:30 UTC | 21h 59m |
| 2026-05-17 | MCT → LKO | May 17, 15:25 UTC | May 17, 22:20 UTC | 6h 55m |
| 2026-05-16 | MCT → DMM | May 16, 23:10 UTC | May 17, 13:55 UTC | 14h 45m |
| 2026-05-16 | MCT → MAA | May 16, 20:00 UTC | May 16, 21:20 UTC | 1h 19m |
| 2026-05-15 | HYD → MCT | May 15, 20:20 UTC | May 16, 10:20 UTC | 14h 1m |
| 2026-05-14 | HYD → MCT | May 14, 23:50 UTC | May 15, 20:35 UTC | 20h 44m |
| 2026-05-14 | HYD → MCT | May 14, 20:00 UTC | May 15, 00:15 UTC | 4h 15m |
| 2026-05-14 | LKO → MCT | May 14, 01:05 UTC | May 15, 00:15 UTC | 23h 10m |
| 2026-05-14 | LKO → MCT | May 14, 00:50 UTC | May 14, 20:10 UTC | 19h 20m |
| 2026-05-13 | MCT → LKO | May 13, 21:45 UTC | May 13, 22:40 UTC | 55m |
| 2026-05-12 | MUX → MCT | May 12, 23:20 UTC | May 12, 23:30 UTC | 10m |
| 2026-05-12 | MCT → MUX | May 12, 22:15 UTC | May 12, 22:31 UTC | 15m |
| 2026-05-12 | CGP → MCT | May 12, 02:45 UTC | May 12, 14:10 UTC | 11h 25m |
| 2026-05-09 | LKO → MCT | May 9, 23:40 UTC | May 10, 01:45 UTC | 2h 5m |
| 2026-05-09 | MCT → LKO | May 9, 14:40 UTC | May 9, 22:34 UTC | 7h 55m |
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 4h ago.