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