Not currently tracked · last seen Jul 26, 21:45 UTC
- Flights observed
- 123 showing last 50
- Avg flight time
- 12h 45m
- Typical route
- PTP → ORY
- Last seen
- Jul 26, 21:45 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | FDF → ORY | Jul 26, 21:35 UTC | Jul 26, 21:45 UTC | 10m |
| 2026-07-26 | ORY → FDF | Jul 26, 10:40 UTC | Jul 26, 18:45 UTC | 8h 5m |
| 2026-07-25 | PTP → ORY | Jul 25, 12:10 UTC | Jul 26, 07:15 UTC | 19h 6m |
| 2026-07-24 | PTP → ORY | Jul 24, 11:50 UTC | Jul 25, 06:45 UTC | 18h 55m |
| 2026-07-24 | PTP → ORY | Jul 24, 11:30 UTC | Jul 25, 06:45 UTC | 19h 15m |
| 2026-07-24 | PTP → ORY | Jul 24, 04:50 UTC | Jul 24, 06:50 UTC | 2h 0m |
| 2026-07-23 | ORY → PTP | Jul 23, 11:45 UTC | Jul 23, 12:55 UTC | 1h 10m |
| 2026-07-23 | RUN → RUN | Jul 23, 03:15 UTC | Jul 23, 07:05 UTC | 3h 50m |
| 2026-07-22 | RUN → RUN | Jul 22, 10:20 UTC | Jul 23, 07:05 UTC | 20h 45m |
| 2026-07-21 | PTP → ORY | Jul 21, 09:50 UTC | Jul 22, 04:15 UTC | 18h 25m |
| 2026-07-21 | PTP → ORY | Jul 21, 09:40 UTC | Jul 22, 04:15 UTC | 18h 35m |
| 2026-07-20 | PTP → ORY | Jul 20, 11:50 UTC | Jul 21, 06:30 UTC | 18h 39m |
| 2026-07-20 | FDF → ORY | Jul 20, 04:40 UTC | Jul 20, 06:05 UTC | 1h 25m |
| 2026-07-19 | - | Jul 19, 11:35 UTC | Jul 19, 12:50 UTC | 1h 15m |
| 2026-07-18 | PTP → ORY | Jul 18, 11:50 UTC | Jul 19, 07:40 UTC | 19h 50m |
| 2026-07-18 | ORY → ORY | Jul 18, 11:40 UTC | Jul 19, 07:40 UTC | 20h 0m |
| 2026-07-17 | ORY → ORY | Jul 17, 14:15 UTC | Jul 18, 08:20 UTC | 18h 6m |
| 2026-07-16 | PTP → ORY | Jul 16, 15:49 UTC | Jul 17, 10:50 UTC | 19h 0m |
| 2026-07-16 | PTP → ORY | Jul 16, 15:25 UTC | Jul 17, 10:50 UTC | 19h 25m |
| 2026-07-16 | - | Jul 16, 02:40 UTC | Jul 16, 07:10 UTC | 4h 30m |
| 2026-07-15 | - | Jul 15, 07:50 UTC | Jul 16, 07:10 UTC | 23h 20m |
| 2026-07-15 | - | Jul 15, 06:30 UTC | Jul 16, 05:45 UTC | 23h 15m |
| 2026-07-13 | ORY → ORY | Jul 13, 12:20 UTC | Jul 14, 07:10 UTC | 18h 50m |
| 2026-07-13 | - | Jul 13, 03:25 UTC | Jul 13, 05:20 UTC | 1h 55m |
| 2026-07-12 | - | Jul 12, 11:10 UTC | Jul 12, 12:15 UTC | 1h 5m |
| 2026-07-11 | - | Jul 11, 13:50 UTC | Jul 12, 07:55 UTC | 18h 5m |
| 2026-07-11 | YUL → ORY | Jul 11, 04:10 UTC | Jul 11, 10:20 UTC | 6h 10m |
| 2026-07-10 | ORY → YUL | Jul 10, 17:55 UTC | Jul 11, 00:50 UTC | 6h 55m |
| 2026-07-10 | SFO → ORY | Jul 10, 00:50 UTC | Jul 10, 10:55 UTC | 10h 5m |
| 2026-07-09 | ORY → SFO | Jul 9, 10:40 UTC | Jul 9, 21:15 UTC | 10h 35m |
| 2026-07-08 | - | Jul 8, 07:00 UTC | Jul 8, 10:00 UTC | 3h 0m |
| 2026-07-06 | ORY → ORY | Jul 6, 14:05 UTC | Jul 7, 08:10 UTC | 18h 5m |
| 2026-07-05 | ORY → ORY | Jul 5, 12:30 UTC | Jul 6, 06:50 UTC | 18h 20m |
| 2026-07-04 | ORY → ORY | Jul 4, 14:35 UTC | Jul 5, 08:40 UTC | 18h 5m |
| 2026-07-04 | - | Jul 4, 04:25 UTC | Jul 4, 06:00 UTC | 1h 35m |
| 2026-07-03 | - | Jul 3, 11:10 UTC | Jul 3, 12:40 UTC | 1h 30m |
| 2026-07-02 | - | Jul 2, 12:40 UTC | Jul 3, 07:05 UTC | 18h 25m |
| 2026-07-01 | EWR → ORY | Jul 1, 04:25 UTC | Jul 1, 11:10 UTC | 6h 45m |
| 2026-06-30 | MXP → EWR | Jun 30, 17:40 UTC | Jul 1, 02:00 UTC | 8h 20m |
| 2026-06-30 | ORY → MXP | Jun 30, 13:30 UTC | Jun 30, 14:35 UTC | 1h 5m |
| 2026-06-30 | - | Jun 30, 03:40 UTC | Jun 30, 06:45 UTC | 3h 5m |
| 2026-06-29 | - | Jun 29, 10:15 UTC | Jun 30, 06:45 UTC | 20h 31m |
| 2026-06-29 | - | Jun 29, 07:50 UTC | Jun 30, 06:45 UTC | 22h 56m |
| 2026-06-29 | - | Jun 29, 06:29 UTC | Jun 30, 05:45 UTC | 23h 15m |
| 2026-06-28 | - | Jun 28, 17:04 UTC | Jun 28, 21:20 UTC | 4h 15m |
| 2026-06-27 | - | Jun 27, 23:50 UTC | Jun 28, 21:20 UTC | 21h 30m |
| 2026-06-27 | - | Jun 27, 21:50 UTC | Jun 28, 21:20 UTC | 23h 30m |
| 2026-06-27 | - | Jun 27, 21:34 UTC | Jun 28, 19:44 UTC | 22h 10m |
| 2026-06-27 | RUN → ORY | Jun 27, 13:44 UTC | Jun 27, 17:55 UTC | 4h 10m |
| 2026-06-26 | RUN → ORY | Jun 26, 17:50 UTC | Jun 27, 17:44 UTC | 23h 55m |
Specifications
| Registration | F-HAJP |
| Aircraft type | AIRBUS A-350-1000 (A35K) |
| Mode-S code | 39812F · 16300457 (octal) |
Looking for transponder-level data? View the Mode-S 39812F page for country allocation, callsign history, and ADS-B signal details.
F-HAJP frequently asked
What type of aircraft is F-HAJP?
F-HAJP is a AIRBUS A-350-1000 (ICAO type code A35K).
What is the Mode-S transponder code for F-HAJP?
F-HAJP broadcasts on Mode-S (ICAO 24-bit) address 39812F (octal 16300457). View the transponder page.
What route does F-HAJP typically fly?
F-HAJP most frequently flies between PTP and ORY based on observed flights.
Where is F-HAJP right now?
F-HAJP is not currently being tracked; last seen Jul 26, 21:45 UTC.