Not currently tracked · last seen 43m ago
- Flights observed
- 396 showing last 50
- Avg flight time
- 2h 10m
- Typical route
- MTY → MTY
- Last seen
- 43m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 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 |
| 2026-07-13 | - | Jul 13, 12:20 UTC | Jul 13, 12:50 UTC | 30m |
| 2026-07-13 | - | Jul 13, 02:35 UTC | Jul 13, 03:40 UTC | 1h 5m |
| 2026-07-13 | AZP → MEX | Jul 13, 01:05 UTC | Jul 13, 01:15 UTC | 10m |
| 2026-07-13 | - | Jul 13, 00:05 UTC | Jul 13, 00:30 UTC | 25m |
| 2026-07-12 | MTY → MTY | Jul 12, 18:35 UTC | Jul 12, 21:05 UTC | 2h 30m |
| 2026-07-12 | MTY → MTY | Jul 12, 13:05 UTC | Jul 12, 17:30 UTC | 4h 25m |
| 2026-07-12 | SJO → MTY | Jul 12, 08:30 UTC | Jul 12, 11:40 UTC | 3h 10m |
| 2026-07-12 | MTY → SJO | Jul 12, 03:40 UTC | Jul 12, 06:55 UTC | 3h 15m |
| 2026-07-11 | MTY → MTY | Jul 11, 19:40 UTC | Jul 11, 23:45 UTC | 4h 5m |
| 2026-07-11 | MTY → MTY | Jul 11, 12:30 UTC | Jul 11, 18:40 UTC | 6h 10m |
| 2026-07-11 | - | Jul 11, 02:30 UTC | Jul 11, 03:45 UTC | 1h 15m |
| 2026-07-11 | MTY → VER | Jul 11, 00:15 UTC | Jul 11, 01:30 UTC | 1h 15m |
| 2026-07-10 | MTY → MTY | Jul 10, 20:50 UTC | Jul 10, 23:20 UTC | 2h 30m |
| 2026-07-10 | - | Jul 10, 19:10 UTC | Jul 10, 19:45 UTC | 35m |
| 2026-07-10 | - | Jul 10, 17:20 UTC | Jul 10, 17:55 UTC | 35m |
| 2026-07-10 | - | Jul 10, 15:20 UTC | Jul 10, 15:50 UTC | 30m |
| 2026-07-10 | - | Jul 10, 13:40 UTC | Jul 10, 14:05 UTC | 25m |
| 2026-07-09 | - | Jul 9, 23:05 UTC | Jul 10, 06:10 UTC | 7h 5m |
| 2026-07-09 | MTY → MTY | Jul 9, 12:45 UTC | Jul 9, 19:05 UTC | 6h 20m |
| 2026-07-08 | MTY → MTY | Jul 8, 23:40 UTC | Jul 9, 05:40 UTC | 6h 0m |
| 2026-07-08 | - | Jul 8, 21:05 UTC | Jul 8, 22:25 UTC | 1h 20m |
| 2026-07-08 | MTY → DFW | Jul 8, 17:40 UTC | Jul 8, 18:55 UTC | 1h 15m |
| 2026-07-08 | - | Jul 8, 15:00 UTC | Jul 8, 16:15 UTC | 1h 15m |
| 2026-07-08 | MTY → VER | Jul 8, 12:30 UTC | Jul 8, 13:45 UTC | 1h 15m |
| 2026-07-08 | - | Jul 8, 02:10 UTC | Jul 8, 04:20 UTC | 2h 10m |
| 2026-07-07 | - | Jul 7, 22:35 UTC | Jul 8, 01:20 UTC | 2h 45m |
| 2026-07-07 | - | Jul 7, 17:40 UTC | Jul 7, 21:00 UTC | 3h 20m |
| 2026-07-07 | - | Jul 7, 15:00 UTC | Jul 7, 16:05 UTC | 1h 5m |
| 2026-07-07 | - | Jul 7, 12:15 UTC | Jul 7, 13:20 UTC | 1h 5m |
| 2026-07-07 | MTY → MTY | Jul 7, 03:45 UTC | Jul 7, 07:05 UTC | 3h 20m |
| 2026-07-06 | MTY → MTY | Jul 6, 23:50 UTC | Jul 7, 02:50 UTC | 3h 0m |
| 2026-07-06 | MTY → MTY | Jul 6, 19:40 UTC | Jul 6, 22:35 UTC | 2h 55m |
| 2026-07-06 | - | Jul 6, 16:55 UTC | Jul 6, 18:25 UTC | 1h 30m |
| 2026-07-06 | - | Jul 6, 14:05 UTC | Jul 6, 15:20 UTC | 1h 15m |
| 2026-07-06 | - | Jul 6, 10:00 UTC | Jul 6, 12:45 UTC | 2h 45m |
| 2026-07-06 | MTY → ORD | Jul 6, 05:25 UTC | Jul 6, 08:10 UTC | 2h 45m |
| 2026-07-05 | DEN → MTY | Jul 5, 22:40 UTC | Jul 6, 00:55 UTC | 2h 15m |
| 2026-07-05 | MTY → DEN | Jul 5, 17:50 UTC | Jul 5, 20:25 UTC | 2h 35m |
| 2026-07-05 | - | Jul 5, 04:25 UTC | Jul 5, 05:45 UTC | 1h 20m |
| 2026-07-05 | MTY → VER | Jul 5, 02:25 UTC | Jul 5, 03:35 UTC | 1h 10m |
| 2026-07-04 | - | Jul 4, 22:55 UTC | Jul 5, 01:20 UTC | 2h 25m |
| 2026-07-04 | - | Jul 4, 19:20 UTC | Jul 4, 21:45 UTC | 2h 25m |
| 2026-07-04 | - | Jul 4, 15:00 UTC | Jul 4, 16:05 UTC | 1h 5m |
| 2026-07-04 | - | Jul 4, 12:15 UTC | Jul 4, 13:20 UTC | 1h 5m |
| 2026-07-04 | - | Jul 4, 07:30 UTC | Jul 4, 10:20 UTC | 2h 50m |
| 2026-07-04 | MTY → ORD | Jul 4, 01:55 UTC | Jul 4, 05:30 UTC | 3h 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 MTY based on observed flights.
Where is XA-VAP right now?
XA-VAP is not currently being tracked; last seen 43m ago.