Not currently tracked · last seen 5h ago
- Flights observed
- 91 showing last 50
- Avg flight time
- 4h 1m
- Typical route
- DAD → MNL
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | - | May 29, 19:55 UTC | May 29, 20:25 UTC | 30m |
| 2026-05-29 | DAD → MNL | May 29, 11:40 UTC | May 29, 18:30 UTC | 6h 50m |
| 2026-05-28 | PUS → DAD | May 28, 19:00 UTC | May 29, 01:40 UTC | 6h 40m |
| 2026-05-28 | HAN → DAD | May 28, 11:10 UTC | May 28, 11:25 UTC | 15m |
| 2026-05-28 | ICN → HAN | May 28, 02:10 UTC | May 28, 06:00 UTC | 3h 50m |
| 2026-05-27 | HAN → ICN | May 27, 22:35 UTC | May 27, 23:00 UTC | 25m |
| 2026-05-27 | HAN → ICN | May 27, 19:05 UTC | May 27, 19:25 UTC | 20m |
| 2026-05-27 | - | May 27, 11:05 UTC | May 27, 15:25 UTC | 4h 20m |
| 2026-05-27 | BKK → HAN | May 27, 07:20 UTC | May 27, 08:15 UTC | 55m |
| 2026-05-27 | HAN → BKK | May 27, 04:49 UTC | May 27, 05:49 UTC | 1h 0m |
| 2026-05-26 | FUK → HAN | May 26, 00:24 UTC | May 26, 00:35 UTC | 10m |
| 2026-05-24 | ICN → HAN | May 24, 21:40 UTC | May 24, 21:45 UTC | 5m |
| 2026-05-24 | RMQ → HAN | May 24, 10:15 UTC | May 24, 20:25 UTC | 10h 10m |
| 2026-05-24 | HAN → RMQ | May 24, 07:45 UTC | May 24, 09:05 UTC | 1h 20m |
| 2026-05-22 | ICN → HAN | May 22, 02:15 UTC | May 22, 02:40 UTC | 25m |
| 2026-05-21 | HAN → ICN | May 21, 10:10 UTC | May 21, 22:35 UTC | 12h 25m |
| 2026-05-20 | - | May 20, 20:20 UTC | May 20, 20:55 UTC | 35m |
| 2026-05-20 | DAD → MNL | May 20, 18:05 UTC | May 20, 18:50 UTC | 45m |
| 2026-05-19 | - | May 19, 20:10 UTC | May 20, 18:50 UTC | 22h 41m |
| 2026-05-19 | DAD → MNL | May 19, 08:05 UTC | May 19, 18:20 UTC | 10h 15m |
| 2026-05-18 | DAD → MNL | May 18, 19:35 UTC | May 19, 18:20 UTC | 22h 45m |
| 2026-05-18 | MNL → SGN | May 18, 19:25 UTC | May 19, 08:30 UTC | 13h 5m |
| 2026-05-18 | SGN → MNL | May 18, 17:35 UTC | May 18, 18:15 UTC | 40m |
| 2026-05-16 | CAN → HAN | May 16, 18:35 UTC | May 16, 18:45 UTC | 10m |
| 2026-05-16 | RMQ → HAN | May 16, 10:50 UTC | May 16, 11:55 UTC | 1h 5m |
| 2026-05-16 | HAN → RMQ | May 16, 08:31 UTC | May 16, 09:40 UTC | 1h 10m |
| 2026-05-16 | FUK → HAN | May 16, 00:35 UTC | May 16, 00:45 UTC | 10m |
| 2026-05-15 | TPE → HAN | May 15, 12:25 UTC | May 15, 13:40 UTC | 1h 15m |
| 2026-05-15 | HAN → TPE | May 15, 08:40 UTC | May 15, 10:25 UTC | 1h 45m |
| 2026-05-11 | HPH → ICN | May 11, 20:20 UTC | May 11, 21:00 UTC | 40m |
| 2026-05-10 | - | May 10, 06:45 UTC | May 10, 06:55 UTC | 10m |
| 2026-05-09 | ICN → HPH | May 9, 22:30 UTC | May 10, 01:24 UTC | 2h 55m |
| 2026-05-09 | HPH → ICN | May 9, 20:10 UTC | May 9, 20:49 UTC | 40m |
| 2026-05-08 | HPH → ICN | May 8, 22:15 UTC | May 9, 20:49 UTC | 22h 35m |
| 2026-05-08 | HPH → ICN | May 8, 20:10 UTC | May 8, 20:50 UTC | 40m |
| 2026-05-05 | CAN → HAN | May 5, 18:50 UTC | May 5, 19:05 UTC | 15m |
| 2026-05-04 | BKK → HAN | May 4, 07:20 UTC | May 4, 07:40 UTC | 20m |
| 2026-05-03 | HAN → BKK | May 3, 19:00 UTC | May 4, 06:00 UTC | 11h 0m |
| 2026-05-03 | - | May 3, 10:40 UTC | May 3, 11:45 UTC | 1h 5m |
| 2026-05-02 | - | May 2, 18:30 UTC | May 3, 08:45 UTC | 14h 14m |
| 2026-05-02 | RMQ → HAN | May 2, 10:15 UTC | May 2, 11:20 UTC | 1h 5m |
| 2026-05-02 | HAN → RMQ | May 2, 07:40 UTC | May 2, 08:45 UTC | 1h 5m |
| 2026-05-02 | FUK → HAN | May 2, 00:20 UTC | May 2, 00:30 UTC | 10m |
| 2026-04-30 | TPE → SGN | Apr 30, 13:05 UTC | Apr 30, 14:10 UTC | 1h 5m |
| 2026-04-30 | SGN → TPE | Apr 30, 10:25 UTC | Apr 30, 11:20 UTC | 55m |
| 2026-04-26 | - | Apr 26, 20:20 UTC | Apr 26, 20:50 UTC | 30m |
| 2026-04-26 | DAD → MNL | Apr 26, 17:40 UTC | Apr 26, 18:25 UTC | 45m |
| 2026-04-26 | SIN → SGN | Apr 26, 11:35 UTC | Apr 26, 11:45 UTC | 10m |
| 2026-04-26 | SIN → SGN | Apr 26, 10:20 UTC | Apr 26, 10:35 UTC | 15m |
| 2026-04-25 | PUS → DAD | Apr 25, 19:10 UTC | Apr 26, 09:10 UTC | 14h 0m |
Specifications
| Registration | VN-A683 |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 88803E · 42100076 (octal) |
Looking for transponder-level data? View the Mode-S 88803E page for country allocation, callsign history, and ADS-B signal details.
VN-A683 frequently asked
What type of aircraft is VN-A683?
VN-A683 is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for VN-A683?
VN-A683 broadcasts on Mode-S (ICAO 24-bit) address 88803E (octal 42100076). View the transponder page.
What route does VN-A683 typically fly?
VN-A683 most frequently flies between DAD and MNL based on observed flights.
Where is VN-A683 right now?
VN-A683 is not currently being tracked; last seen 5h ago.