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