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