Not currently tracked · last seen Jul 25, 15:55 UTC
- Flights observed
- 294 showing last 50
- Avg flight time
- 1h 9m
- Typical route
- BJC → BJC
- Last seen
- Jul 25, 15:55 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-25 | BJC → BJC | Jul 25, 14:00 UTC | Jul 25, 15:50 UTC | 1h 50m |
| 2026-07-24 | BJC → BJC | Jul 24, 19:55 UTC | Jul 24, 20:50 UTC | 55m |
| 2026-07-24 | BJC → BJC | Jul 24, 14:45 UTC | Jul 24, 15:40 UTC | 55m |
| 2026-07-24 | BJC → BJC | Jul 24, 00:40 UTC | Jul 24, 01:10 UTC | 30m |
| 2026-07-23 | BJC → BJC | Jul 23, 18:55 UTC | Jul 23, 19:40 UTC | 45m |
| 2026-07-23 | BJC → BJC | Jul 23, 16:40 UTC | Jul 23, 17:25 UTC | 45m |
| 2026-07-23 | - | Jul 23, 14:35 UTC | Jul 23, 14:50 UTC | 15m |
| 2026-07-23 | - | Jul 23, 14:00 UTC | Jul 23, 14:05 UTC | 5m |
| 2026-07-23 | - | Jul 23, 13:30 UTC | Jul 23, 13:55 UTC | 25m |
| 2026-07-22 | BJC → BJC | Jul 22, 16:55 UTC | Jul 22, 18:20 UTC | 1h 25m |
| 2026-07-22 | - | Jul 22, 14:40 UTC | Jul 22, 15:50 UTC | 1h 10m |
| 2026-07-22 | BJC → BJC | Jul 22, 12:40 UTC | Jul 22, 13:55 UTC | 1h 15m |
| 2026-07-21 | BJC → BJC | Jul 21, 21:00 UTC | Jul 21, 22:05 UTC | 1h 5m |
| 2026-07-21 | - | Jul 21, 17:50 UTC | Jul 21, 18:50 UTC | 1h 0m |
| 2026-07-21 | - | Jul 21, 15:55 UTC | Jul 21, 16:50 UTC | 55m |
| 2026-07-21 | BJC → BJC | Jul 21, 13:50 UTC | Jul 21, 15:10 UTC | 1h 20m |
| 2026-07-20 | BJC → BJC | Jul 20, 15:40 UTC | Jul 20, 16:50 UTC | 1h 10m |
| 2026-07-20 | BJC → BJC | Jul 20, 12:45 UTC | Jul 20, 14:35 UTC | 1h 50m |
| 2026-07-19 | BJC → BJC | Jul 19, 19:20 UTC | Jul 19, 20:20 UTC | 1h 0m |
| 2026-07-19 | BJC → BJC | Jul 19, 16:00 UTC | Jul 19, 17:15 UTC | 1h 15m |
| 2026-07-19 | BJC → BJC | Jul 19, 13:30 UTC | Jul 19, 14:10 UTC | 40m |
| 2026-07-18 | BJC → BJC | Jul 18, 13:45 UTC | Jul 18, 14:35 UTC | 50m |
| 2026-07-18 | - | Jul 18, 08:20 UTC | Jul 18, 10:00 UTC | 1h 40m |
| 2026-07-18 | - | Jul 18, 03:10 UTC | Jul 18, 05:00 UTC | 1h 50m |
| 2026-07-17 | BJC → BJC | Jul 17, 17:40 UTC | Jul 17, 19:20 UTC | 1h 40m |
| 2026-07-17 | BJC → BJC | Jul 17, 15:20 UTC | Jul 17, 16:49 UTC | 1h 30m |
| 2026-07-17 | BJC → BJC | Jul 17, 12:50 UTC | Jul 17, 14:15 UTC | 1h 25m |
| 2026-07-16 | BJC → BJC | Jul 16, 19:20 UTC | Jul 16, 20:35 UTC | 1h 15m |
| 2026-07-16 | BJC → BJC | Jul 16, 16:55 UTC | Jul 16, 18:19 UTC | 1h 25m |
| 2026-07-16 | BJC → BJC | Jul 16, 14:29 UTC | Jul 16, 15:45 UTC | 1h 15m |
| 2026-07-16 | BJC → BJC | Jul 16, 03:55 UTC | Jul 16, 04:15 UTC | 20m |
| 2026-07-16 | BJC → BJC | Jul 16, 01:25 UTC | Jul 16, 02:50 UTC | 1h 25m |
| 2026-07-15 | BJC → BJC | Jul 15, 17:50 UTC | Jul 15, 18:20 UTC | 30m |
| 2026-07-15 | BJC → BJC | Jul 15, 13:15 UTC | Jul 15, 14:15 UTC | 1h 0m |
| 2026-07-15 | BJC → BJC | Jul 15, 03:55 UTC | Jul 15, 05:40 UTC | 1h 45m |
| 2026-07-15 | BJC → BJC | Jul 15, 01:20 UTC | Jul 15, 02:45 UTC | 1h 25m |
| 2026-07-14 | BJC → BJC | Jul 14, 18:40 UTC | Jul 14, 19:45 UTC | 1h 5m |
| 2026-07-14 | BJC → BJC | Jul 14, 14:45 UTC | Jul 14, 15:55 UTC | 1h 10m |
| 2026-07-14 | BJC → BJC | Jul 14, 12:00 UTC | Jul 14, 13:05 UTC | 1h 5m |
| 2026-07-14 | BJC → BJC | Jul 14, 01:30 UTC | Jul 14, 02:40 UTC | 1h 10m |
| 2026-07-13 | BJC → BJC | Jul 13, 21:55 UTC | Jul 13, 23:10 UTC | 1h 15m |
| 2026-07-13 | BJC → BJC | Jul 13, 16:00 UTC | Jul 13, 18:00 UTC | 2h 0m |
| 2026-07-13 | BJC → BJC | Jul 13, 12:55 UTC | Jul 13, 14:15 UTC | 1h 20m |
| 2026-07-12 | - | Jul 12, 19:30 UTC | Jul 12, 20:40 UTC | 1h 10m |
| 2026-07-12 | - | Jul 12, 15:40 UTC | Jul 12, 17:05 UTC | 1h 25m |
| 2026-07-11 | BJC → BJC | Jul 11, 18:00 UTC | Jul 11, 19:15 UTC | 1h 15m |
| 2026-07-11 | BJC → BJC | Jul 11, 15:30 UTC | Jul 11, 16:30 UTC | 1h 0m |
| 2026-07-11 | BJC → BJC | Jul 11, 12:15 UTC | Jul 11, 13:45 UTC | 1h 30m |
| 2026-07-10 | - | Jul 10, 22:15 UTC | Jul 11, 00:00 UTC | 1h 45m |
| 2026-07-10 | - | Jul 10, 20:10 UTC | Jul 10, 21:10 UTC | 1h 0m |
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 Jul 25, 15:55 UTC.