Not currently tracked · last seen 12h ago
- Flights observed
- 79 showing last 50
- Avg flight time
- 1h 16m
- Typical route
- SQL → SMO
- Last seen
- 12h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-17 | - | Jul 17, 19:35 UTC | Jul 17, 20:35 UTC | 1h 0m |
| 2026-07-17 | - | Jul 17, 12:25 UTC | Jul 17, 13:29 UTC | 1h 5m |
| 2026-07-16 | - | Jul 16, 21:15 UTC | Jul 16, 22:00 UTC | 45m |
| 2026-07-13 | - | Jul 13, 00:45 UTC | Jul 13, 01:25 UTC | 40m |
| 2026-07-12 | - | Jul 12, 21:45 UTC | Jul 12, 22:25 UTC | 40m |
| 2026-07-11 | SMO → SQL | Jul 11, 18:20 UTC | Jul 11, 19:25 UTC | 1h 5m |
| 2026-07-10 | - | Jul 10, 22:30 UTC | Jul 10, 23:40 UTC | 1h 10m |
| 2026-07-10 | - | Jul 10, 21:00 UTC | Jul 10, 21:40 UTC | 40m |
| 2026-07-07 | PAO → SQL | Jul 7, 20:45 UTC | Jul 7, 21:00 UTC | 15m |
| 2026-07-07 | - | Jul 7, 19:35 UTC | Jul 7, 20:10 UTC | 35m |
| 2026-07-07 | - | Jul 7, 17:40 UTC | Jul 7, 18:25 UTC | 45m |
| 2026-07-07 | - | Jul 7, 13:35 UTC | Jul 7, 15:55 UTC | 2h 20m |
| 2026-06-30 | RDM → RDM | Jun 30, 04:35 UTC | Jun 30, 05:00 UTC | 25m |
| 2026-06-28 | - | Jun 28, 22:34 UTC | Jun 29, 02:05 UTC | 3h 30m |
| 2026-06-28 | - | Jun 28, 21:14 UTC | Jun 28, 21:20 UTC | 5m |
| 2026-06-28 | - | Jun 28, 17:30 UTC | Jun 28, 17:39 UTC | 10m |
| 2026-06-28 | - | Jun 28, 14:30 UTC | Jun 28, 16:29 UTC | 2h 0m |
| 2026-06-28 | - | Jun 28, 00:04 UTC | Jun 28, 00:39 UTC | 35m |
| 2026-06-26 | - | Jun 26, 17:59 UTC | Jun 26, 18:09 UTC | 10m |
| 2026-06-26 | - | Jun 26, 15:29 UTC | Jun 26, 16:00 UTC | 30m |
| 2026-06-22 | - | Jun 22, 03:45 UTC | Jun 22, 06:39 UTC | 2h 55m |
| 2026-06-17 | - | Jun 17, 22:15 UTC | Jun 17, 22:40 UTC | 25m |
| 2026-06-17 | SQL → SMO | Jun 17, 20:25 UTC | Jun 17, 21:40 UTC | 1h 15m |
| 2026-06-16 | - | Jun 16, 18:55 UTC | Jun 16, 20:10 UTC | 1h 16m |
| 2026-06-16 | - | Jun 16, 16:15 UTC | Jun 16, 18:09 UTC | 1h 55m |
| 2026-06-14 | - | Jun 14, 16:05 UTC | Jun 14, 18:10 UTC | 2h 5m |
| 2026-06-14 | - | Jun 14, 03:15 UTC | Jun 14, 03:30 UTC | 15m |
| 2026-06-14 | - | Jun 14, 01:30 UTC | Jun 14, 02:40 UTC | 1h 10m |
| 2026-06-13 | - | Jun 13, 17:40 UTC | Jun 13, 18:40 UTC | 1h 0m |
| 2026-06-13 | - | Jun 13, 00:10 UTC | Jun 13, 01:25 UTC | 1h 15m |
| 2026-06-12 | - | Jun 12, 17:45 UTC | Jun 12, 19:00 UTC | 1h 15m |
| 2026-06-06 | - | Jun 6, 17:44 UTC | Jun 6, 20:05 UTC | 2h 20m |
| 2026-06-05 | - | Jun 5, 16:10 UTC | Jun 5, 19:10 UTC | 3h 0m |
| 2026-06-04 | - | Jun 4, 21:25 UTC | Jun 4, 23:40 UTC | 2h 15m |
| 2026-06-04 | - | Jun 4, 17:20 UTC | Jun 4, 18:30 UTC | 1h 10m |
| 2026-06-03 | - | Jun 3, 12:15 UTC | Jun 3, 15:15 UTC | 3h 0m |
| 2026-06-02 | - | Jun 2, 22:45 UTC | Jun 3, 02:25 UTC | 3h 40m |
| 2026-05-30 | - | May 30, 22:05 UTC | May 31, 00:30 UTC | 2h 25m |
| 2026-05-30 | SQL → EMT | May 30, 17:00 UTC | May 30, 18:10 UTC | 1h 10m |
| 2026-05-30 | - | May 30, 14:45 UTC | May 30, 16:25 UTC | 1h 40m |
| 2026-05-30 | - | May 30, 01:00 UTC | May 30, 01:30 UTC | 30m |
| 2026-05-29 | APC → PDX | May 29, 22:25 UTC | May 30, 00:10 UTC | 1h 45m |
| 2026-05-29 | - | May 29, 19:30 UTC | May 29, 21:25 UTC | 1h 55m |
| 2026-05-29 | - | May 29, 02:05 UTC | May 29, 02:25 UTC | 20m |
| 2026-05-28 | SQL → SMO | May 28, 02:50 UTC | May 28, 04:00 UTC | 1h 10m |
| 2026-05-25 | - | May 25, 23:10 UTC | May 25, 23:49 UTC | 40m |
| 2026-05-25 | - | May 25, 19:35 UTC | May 25, 20:45 UTC | 1h 10m |
| 2026-05-25 | SQL → VNY | May 25, 17:05 UTC | May 25, 18:10 UTC | 1h 5m |
| 2026-05-25 | - | May 25, 15:00 UTC | May 25, 15:40 UTC | 40m |
| 2026-05-23 | - | May 23, 17:25 UTC | May 23, 18:00 UTC | 35m |
Specifications
| Registration | N278TF |
| Operator | REGISTRATION PENDING |
| Mode-S code | A2C5E3 · 50542743 (octal) |
Looking for transponder-level data? View the Mode-S A2C5E3 page for country allocation, callsign history, and ADS-B signal details.
N278TF frequently asked
Who operates N278TF?
N278TF is operated by REGISTRATION PENDING.
What is the Mode-S transponder code for N278TF?
N278TF broadcasts on Mode-S (ICAO 24-bit) address A2C5E3 (octal 50542743). View the transponder page.
What route does N278TF typically fly?
N278TF most frequently flies between SQL and SMO based on observed flights.
Where is N278TF right now?
N278TF is not currently being tracked; last seen 12h ago.