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