Not currently tracked · last seen 8h ago
- Flights observed
- 142 showing last 50
- Avg flight time
- 58m
- Typical route
- ORY → BVE
- Last seen
- 8h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | ORY → BVE | May 29, 18:00 UTC | May 29, 18:50 UTC | 50m |
| 2026-05-29 | BVE → ORY | May 29, 16:05 UTC | May 29, 17:10 UTC | 1h 5m |
| 2026-05-29 | ORY → BVE | May 29, 07:15 UTC | May 29, 08:05 UTC | 50m |
| 2026-05-29 | BVE → ORY | May 29, 05:10 UTC | May 29, 06:05 UTC | 55m |
| 2026-05-28 | ORY → BVE | May 28, 18:05 UTC | May 28, 18:55 UTC | 50m |
| 2026-05-28 | BVE → ORY | May 28, 16:05 UTC | May 28, 17:00 UTC | 55m |
| 2026-05-27 | ORY → BVE | May 27, 18:00 UTC | May 27, 18:55 UTC | 55m |
| 2026-05-27 | BVE → ORY | May 27, 16:05 UTC | May 27, 17:00 UTC | 55m |
| 2026-05-27 | ORY → BVE | May 27, 07:15 UTC | May 27, 08:05 UTC | 50m |
| 2026-05-27 | BVE → ORY | May 27, 05:09 UTC | May 27, 05:59 UTC | 50m |
| 2026-05-26 | ORY → BVE | May 26, 17:44 UTC | May 26, 18:40 UTC | 55m |
| 2026-05-26 | BVE → ORY | May 26, 15:49 UTC | May 26, 16:55 UTC | 1h 5m |
| 2026-05-26 | ORY → BVE | May 26, 06:59 UTC | May 26, 07:59 UTC | 1h 0m |
| 2026-05-26 | BVE → ORY | May 26, 05:10 UTC | May 26, 06:04 UTC | 55m |
| 2026-05-25 | ORY → BVE | May 25, 17:55 UTC | May 25, 18:50 UTC | 55m |
| 2026-05-25 | BVE → ORY | May 25, 15:55 UTC | May 25, 16:50 UTC | 55m |
| 2026-05-22 | ORY → BVE | May 22, 18:00 UTC | May 22, 18:55 UTC | 55m |
| 2026-05-22 | BVE → ORY | May 22, 16:00 UTC | May 22, 16:55 UTC | 55m |
| 2026-05-22 | ORY → BVE | May 22, 07:00 UTC | May 22, 07:55 UTC | 55m |
| 2026-05-22 | BVE → ORY | May 22, 05:05 UTC | May 22, 06:00 UTC | 55m |
| 2026-05-21 | ORY → BVE | May 21, 17:55 UTC | May 21, 18:50 UTC | 55m |
| 2026-05-21 | BVE → ORY | May 21, 15:55 UTC | May 21, 16:50 UTC | 55m |
| 2026-05-20 | ORY → BVE | May 20, 18:05 UTC | May 20, 18:55 UTC | 50m |
| 2026-05-20 | BVE → ORY | May 20, 16:05 UTC | May 20, 17:10 UTC | 1h 5m |
| 2026-05-20 | ORY → BVE | May 20, 07:15 UTC | May 20, 08:05 UTC | 50m |
| 2026-05-20 | BVE → ORY | May 20, 05:15 UTC | May 20, 06:25 UTC | 1h 10m |
| 2026-05-19 | ORY → BVE | May 19, 18:00 UTC | May 19, 18:50 UTC | 50m |
| 2026-05-19 | BVE → ORY | May 19, 16:00 UTC | May 19, 17:10 UTC | 1h 10m |
| 2026-05-19 | ORY → BVE | May 19, 07:00 UTC | May 19, 07:50 UTC | 50m |
| 2026-05-19 | BVE → ORY | May 19, 05:10 UTC | May 19, 06:10 UTC | 1h 0m |
| 2026-05-18 | ORY → BVE | May 18, 17:50 UTC | May 18, 18:40 UTC | 49m |
| 2026-05-18 | BVE → ORY | May 18, 16:00 UTC | May 18, 17:05 UTC | 1h 5m |
| 2026-05-18 | ORY → BVE | May 18, 07:05 UTC | May 18, 08:01 UTC | 55m |
| 2026-05-18 | BVE → ORY | May 18, 05:05 UTC | May 18, 06:20 UTC | 1h 15m |
| 2026-05-17 | ORY → BVE | May 17, 18:05 UTC | May 17, 18:55 UTC | 50m |
| 2026-05-17 | BVE → ORY | May 17, 16:05 UTC | May 17, 17:10 UTC | 1h 5m |
| 2026-05-17 | EBU → LIG | May 17, 11:25 UTC | May 17, 12:05 UTC | 40m |
| 2026-05-16 | CWL → VNE | May 16, 18:25 UTC | May 16, 19:45 UTC | 1h 20m |
| 2026-05-15 | - | May 15, 13:00 UTC | May 15, 14:25 UTC | 1h 25m |
| 2026-05-15 | - | May 15, 11:30 UTC | May 15, 12:05 UTC | 35m |
| 2026-05-14 | ORY → BVE | May 14, 07:15 UTC | May 14, 08:05 UTC | 50m |
| 2026-05-14 | BVE → ORY | May 14, 05:05 UTC | May 14, 06:10 UTC | 1h 5m |
| 2026-05-13 | ORY → BVE | May 13, 18:30 UTC | May 13, 19:25 UTC | 55m |
| 2026-05-13 | BVE → ORY | May 13, 16:10 UTC | May 13, 17:20 UTC | 1h 10m |
| 2026-05-13 | ORY → BVE | May 13, 07:05 UTC | May 13, 08:00 UTC | 55m |
| 2026-05-13 | BVE → ORY | May 13, 05:05 UTC | May 13, 06:15 UTC | 1h 10m |
| 2026-05-12 | ORY → BVE | May 12, 17:50 UTC | May 12, 18:45 UTC | 55m |
| 2026-05-12 | BVE → ORY | May 12, 16:00 UTC | May 12, 17:10 UTC | 1h 10m |
| 2026-05-12 | ORY → BVE | May 12, 07:15 UTC | May 12, 08:05 UTC | 50m |
| 2026-05-12 | BVE → ORY | May 12, 05:05 UTC | May 12, 06:20 UTC | 1h 15m |
Specifications
| Registration | F-HBCM |
| Aircraft type | ATR-72-600 (AT76) |
| Mode-S code | 39844C · 16302114 (octal) |
Looking for transponder-level data? View the Mode-S 39844C page for country allocation, callsign history, and ADS-B signal details.
F-HBCM frequently asked
What type of aircraft is F-HBCM?
F-HBCM is a ATR-72-600 (ICAO type code AT76).
What is the Mode-S transponder code for F-HBCM?
F-HBCM broadcasts on Mode-S (ICAO 24-bit) address 39844C (octal 16302114). View the transponder page.
What route does F-HBCM typically fly?
F-HBCM most frequently flies between ORY and BVE based on observed flights.
Where is F-HBCM right now?
F-HBCM is not currently being tracked; last seen 8h ago.