Not currently tracked · last seen 4d ago
- Flights observed
- 34
- Avg flight time
- 57m
- Typical route
- -
- Last seen
- 4d ago
Last known area
Recent flights last 34
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-04 | - | Jun 4, 15:55 UTC | Jun 4, 17:35 UTC | 1h 40m |
| 2026-06-04 | - | Jun 4, 13:45 UTC | Jun 4, 15:00 UTC | 1h 15m |
| 2026-06-02 | - | Jun 2, 16:25 UTC | Jun 2, 17:55 UTC | 1h 30m |
| 2026-05-29 | - | May 29, 15:45 UTC | May 29, 16:20 UTC | 35m |
| 2026-05-22 | - | May 22, 19:20 UTC | May 22, 19:45 UTC | 25m |
| 2026-05-22 | - | May 22, 15:35 UTC | May 22, 15:55 UTC | 20m |
| 2026-05-22 | - | May 22, 00:05 UTC | May 22, 01:40 UTC | 1h 35m |
| 2026-05-21 | - | May 21, 20:35 UTC | May 21, 21:55 UTC | 1h 20m |
| 2026-05-21 | - | May 21, 15:20 UTC | May 21, 15:50 UTC | 30m |
| 2026-05-21 | - | May 21, 13:25 UTC | May 21, 14:20 UTC | 55m |
| 2026-05-19 | - | May 19, 16:05 UTC | May 19, 17:30 UTC | 1h 25m |
| 2026-05-19 | - | May 19, 14:00 UTC | May 19, 15:20 UTC | 1h 20m |
| 2026-05-15 | LNA → LAL | May 15, 14:05 UTC | May 15, 15:10 UTC | 1h 4m |
| 2026-05-13 | LAL → LNA | May 13, 18:50 UTC | May 13, 19:55 UTC | 1h 5m |
| 2026-05-11 | - | May 11, 14:05 UTC | May 11, 15:05 UTC | 1h 0m |
| 2026-05-11 | - | May 11, 13:45 UTC | May 11, 14:00 UTC | 15m |
| 2026-05-08 | - | May 8, 17:05 UTC | May 8, 18:25 UTC | 1h 20m |
| 2026-05-08 | - | May 8, 13:15 UTC | May 8, 14:40 UTC | 1h 25m |
| 2026-05-07 | - | May 7, 13:20 UTC | May 7, 14:10 UTC | 50m |
| 2026-05-06 | - | May 6, 17:30 UTC | May 6, 18:50 UTC | 1h 19m |
| 2026-05-05 | - | May 5, 15:01 UTC | May 5, 16:35 UTC | 1h 35m |
| 2026-04-27 | - | Apr 27, 15:20 UTC | Apr 27, 17:30 UTC | 2h 10m |
| 2026-04-24 | - | Apr 24, 21:05 UTC | Apr 24, 21:40 UTC | 35m |
| 2026-04-24 | - | Apr 24, 19:30 UTC | Apr 24, 20:05 UTC | 35m |
| 2026-04-22 | - | Apr 22, 21:20 UTC | Apr 22, 22:05 UTC | 45m |
| 2026-04-22 | - | Apr 22, 19:05 UTC | Apr 22, 19:35 UTC | 30m |
| 2026-04-22 | - | Apr 22, 17:25 UTC | Apr 22, 18:05 UTC | 40m |
| 2026-04-22 | - | Apr 22, 15:10 UTC | Apr 22, 15:50 UTC | 40m |
| 2026-04-22 | - | Apr 22, 13:55 UTC | Apr 22, 14:35 UTC | 40m |
| 2026-04-21 | - | Apr 21, 16:20 UTC | Apr 21, 16:55 UTC | 35m |
| 2026-04-21 | - | Apr 21, 14:40 UTC | Apr 21, 15:20 UTC | 40m |
| 2026-04-20 | - | Apr 20, 20:15 UTC | Apr 20, 21:00 UTC | 45m |
| 2026-04-20 | - | Apr 20, 12:45 UTC | Apr 20, 13:25 UTC | 40m |
| 2026-04-18 | - | Apr 18, 14:05 UTC | Apr 18, 14:15 UTC | 10m |
Specifications
| Registration | N6384J |
| Operator | FLORIDA STATE GUARD |
| Mode-S code | A85E61 · 52057141 (octal) |
Looking for transponder-level data? View the Mode-S A85E61 page for country allocation, callsign history, and ADS-B signal details.
N6384J frequently asked
Who operates N6384J?
N6384J is operated by FLORIDA STATE GUARD.
What is the Mode-S transponder code for N6384J?
N6384J broadcasts on Mode-S (ICAO 24-bit) address A85E61 (octal 52057141). View the transponder page.
Where is N6384J right now?
N6384J is not currently being tracked; last seen 4d ago.