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