Not currently tracked · last seen 3d ago
- Flights observed
- 75 showing last 50
- Avg flight time
- 6h 50m
- Typical route
- BON → AMS
- Last seen
- 3d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-31 | - | May 31, 12:50 UTC | Jun 1, 03:55 UTC | 15h 5m |
| 2026-05-31 | BON → AMS | May 31, 08:25 UTC | May 31, 09:50 UTC | 1h 25m |
| 2026-05-30 | BON → AMS | May 30, 23:30 UTC | May 30, 23:45 UTC | 15m |
| 2026-05-30 | BON → AMS | May 30, 22:00 UTC | May 30, 22:15 UTC | 15m |
| 2026-05-30 | BON → AMS | May 30, 12:25 UTC | May 30, 21:20 UTC | 8h 55m |
| 2026-05-30 | YEG → AMS | May 30, 01:05 UTC | May 30, 07:45 UTC | 6h 40m |
| 2026-05-29 | YEG → AMS | May 29, 23:30 UTC | May 29, 23:40 UTC | 10m |
| 2026-05-29 | AMS → SFO | May 29, 21:30 UTC | May 29, 21:45 UTC | 15m |
| 2026-05-29 | AMS → SFO | May 29, 13:15 UTC | May 29, 19:55 UTC | 6h 40m |
| 2026-05-29 | YEG → AMS | May 29, 02:50 UTC | May 29, 07:55 UTC | 5h 5m |
| 2026-05-28 | YEG → AMS | May 28, 23:55 UTC | May 29, 00:05 UTC | 10m |
| 2026-05-28 | AMS → SFO | May 28, 21:50 UTC | May 28, 22:00 UTC | 10m |
| 2026-05-28 | AMS → SFO | May 28, 13:40 UTC | May 28, 20:05 UTC | 6h 25m |
| 2026-05-27 | YUL → AMS | May 27, 23:10 UTC | May 28, 05:45 UTC | 6h 35m |
| 2026-05-27 | AMS → YUL | May 27, 13:55 UTC | May 27, 20:50 UTC | 6h 55m |
| 2026-05-27 | BON → AMS | May 27, 08:40 UTC | May 27, 10:25 UTC | 1h 45m |
| 2026-05-26 | BON → AMS | May 26, 23:10 UTC | May 26, 23:19 UTC | 10m |
| 2026-05-26 | BON → AMS | May 26, 21:29 UTC | May 26, 21:44 UTC | 15m |
| 2026-05-26 | BON → AMS | May 26, 12:05 UTC | May 26, 20:54 UTC | 8h 50m |
| 2026-05-25 | POS → AMS | May 25, 04:55 UTC | May 25, 06:35 UTC | 1h 40m |
| 2026-05-24 | POS → AMS | May 24, 09:50 UTC | May 25, 06:35 UTC | 20h 45m |
| 2026-05-24 | POS → AMS | May 24, 09:10 UTC | May 25, 06:35 UTC | 21h 25m |
| 2026-05-22 | LOS → AMS | May 22, 13:05 UTC | May 23, 03:45 UTC | 14h 39m |
| 2026-05-21 | YEG → AMS | May 21, 23:45 UTC | May 22, 07:55 UTC | 8h 10m |
| 2026-05-21 | AMS → SFO | May 21, 21:35 UTC | May 21, 21:50 UTC | 15m |
| 2026-05-21 | AMS → SFO | May 21, 13:25 UTC | May 21, 20:10 UTC | 6h 45m |
| 2026-05-21 | BON → AMS | May 21, 02:20 UTC | May 21, 10:20 UTC | 8h 0m |
| 2026-05-20 | BON → AMS | May 20, 23:35 UTC | May 20, 23:50 UTC | 15m |
| 2026-05-20 | BON → AMS | May 20, 21:45 UTC | May 20, 22:00 UTC | 15m |
| 2026-05-20 | BON → AMS | May 20, 12:05 UTC | May 20, 21:10 UTC | 9h 5m |
| 2026-05-19 | YUL → AMS | May 19, 23:25 UTC | May 20, 05:35 UTC | 6h 11m |
| 2026-05-19 | AMS → YUL | May 19, 13:45 UTC | May 19, 20:45 UTC | 7h 0m |
| 2026-05-19 | BON → AMS | May 19, 08:25 UTC | May 19, 09:45 UTC | 1h 20m |
| 2026-05-18 | BON → AMS | May 18, 23:25 UTC | May 18, 23:40 UTC | 15m |
| 2026-05-18 | BON → AMS | May 18, 21:45 UTC | May 18, 22:00 UTC | 15m |
| 2026-05-18 | BON → AMS | May 18, 12:10 UTC | May 18, 21:10 UTC | 8h 59m |
| 2026-05-18 | AMS → CHS | May 18, 02:05 UTC | May 18, 09:10 UTC | 7h 5m |
| 2026-05-17 | AMS → YYZ | May 17, 16:10 UTC | May 17, 23:40 UTC | 7h 30m |
| 2026-05-17 | BON → AMS | May 17, 01:55 UTC | May 17, 10:00 UTC | 8h 5m |
| 2026-05-16 | BON → AMS | May 16, 23:30 UTC | May 16, 23:40 UTC | 10m |
| 2026-05-16 | BON → AMS | May 16, 21:30 UTC | May 16, 21:40 UTC | 10m |
| 2026-05-16 | BON → AMS | May 16, 12:05 UTC | May 16, 20:50 UTC | 8h 45m |
| 2026-05-13 | POS → AMS | May 13, 03:55 UTC | May 13, 06:25 UTC | 2h 30m |
| 2026-05-12 | POS → AMS | May 12, 09:50 UTC | May 13, 06:25 UTC | 20h 35m |
| 2026-05-12 | POS → AMS | May 12, 08:55 UTC | May 13, 06:25 UTC | 21h 30m |
| 2026-05-11 | - | May 11, 14:10 UTC | May 12, 04:45 UTC | 14h 36m |
| 2026-05-09 | CUR → AMS | May 9, 03:55 UTC | May 9, 06:10 UTC | 2h 15m |
| 2026-05-08 | CUR → AMS | May 8, 09:49 UTC | May 9, 06:10 UTC | 20h 20m |
| 2026-05-08 | CUR → AMS | May 8, 08:40 UTC | May 9, 06:10 UTC | 21h 30m |
| 2026-05-07 | - | May 7, 12:45 UTC | May 8, 03:49 UTC | 15h 4m |
Specifications
| Registration | PH-AOA |
| Aircraft type | AIRBUS A-330-200 (A332) |
| Mode-S code | 48440F · 22042017 (octal) |
Looking for transponder-level data? View the Mode-S 48440F page for country allocation, callsign history, and ADS-B signal details.
PH-AOA frequently asked
What type of aircraft is PH-AOA?
PH-AOA is a AIRBUS A-330-200 (ICAO type code A332).
What is the Mode-S transponder code for PH-AOA?
PH-AOA broadcasts on Mode-S (ICAO 24-bit) address 48440F (octal 22042017). View the transponder page.
What route does PH-AOA typically fly?
PH-AOA most frequently flies between BON and AMS based on observed flights.
Where is PH-AOA right now?
PH-AOA is not currently being tracked; last seen 3d ago.