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