Not currently tracked · last seen 1h ago
- Flights observed
- 365 showing last 50
- Avg flight time
- 2h 31m
- Typical route
- ORY → ORY
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 09:35 UTC | Jul 14, 11:15 UTC | 1h 40m |
| 2026-07-14 | - | Jul 14, 05:50 UTC | Jul 14, 08:10 UTC | 2h 20m |
| 2026-07-13 | - | Jul 13, 19:10 UTC | Jul 13, 20:50 UTC | 1h 40m |
| 2026-07-13 | - | Jul 13, 16:10 UTC | Jul 13, 18:10 UTC | 2h 0m |
| 2026-07-13 | - | Jul 13, 10:10 UTC | Jul 13, 14:25 UTC | 4h 15m |
| 2026-07-13 | - | Jul 13, 07:25 UTC | Jul 13, 08:40 UTC | 1h 15m |
| 2026-07-13 | - | Jul 13, 04:35 UTC | Jul 13, 06:01 UTC | 1h 25m |
| 2026-07-12 | - | Jul 12, 18:55 UTC | Jul 12, 22:10 UTC | 3h 15m |
| 2026-07-12 | - | Jul 12, 18:20 UTC | Jul 12, 18:45 UTC | 25m |
| 2026-07-12 | - | Jul 12, 13:25 UTC | Jul 12, 16:50 UTC | 3h 25m |
| 2026-07-12 | - | Jul 12, 08:30 UTC | Jul 12, 11:25 UTC | 2h 55m |
| 2026-07-12 | - | Jul 12, 04:15 UTC | Jul 12, 06:55 UTC | 2h 40m |
| 2026-07-11 | - | Jul 11, 12:45 UTC | Jul 11, 19:50 UTC | 7h 5m |
| 2026-07-11 | ORY → ORY | Jul 11, 04:20 UTC | Jul 11, 11:05 UTC | 6h 45m |
| 2026-07-10 | OPO → ORY | Jul 10, 19:05 UTC | Jul 10, 20:50 UTC | 1h 45m |
| 2026-07-10 | ORY → OPO | Jul 10, 16:00 UTC | Jul 10, 17:55 UTC | 1h 55m |
| 2026-07-10 | ORY → ORY | Jul 10, 07:35 UTC | Jul 10, 14:20 UTC | 6h 45m |
| 2026-07-10 | - | Jul 10, 04:15 UTC | Jul 10, 06:10 UTC | 1h 55m |
| 2026-07-09 | - | Jul 9, 18:25 UTC | Jul 9, 20:30 UTC | 2h 5m |
| 2026-07-09 | JMK → ORY | Jul 9, 13:00 UTC | Jul 9, 16:10 UTC | 3h 10m |
| 2026-07-09 | ORY → JMK | Jul 9, 08:45 UTC | Jul 9, 11:40 UTC | 2h 55m |
| 2026-07-09 | FAO → ORY | Jul 9, 05:15 UTC | Jul 9, 07:25 UTC | 2h 10m |
| 2026-07-08 | ORY → FAO | Jul 8, 19:25 UTC | Jul 8, 21:35 UTC | 2h 10m |
| 2026-07-08 | ORY → ORY | Jul 8, 05:50 UTC | Jul 8, 15:10 UTC | 9h 20m |
| 2026-07-07 | CMN → ORY | Jul 7, 17:40 UTC | Jul 7, 20:15 UTC | 2h 35m |
| 2026-07-07 | - | Jul 7, 13:40 UTC | Jul 7, 16:00 UTC | 2h 20m |
| 2026-07-07 | - | Jul 7, 08:25 UTC | Jul 7, 10:10 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 05:45 UTC | Jul 7, 07:20 UTC | 1h 35m |
| 2026-07-06 | - | Jul 6, 18:50 UTC | Jul 6, 20:15 UTC | 1h 25m |
| 2026-07-06 | ORY → PSA | Jul 6, 15:55 UTC | Jul 6, 17:20 UTC | 1h 25m |
| 2026-07-06 | FAO → ORY | Jul 6, 12:35 UTC | Jul 6, 14:45 UTC | 2h 10m |
| 2026-07-06 | ORY → FAO | Jul 6, 09:10 UTC | Jul 6, 11:20 UTC | 2h 10m |
| 2026-07-04 | MXP → ORY | Jul 4, 11:30 UTC | Jul 4, 12:30 UTC | 1h 0m |
| 2026-07-04 | ORY → MXP | Jul 4, 08:45 UTC | Jul 4, 09:50 UTC | 1h 5m |
| 2026-07-04 | - | Jul 4, 05:10 UTC | Jul 4, 07:10 UTC | 2h 0m |
| 2026-07-03 | - | Jul 3, 20:00 UTC | Jul 3, 21:00 UTC | 1h 0m |
| 2026-07-03 | - | Jul 3, 17:50 UTC | Jul 3, 19:00 UTC | 1h 10m |
| 2026-07-03 | - | Jul 3, 14:45 UTC | Jul 3, 16:25 UTC | 1h 40m |
| 2026-07-03 | MAD → ORY | Jul 3, 11:40 UTC | Jul 3, 13:15 UTC | 1h 35m |
| 2026-07-03 | ORY → MAD | Jul 3, 08:35 UTC | Jul 3, 10:05 UTC | 1h 30m |
| 2026-07-03 | LIS → ORY | Jul 3, 05:20 UTC | Jul 3, 07:25 UTC | 2h 5m |
| 2026-07-02 | ORY → LIS | Jul 2, 20:25 UTC | Jul 2, 22:30 UTC | 2h 5m |
| 2026-07-01 | ORY → ORY | Jul 1, 14:00 UTC | Jul 1, 19:15 UTC | 5h 15m |
| 2026-07-01 | FAO → ORY | Jul 1, 09:25 UTC | Jul 1, 11:50 UTC | 2h 25m |
| 2026-07-01 | ORY → FAO | Jul 1, 06:05 UTC | Jul 1, 08:10 UTC | 2h 5m |
| 2026-06-30 | - | Jun 30, 18:10 UTC | Jun 30, 20:10 UTC | 2h 0m |
| 2026-06-30 | - | Jun 30, 14:55 UTC | Jun 30, 16:40 UTC | 1h 45m |
| 2026-06-30 | - | Jun 30, 09:40 UTC | Jun 30, 11:45 UTC | 2h 5m |
| 2026-06-30 | - | Jun 30, 05:45 UTC | Jun 30, 07:55 UTC | 2h 10m |
| 2026-06-29 | - | Jun 29, 14:54 UTC | Jun 29, 16:55 UTC | 2h 0m |
Specifications
| Registration | F-HTVF |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 39CEA5 · 16347245 (octal) |
Looking for transponder-level data? View the Mode-S 39CEA5 page for country allocation, callsign history, and ADS-B signal details.
F-HTVF frequently asked
What type of aircraft is F-HTVF?
F-HTVF is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for F-HTVF?
F-HTVF broadcasts on Mode-S (ICAO 24-bit) address 39CEA5 (octal 16347245). View the transponder page.
What route does F-HTVF typically fly?
F-HTVF most frequently flies between ORY and ORY based on observed flights.
Where is F-HTVF right now?
F-HTVF is not currently being tracked; last seen 1h ago.