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