Not currently tracked · last seen Jul 26, 18:25 UTC
- Flights observed
- 442 showing last 50
- Avg flight time
- 4h 27m
- Typical route
- MTY → MEX
- Last seen
- Jul 26, 18:25 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | CUN → GDL | Jul 26, 17:05 UTC | Jul 26, 18:25 UTC | 1h 20m |
| 2026-07-26 | OAK → GDL | Jul 26, 07:20 UTC | Jul 26, 15:10 UTC | 7h 50m |
| 2026-07-25 | GDL → OAK | Jul 25, 20:40 UTC | Jul 26, 05:15 UTC | 8h 35m |
| 2026-07-25 | GDL → TIJ | Jul 25, 14:20 UTC | Jul 25, 19:25 UTC | 5h 5m |
| 2026-07-25 | GDL → MEX | Jul 25, 03:10 UTC | Jul 25, 13:05 UTC | 9h 55m |
| 2026-07-25 | NLU → GDL | Jul 25, 01:25 UTC | Jul 25, 01:50 UTC | 25m |
| 2026-07-25 | NLU → TAM | Jul 25, 00:00 UTC | Jul 25, 00:15 UTC | 15m |
| 2026-07-24 | GDL → TGZ | Jul 24, 13:55 UTC | Jul 24, 22:45 UTC | 8h 50m |
| 2026-07-23 | GDL → REX | Jul 23, 19:30 UTC | Jul 24, 12:55 UTC | 17h 25m |
| 2026-07-23 | TQO → NLU | Jul 23, 16:45 UTC | Jul 23, 18:10 UTC | 1h 25m |
| 2026-07-23 | - | Jul 23, 14:10 UTC | Jul 23, 15:40 UTC | 1h 30m |
| 2026-07-22 | LAS → GDL | Jul 22, 20:25 UTC | Jul 23, 13:10 UTC | 16h 45m |
| 2026-07-21 | GDL → LAS | Jul 21, 22:50 UTC | Jul 22, 18:30 UTC | 19h 40m |
| 2026-07-21 | GDL → LAS | Jul 21, 22:10 UTC | Jul 22, 18:30 UTC | 20h 20m |
| 2026-07-21 | GDL → MID | Jul 21, 12:15 UTC | Jul 22, 01:50 UTC | 13h 35m |
| 2026-07-20 | MTY → CJS | Jul 20, 15:35 UTC | Jul 21, 12:20 UTC | 20h 44m |
| 2026-07-20 | MTY → BJX | Jul 20, 04:25 UTC | Jul 20, 13:10 UTC | 8h 45m |
| 2026-07-20 | MTY → BJX | Jul 20, 03:50 UTC | Jul 20, 04:15 UTC | 25m |
| 2026-07-19 | - | Jul 19, 16:50 UTC | Jul 20, 03:35 UTC | 10h 45m |
| 2026-07-19 | - | Jul 19, 08:45 UTC | Jul 19, 15:35 UTC | 6h 50m |
| 2026-07-19 | - | Jul 19, 01:20 UTC | Jul 19, 07:20 UTC | 6h 0m |
| 2026-07-18 | - | Jul 18, 20:40 UTC | Jul 19, 00:10 UTC | 3h 30m |
| 2026-07-18 | BJX → NLU | Jul 18, 14:20 UTC | Jul 18, 14:30 UTC | 10m |
| 2026-07-18 | MTY → BJX | Jul 18, 04:20 UTC | Jul 18, 04:45 UTC | 25m |
| 2026-07-17 | MTY → QRO | Jul 17, 23:14 UTC | Jul 18, 02:14 UTC | 3h 0m |
| 2026-07-17 | MTY → MTY | Jul 17, 18:55 UTC | Jul 17, 22:05 UTC | 3h 10m |
| 2026-07-17 | TQO → MTY | Jul 17, 15:35 UTC | Jul 17, 17:30 UTC | 1h 55m |
| 2026-07-17 | MTY → TQO | Jul 17, 12:30 UTC | Jul 17, 14:24 UTC | 1h 55m |
| 2026-07-17 | - | Jul 17, 04:49 UTC | Jul 17, 05:30 UTC | 40m |
| 2026-07-17 | - | Jul 17, 03:05 UTC | Jul 17, 03:30 UTC | 25m |
| 2026-07-16 | - | Jul 16, 20:45 UTC | Jul 16, 21:50 UTC | 1h 5m |
| 2026-07-16 | MTY → MEX | Jul 16, 18:19 UTC | Jul 16, 19:20 UTC | 1h 0m |
| 2026-07-16 | - | Jul 16, 15:10 UTC | Jul 16, 16:35 UTC | 1h 25m |
| 2026-07-16 | - | Jul 16, 12:40 UTC | Jul 16, 13:49 UTC | 1h 10m |
| 2026-07-16 | - | Jul 16, 02:35 UTC | Jul 16, 05:00 UTC | 2h 25m |
| 2026-07-15 | - | Jul 15, 23:10 UTC | Jul 16, 01:35 UTC | 2h 25m |
| 2026-07-15 | - | Jul 15, 20:35 UTC | Jul 15, 21:45 UTC | 1h 10m |
| 2026-07-15 | MTY → MEX | Jul 15, 18:20 UTC | Jul 15, 19:25 UTC | 1h 5m |
| 2026-07-15 | - | Jul 15, 15:40 UTC | Jul 15, 16:50 UTC | 1h 10m |
| 2026-07-15 | MTY → MEX | Jul 15, 13:10 UTC | Jul 15, 14:15 UTC | 1h 5m |
| 2026-07-15 | - | Jul 15, 05:45 UTC | Jul 15, 06:55 UTC | 1h 10m |
| 2026-07-15 | MTY → MEX | Jul 15, 03:30 UTC | Jul 15, 04:40 UTC | 1h 10m |
| 2026-07-14 | - | Jul 14, 20:40 UTC | Jul 14, 21:45 UTC | 1h 5m |
| 2026-07-14 | - | Jul 14, 19:05 UTC | Jul 14, 19:10 UTC | 5m |
| 2026-07-14 | - | Jul 14, 18:10 UTC | Jul 14, 18:35 UTC | 25m |
| 2026-07-14 | - | Jul 14, 12:10 UTC | Jul 14, 13:20 UTC | 1h 10m |
| 2026-07-14 | - | Jul 14, 04:00 UTC | Jul 14, 04:20 UTC | 20m |
| 2026-07-13 | - | Jul 13, 18:25 UTC | Jul 13, 19:00 UTC | 35m |
| 2026-07-13 | - | Jul 13, 16:20 UTC | Jul 13, 17:00 UTC | 40m |
| 2026-07-13 | - | Jul 13, 14:05 UTC | Jul 13, 14:40 UTC | 35m |
Specifications
| Registration | XA-VAP |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 0D0963 · 03204543 (octal) |
Looking for transponder-level data? View the Mode-S 0D0963 page for country allocation, callsign history, and ADS-B signal details.
XA-VAP frequently asked
What type of aircraft is XA-VAP?
XA-VAP is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for XA-VAP?
XA-VAP broadcasts on Mode-S (ICAO 24-bit) address 0D0963 (octal 03204543). View the transponder page.
What route does XA-VAP typically fly?
XA-VAP most frequently flies between MTY and MEX based on observed flights.
Where is XA-VAP right now?
XA-VAP is not currently being tracked; last seen Jul 26, 18:25 UTC.