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