Not currently tracked · last seen Jul 13, 00:40 UTC
- Flights observed
- 252 showing last 50
- Avg flight time
- 48m
- Typical route
- PAO → PAO
- Last seen
- Jul 13, 00:40 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-12 | PAO → PAO | Jul 12, 23:10 UTC | Jul 13, 00:35 UTC | 1h 25m |
| 2026-07-12 | PAO → PAO | Jul 12, 21:25 UTC | Jul 12, 22:25 UTC | 1h 0m |
| 2026-07-12 | PAO → PAO | Jul 12, 18:25 UTC | Jul 12, 18:35 UTC | 10m |
| 2026-07-12 | PAO → PAO | Jul 12, 18:10 UTC | Jul 12, 18:20 UTC | 10m |
| 2026-07-12 | - | Jul 12, 17:55 UTC | Jul 12, 18:05 UTC | 10m |
| 2026-07-12 | PAO → PAO | Jul 12, 17:35 UTC | Jul 12, 17:40 UTC | 5m |
| 2026-07-11 | PAO → PAO | Jul 11, 23:05 UTC | Jul 11, 23:55 UTC | 50m |
| 2026-07-11 | PAO → PAO | Jul 11, 20:20 UTC | Jul 11, 22:10 UTC | 1h 50m |
| 2026-07-11 | PAO → PAO | Jul 11, 00:45 UTC | Jul 11, 02:35 UTC | 1h 50m |
| 2026-07-10 | PAO → PAO | Jul 10, 23:00 UTC | Jul 10, 23:50 UTC | 50m |
| 2026-07-10 | PAO → PAO | Jul 10, 19:00 UTC | Jul 10, 19:45 UTC | 45m |
| 2026-07-10 | - | Jul 10, 00:40 UTC | Jul 10, 01:45 UTC | 1h 5m |
| 2026-07-10 | PAO → CCR | Jul 10, 00:05 UTC | Jul 10, 00:35 UTC | 30m |
| 2026-07-09 | PAO → PAO | Jul 9, 18:45 UTC | Jul 9, 19:45 UTC | 1h 0m |
| 2026-07-09 | PAO → PAO | Jul 9, 17:30 UTC | Jul 9, 17:40 UTC | 10m |
| 2026-07-09 | PAO → PAO | Jul 9, 17:15 UTC | Jul 9, 17:25 UTC | 10m |
| 2026-07-09 | PAO → PAO | Jul 9, 16:45 UTC | Jul 9, 17:05 UTC | 20m |
| 2026-07-08 | SQL → PAO | Jul 8, 19:50 UTC | Jul 8, 20:40 UTC | 50m |
| 2026-07-08 | PAO → SQL | Jul 8, 19:40 UTC | Jul 8, 19:45 UTC | 5m |
| 2026-07-07 | PAO → PAO | Jul 7, 20:15 UTC | Jul 7, 20:35 UTC | 20m |
| 2026-07-07 | PAO → PAO | Jul 7, 19:55 UTC | Jul 7, 20:05 UTC | 10m |
| 2026-07-07 | PAO → PAO | Jul 7, 15:45 UTC | Jul 7, 16:20 UTC | 35m |
| 2026-07-05 | PAO → PAO | Jul 5, 18:10 UTC | Jul 5, 18:55 UTC | 45m |
| 2026-07-05 | PAO → PAO | Jul 5, 05:00 UTC | Jul 5, 06:35 UTC | 1h 35m |
| 2026-07-05 | SJC → PAO | Jul 5, 04:10 UTC | Jul 5, 04:20 UTC | 10m |
| 2026-07-05 | PAO → RHV | Jul 5, 03:05 UTC | Jul 5, 03:20 UTC | 15m |
| 2026-07-04 | PAO → PAO | Jul 4, 19:15 UTC | Jul 4, 19:20 UTC | 5m |
| 2026-07-04 | - | Jul 4, 18:45 UTC | Jul 4, 18:55 UTC | 10m |
| 2026-07-04 | PAO → PAO | Jul 4, 18:15 UTC | Jul 4, 18:25 UTC | 10m |
| 2026-07-04 | PAO → PAO | Jul 4, 17:50 UTC | Jul 4, 18:10 UTC | 20m |
| 2026-07-04 | PAO → PAO | Jul 4, 05:25 UTC | Jul 4, 05:50 UTC | 25m |
| 2026-07-03 | - | Jul 3, 21:50 UTC | Jul 3, 22:25 UTC | 35m |
| 2026-07-03 | PAO → PAO | Jul 3, 21:20 UTC | Jul 3, 21:45 UTC | 25m |
| 2026-07-03 | PAO → PAO | Jul 3, 17:25 UTC | Jul 3, 18:55 UTC | 1h 30m |
| 2026-07-02 | PAO → PAO | Jul 2, 23:15 UTC | Jul 2, 23:50 UTC | 35m |
| 2026-07-02 | PAO → PAO | Jul 2, 15:25 UTC | Jul 2, 17:15 UTC | 1h 50m |
| 2026-07-01 | PAO → PAO | Jul 1, 16:25 UTC | Jul 1, 16:35 UTC | 10m |
| 2026-07-01 | PAO → PAO | Jul 1, 15:40 UTC | Jul 1, 16:20 UTC | 40m |
| 2026-06-30 | PAO → PAO | Jun 30, 02:05 UTC | Jun 30, 04:00 UTC | 1h 55m |
| 2026-06-29 | PAO → PAO | Jun 29, 20:49 UTC | Jun 29, 23:34 UTC | 2h 45m |
| 2026-06-29 | PAO → PAO | Jun 29, 17:30 UTC | Jun 29, 19:29 UTC | 2h 0m |
| 2026-06-28 | PAO → PAO | Jun 28, 21:59 UTC | Jun 28, 23:25 UTC | 1h 25m |
| 2026-06-27 | PAO → PAO | Jun 27, 22:35 UTC | Jun 28, 02:10 UTC | 3h 35m |
| 2026-06-27 | PAO → PAO | Jun 27, 19:59 UTC | Jun 27, 21:40 UTC | 1h 40m |
| 2026-06-27 | PAO → PAO | Jun 27, 17:55 UTC | Jun 27, 18:54 UTC | 1h 0m |
| 2026-06-26 | PAO → PAO | Jun 26, 23:25 UTC | Jun 27, 00:25 UTC | 1h 0m |
| 2026-06-26 | PAO → PAO | Jun 26, 19:39 UTC | Jun 26, 19:45 UTC | 5m |
| 2026-06-26 | PAO → PAO | Jun 26, 19:24 UTC | Jun 26, 19:30 UTC | 5m |
| 2026-06-26 | PAO → PAO | Jun 26, 19:04 UTC | Jun 26, 19:20 UTC | 15m |
| 2026-06-26 | PAO → PAO | Jun 26, 17:09 UTC | Jun 26, 17:19 UTC | 10m |
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 Jul 13, 00:40 UTC.