Not currently tracked · last seen 1d ago
- Flights observed
- 38
- Avg flight time
- 24m
- Typical route
- -
- Last seen
- 1d ago
Last known area
Recent flights last 38
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-17 | - | Jul 17, 23:35 UTC | Jul 18, 00:15 UTC | 40m |
| 2026-07-17 | - | Jul 17, 21:25 UTC | Jul 17, 21:44 UTC | 20m |
| 2026-07-14 | - | Jul 14, 02:50 UTC | Jul 14, 03:00 UTC | 10m |
| 2026-07-11 | - | Jul 11, 21:10 UTC | Jul 11, 21:50 UTC | 40m |
| 2026-07-06 | - | Jul 6, 23:40 UTC | Jul 6, 23:55 UTC | 15m |
| 2026-05-30 | - | May 30, 18:45 UTC | May 30, 18:55 UTC | 10m |
| 2026-05-26 | - | May 26, 01:05 UTC | May 26, 01:34 UTC | 30m |
| 2026-05-25 | - | May 25, 22:40 UTC | May 25, 23:04 UTC | 25m |
| 2026-05-25 | - | May 25, 02:00 UTC | May 25, 02:25 UTC | 25m |
| 2026-05-06 | - | May 6, 00:10 UTC | May 6, 00:31 UTC | 20m |
| 2026-05-05 | - | May 5, 22:10 UTC | May 5, 22:20 UTC | 10m |
| 2026-05-05 | - | May 5, 21:05 UTC | May 5, 21:20 UTC | 15m |
| 2026-05-04 | - | May 4, 04:00 UTC | May 4, 04:09 UTC | 10m |
| 2026-05-04 | - | May 4, 01:20 UTC | May 4, 01:35 UTC | 15m |
| 2026-05-03 | - | May 3, 18:14 UTC | May 3, 19:00 UTC | 45m |
| 2026-05-03 | - | May 3, 16:20 UTC | May 3, 16:40 UTC | 20m |
| 2026-05-03 | - | May 3, 03:05 UTC | May 3, 03:15 UTC | 10m |
| 2026-05-02 | - | May 2, 20:50 UTC | May 2, 21:00 UTC | 10m |
| 2026-05-02 | - | May 2, 20:20 UTC | May 2, 20:40 UTC | 20m |
| 2026-05-02 | - | May 2, 15:30 UTC | May 2, 16:10 UTC | 40m |
| 2026-05-02 | - | May 2, 14:50 UTC | May 2, 15:00 UTC | 10m |
| 2026-05-01 | - | May 1, 04:15 UTC | May 1, 04:30 UTC | 15m |
| 2026-05-01 | - | May 1, 02:45 UTC | May 1, 03:20 UTC | 35m |
| 2026-05-01 | - | May 1, 00:10 UTC | May 1, 00:55 UTC | 45m |
| 2026-04-20 | - | Apr 20, 23:40 UTC | Apr 20, 23:55 UTC | 15m |
| 2026-04-20 | RNT → RNT | Apr 20, 22:35 UTC | Apr 20, 23:05 UTC | 30m |
| 2026-04-20 | - | Apr 20, 18:35 UTC | Apr 20, 19:00 UTC | 25m |
| 2026-04-20 | - | Apr 20, 04:40 UTC | Apr 20, 05:00 UTC | 20m |
| 2026-04-20 | - | Apr 20, 02:05 UTC | Apr 20, 03:05 UTC | 1h 0m |
| 2026-04-20 | - | Apr 20, 01:05 UTC | Apr 20, 01:15 UTC | 10m |
| 2026-04-19 | - | Apr 19, 23:20 UTC | Apr 20, 00:15 UTC | 55m |
| 2026-04-19 | - | Apr 19, 22:10 UTC | Apr 19, 22:40 UTC | 30m |
| 2026-04-17 | - | Apr 17, 03:40 UTC | Apr 17, 03:50 UTC | 10m |
| 2026-04-16 | - | Apr 16, 23:35 UTC | Apr 17, 00:10 UTC | 35m |
| 2026-04-16 | - | Apr 16, 19:15 UTC | Apr 16, 19:35 UTC | 20m |
| 2026-04-16 | - | Apr 16, 18:35 UTC | Apr 16, 19:10 UTC | 35m |
| 2026-04-13 | - | Apr 13, 03:15 UTC | Apr 13, 03:25 UTC | 10m |
| 2026-04-12 | - | Apr 12, 23:55 UTC | Apr 13, 00:05 UTC | 10m |
Specifications
| Registration | N714CM |
| Operator | LAMBERT MICHAEL R |
| Mode-S code | A98B27 · 52305447 (octal) |
Looking for transponder-level data? View the Mode-S A98B27 page for country allocation, callsign history, and ADS-B signal details.
N714CM frequently asked
Who operates N714CM?
N714CM is operated by LAMBERT MICHAEL R.
What is the Mode-S transponder code for N714CM?
N714CM broadcasts on Mode-S (ICAO 24-bit) address A98B27 (octal 52305447). View the transponder page.
Where is N714CM right now?
N714CM is not currently being tracked; last seen 1d ago.