Not currently tracked · last seen 10h ago
- Flights observed
- 126 showing last 50
- Avg flight time
- 1h 2m
- Typical route
- BJC → BJC
- Last seen
- 10h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | - | May 29, 18:40 UTC | May 29, 19:00 UTC | 20m |
| 2026-05-29 | - | May 29, 17:30 UTC | May 29, 18:35 UTC | 1h 5m |
| 2026-05-28 | - | May 28, 23:25 UTC | May 28, 23:55 UTC | 30m |
| 2026-05-28 | - | May 28, 22:30 UTC | May 28, 23:20 UTC | 50m |
| 2026-05-28 | BJC → BJC | May 28, 19:50 UTC | May 28, 21:20 UTC | 1h 30m |
| 2026-05-28 | BJC → BJC | May 28, 15:35 UTC | May 28, 17:00 UTC | 1h 25m |
| 2026-05-28 | BJC → BJC | May 28, 12:15 UTC | May 28, 13:45 UTC | 1h 30m |
| 2026-05-27 | BJC → BJC | May 27, 22:40 UTC | May 28, 00:00 UTC | 1h 20m |
| 2026-05-27 | BJC → BJC | May 27, 17:55 UTC | May 27, 19:05 UTC | 1h 10m |
| 2026-05-27 | BJC → BJC | May 27, 15:35 UTC | May 27, 16:35 UTC | 1h 0m |
| 2026-05-27 | BJC → BJC | May 27, 13:15 UTC | May 27, 14:25 UTC | 1h 10m |
| 2026-05-26 | BJC → BJC | May 26, 19:45 UTC | May 26, 21:20 UTC | 1h 35m |
| 2026-05-26 | BJC → BJC | May 26, 17:25 UTC | May 26, 18:34 UTC | 1h 10m |
| 2026-05-26 | BJC → BJC | May 26, 15:00 UTC | May 26, 16:10 UTC | 1h 10m |
| 2026-05-26 | BJC → BJC | May 26, 12:35 UTC | May 26, 13:29 UTC | 55m |
| 2026-05-26 | BJC → BJC | May 26, 00:49 UTC | May 26, 02:04 UTC | 1h 15m |
| 2026-05-25 | BJC → BJC | May 25, 21:30 UTC | May 25, 22:19 UTC | 50m |
| 2026-05-25 | BJC → BJC | May 25, 17:15 UTC | May 25, 17:40 UTC | 25m |
| 2026-05-25 | BJC → BJC | May 25, 13:55 UTC | May 25, 14:45 UTC | 50m |
| 2026-05-25 | BJC → BJC | May 25, 04:50 UTC | May 25, 05:30 UTC | 40m |
| 2026-05-25 | - | May 25, 04:35 UTC | May 25, 04:45 UTC | 10m |
| 2026-05-25 | BJC → BJC | May 25, 04:25 UTC | May 25, 04:30 UTC | 5m |
| 2026-05-24 | - | May 24, 18:35 UTC | May 24, 19:40 UTC | 1h 5m |
| 2026-05-24 | - | May 24, 17:20 UTC | May 24, 18:05 UTC | 45m |
| 2026-05-24 | BJC → BJC | May 24, 15:25 UTC | May 24, 16:05 UTC | 40m |
| 2026-05-24 | - | May 24, 00:15 UTC | May 24, 01:55 UTC | 1h 40m |
| 2026-05-23 | - | May 23, 22:35 UTC | May 23, 23:25 UTC | 50m |
| 2026-05-23 | BJC → BJC | May 23, 17:40 UTC | May 23, 19:20 UTC | 1h 40m |
| 2026-05-23 | BJC → BJC | May 23, 14:40 UTC | May 23, 15:50 UTC | 1h 10m |
| 2026-05-22 | BJC → BJC | May 22, 21:25 UTC | May 22, 22:40 UTC | 1h 15m |
| 2026-05-22 | BJC → BJC | May 22, 18:40 UTC | May 22, 20:05 UTC | 1h 25m |
| 2026-05-22 | BJC → BJC | May 22, 15:10 UTC | May 22, 16:45 UTC | 1h 35m |
| 2026-05-22 | BJC → BJC | May 22, 13:45 UTC | May 22, 13:55 UTC | 10m |
| 2026-05-22 | BJC → BJC | May 22, 13:05 UTC | May 22, 13:10 UTC | 5m |
| 2026-05-22 | BJC → BJC | May 22, 12:55 UTC | May 22, 13:00 UTC | 5m |
| 2026-05-21 | BJC → BJC | May 21, 22:35 UTC | May 21, 23:35 UTC | 1h 0m |
| 2026-05-21 | BJC → BJC | May 21, 20:10 UTC | May 21, 21:45 UTC | 1h 35m |
| 2026-05-21 | BJC → BJC | May 21, 17:50 UTC | May 21, 19:15 UTC | 1h 25m |
| 2026-05-21 | BJC → BJC | May 21, 15:10 UTC | May 21, 16:10 UTC | 1h 0m |
| 2026-05-21 | BJC → BJC | May 21, 12:15 UTC | May 21, 13:55 UTC | 1h 40m |
| 2026-05-20 | BJC → BJC | May 20, 22:05 UTC | May 20, 23:30 UTC | 1h 25m |
| 2026-05-20 | BJC → BJC | May 20, 18:35 UTC | May 20, 20:20 UTC | 1h 45m |
| 2026-05-17 | - | May 17, 16:10 UTC | May 17, 17:40 UTC | 1h 30m |
| 2026-05-17 | BJC → BJC | May 17, 13:10 UTC | May 17, 15:20 UTC | 2h 10m |
| 2026-05-16 | BJC → BJC | May 16, 17:15 UTC | May 16, 18:40 UTC | 1h 25m |
| 2026-05-16 | BJC → BJC | May 16, 14:31 UTC | May 16, 15:20 UTC | 50m |
| 2026-05-15 | - | May 15, 23:20 UTC | May 15, 23:35 UTC | 15m |
| 2026-05-15 | - | May 15, 22:30 UTC | May 15, 23:15 UTC | 45m |
| 2026-05-15 | BJC → BJC | May 15, 17:45 UTC | May 15, 18:40 UTC | 55m |
| 2026-05-15 | BJC → BJC | May 15, 00:20 UTC | May 15, 00:45 UTC | 25m |
Specifications
| Registration | N268FM |
| Operator | RUNAMUCK LLC |
| Mode-S code | A29D3E · 50516476 (octal) |
Looking for transponder-level data? View the Mode-S A29D3E page for country allocation, callsign history, and ADS-B signal details.
N268FM frequently asked
Who operates N268FM?
N268FM is operated by RUNAMUCK LLC.
What is the Mode-S transponder code for N268FM?
N268FM broadcasts on Mode-S (ICAO 24-bit) address A29D3E (octal 50516476). View the transponder page.
What route does N268FM typically fly?
N268FM most frequently flies between BJC and BJC based on observed flights.
Where is N268FM right now?
N268FM is not currently being tracked; last seen 10h ago.