Not currently tracked · last seen 37m ago
- Flights observed
- 131 showing last 50
- Avg flight time
- 1h 3m
- Typical route
- TMB → TMB
- Last seen
- 37m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-03 | - | Jun 3, 11:25 UTC | Jun 3, 12:40 UTC | 1h 15m |
| 2026-06-02 | TMB → TMB | Jun 2, 20:35 UTC | Jun 2, 21:30 UTC | 55m |
| 2026-06-02 | TMB → TMB | Jun 2, 18:40 UTC | Jun 2, 19:40 UTC | 1h 0m |
| 2026-06-02 | TMB → TMB | Jun 2, 14:40 UTC | Jun 2, 15:45 UTC | 1h 5m |
| 2026-06-02 | - | Jun 2, 12:45 UTC | Jun 2, 13:55 UTC | 1h 10m |
| 2026-06-02 | - | Jun 2, 10:55 UTC | Jun 2, 11:55 UTC | 1h 0m |
| 2026-06-01 | - | Jun 1, 18:45 UTC | Jun 1, 19:40 UTC | 55m |
| 2026-06-01 | TMB → TMB | Jun 1, 16:35 UTC | Jun 1, 17:50 UTC | 1h 15m |
| 2026-06-01 | - | Jun 1, 14:40 UTC | Jun 1, 15:50 UTC | 1h 10m |
| 2026-06-01 | TMB → TMB | Jun 1, 12:50 UTC | Jun 1, 13:35 UTC | 45m |
| 2026-05-31 | TMB → TMB | May 31, 18:40 UTC | May 31, 19:35 UTC | 55m |
| 2026-05-31 | TMB → TMB | May 31, 16:45 UTC | May 31, 17:55 UTC | 1h 10m |
| 2026-05-31 | TMB → TMB | May 31, 15:05 UTC | May 31, 15:50 UTC | 45m |
| 2026-05-30 | TMB → TMB | May 30, 16:35 UTC | May 30, 17:45 UTC | 1h 10m |
| 2026-05-30 | - | May 30, 14:20 UTC | May 30, 15:30 UTC | 1h 10m |
| 2026-05-29 | - | May 29, 16:40 UTC | May 29, 17:35 UTC | 55m |
| 2026-05-29 | TMB → TMB | May 29, 14:50 UTC | May 29, 16:00 UTC | 1h 10m |
| 2026-05-29 | - | May 29, 10:50 UTC | May 29, 11:50 UTC | 1h 0m |
| 2026-05-28 | - | May 28, 20:50 UTC | May 28, 21:35 UTC | 45m |
| 2026-05-27 | TMB → TMB | May 27, 22:55 UTC | May 27, 23:30 UTC | 35m |
| 2026-05-27 | TMB → TMB | May 27, 20:25 UTC | May 27, 21:25 UTC | 1h 0m |
| 2026-05-26 | - | May 26, 19:34 UTC | May 26, 20:34 UTC | 1h 0m |
| 2026-05-26 | - | May 26, 16:50 UTC | May 26, 18:24 UTC | 1h 35m |
| 2026-05-25 | TMB → TMB | May 25, 22:49 UTC | May 25, 23:35 UTC | 45m |
| 2026-05-25 | TMB → TMB | May 25, 18:55 UTC | May 25, 19:59 UTC | 1h 5m |
| 2026-05-25 | - | May 25, 14:05 UTC | May 25, 14:40 UTC | 35m |
| 2026-05-25 | - | May 25, 12:20 UTC | May 25, 12:55 UTC | 35m |
| 2026-05-24 | - | May 24, 15:20 UTC | May 24, 16:45 UTC | 1h 25m |
| 2026-05-24 | - | May 24, 12:30 UTC | May 24, 13:35 UTC | 1h 5m |
| 2026-05-23 | - | May 23, 12:20 UTC | May 23, 13:30 UTC | 1h 10m |
| 2026-05-22 | TMB → TMB | May 22, 22:40 UTC | May 22, 23:55 UTC | 1h 15m |
| 2026-05-22 | - | May 22, 14:25 UTC | May 22, 15:40 UTC | 1h 15m |
| 2026-05-21 | - | May 21, 20:30 UTC | May 21, 21:30 UTC | 1h 0m |
| 2026-05-21 | TMB → TMB | May 21, 15:55 UTC | May 21, 17:30 UTC | 1h 35m |
| 2026-05-21 | TMB → TMB | May 21, 12:35 UTC | May 21, 13:20 UTC | 45m |
| 2026-05-21 | - | May 21, 00:50 UTC | May 21, 02:20 UTC | 1h 30m |
| 2026-05-20 | - | May 20, 22:35 UTC | May 20, 23:45 UTC | 1h 10m |
| 2026-05-20 | - | May 20, 20:35 UTC | May 20, 21:40 UTC | 1h 5m |
| 2026-05-20 | TMB → TMB | May 20, 18:40 UTC | May 20, 19:50 UTC | 1h 10m |
| 2026-05-20 | - | May 20, 17:15 UTC | May 20, 17:55 UTC | 40m |
| 2026-05-20 | - | May 20, 13:05 UTC | May 20, 13:55 UTC | 50m |
| 2026-05-19 | TMB → TMB | May 19, 20:25 UTC | May 19, 21:35 UTC | 1h 10m |
| 2026-05-19 | TMB → TMB | May 19, 18:55 UTC | May 19, 19:55 UTC | 1h 0m |
| 2026-05-18 | - | May 18, 16:35 UTC | May 18, 17:50 UTC | 1h 15m |
| 2026-05-18 | - | May 18, 14:30 UTC | May 18, 15:45 UTC | 1h 15m |
| 2026-05-18 | - | May 18, 12:25 UTC | May 18, 13:30 UTC | 1h 5m |
| 2026-05-16 | TMB → TMB | May 16, 20:50 UTC | May 16, 21:30 UTC | 40m |
| 2026-05-16 | TMB → TMB | May 16, 12:31 UTC | May 16, 13:51 UTC | 1h 20m |
| 2026-05-15 | TMB → TMB | May 15, 18:40 UTC | May 15, 19:50 UTC | 1h 10m |
| 2026-05-15 | TMB → TMB | May 15, 15:45 UTC | May 15, 16:45 UTC | 1h 0m |
Specifications
| Registration | N80BF |
| Operator | AIR FUTURE AIRWAYS CORP |
| Mode-S code | AADFA3 · 52557643 (octal) |
Looking for transponder-level data? View the Mode-S AADFA3 page for country allocation, callsign history, and ADS-B signal details.
N80BF frequently asked
Who operates N80BF?
N80BF is operated by AIR FUTURE AIRWAYS CORP.
What is the Mode-S transponder code for N80BF?
N80BF broadcasts on Mode-S (ICAO 24-bit) address AADFA3 (octal 52557643). View the transponder page.
What route does N80BF typically fly?
N80BF most frequently flies between TMB and TMB based on observed flights.
Where is N80BF right now?
N80BF is not currently being tracked; last seen 37m ago.