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