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