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