Not currently tracked · last seen Jul 26, 22:10 UTC
- Flights observed
- 157 showing last 50
- Avg flight time
- 11h 20m
- Typical route
- ORY → ORY
- Last seen
- Jul 26, 22:10 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | ORY → TNR | Jul 26, 19:20 UTC | Jul 26, 22:10 UTC | 2h 50m |
| 2026-07-26 | MRU → ORY | Jul 26, 01:10 UTC | Jul 26, 04:40 UTC | 3h 30m |
| 2026-07-24 | ORY → MRU | Jul 24, 19:40 UTC | Jul 24, 22:25 UTC | 2h 45m |
| 2026-07-24 | RUN → ORY | Jul 24, 12:45 UTC | Jul 24, 16:55 UTC | 4h 10m |
| 2026-07-23 | RUN → ORY | Jul 23, 17:05 UTC | Jul 24, 16:55 UTC | 23h 50m |
| 2026-07-23 | ORY → RUN | Jul 23, 16:00 UTC | Jul 24, 15:00 UTC | 23h 0m |
| 2026-07-23 | FDF → ORY | Jul 23, 04:25 UTC | Jul 23, 06:20 UTC | 1h 55m |
| 2026-07-22 | - | Jul 22, 22:30 UTC | Jul 22, 22:45 UTC | 15m |
| 2026-07-22 | - | Jul 22, 18:40 UTC | Jul 22, 19:00 UTC | 20m |
| 2026-07-22 | - | Jul 22, 11:10 UTC | Jul 22, 12:35 UTC | 1h 25m |
| 2026-07-21 | PTP → ORY | Jul 21, 11:05 UTC | Jul 22, 05:25 UTC | 18h 20m |
| 2026-07-20 | RUN → ORY | Jul 20, 01:45 UTC | Jul 20, 05:05 UTC | 3h 20m |
| 2026-07-18 | ORY → RUN | Jul 18, 20:10 UTC | Jul 18, 23:00 UTC | 2h 50m |
| 2026-07-18 | - | Jul 18, 12:35 UTC | Jul 18, 16:30 UTC | 3h 55m |
| 2026-07-17 | - | Jul 17, 17:05 UTC | Jul 18, 16:30 UTC | 23h 26m |
| 2026-07-17 | - | Jul 17, 16:00 UTC | Jul 18, 15:00 UTC | 23h 1m |
| 2026-07-17 | RUN → ORY | Jul 17, 00:14 UTC | Jul 17, 04:10 UTC | 3h 55m |
| 2026-07-15 | - | Jul 15, 19:55 UTC | Jul 15, 23:25 UTC | 3h 30m |
| 2026-07-15 | - | Jul 15, 12:35 UTC | Jul 15, 17:05 UTC | 4h 30m |
| 2026-07-14 | - | Jul 14, 17:05 UTC | Jul 15, 17:00 UTC | 23h 54m |
| 2026-07-14 | - | Jul 14, 16:15 UTC | Jul 15, 15:00 UTC | 22h 44m |
| 2026-07-13 | ORY → ORY | Jul 13, 11:20 UTC | Jul 14, 06:05 UTC | 18h 45m |
| 2026-07-12 | - | Jul 12, 16:40 UTC | Jul 12, 18:15 UTC | 1h 35m |
| 2026-07-11 | - | Jul 11, 09:40 UTC | Jul 11, 10:45 UTC | 1h 5m |
| 2026-07-09 | ORY → ORY | Jul 9, 16:25 UTC | Jul 10, 10:55 UTC | 18h 30m |
| 2026-07-08 | - | Jul 8, 12:40 UTC | Jul 8, 16:40 UTC | 4h 0m |
| 2026-07-07 | - | Jul 7, 19:05 UTC | Jul 8, 16:40 UTC | 21h 35m |
| 2026-07-07 | - | Jul 7, 17:05 UTC | Jul 8, 16:40 UTC | 23h 35m |
| 2026-07-07 | - | Jul 7, 15:35 UTC | Jul 8, 15:00 UTC | 23h 25m |
| 2026-07-06 | - | Jul 6, 15:05 UTC | Jul 7, 09:30 UTC | 18h 25m |
| 2026-07-06 | ORY → ORY | Jul 6, 14:45 UTC | Jul 7, 09:30 UTC | 18h 45m |
| 2026-07-06 | - | Jul 6, 06:25 UTC | Jul 6, 08:20 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 00:10 UTC | Jul 6, 00:20 UTC | 10m |
| 2026-07-05 | - | Jul 5, 13:05 UTC | Jul 5, 14:30 UTC | 1h 25m |
| 2026-07-04 | - | Jul 4, 15:05 UTC | Jul 5, 09:45 UTC | 18h 40m |
| 2026-07-04 | ORY → ORY | Jul 4, 14:45 UTC | Jul 5, 09:45 UTC | 19h 0m |
| 2026-07-03 | - | Jul 3, 11:05 UTC | Jul 4, 06:05 UTC | 19h 0m |
| 2026-07-03 | ORY → ORY | Jul 3, 10:55 UTC | Jul 4, 06:05 UTC | 19h 10m |
| 2026-07-03 | - | Jul 3, 00:55 UTC | Jul 3, 04:05 UTC | 3h 10m |
| 2026-07-01 | - | Jul 1, 19:40 UTC | Jul 1, 23:10 UTC | 3h 30m |
| 2026-07-01 | - | Jul 1, 12:25 UTC | Jul 1, 16:30 UTC | 4h 5m |
| 2026-06-30 | - | Jun 30, 17:05 UTC | Jul 1, 16:30 UTC | 23h 25m |
| 2026-06-30 | - | Jun 30, 15:45 UTC | Jul 1, 15:00 UTC | 23h 15m |
| 2026-06-30 | - | Jun 30, 00:30 UTC | Jun 30, 04:30 UTC | 4h 1m |
| 2026-06-28 | - | Jun 28, 20:34 UTC | Jun 28, 23:39 UTC | 3h 5m |
| 2026-06-28 | - | Jun 28, 00:25 UTC | Jun 28, 04:20 UTC | 3h 55m |
| 2026-06-26 | - | Jun 26, 19:39 UTC | Jun 26, 23:15 UTC | 3h 35m |
| 2026-06-25 | - | Jun 25, 19:24 UTC | Jun 26, 16:49 UTC | 21h 25m |
| 2026-06-25 | - | Jun 25, 17:05 UTC | Jun 26, 16:49 UTC | 23h 45m |
| 2026-06-25 | - | Jun 25, 15:50 UTC | Jun 26, 14:59 UTC | 23h 10m |
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 ORY and ORY based on observed flights.
Where is F-HETE right now?
F-HETE is not currently being tracked; last seen Jul 26, 22:10 UTC.