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