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