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