Not currently tracked · last seen 15h ago
- Flights observed
- 125 showing last 50
- Avg flight time
- 1h 27m
- Typical route
- GLO → GLO
- Last seen
- 15h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | - | May 29, 14:50 UTC | May 29, 16:45 UTC | 1h 55m |
| 2026-05-29 | GLO → GLO | May 29, 12:35 UTC | May 29, 13:55 UTC | 1h 20m |
| 2026-05-29 | - | May 29, 09:40 UTC | May 29, 11:15 UTC | 1h 35m |
| 2026-05-28 | - | May 28, 15:10 UTC | May 28, 16:50 UTC | 1h 40m |
| 2026-05-28 | GLO → GLO | May 28, 13:05 UTC | May 28, 14:20 UTC | 1h 15m |
| 2026-05-28 | GLO → GLO | May 28, 10:00 UTC | May 28, 12:20 UTC | 2h 20m |
| 2026-05-27 | - | May 27, 15:20 UTC | May 27, 17:05 UTC | 1h 45m |
| 2026-05-27 | GLO → GLO | May 27, 09:40 UTC | May 27, 11:35 UTC | 1h 55m |
| 2026-05-26 | - | May 26, 15:29 UTC | May 26, 16:40 UTC | 1h 10m |
| 2026-05-26 | GLO → GLO | May 26, 13:04 UTC | May 26, 14:40 UTC | 1h 35m |
| 2026-05-25 | GLO → GLO | May 25, 08:55 UTC | May 25, 09:45 UTC | 50m |
| 2026-05-23 | - | May 23, 11:50 UTC | May 23, 13:35 UTC | 1h 45m |
| 2026-05-23 | - | May 23, 08:20 UTC | May 23, 09:40 UTC | 1h 20m |
| 2026-05-22 | GLO → GLO | May 22, 13:20 UTC | May 22, 15:15 UTC | 1h 55m |
| 2026-05-22 | - | May 22, 11:20 UTC | May 22, 12:35 UTC | 1h 16m |
| 2026-05-22 | GLO → GLO | May 22, 08:35 UTC | May 22, 10:10 UTC | 1h 35m |
| 2026-05-21 | - | May 21, 08:30 UTC | May 21, 10:20 UTC | 1h 50m |
| 2026-05-20 | - | May 20, 16:10 UTC | May 20, 17:50 UTC | 1h 40m |
| 2026-05-20 | - | May 20, 11:00 UTC | May 20, 12:45 UTC | 1h 45m |
| 2026-05-18 | GLO → GLO | May 18, 14:50 UTC | May 18, 15:55 UTC | 1h 5m |
| 2026-05-18 | - | May 18, 11:15 UTC | May 18, 13:00 UTC | 1h 45m |
| 2026-05-16 | - | May 16, 11:11 UTC | May 16, 12:25 UTC | 1h 15m |
| 2026-05-16 | - | May 16, 08:46 UTC | May 16, 09:56 UTC | 1h 10m |
| 2026-05-15 | GLO → GLO | May 15, 17:35 UTC | May 15, 18:30 UTC | 55m |
| 2026-05-15 | GLO → GLO | May 15, 15:55 UTC | May 15, 17:05 UTC | 1h 10m |
| 2026-05-15 | - | May 15, 13:35 UTC | May 15, 14:50 UTC | 1h 14m |
| 2026-05-15 | GLO → GLO | May 15, 11:40 UTC | May 15, 12:50 UTC | 1h 10m |
| 2026-05-15 | - | May 15, 09:00 UTC | May 15, 10:50 UTC | 1h 50m |
| 2026-05-14 | - | May 14, 17:00 UTC | May 14, 17:15 UTC | 15m |
| 2026-05-14 | - | May 14, 15:20 UTC | May 14, 16:35 UTC | 1h 15m |
| 2026-05-14 | - | May 14, 10:35 UTC | May 14, 11:40 UTC | 1h 5m |
| 2026-05-13 | GLO → GLO | May 13, 14:55 UTC | May 13, 16:45 UTC | 1h 50m |
| 2026-05-13 | GLO → GLO | May 13, 14:00 UTC | May 13, 14:10 UTC | 10m |
| 2026-05-13 | GLO → GLO | May 13, 13:10 UTC | May 13, 13:55 UTC | 45m |
| 2026-05-13 | GLO → GLO | May 13, 11:15 UTC | May 13, 12:20 UTC | 1h 5m |
| 2026-05-13 | - | May 13, 08:05 UTC | May 13, 09:55 UTC | 1h 50m |
| 2026-05-12 | - | May 12, 16:45 UTC | May 12, 18:20 UTC | 1h 35m |
| 2026-05-12 | - | May 12, 14:20 UTC | May 12, 16:00 UTC | 1h 40m |
| 2026-05-12 | - | May 12, 11:15 UTC | May 12, 13:15 UTC | 2h 0m |
| 2026-05-11 | - | May 11, 15:50 UTC | May 11, 17:45 UTC | 1h 55m |
| 2026-05-11 | - | May 11, 11:05 UTC | May 11, 13:10 UTC | 2h 5m |
| 2026-05-10 | GLO → GLO | May 10, 15:39 UTC | May 10, 17:15 UTC | 1h 35m |
| 2026-05-10 | GLO → GLO | May 10, 13:35 UTC | May 10, 14:40 UTC | 1h 5m |
| 2026-05-10 | - | May 10, 11:10 UTC | May 10, 12:59 UTC | 1h 50m |
| 2026-05-09 | - | May 9, 15:40 UTC | May 9, 16:55 UTC | 1h 15m |
| 2026-05-09 | - | May 9, 11:10 UTC | May 9, 12:45 UTC | 1h 35m |
| 2026-05-07 | GLO → GLO | May 7, 15:20 UTC | May 7, 16:25 UTC | 1h 5m |
| 2026-05-07 | - | May 7, 13:05 UTC | May 7, 14:35 UTC | 1h 30m |
| 2026-05-07 | GLO → GLO | May 7, 10:45 UTC | May 7, 12:05 UTC | 1h 20m |
| 2026-05-07 | - | May 7, 08:10 UTC | May 7, 10:00 UTC | 1h 50m |
Specifications
| Registration | G-COMS |
| Aircraft type | DIAMOND DA-42 Guardian (DA42) |
| Mode-S code | 407B4B · 20075513 (octal) |
Looking for transponder-level data? View the Mode-S 407B4B page for country allocation, callsign history, and ADS-B signal details.
G-COMS frequently asked
What type of aircraft is G-COMS?
G-COMS is a DIAMOND DA-42 Guardian (ICAO type code DA42).
What is the Mode-S transponder code for G-COMS?
G-COMS broadcasts on Mode-S (ICAO 24-bit) address 407B4B (octal 20075513). View the transponder page.
What route does G-COMS typically fly?
G-COMS most frequently flies between GLO and GLO based on observed flights.
Where is G-COMS right now?
G-COMS is not currently being tracked; last seen 15h ago.