Not currently tracked · last seen Apr 26, 22:15 UTC
- Flights observed
- 7
- Avg flight time
- 24m
- Typical route
- RUN → JNB
- Last seen
- Apr 26, 22:15 UTC
Last known area
Recent flights last 7
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-04-26 | JNB → RUN | Apr 26, 21:55 UTC | Apr 26, 22:15 UTC | 20m |
| 2026-04-26 | RUN → JNB | Apr 26, 19:55 UTC | Apr 26, 20:30 UTC | 35m |
| 2026-04-19 | JNB → RUN | Apr 19, 23:00 UTC | Apr 19, 23:20 UTC | 20m |
| 2026-04-19 | RUN → JNB | Apr 19, 21:10 UTC | Apr 19, 21:40 UTC | 30m |
| 2026-04-17 | - | Apr 17, 23:10 UTC | Apr 17, 23:20 UTC | 10m |
| 2026-04-17 | - | Apr 17, 21:25 UTC | Apr 17, 21:50 UTC | 25m |
| 2026-04-12 | RUN → JNB | Apr 12, 19:50 UTC | Apr 12, 20:15 UTC | 25m |
Specifications
| Registration | F-OMER |
| Aircraft type | AIRBUS A220-300 (BCS3) |
| Mode-S code | 3A3091 · 16430221 (octal) |
Looking for transponder-level data? View the Mode-S 3A3091 page for country allocation, callsign history, and ADS-B signal details.
F-OMER frequently asked
What type of aircraft is F-OMER?
F-OMER is a AIRBUS A220-300 (ICAO type code BCS3).
What is the Mode-S transponder code for F-OMER?
F-OMER broadcasts on Mode-S (ICAO 24-bit) address 3A3091 (octal 16430221). View the transponder page.
What route does F-OMER typically fly?
F-OMER most frequently flies between RUN and JNB based on observed flights.
Where is F-OMER right now?
F-OMER is not currently being tracked; last seen Apr 26, 22:15 UTC.