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