Airborne now · flying as TVF216P at 1,100 ft
- Flights observed
- 362 showing last 50
- Avg flight time
- 2h 49m
- Typical route
- JMK → ORY
- Last seen
- 1h ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 05:35 UTC | Jul 14, 06:30 UTC | 55m |
| 2026-07-13 | - | Jul 13, 18:15 UTC | Jul 13, 20:40 UTC | 2h 25m |
| 2026-07-13 | - | Jul 13, 14:30 UTC | Jul 13, 16:30 UTC | 2h 0m |
| 2026-07-13 | - | Jul 13, 10:10 UTC | Jul 13, 13:05 UTC | 2h 55m |
| 2026-07-12 | RNS → ORY | Jul 12, 17:25 UTC | Jul 13, 08:15 UTC | 14h 50m |
| 2026-07-12 | - | Jul 12, 09:35 UTC | Jul 12, 15:50 UTC | 6h 15m |
| 2026-07-11 | - | Jul 11, 17:20 UTC | Jul 12, 07:55 UTC | 14h 35m |
| 2026-07-11 | ORY → ORY | Jul 11, 09:15 UTC | Jul 11, 16:00 UTC | 6h 45m |
| 2026-07-11 | - | Jul 11, 05:10 UTC | Jul 11, 07:20 UTC | 2h 10m |
| 2026-07-10 | ORY → FAO | Jul 10, 19:35 UTC | Jul 10, 21:50 UTC | 2h 15m |
| 2026-07-10 | JMK → ORY | Jul 10, 15:00 UTC | Jul 10, 18:10 UTC | 3h 10m |
| 2026-07-10 | ORY → JMK | Jul 10, 11:00 UTC | Jul 10, 14:00 UTC | 3h 0m |
| 2026-07-10 | TLS → ORY | Jul 10, 08:50 UTC | Jul 10, 09:50 UTC | 1h 0m |
| 2026-07-10 | ORY → TLS | Jul 10, 06:50 UTC | Jul 10, 07:50 UTC | 1h 0m |
| 2026-07-10 | MRS → ORY | Jul 10, 04:40 UTC | Jul 10, 05:45 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 20:35 UTC | Jul 9, 21:35 UTC | 1h 0m |
| 2026-07-09 | TLS → ORY | Jul 9, 18:45 UTC | Jul 9, 19:35 UTC | 50m |
| 2026-07-09 | ORY → TLS | Jul 9, 14:40 UTC | Jul 9, 15:35 UTC | 55m |
| 2026-07-09 | - | Jul 9, 11:05 UTC | Jul 9, 12:05 UTC | 1h 0m |
| 2026-07-09 | ORY → MXP | Jul 9, 08:30 UTC | Jul 9, 09:35 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 04:55 UTC | Jul 9, 06:45 UTC | 1h 50m |
| 2026-07-08 | - | Jul 8, 20:05 UTC | Jul 8, 21:55 UTC | 1h 50m |
| 2026-07-08 | - | Jul 8, 15:50 UTC | Jul 8, 18:05 UTC | 2h 15m |
| 2026-07-08 | - | Jul 8, 12:40 UTC | Jul 8, 14:55 UTC | 2h 15m |
| 2026-07-08 | - | Jul 8, 08:10 UTC | Jul 8, 10:35 UTC | 2h 25m |
| 2026-07-08 | - | Jul 8, 05:10 UTC | Jul 8, 06:55 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 19:35 UTC | Jul 7, 21:20 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 17:10 UTC | Jul 7, 18:35 UTC | 1h 25m |
| 2026-07-07 | - | Jul 7, 14:20 UTC | Jul 7, 15:45 UTC | 1h 25m |
| 2026-07-07 | - | Jul 7, 11:30 UTC | Jul 7, 13:10 UTC | 1h 40m |
| 2026-07-07 | - | Jul 7, 07:10 UTC | Jul 7, 08:55 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 04:25 UTC | Jul 7, 05:35 UTC | 1h 10m |
| 2026-07-06 | - | Jul 6, 19:00 UTC | Jul 6, 21:50 UTC | 2h 50m |
| 2026-07-06 | - | Jul 6, 14:50 UTC | Jul 6, 17:20 UTC | 2h 30m |
| 2026-07-06 | - | Jul 6, 09:05 UTC | Jul 6, 12:35 UTC | 3h 30m |
| 2026-07-06 | - | Jul 6, 04:35 UTC | Jul 6, 07:30 UTC | 2h 55m |
| 2026-07-05 | - | Jul 5, 15:20 UTC | Jul 5, 21:35 UTC | 6h 15m |
| 2026-07-05 | - | Jul 5, 09:55 UTC | Jul 5, 12:55 UTC | 3h 0m |
| 2026-07-05 | - | Jul 5, 06:05 UTC | Jul 5, 08:25 UTC | 2h 20m |
| 2026-07-04 | ORY → LYS | Jul 4, 12:55 UTC | Jul 4, 19:45 UTC | 6h 50m |
| 2026-07-04 | - | Jul 4, 08:55 UTC | Jul 4, 11:15 UTC | 2h 20m |
| 2026-07-04 | - | Jul 4, 05:35 UTC | Jul 4, 07:40 UTC | 2h 5m |
| 2026-07-03 | - | Jul 3, 19:10 UTC | Jul 3, 20:40 UTC | 1h 30m |
| 2026-07-03 | - | Jul 3, 16:45 UTC | Jul 3, 18:00 UTC | 1h 15m |
| 2026-07-03 | JMK → ORY | Jul 3, 11:55 UTC | Jul 3, 15:00 UTC | 3h 5m |
| 2026-07-03 | ORY → JMK | Jul 3, 07:35 UTC | Jul 3, 10:30 UTC | 2h 55m |
| 2026-07-02 | - | Jul 2, 18:25 UTC | Jul 2, 20:35 UTC | 2h 10m |
| 2026-07-02 | - | Jul 2, 15:30 UTC | Jul 2, 16:55 UTC | 1h 25m |
| 2026-07-02 | SVQ → NTE | Jul 2, 12:20 UTC | Jul 2, 14:00 UTC | 1h 40m |
| 2026-07-02 | - | Jul 2, 09:35 UTC | Jul 2, 11:10 UTC | 1h 35m |
Specifications
| Registration | F-HTVC |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 39CEA2 · 16347242 (octal) |
Looking for transponder-level data? View the Mode-S 39CEA2 page for country allocation, callsign history, and ADS-B signal details.
F-HTVC frequently asked
What type of aircraft is F-HTVC?
F-HTVC is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for F-HTVC?
F-HTVC broadcasts on Mode-S (ICAO 24-bit) address 39CEA2 (octal 16347242). View the transponder page.
What route does F-HTVC typically fly?
F-HTVC most frequently flies between JMK and ORY based on observed flights.
Where is F-HTVC right now?
F-HTVC is currently airborne flying as TVF216P. Live position is shown on the map above.