Not currently tracked · last seen 8h ago
- Flights observed
- 184 showing last 50
- Avg flight time
- 2h 40m
- Typical route
- BED → MDT
- Last seen
- 8h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 18:55 UTC | Jul 14, 00:50 UTC | 5h 55m |
| 2026-07-13 | - | Jul 13, 16:15 UTC | Jul 13, 17:05 UTC | 50m |
| 2026-07-12 | - | Jul 12, 07:40 UTC | Jul 12, 07:50 UTC | 10m |
| 2026-07-11 | - | Jul 11, 21:50 UTC | Jul 12, 04:45 UTC | 6h 55m |
| 2026-07-11 | - | Jul 11, 18:20 UTC | Jul 11, 19:45 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 20:30 UTC | Jul 10, 21:35 UTC | 1h 5m |
| 2026-07-10 | AZA → NKX | Jul 10, 14:45 UTC | Jul 10, 19:10 UTC | 4h 25m |
| 2026-07-09 | NKX → AZA | Jul 9, 03:05 UTC | Jul 9, 04:05 UTC | 1h 0m |
| 2026-07-09 | - | Jul 9, 00:35 UTC | Jul 9, 01:45 UTC | 1h 10m |
| 2026-07-08 | - | Jul 8, 20:35 UTC | Jul 8, 22:00 UTC | 1h 25m |
| 2026-07-08 | - | Jul 8, 13:55 UTC | Jul 8, 16:05 UTC | 2h 10m |
| 2026-07-08 | - | Jul 8, 01:40 UTC | Jul 8, 02:35 UTC | 55m |
| 2026-07-07 | - | Jul 7, 20:20 UTC | Jul 8, 00:25 UTC | 4h 5m |
| 2026-07-07 | - | Jul 7, 15:15 UTC | Jul 7, 18:40 UTC | 3h 25m |
| 2026-07-06 | - | Jul 6, 21:20 UTC | Jul 7, 00:50 UTC | 3h 30m |
| 2026-07-06 | - | Jul 6, 17:45 UTC | Jul 6, 19:40 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 14:00 UTC | Jul 6, 16:05 UTC | 2h 5m |
| 2026-07-06 | - | Jul 6, 04:00 UTC | Jul 6, 04:55 UTC | 55m |
| 2026-07-05 | - | Jul 5, 21:50 UTC | Jul 6, 02:25 UTC | 4h 35m |
| 2026-07-05 | - | Jul 5, 15:05 UTC | Jul 5, 19:10 UTC | 4h 5m |
| 2026-07-04 | - | Jul 4, 20:05 UTC | Jul 4, 23:55 UTC | 3h 50m |
| 2026-07-04 | - | Jul 4, 17:45 UTC | Jul 4, 18:25 UTC | 40m |
| 2026-07-04 | - | Jul 4, 14:20 UTC | Jul 4, 16:25 UTC | 2h 5m |
| 2026-07-03 | - | Jul 3, 21:20 UTC | Jul 3, 21:50 UTC | 30m |
| 2026-07-03 | - | Jul 3, 17:55 UTC | Jul 3, 19:00 UTC | 1h 5m |
| 2026-07-03 | AZA → DEN | Jul 3, 15:00 UTC | Jul 3, 16:20 UTC | 1h 20m |
| 2026-07-03 | - | Jul 3, 02:35 UTC | Jul 3, 05:00 UTC | 2h 25m |
| 2026-07-01 | - | Jul 1, 12:30 UTC | Jul 1, 13:25 UTC | 55m |
| 2026-06-30 | - | Jun 30, 20:05 UTC | Jun 30, 21:20 UTC | 1h 15m |
| 2026-06-30 | - | Jun 30, 16:25 UTC | Jun 30, 18:25 UTC | 2h 0m |
| 2026-06-30 | - | Jun 30, 13:55 UTC | Jun 30, 15:00 UTC | 1h 5m |
| 2026-06-29 | - | Jun 29, 22:59 UTC | Jun 30, 00:20 UTC | 1h 20m |
| 2026-06-29 | - | Jun 29, 20:09 UTC | Jun 29, 21:24 UTC | 1h 15m |
| 2026-06-29 | OAK → HRL | Jun 29, 15:39 UTC | Jun 29, 17:40 UTC | 2h 0m |
| 2026-06-28 | - | Jun 28, 23:20 UTC | Jun 29, 01:34 UTC | 2h 15m |
| 2026-06-28 | - | Jun 28, 15:14 UTC | Jun 28, 21:55 UTC | 6h 40m |
| 2026-06-28 | - | Jun 28, 00:20 UTC | Jun 28, 01:10 UTC | 50m |
| 2026-06-27 | - | Jun 27, 08:25 UTC | Jun 27, 10:45 UTC | 2h 20m |
| 2026-06-27 | - | Jun 27, 00:10 UTC | Jun 27, 04:19 UTC | 4h 10m |
| 2026-06-26 | SAP → AEX | Jun 26, 15:20 UTC | Jun 26, 22:19 UTC | 7h 0m |
| 2026-06-26 | BED → MDT | Jun 26, 12:29 UTC | Jun 26, 13:55 UTC | 1h 25m |
| 2026-06-25 | - | Jun 25, 15:50 UTC | Jun 25, 22:54 UTC | 7h 5m |
| 2026-06-25 | - | Jun 25, 13:24 UTC | Jun 25, 14:20 UTC | 55m |
| 2026-06-23 | - | Jun 23, 18:50 UTC | Jun 23, 21:39 UTC | 2h 50m |
| 2026-06-23 | BED → MDT | Jun 23, 13:00 UTC | Jun 23, 15:19 UTC | 2h 20m |
| 2026-06-22 | - | Jun 22, 15:40 UTC | Jun 22, 21:49 UTC | 6h 10m |
| 2026-06-22 | HRL → AEX | Jun 22, 12:00 UTC | Jun 22, 13:49 UTC | 1h 50m |
| 2026-06-20 | - | Jun 20, 18:59 UTC | Jun 20, 23:25 UTC | 4h 25m |
| 2026-06-20 | - | Jun 20, 10:59 UTC | Jun 20, 16:14 UTC | 5h 15m |
| 2026-06-19 | - | Jun 19, 18:44 UTC | Jun 19, 22:55 UTC | 4h 10m |
Specifications
| Registration | N278GX |
| Operator | UMB BANK NA TRUSTEE |
| Mode-S code | A2C4E0 · 50542340 (octal) |
Looking for transponder-level data? View the Mode-S A2C4E0 page for country allocation, callsign history, and ADS-B signal details.
N278GX frequently asked
Who operates N278GX?
N278GX is operated by UMB BANK NA TRUSTEE.
What is the Mode-S transponder code for N278GX?
N278GX broadcasts on Mode-S (ICAO 24-bit) address A2C4E0 (octal 50542340). View the transponder page.
What route does N278GX typically fly?
N278GX most frequently flies between BED and MDT based on observed flights.
Where is N278GX right now?
N278GX is not currently being tracked; last seen 8h ago.