Airborne now · flying as N580ET at 7,175 ft
- Flights observed
- 164 showing last 50
- Avg flight time
- 1h 9m
- Typical route
- BJC → BJC
- Last seen
- 2h ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | BJC → BJC | Jul 14, 13:30 UTC | Jul 14, 14:05 UTC | 35m |
| 2026-07-14 | BJC → BJC | Jul 14, 00:45 UTC | Jul 14, 02:50 UTC | 2h 5m |
| 2026-07-13 | - | Jul 13, 18:45 UTC | Jul 13, 19:45 UTC | 1h 0m |
| 2026-07-13 | BJC → BJC | Jul 13, 16:10 UTC | Jul 13, 17:55 UTC | 1h 45m |
| 2026-07-13 | BJC → BJC | Jul 13, 13:05 UTC | Jul 13, 14:55 UTC | 1h 50m |
| 2026-07-13 | BJC → BJC | Jul 13, 01:10 UTC | Jul 13, 02:30 UTC | 1h 20m |
| 2026-07-12 | BJC → BJC | Jul 12, 17:35 UTC | Jul 12, 19:30 UTC | 1h 55m |
| 2026-07-12 | BJC → BJC | Jul 12, 13:35 UTC | Jul 12, 14:25 UTC | 50m |
| 2026-07-11 | BJC → BJC | Jul 11, 17:45 UTC | Jul 11, 19:00 UTC | 1h 15m |
| 2026-07-11 | BJC → BJC | Jul 11, 15:05 UTC | Jul 11, 16:30 UTC | 1h 25m |
| 2026-07-11 | BJC → BJC | Jul 11, 00:10 UTC | Jul 11, 01:40 UTC | 1h 30m |
| 2026-07-10 | BJC → BJC | Jul 10, 17:35 UTC | Jul 10, 18:40 UTC | 1h 5m |
| 2026-07-10 | BJC → BJC | Jul 10, 13:15 UTC | Jul 10, 14:45 UTC | 1h 30m |
| 2026-07-10 | BJC → BJC | Jul 10, 02:10 UTC | Jul 10, 03:00 UTC | 50m |
| 2026-07-09 | BJC → BJC | Jul 9, 16:25 UTC | Jul 9, 18:25 UTC | 2h 0m |
| 2026-07-09 | BJC → BJC | Jul 9, 12:25 UTC | Jul 9, 13:10 UTC | 45m |
| 2026-07-09 | BJC → BJC | Jul 9, 01:35 UTC | Jul 9, 02:35 UTC | 1h 0m |
| 2026-07-08 | - | Jul 8, 17:25 UTC | Jul 8, 17:40 UTC | 15m |
| 2026-07-08 | - | Jul 8, 16:15 UTC | Jul 8, 17:15 UTC | 1h 0m |
| 2026-07-08 | BJC → BJC | Jul 8, 12:10 UTC | Jul 8, 13:00 UTC | 50m |
| 2026-07-08 | BJC → BJC | Jul 8, 03:55 UTC | Jul 8, 04:35 UTC | 40m |
| 2026-07-07 | BJC → BJC | Jul 7, 22:05 UTC | Jul 7, 22:50 UTC | 45m |
| 2026-07-07 | BJC → BJC | Jul 7, 17:05 UTC | Jul 7, 17:45 UTC | 40m |
| 2026-07-07 | BJC → BJC | Jul 7, 03:35 UTC | Jul 7, 04:05 UTC | 30m |
| 2026-07-06 | BJC → BJC | Jul 6, 21:00 UTC | Jul 6, 22:05 UTC | 1h 5m |
| 2026-07-06 | BJC → BJC | Jul 6, 16:40 UTC | Jul 6, 18:20 UTC | 1h 40m |
| 2026-07-06 | BJC → BJC | Jul 6, 13:15 UTC | Jul 6, 14:30 UTC | 1h 15m |
| 2026-07-03 | BJC → BJC | Jul 3, 19:45 UTC | Jul 3, 21:45 UTC | 2h 0m |
| 2026-07-03 | BJC → BJC | Jul 3, 16:15 UTC | Jul 3, 17:15 UTC | 1h 0m |
| 2026-07-03 | BJC → BJC | Jul 3, 11:30 UTC | Jul 3, 12:50 UTC | 1h 20m |
| 2026-07-02 | - | Jul 2, 18:15 UTC | Jul 2, 18:40 UTC | 25m |
| 2026-07-02 | BJC → APA | Jul 2, 15:35 UTC | Jul 2, 16:10 UTC | 35m |
| 2026-07-02 | BJC → BJC | Jul 2, 12:35 UTC | Jul 2, 13:50 UTC | 1h 15m |
| 2026-07-01 | BJC → BJC | Jul 1, 22:35 UTC | Jul 1, 23:40 UTC | 1h 5m |
| 2026-07-01 | BJC → BJC | Jul 1, 19:05 UTC | Jul 1, 20:40 UTC | 1h 35m |
| 2026-07-01 | BJC → BJC | Jul 1, 16:20 UTC | Jul 1, 17:15 UTC | 55m |
| 2026-07-01 | BJC → BJC | Jul 1, 11:40 UTC | Jul 1, 12:40 UTC | 1h 0m |
| 2026-06-30 | BJC → BJC | Jun 30, 15:00 UTC | Jun 30, 16:25 UTC | 1h 25m |
| 2026-06-30 | - | Jun 30, 05:20 UTC | Jun 30, 06:00 UTC | 40m |
| 2026-06-30 | - | Jun 30, 01:00 UTC | Jun 30, 03:00 UTC | 2h 1m |
| 2026-06-29 | - | Jun 29, 22:35 UTC | Jun 29, 23:29 UTC | 55m |
| 2026-06-28 | - | Jun 28, 22:49 UTC | Jun 29, 01:00 UTC | 2h 10m |
| 2026-06-28 | - | Jun 28, 18:44 UTC | Jun 28, 19:34 UTC | 50m |
| 2026-06-28 | BJC → BJC | Jun 28, 15:49 UTC | Jun 28, 16:49 UTC | 1h 0m |
| 2026-06-27 | BJC → BJC | Jun 27, 16:04 UTC | Jun 27, 17:39 UTC | 1h 35m |
| 2026-06-27 | BJC → BJC | Jun 27, 12:50 UTC | Jun 27, 14:14 UTC | 1h 25m |
| 2026-06-27 | BJC → BJC | Jun 27, 03:15 UTC | Jun 27, 04:49 UTC | 1h 35m |
| 2026-06-26 | - | Jun 26, 18:39 UTC | Jun 26, 19:30 UTC | 50m |
| 2026-06-26 | - | Jun 26, 17:35 UTC | Jun 26, 18:04 UTC | 30m |
| 2026-06-26 | BJC → APA | Jun 26, 15:54 UTC | Jun 26, 16:14 UTC | 20m |
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 currently airborne flying as N580ET. Live position is shown on the map above.