Not currently tracked · last seen 2d ago
- Flights observed
- 56 showing last 50
- Avg flight time
- 1h 5m
- Typical route
- BTS → VOD
- Last seen
- 2d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-05 | BTS → AVN | Jun 5, 08:50 UTC | Jun 5, 10:40 UTC | 1h 50m |
| 2026-06-04 | - | Jun 4, 14:10 UTC | Jun 4, 14:45 UTC | 35m |
| 2026-06-04 | BTS → VOD | Jun 4, 06:05 UTC | Jun 4, 06:45 UTC | 40m |
| 2026-06-03 | - | Jun 3, 18:10 UTC | Jun 3, 20:15 UTC | 2h 5m |
| 2026-06-03 | - | Jun 3, 15:00 UTC | Jun 3, 17:15 UTC | 2h 15m |
| 2026-06-02 | - | Jun 2, 15:45 UTC | Jun 2, 17:30 UTC | 1h 45m |
| 2026-06-02 | BTS → LBG | Jun 2, 06:20 UTC | Jun 2, 08:05 UTC | 1h 45m |
| 2026-05-31 | - | May 31, 20:25 UTC | May 31, 21:45 UTC | 1h 20m |
| 2026-05-31 | - | May 31, 15:50 UTC | May 31, 17:10 UTC | 1h 20m |
| 2026-05-29 | VIE → BTS | May 29, 13:30 UTC | May 29, 13:50 UTC | 20m |
| 2026-05-27 | - | May 27, 04:39 UTC | May 27, 04:55 UTC | 15m |
| 2026-05-26 | VOD → BTS | May 26, 11:39 UTC | May 26, 12:24 UTC | 45m |
| 2026-05-26 | BTS → VOD | May 26, 07:29 UTC | May 26, 08:04 UTC | 35m |
| 2026-05-25 | - | May 25, 15:55 UTC | May 25, 16:50 UTC | 55m |
| 2026-05-25 | - | May 25, 10:00 UTC | May 25, 10:50 UTC | 50m |
| 2026-05-22 | LIN → BTS | May 22, 17:15 UTC | May 22, 18:20 UTC | 1h 5m |
| 2026-05-21 | BTS → LIN | May 21, 11:25 UTC | May 21, 12:30 UTC | 1h 5m |
| 2026-05-19 | BUD → BTS | May 19, 17:30 UTC | May 19, 17:55 UTC | 25m |
| 2026-05-19 | - | May 19, 15:15 UTC | May 19, 16:30 UTC | 1h 15m |
| 2026-05-18 | - | May 18, 17:00 UTC | May 18, 17:10 UTC | 10m |
| 2026-05-18 | - | May 18, 14:15 UTC | May 18, 15:30 UTC | 1h 15m |
| 2026-05-18 | BTS → BUD | May 18, 12:15 UTC | May 18, 12:40 UTC | 25m |
| 2026-05-16 | - | May 16, 19:20 UTC | May 16, 20:40 UTC | 1h 20m |
| 2026-05-16 | - | May 16, 06:10 UTC | May 16, 07:31 UTC | 1h 20m |
| 2026-05-15 | TBS → BTS | May 15, 08:20 UTC | May 15, 12:00 UTC | 3h 40m |
| 2026-05-15 | - | May 15, 05:55 UTC | May 15, 07:05 UTC | 1h 10m |
| 2026-05-13 | - | May 13, 10:05 UTC | May 13, 11:15 UTC | 1h 10m |
| 2026-05-13 | - | May 13, 08:45 UTC | May 13, 09:00 UTC | 15m |
| 2026-05-13 | - | May 13, 05:50 UTC | May 13, 07:05 UTC | 1h 15m |
| 2026-05-11 | - | May 11, 15:05 UTC | May 11, 15:45 UTC | 40m |
| 2026-05-11 | BTS → VOD | May 11, 07:05 UTC | May 11, 07:40 UTC | 35m |
| 2026-05-08 | - | May 8, 12:39 UTC | May 8, 13:30 UTC | 50m |
| 2026-05-08 | - | May 8, 10:14 UTC | May 8, 11:19 UTC | 1h 5m |
| 2026-05-08 | BTS → PRG | May 8, 08:14 UTC | May 8, 08:49 UTC | 35m |
| 2026-05-07 | - | May 7, 15:05 UTC | May 7, 15:45 UTC | 40m |
| 2026-05-07 | - | May 7, 12:50 UTC | May 7, 14:05 UTC | 1h 15m |
| 2026-05-07 | - | May 7, 09:30 UTC | May 7, 11:05 UTC | 1h 35m |
| 2026-05-06 | STR → BTS | May 6, 13:45 UTC | May 6, 14:50 UTC | 1h 5m |
| 2026-05-06 | BTS → STR | May 6, 04:40 UTC | May 6, 05:40 UTC | 1h 0m |
| 2026-05-05 | - | May 5, 13:00 UTC | May 5, 14:30 UTC | 1h 30m |
| 2026-05-05 | - | May 5, 06:20 UTC | May 5, 07:30 UTC | 1h 10m |
| 2026-05-03 | ATH → BTS | May 3, 08:45 UTC | May 3, 10:45 UTC | 2h 0m |
| 2026-05-03 | - | May 3, 06:40 UTC | May 3, 07:15 UTC | 35m |
| 2026-04-30 | - | Apr 30, 16:45 UTC | Apr 30, 17:10 UTC | 25m |
| 2026-04-30 | BTS → ATH | Apr 30, 13:55 UTC | Apr 30, 15:45 UTC | 1h 50m |
| 2026-04-29 | DBV → BTS | Apr 29, 08:40 UTC | Apr 29, 09:50 UTC | 1h 11m |
| 2026-04-28 | BTS → DBV | Apr 28, 07:40 UTC | Apr 28, 08:40 UTC | 1h 0m |
| 2026-04-26 | - | Apr 26, 20:35 UTC | Apr 26, 21:15 UTC | 40m |
| 2026-04-26 | - | Apr 26, 14:10 UTC | Apr 26, 14:35 UTC | 25m |
| 2026-04-23 | VOD → BTS | Apr 23, 12:35 UTC | Apr 23, 13:20 UTC | 45m |
Specifications
| Registration | OM-FLY |
| Aircraft type | CESSNA 560XL Citation XLS (C56X) |
| Mode-S code | 505D99 · 24056631 (octal) |
Looking for transponder-level data? View the Mode-S 505D99 page for country allocation, callsign history, and ADS-B signal details.
OM-FLY frequently asked
What type of aircraft is OM-FLY?
OM-FLY is a CESSNA 560XL Citation XLS (ICAO type code C56X).
What is the Mode-S transponder code for OM-FLY?
OM-FLY broadcasts on Mode-S (ICAO 24-bit) address 505D99 (octal 24056631). View the transponder page.
What route does OM-FLY typically fly?
OM-FLY most frequently flies between BTS and VOD based on observed flights.
Where is OM-FLY right now?
OM-FLY is not currently being tracked; last seen 2d ago.