On the ground · transponder active
- Flights observed
- 281 showing last 50
- Avg flight time
- 3h 45m
- Typical route
- RTM → AYT
- Last seen
- Jul 26, 21:15 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | RTM → NDR | Jul 26, 20:05 UTC | Jul 26, 21:15 UTC | 1h 10m |
| 2026-07-26 | AYT → RTM | Jul 26, 11:40 UTC | Jul 26, 15:30 UTC | 3h 50m |
| 2026-07-26 | RTM → AYT | Jul 26, 07:00 UTC | Jul 26, 10:10 UTC | 3h 10m |
| 2026-07-25 | RTM → LPA | Jul 25, 06:40 UTC | Jul 25, 16:15 UTC | 9h 35m |
| 2026-07-24 | - | Jul 24, 13:40 UTC | Jul 24, 17:10 UTC | 3h 30m |
| 2026-07-24 | RTM → TFS | Jul 24, 07:55 UTC | Jul 24, 12:05 UTC | 4h 10m |
| 2026-07-24 | CRL → LPA | Jul 24, 02:35 UTC | Jul 24, 05:05 UTC | 2h 30m |
| 2026-07-23 | - | Jul 23, 19:55 UTC | Jul 23, 22:35 UTC | 2h 40m |
| 2026-07-23 | - | Jul 23, 14:05 UTC | Jul 23, 17:40 UTC | 3h 35m |
| 2026-07-23 | - | Jul 23, 08:40 UTC | Jul 23, 12:45 UTC | 4h 5m |
| 2026-07-22 | - | Jul 22, 10:20 UTC | Jul 22, 18:20 UTC | 8h 0m |
| 2026-07-21 | - | Jul 21, 15:00 UTC | Jul 21, 18:40 UTC | 3h 40m |
| 2026-07-21 | RTM → LPA | Jul 21, 09:10 UTC | Jul 21, 13:05 UTC | 3h 55m |
| 2026-07-21 | CRL → LPA | Jul 21, 02:30 UTC | Jul 21, 05:05 UTC | 2h 35m |
| 2026-07-20 | - | Jul 20, 20:00 UTC | Jul 20, 22:45 UTC | 2h 45m |
| 2026-07-20 | - | Jul 20, 13:40 UTC | Jul 20, 17:20 UTC | 3h 40m |
| 2026-07-20 | - | Jul 20, 07:50 UTC | Jul 20, 12:05 UTC | 4h 15m |
| 2026-07-20 | CRL → LPA | Jul 20, 02:25 UTC | Jul 20, 05:00 UTC | 2h 35m |
| 2026-07-19 | - | Jul 19, 19:55 UTC | Jul 19, 22:40 UTC | 2h 45m |
| 2026-07-19 | - | Jul 19, 12:05 UTC | Jul 19, 15:50 UTC | 3h 45m |
| 2026-07-19 | RTM → AYT | Jul 19, 07:05 UTC | Jul 19, 10:20 UTC | 3h 15m |
| 2026-07-18 | - | Jul 18, 12:20 UTC | Jul 18, 16:00 UTC | 3h 40m |
| 2026-07-18 | RTM → LPA | Jul 18, 06:35 UTC | Jul 18, 10:35 UTC | 4h 0m |
| 2026-07-17 | - | Jul 17, 13:55 UTC | Jul 17, 17:30 UTC | 3h 35m |
| 2026-07-17 | - | Jul 17, 08:10 UTC | Jul 17, 12:19 UTC | 4h 10m |
| 2026-07-17 | - | Jul 17, 02:34 UTC | Jul 17, 05:10 UTC | 2h 35m |
| 2026-07-16 | - | Jul 16, 20:15 UTC | Jul 16, 23:05 UTC | 2h 50m |
| 2026-07-16 | - | Jul 16, 14:15 UTC | Jul 16, 17:49 UTC | 3h 35m |
| 2026-07-16 | - | Jul 16, 08:35 UTC | Jul 16, 12:44 UTC | 4h 10m |
| 2026-07-15 | - | Jul 15, 14:55 UTC | Jul 15, 18:40 UTC | 3h 45m |
| 2026-07-15 | - | Jul 15, 09:15 UTC | Jul 15, 13:30 UTC | 4h 15m |
| 2026-07-14 | RTM → RTM | Jul 14, 09:05 UTC | Jul 14, 18:40 UTC | 9h 35m |
| 2026-07-14 | MLN → RTM | Jul 14, 02:40 UTC | Jul 14, 05:05 UTC | 2h 25m |
| 2026-07-13 | - | Jul 13, 20:00 UTC | Jul 13, 22:45 UTC | 2h 45m |
| 2026-07-13 | - | Jul 13, 14:10 UTC | Jul 13, 17:40 UTC | 3h 30m |
| 2026-07-13 | - | Jul 13, 07:50 UTC | Jul 13, 12:10 UTC | 4h 20m |
| 2026-07-13 | - | Jul 13, 02:40 UTC | Jul 13, 05:05 UTC | 2h 25m |
| 2026-07-12 | - | Jul 12, 19:45 UTC | Jul 12, 22:35 UTC | 2h 50m |
| 2026-07-12 | - | Jul 12, 11:55 UTC | Jul 12, 15:40 UTC | 3h 45m |
| 2026-07-12 | RTM → AYT | Jul 12, 06:55 UTC | Jul 12, 10:20 UTC | 3h 25m |
| 2026-07-11 | - | Jul 11, 12:40 UTC | Jul 11, 16:10 UTC | 3h 30m |
| 2026-07-11 | - | Jul 11, 06:45 UTC | Jul 11, 10:40 UTC | 3h 55m |
| 2026-07-10 | - | Jul 10, 13:40 UTC | Jul 10, 17:20 UTC | 3h 40m |
| 2026-07-10 | - | Jul 10, 07:40 UTC | Jul 10, 11:50 UTC | 4h 10m |
| 2026-07-10 | - | Jul 10, 02:25 UTC | Jul 10, 05:05 UTC | 2h 40m |
| 2026-07-09 | - | Jul 9, 20:10 UTC | Jul 9, 22:50 UTC | 2h 40m |
| 2026-07-09 | - | Jul 9, 14:05 UTC | Jul 9, 17:45 UTC | 3h 40m |
| 2026-07-09 | - | Jul 9, 08:25 UTC | Jul 9, 12:30 UTC | 4h 5m |
| 2026-07-08 | - | Jul 8, 14:40 UTC | Jul 8, 18:30 UTC | 3h 50m |
| 2026-07-08 | - | Jul 8, 09:05 UTC | Jul 8, 13:15 UTC | 4h 10m |
Specifications
| Registration | PH-TFT |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 485A85 · 22055205 (octal) |
Looking for transponder-level data? View the Mode-S 485A85 page for country allocation, callsign history, and ADS-B signal details.
PH-TFT frequently asked
What type of aircraft is PH-TFT?
PH-TFT is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for PH-TFT?
PH-TFT broadcasts on Mode-S (ICAO 24-bit) address 485A85 (octal 22055205). View the transponder page.
What route does PH-TFT typically fly?
PH-TFT most frequently flies between RTM and AYT based on observed flights.
Where is PH-TFT right now?
PH-TFT is currently on the ground with its transponder active.