Not currently tracked · last seen Jul 26, 21:00 UTC
- Flights observed
- 206 showing last 50
- Avg flight time
- 1h 5m
- Typical route
- BJC → BJC
- Last seen
- Jul 26, 21:00 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | BJC → BJC | Jul 26, 19:30 UTC | Jul 26, 21:00 UTC | 1h 30m |
| 2026-07-26 | BJC → BJC | Jul 26, 16:45 UTC | Jul 26, 17:55 UTC | 1h 10m |
| 2026-07-26 | BJC → BJC | Jul 26, 14:15 UTC | Jul 26, 15:45 UTC | 1h 30m |
| 2026-07-26 | - | Jul 26, 05:05 UTC | Jul 26, 06:10 UTC | 1h 5m |
| 2026-07-26 | - | Jul 26, 03:45 UTC | Jul 26, 04:10 UTC | 25m |
| 2026-07-26 | - | Jul 26, 00:30 UTC | Jul 26, 01:45 UTC | 1h 15m |
| 2026-07-25 | BJC → BJC | Jul 25, 18:55 UTC | Jul 25, 19:50 UTC | 55m |
| 2026-07-25 | BJC → BJC | Jul 25, 12:40 UTC | Jul 25, 13:50 UTC | 1h 10m |
| 2026-07-25 | BJC → BJC | Jul 25, 02:55 UTC | Jul 25, 03:55 UTC | 1h 0m |
| 2026-07-25 | BJC → BJC | Jul 25, 00:45 UTC | Jul 25, 01:45 UTC | 1h 0m |
| 2026-07-24 | BJC → BJC | Jul 24, 14:20 UTC | Jul 24, 15:15 UTC | 55m |
| 2026-07-23 | BJC → BJC | Jul 23, 19:05 UTC | Jul 23, 19:55 UTC | 50m |
| 2026-07-23 | BJC → BJC | Jul 23, 16:00 UTC | Jul 23, 17:45 UTC | 1h 45m |
| 2026-07-23 | BJC → BJC | Jul 23, 12:15 UTC | Jul 23, 14:05 UTC | 1h 50m |
| 2026-07-22 | BJC → BJC | Jul 22, 23:50 UTC | Jul 23, 00:00 UTC | 10m |
| 2026-07-22 | BJC → BJC | Jul 22, 19:35 UTC | Jul 22, 20:45 UTC | 1h 10m |
| 2026-07-22 | - | Jul 22, 15:40 UTC | Jul 22, 17:20 UTC | 1h 40m |
| 2026-07-22 | BJC → BJC | Jul 22, 13:45 UTC | Jul 22, 14:55 UTC | 1h 10m |
| 2026-07-21 | BJC → BJC | Jul 21, 17:40 UTC | Jul 21, 19:45 UTC | 2h 5m |
| 2026-07-21 | BJC → BJC | Jul 21, 12:55 UTC | Jul 21, 13:45 UTC | 50m |
| 2026-07-20 | - | Jul 20, 20:25 UTC | Jul 20, 21:10 UTC | 45m |
| 2026-07-19 | - | Jul 19, 15:25 UTC | Jul 19, 16:15 UTC | 50m |
| 2026-07-19 | BJC → BJC | Jul 19, 12:55 UTC | Jul 19, 14:05 UTC | 1h 10m |
| 2026-07-18 | - | Jul 18, 22:50 UTC | Jul 18, 23:55 UTC | 1h 5m |
| 2026-07-18 | - | Jul 18, 21:05 UTC | Jul 18, 21:45 UTC | 40m |
| 2026-07-18 | - | Jul 18, 19:15 UTC | Jul 18, 19:40 UTC | 25m |
| 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 |
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 Jul 26, 21:00 UTC.