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