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