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