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