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