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