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