Not currently tracked · last seen 3d ago
- Flights observed
- 27
- Avg flight time
- 41m
- Typical route
- -
- Last seen
- 3d ago
Last known area
Recent flights last 27
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | - | May 30, 14:15 UTC | May 30, 14:40 UTC | 25m |
| 2026-05-30 | - | May 30, 13:15 UTC | May 30, 13:35 UTC | 20m |
| 2026-05-30 | - | May 30, 12:25 UTC | May 30, 12:45 UTC | 20m |
| 2026-05-30 | - | May 30, 11:15 UTC | May 30, 11:25 UTC | 10m |
| 2026-05-30 | - | May 30, 09:50 UTC | May 30, 10:35 UTC | 45m |
| 2026-05-30 | - | May 30, 08:35 UTC | May 30, 08:55 UTC | 20m |
| 2026-05-30 | - | May 30, 06:45 UTC | May 30, 07:10 UTC | 25m |
| 2026-05-25 | - | May 25, 14:10 UTC | May 25, 14:40 UTC | 30m |
| 2026-05-25 | - | May 25, 07:00 UTC | May 25, 07:30 UTC | 30m |
| 2026-05-21 | - | May 21, 14:55 UTC | May 21, 16:10 UTC | 1h 15m |
| 2026-05-21 | - | May 21, 09:00 UTC | May 21, 10:30 UTC | 1h 30m |
| 2026-05-18 | - | May 18, 14:00 UTC | May 18, 15:35 UTC | 1h 35m |
| 2026-05-18 | - | May 18, 09:35 UTC | May 18, 11:00 UTC | 1h 25m |
| 2026-05-16 | - | May 16, 11:05 UTC | May 16, 11:51 UTC | 45m |
| 2026-05-16 | - | May 16, 08:46 UTC | May 16, 09:25 UTC | 40m |
| 2026-05-10 | - | May 10, 14:14 UTC | May 10, 14:40 UTC | 25m |
| 2026-05-09 | - | May 9, 10:05 UTC | May 9, 10:35 UTC | 30m |
| 2026-05-08 | - | May 8, 14:20 UTC | May 8, 15:05 UTC | 45m |
| 2026-04-29 | - | Apr 29, 10:50 UTC | Apr 29, 11:25 UTC | 35m |
| 2026-04-19 | - | Apr 19, 15:00 UTC | Apr 19, 15:50 UTC | 50m |
| 2026-04-19 | - | Apr 19, 11:55 UTC | Apr 19, 12:35 UTC | 40m |
| 2026-04-18 | GRQ → LEY | Apr 18, 17:05 UTC | Apr 18, 17:35 UTC | 30m |
| 2026-04-18 | - | Apr 18, 15:40 UTC | Apr 18, 16:30 UTC | 50m |
| 2026-04-18 | - | Apr 18, 14:05 UTC | Apr 18, 14:50 UTC | 45m |
| 2026-04-15 | - | Apr 15, 14:05 UTC | Apr 15, 14:50 UTC | 44m |
| 2026-04-15 | - | Apr 15, 12:35 UTC | Apr 15, 12:55 UTC | 20m |
| 2026-04-15 | - | Apr 15, 10:10 UTC | Apr 15, 10:40 UTC | 30m |
Specifications
| Registration | PH-COM |
| Aircraft type | PIPER PA-30 Twin Comanche (PA30) |
| Mode-S code | 4844D5 · 22042325 (octal) |
Looking for transponder-level data? View the Mode-S 4844D5 page for country allocation, callsign history, and ADS-B signal details.
PH-COM frequently asked
What type of aircraft is PH-COM?
PH-COM is a PIPER PA-30 Twin Comanche (ICAO type code PA30).
What is the Mode-S transponder code for PH-COM?
PH-COM broadcasts on Mode-S (ICAO 24-bit) address 4844D5 (octal 22042325). View the transponder page.
Where is PH-COM right now?
PH-COM is not currently being tracked; last seen 3d ago.