Not currently tracked · last seen Jul 26, 04:40 UTC
- Flights observed
- 303 showing last 50
- Avg flight time
- 3h 5m
- Typical route
- MTY → MTY
- Last seen
- Jul 26, 04:40 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | HMO → MEX | Jul 26, 04:30 UTC | Jul 26, 04:35 UTC | 5m |
| 2026-07-26 | HMO → MEX | Jul 26, 02:15 UTC | Jul 26, 02:35 UTC | 20m |
| 2026-07-26 | TIJ → HMO | Jul 26, 00:15 UTC | Jul 26, 01:20 UTC | 1h 5m |
| 2026-07-25 | LMM → TIJ | Jul 25, 22:10 UTC | Jul 25, 23:20 UTC | 1h 10m |
| 2026-07-25 | TIJ → LMM | Jul 25, 19:30 UTC | Jul 25, 20:45 UTC | 1h 15m |
| 2026-07-25 | - | Jul 25, 13:50 UTC | Jul 25, 16:55 UTC | 3h 5m |
| 2026-07-25 | TIJ → ACA | Jul 25, 09:10 UTC | Jul 25, 12:20 UTC | 3h 10m |
| 2026-07-25 | MTY → TIJ | Jul 25, 04:30 UTC | Jul 25, 06:50 UTC | 2h 20m |
| 2026-07-25 | TIJ → MTY | Jul 25, 00:05 UTC | Jul 25, 02:35 UTC | 2h 30m |
| 2026-07-24 | - | Jul 24, 15:35 UTC | Jul 24, 20:25 UTC | 4h 50m |
| 2026-07-23 | GDL → CUL | Jul 23, 21:55 UTC | Jul 24, 03:55 UTC | 6h 0m |
| 2026-07-23 | - | Jul 23, 15:35 UTC | Jul 23, 20:50 UTC | 5h 15m |
| 2026-07-23 | MTY → TIJ | Jul 23, 03:45 UTC | Jul 23, 06:05 UTC | 2h 20m |
| 2026-07-22 | QRO → MTY | Jul 22, 18:20 UTC | Jul 23, 01:05 UTC | 6h 45m |
| 2026-07-22 | TIJ → QRO | Jul 22, 01:55 UTC | Jul 22, 17:05 UTC | 15h 10m |
| 2026-07-21 | LTO → TIJ | Jul 21, 23:45 UTC | Jul 22, 00:55 UTC | 1h 10m |
| 2026-07-21 | - | Jul 21, 21:30 UTC | Jul 21, 22:30 UTC | 1h 0m |
| 2026-07-21 | - | Jul 21, 03:10 UTC | Jul 21, 20:35 UTC | 17h 25m |
| 2026-07-20 | MTY → MTY | Jul 20, 21:40 UTC | Jul 21, 02:10 UTC | 4h 29m |
| 2026-07-20 | - | Jul 20, 16:25 UTC | Jul 20, 20:40 UTC | 4h 15m |
| 2026-07-20 | MTY → CUL | Jul 20, 12:25 UTC | Jul 20, 15:35 UTC | 3h 10m |
| 2026-07-19 | - | Jul 19, 20:45 UTC | Jul 20, 02:20 UTC | 5h 35m |
| 2026-07-19 | CUN → OAX | Jul 19, 17:55 UTC | Jul 19, 19:15 UTC | 1h 20m |
| 2026-07-19 | OAX → CUN | Jul 19, 15:10 UTC | Jul 19, 16:45 UTC | 1h 35m |
| 2026-07-19 | TIJ → MLM | Jul 19, 13:25 UTC | Jul 19, 13:55 UTC | 30m |
| 2026-07-18 | - | Jul 18, 23:15 UTC | Jul 19, 02:05 UTC | 2h 50m |
| 2026-07-18 | GDL → MEX | Jul 18, 18:05 UTC | Jul 18, 21:25 UTC | 3h 20m |
| 2026-07-18 | MTY → MEX | Jul 18, 12:15 UTC | Jul 18, 13:25 UTC | 1h 10m |
| 2026-07-18 | MEX → MTY | Jul 18, 04:25 UTC | Jul 18, 05:40 UTC | 1h 15m |
| 2026-07-18 | TIJ → MEX | Jul 18, 02:35 UTC | Jul 18, 02:45 UTC | 10m |
| 2026-07-17 | TIJ → MEX | Jul 17, 23:39 UTC | Jul 18, 00:45 UTC | 1h 5m |
| 2026-07-17 | MEX → TIJ | Jul 17, 19:00 UTC | Jul 17, 22:00 UTC | 3h 0m |
| 2026-07-17 | - | Jul 17, 12:04 UTC | Jul 17, 16:19 UTC | 4h 15m |
| 2026-07-17 | TIJ → MEX | Jul 17, 06:15 UTC | Jul 17, 06:20 UTC | 5m |
| 2026-07-17 | TIJ → MEX | Jul 17, 03:20 UTC | Jul 17, 04:29 UTC | 1h 10m |
| 2026-07-17 | - | Jul 17, 01:09 UTC | Jul 17, 02:15 UTC | 1h 5m |
| 2026-07-14 | - | Jul 14, 15:40 UTC | Jul 14, 17:25 UTC | 1h 45m |
| 2026-07-14 | - | Jul 14, 12:40 UTC | Jul 14, 14:35 UTC | 1h 55m |
| 2026-07-14 | - | Jul 14, 02:45 UTC | Jul 14, 04:05 UTC | 1h 20m |
| 2026-07-13 | - | Jul 13, 19:55 UTC | Jul 14, 01:40 UTC | 5h 45m |
| 2026-07-13 | - | Jul 13, 16:25 UTC | Jul 13, 18:50 UTC | 2h 25m |
| 2026-07-13 | MTY → MTY | Jul 13, 12:00 UTC | Jul 13, 15:25 UTC | 3h 25m |
| 2026-07-13 | CUN → MTY | Jul 13, 03:55 UTC | Jul 13, 05:50 UTC | 1h 55m |
| 2026-07-13 | MTY → CUN | Jul 13, 00:50 UTC | Jul 13, 02:55 UTC | 2h 5m |
| 2026-07-12 | MTY → MTY | Jul 12, 20:20 UTC | Jul 12, 23:40 UTC | 3h 20m |
| 2026-07-12 | MTY → MTY | Jul 12, 15:55 UTC | Jul 12, 19:25 UTC | 3h 30m |
| 2026-07-12 | MTY → MTY | Jul 12, 12:15 UTC | Jul 12, 15:01 UTC | 2h 45m |
| 2026-07-12 | CUN → MTY | Jul 12, 00:40 UTC | Jul 12, 02:45 UTC | 2h 5m |
| 2026-07-11 | MTY → CUN | Jul 11, 21:40 UTC | Jul 11, 23:45 UTC | 2h 5m |
| 2026-07-11 | MTY → MTY | Jul 11, 16:25 UTC | Jul 11, 20:45 UTC | 4h 20m |
Specifications
| Registration | XA-VVA |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 0D0FFD · 03207775 (octal) |
Looking for transponder-level data? View the Mode-S 0D0FFD page for country allocation, callsign history, and ADS-B signal details.
XA-VVA frequently asked
What type of aircraft is XA-VVA?
XA-VVA is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for XA-VVA?
XA-VVA broadcasts on Mode-S (ICAO 24-bit) address 0D0FFD (octal 03207775). View the transponder page.
What route does XA-VVA typically fly?
XA-VVA most frequently flies between MTY and MTY based on observed flights.
Where is XA-VVA right now?
XA-VVA is not currently being tracked; last seen Jul 26, 04:40 UTC.