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