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