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