Not currently tracked · last seen Jul 26, 16:20 UTC
- Flights observed
- 255 showing last 50
- Avg flight time
- 35m
- Typical route
- DAD → HAN
- Last seen
- Jul 26, 16:20 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | HAN → SGN | Jul 26, 16:10 UTC | Jul 26, 16:20 UTC | 10m |
| 2026-07-26 | DAD → HAN | Jul 26, 14:40 UTC | Jul 26, 14:55 UTC | 15m |
| 2026-07-26 | HAN → DAD | Jul 26, 12:10 UTC | Jul 26, 12:25 UTC | 15m |
| 2026-07-26 | VCA → HAN | Jul 26, 10:25 UTC | Jul 26, 10:40 UTC | 15m |
| 2026-07-26 | HAN → VCA | Jul 26, 06:05 UTC | Jul 26, 06:25 UTC | 20m |
| 2026-07-26 | DAD → HAN | Jul 26, 04:00 UTC | Jul 26, 04:10 UTC | 10m |
| 2026-07-26 | HAN → DAD | Jul 26, 01:35 UTC | Jul 26, 01:50 UTC | 15m |
| 2026-07-25 | SGN → HAN | Jul 25, 23:35 UTC | Jul 25, 23:55 UTC | 20m |
| 2026-07-25 | DAD → HAN | Jul 25, 14:00 UTC | Jul 25, 14:10 UTC | 10m |
| 2026-07-25 | HAN → DAD | Jul 25, 11:35 UTC | Jul 25, 11:50 UTC | 15m |
| 2026-07-25 | DAD → HAN | Jul 25, 04:45 UTC | Jul 25, 05:00 UTC | 15m |
| 2026-07-25 | HAN → DAD | Jul 25, 02:20 UTC | Jul 25, 02:35 UTC | 15m |
| 2026-07-24 | SGN → HAN | Jul 24, 23:35 UTC | Jul 25, 00:00 UTC | 25m |
| 2026-07-24 | - | Jul 24, 17:15 UTC | Jul 24, 17:30 UTC | 15m |
| 2026-07-24 | - | Jul 24, 16:05 UTC | Jul 24, 16:15 UTC | 10m |
| 2026-07-23 | - | Jul 23, 16:55 UTC | Jul 23, 17:05 UTC | 10m |
| 2026-07-23 | - | Jul 23, 15:40 UTC | Jul 23, 15:50 UTC | 10m |
| 2026-07-22 | - | Jul 22, 16:50 UTC | Jul 22, 17:00 UTC | 10m |
| 2026-07-22 | DAD → HAN | Jul 22, 14:15 UTC | Jul 22, 15:35 UTC | 1h 20m |
| 2026-07-22 | - | Jul 22, 12:00 UTC | Jul 22, 12:10 UTC | 10m |
| 2026-07-22 | DAD → HAN | Jul 22, 04:00 UTC | Jul 22, 04:20 UTC | 20m |
| 2026-07-22 | HAN → DAD | Jul 22, 01:20 UTC | Jul 22, 01:30 UTC | 10m |
| 2026-07-21 | SGN → HAN | Jul 21, 23:30 UTC | Jul 21, 23:50 UTC | 20m |
| 2026-07-21 | - | Jul 21, 16:10 UTC | Jul 21, 16:25 UTC | 15m |
| 2026-07-21 | DAD → HAN | Jul 21, 14:10 UTC | Jul 21, 14:20 UTC | 10m |
| 2026-07-21 | - | Jul 21, 11:30 UTC | Jul 21, 11:40 UTC | 10m |
| 2026-07-21 | VCA → HAN | Jul 21, 10:05 UTC | Jul 21, 10:15 UTC | 10m |
| 2026-07-21 | HAN → VCA | Jul 21, 05:50 UTC | Jul 21, 06:05 UTC | 15m |
| 2026-07-21 | DAD → HAN | Jul 21, 04:20 UTC | Jul 21, 04:30 UTC | 10m |
| 2026-07-21 | HAN → DAD | Jul 21, 01:40 UTC | Jul 21, 01:50 UTC | 10m |
| 2026-07-20 | - | Jul 20, 16:05 UTC | Jul 20, 23:35 UTC | 7h 30m |
| 2026-07-20 | DAD → HAN | Jul 20, 14:30 UTC | Jul 20, 14:45 UTC | 15m |
| 2026-07-20 | - | Jul 20, 12:00 UTC | Jul 20, 12:15 UTC | 15m |
| 2026-07-20 | VCA → HAN | Jul 20, 10:25 UTC | Jul 20, 10:35 UTC | 10m |
| 2026-07-20 | HAN → VCA | Jul 20, 06:05 UTC | Jul 20, 06:15 UTC | 10m |
| 2026-07-20 | DAD → HAN | Jul 20, 01:30 UTC | Jul 20, 04:20 UTC | 2h 50m |
| 2026-07-19 | SGN → HAN | Jul 19, 23:40 UTC | Jul 19, 23:50 UTC | 10m |
| 2026-07-19 | - | Jul 19, 17:05 UTC | Jul 19, 17:20 UTC | 15m |
| 2026-07-19 | DAD → HAN | Jul 19, 15:30 UTC | Jul 19, 15:45 UTC | 15m |
| 2026-07-19 | - | Jul 19, 13:10 UTC | Jul 19, 13:20 UTC | 10m |
| 2026-07-19 | HAN → VCA | Jul 19, 06:50 UTC | Jul 19, 11:00 UTC | 4h 10m |
| 2026-07-19 | DAD → HAN | Jul 19, 01:25 UTC | Jul 19, 04:35 UTC | 3h 10m |
| 2026-07-18 | - | Jul 18, 16:05 UTC | Jul 18, 16:20 UTC | 15m |
| 2026-07-18 | - | Jul 18, 11:40 UTC | Jul 18, 11:55 UTC | 15m |
| 2026-07-18 | - | Jul 18, 10:20 UTC | Jul 18, 10:35 UTC | 15m |
| 2026-07-18 | - | Jul 18, 06:25 UTC | Jul 18, 06:35 UTC | 10m |
| 2026-07-18 | DAD → HAN | Jul 18, 04:25 UTC | Jul 18, 04:50 UTC | 25m |
| 2026-07-18 | - | Jul 18, 01:45 UTC | Jul 18, 01:54 UTC | 10m |
| 2026-07-17 | SGN → HAN | Jul 17, 23:35 UTC | Jul 17, 23:45 UTC | 10m |
| 2026-07-17 | - | Jul 17, 16:15 UTC | Jul 17, 16:24 UTC | 10m |
Specifications
| Registration | VN-A363 |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 888061 · 42100141 (octal) |
Looking for transponder-level data? View the Mode-S 888061 page for country allocation, callsign history, and ADS-B signal details.
VN-A363 frequently asked
What type of aircraft is VN-A363?
VN-A363 is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for VN-A363?
VN-A363 broadcasts on Mode-S (ICAO 24-bit) address 888061 (octal 42100141). View the transponder page.
What route does VN-A363 typically fly?
VN-A363 most frequently flies between DAD and HAN based on observed flights.
Where is VN-A363 right now?
VN-A363 is not currently being tracked; last seen Jul 26, 16:20 UTC.