Not currently tracked · last seen 16h ago
- Flights observed
- 80 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-05-29 | BJC → BJC | May 29, 17:40 UTC | May 29, 18:25 UTC | 45m |
| 2026-05-28 | BJC → BJC | May 28, 12:40 UTC | May 28, 14:15 UTC | 1h 35m |
| 2026-05-27 | BJC → BJC | May 27, 02:09 UTC | May 27, 03:34 UTC | 1h 25m |
| 2026-05-26 | BJC → BJC | May 26, 19:45 UTC | May 26, 21:04 UTC | 1h 20m |
| 2026-05-26 | BJC → BJC | May 26, 17:20 UTC | May 26, 18:30 UTC | 1h 10m |
| 2026-05-26 | BJC → BJC | May 26, 14:14 UTC | May 26, 15:20 UTC | 1h 5m |
| 2026-05-25 | BJC → BJC | May 25, 16:45 UTC | May 25, 17:50 UTC | 1h 5m |
| 2026-05-25 | BJC → BJC | May 25, 13:35 UTC | May 25, 15:10 UTC | 1h 35m |
| 2026-05-24 | BJC → BJC | May 24, 15:10 UTC | May 24, 16:50 UTC | 1h 40m |
| 2026-05-23 | BJC → BJC | May 23, 20:00 UTC | May 23, 22:30 UTC | 2h 30m |
| 2026-05-23 | BJC → BJC | May 23, 14:45 UTC | May 23, 17:20 UTC | 2h 35m |
| 2026-05-22 | - | May 22, 18:55 UTC | May 22, 19:45 UTC | 50m |
| 2026-05-22 | - | May 22, 16:30 UTC | May 22, 18:20 UTC | 1h 50m |
| 2026-05-22 | BJC → BJC | May 22, 13:30 UTC | May 22, 14:50 UTC | 1h 20m |
| 2026-05-21 | BJC → BJC | May 21, 22:10 UTC | May 22, 00:20 UTC | 2h 10m |
| 2026-05-21 | BJC → BJC | May 21, 15:35 UTC | May 21, 18:20 UTC | 2h 45m |
| 2026-05-20 | BJC → BJC | May 20, 14:05 UTC | May 20, 15:25 UTC | 1h 20m |
| 2026-05-20 | BJC → BJC | May 20, 02:10 UTC | May 20, 03:25 UTC | 1h 15m |
| 2026-05-17 | BJC → BJC | May 17, 12:50 UTC | May 17, 14:01 UTC | 1h 10m |
| 2026-05-16 | BJC → BJC | May 16, 12:50 UTC | May 16, 13:51 UTC | 1h 0m |
| 2026-05-15 | BJC → BJC | May 15, 23:35 UTC | May 16, 00:55 UTC | 1h 20m |
| 2026-05-15 | BJC → BJC | May 15, 20:30 UTC | May 15, 21:35 UTC | 1h 5m |
| 2026-05-15 | BJC → BJC | May 15, 17:40 UTC | May 15, 18:35 UTC | 55m |
| 2026-05-15 | BJC → BJC | May 15, 15:35 UTC | May 15, 16:45 UTC | 1h 10m |
| 2026-05-15 | BJC → BJC | May 15, 13:45 UTC | May 15, 14:35 UTC | 50m |
| 2026-05-14 | - | May 14, 22:05 UTC | May 14, 23:05 UTC | 1h 0m |
| 2026-05-14 | - | May 14, 21:10 UTC | May 14, 21:20 UTC | 10m |
| 2026-05-14 | - | May 14, 13:20 UTC | May 14, 14:30 UTC | 1h 10m |
| 2026-05-13 | - | May 13, 23:00 UTC | May 14, 00:00 UTC | 1h 0m |
| 2026-05-13 | - | May 13, 19:05 UTC | May 13, 19:15 UTC | 10m |
| 2026-05-12 | - | May 12, 20:01 UTC | May 12, 20:10 UTC | 10m |
| 2026-05-12 | - | May 12, 18:30 UTC | May 12, 18:40 UTC | 10m |
| 2026-05-12 | - | May 12, 16:45 UTC | May 12, 17:35 UTC | 50m |
| 2026-05-12 | BJC → BJC | May 12, 14:25 UTC | May 12, 15:50 UTC | 1h 25m |
| 2026-05-12 | - | May 12, 02:45 UTC | May 12, 03:00 UTC | 15m |
| 2026-05-11 | BJC → BJC | May 11, 19:20 UTC | May 11, 20:45 UTC | 1h 25m |
| 2026-05-11 | BJC → BJC | May 11, 15:05 UTC | May 11, 17:10 UTC | 2h 6m |
| 2026-05-11 | BJC → BJC | May 11, 01:40 UTC | May 11, 03:45 UTC | 2h 5m |
| 2026-05-10 | - | May 10, 22:45 UTC | May 10, 23:05 UTC | 20m |
| 2026-05-10 | - | May 10, 21:59 UTC | May 10, 22:15 UTC | 15m |
| 2026-05-10 | BJC → BJC | May 10, 19:00 UTC | May 10, 20:20 UTC | 1h 20m |
| 2026-05-02 | BJC → BJC | May 2, 14:10 UTC | May 2, 14:55 UTC | 45m |
| 2026-05-01 | BJC → BJC | May 1, 20:40 UTC | May 1, 21:35 UTC | 55m |
| 2026-05-01 | BJC → BJC | May 1, 15:40 UTC | May 1, 17:30 UTC | 1h 50m |
| 2026-05-01 | BJC → BJC | May 1, 13:45 UTC | May 1, 14:35 UTC | 50m |
| 2026-05-01 | - | May 1, 00:30 UTC | May 1, 00:55 UTC | 25m |
| 2026-04-30 | - | Apr 30, 23:50 UTC | May 1, 00:25 UTC | 35m |
| 2026-04-30 | BJC → BJC | Apr 30, 17:35 UTC | Apr 30, 19:20 UTC | 1h 45m |
| 2026-04-30 | BJC → BJC | Apr 30, 03:00 UTC | Apr 30, 04:35 UTC | 1h 35m |
| 2026-04-30 | BJC → BJC | Apr 30, 00:05 UTC | Apr 30, 00:45 UTC | 40m |
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 16h ago.