Not currently tracked · last seen 6h ago
- Flights observed
- 572 showing last 50
- Avg flight time
- 1h 14m
- Typical route
- SAN → SFO
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-15 | - | Jul 15, 02:05 UTC | Jul 15, 02:20 UTC | 15m |
| 2026-07-15 | - | Jul 15, 00:30 UTC | Jul 15, 01:15 UTC | 45m |
| 2026-07-14 | - | Jul 14, 21:10 UTC | Jul 14, 23:05 UTC | 1h 54m |
| 2026-07-14 | BOI → PHX | Jul 14, 21:15 UTC | Jul 14, 23:02 UTC | 1h 47m |
| 2026-07-14 | BUR → BOI | Jul 14, 18:22 UTC | Jul 14, 19:39 UTC | 1h 17m |
| 2026-07-14 | - | Jul 14, 18:15 UTC | Jul 14, 19:45 UTC | 1h 30m |
| 2026-07-14 | - | Jul 14, 16:05 UTC | Jul 14, 17:05 UTC | 1h 0m |
| 2026-07-14 | - | Jul 14, 15:15 UTC | Jul 14, 15:30 UTC | 15m |
| 2026-07-14 | GEG → BOI | Jul 14, 02:46 UTC | Jul 14, 03:16 UTC | 30m |
| 2026-07-14 | - | Jul 14, 02:30 UTC | Jul 14, 03:20 UTC | 50m |
| 2026-07-14 | - | Jul 14, 00:50 UTC | Jul 14, 01:35 UTC | 45m |
| 2026-07-13 | - | Jul 13, 20:00 UTC | Jul 13, 23:55 UTC | 3h 55m |
| 2026-07-13 | - | Jul 13, 17:45 UTC | Jul 13, 18:50 UTC | 1h 5m |
| 2026-07-13 | MSO → SEA | Jul 13, 17:43 UTC | Jul 13, 18:46 UTC | 1h 3m |
| 2026-07-13 | - | Jul 13, 15:45 UTC | Jul 13, 16:30 UTC | 45m |
| 2026-07-13 | SEA → MSO | Jul 13, 15:26 UTC | Jul 13, 16:39 UTC | 1h 13m |
| 2026-07-13 | - | Jul 13, 13:10 UTC | Jul 13, 13:50 UTC | 40m |
| 2026-07-13 | - | Jul 13, 03:01 UTC | Jul 13, 03:50 UTC | 50m |
| 2026-07-12 | - | Jul 12, 23:10 UTC | Jul 13, 00:05 UTC | 55m |
| 2026-07-12 | - | Jul 12, 20:30 UTC | Jul 12, 21:45 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 18:01 UTC | Jul 12, 18:35 UTC | 35m |
| 2026-07-12 | - | Jul 12, 15:40 UTC | Jul 12, 16:25 UTC | 45m |
| 2026-07-12 | SEA → BLI | Jul 12, 06:30 UTC | Jul 12, 06:55 UTC | 25m |
| 2026-07-11 | SEA → SEA | Jul 11, 22:50 UTC | Jul 12, 03:30 UTC | 4h 40m |
| 2026-07-11 | - | Jul 11, 21:00 UTC | Jul 11, 21:45 UTC | 45m |
| 2026-07-11 | SEA → EUG | Jul 11, 19:05 UTC | Jul 11, 19:55 UTC | 50m |
| 2026-07-11 | SLC → SEA | Jul 11, 15:35 UTC | Jul 11, 17:35 UTC | 2h 0m |
| 2026-07-11 | SLC → SEA | Jul 11, 15:31 UTC | Jul 11, 17:30 UTC | 1h 59m |
| 2026-07-11 | SAN → SLC | Jul 11, 01:55 UTC | Jul 11, 03:25 UTC | 1h 30m |
| 2026-07-10 | SFO → SAN | Jul 10, 23:35 UTC | Jul 11, 00:50 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 21:00 UTC | Jul 10, 22:00 UTC | 1h 0m |
| 2026-07-10 | SAN → SFO | Jul 10, 20:55 UTC | Jul 10, 21:59 UTC | 1h 4m |
| 2026-07-10 | - | Jul 10, 18:40 UTC | Jul 10, 19:55 UTC | 1h 15m |
| 2026-07-10 | SAN → STS | Jul 10, 15:49 UTC | Jul 10, 16:59 UTC | 1h 10m |
| 2026-07-10 | - | Jul 10, 15:45 UTC | Jul 10, 17:00 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 13:25 UTC | Jul 10, 14:35 UTC | 1h 10m |
| 2026-07-10 | - | Jul 10, 04:20 UTC | Jul 10, 05:25 UTC | 1h 5m |
| 2026-07-10 | - | Jul 10, 01:40 UTC | Jul 10, 02:45 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 23:15 UTC | Jul 10, 00:30 UTC | 1h 15m |
| 2026-07-09 | - | Jul 9, 21:15 UTC | Jul 9, 22:10 UTC | 55m |
| 2026-07-09 | SAN → SFO | Jul 9, 19:05 UTC | Jul 9, 20:10 UTC | 1h 5m |
| 2026-07-09 | SAN → SFO | Jul 9, 18:50 UTC | Jul 9, 20:09 UTC | 1h 19m |
| 2026-07-09 | - | Jul 9, 15:05 UTC | Jul 9, 17:05 UTC | 2h 0m |
| 2026-07-09 | - | Jul 9, 02:35 UTC | Jul 9, 04:30 UTC | 1h 55m |
| 2026-07-09 | SAN → EUG | Jul 9, 02:41 UTC | Jul 9, 04:27 UTC | 1h 46m |
| 2026-07-09 | LEX → ORD | Jul 9, 00:30 UTC | Jul 9, 01:35 UTC | 1h 5m |
| 2026-07-08 | ORD → LEX | Jul 8, 21:55 UTC | Jul 8, 23:25 UTC | 1h 30m |
| 2026-07-08 | STS → PSP | Jul 8, 19:45 UTC | Jul 8, 20:10 UTC | 25m |
| 2026-07-08 | - | Jul 8, 18:10 UTC | Jul 8, 18:40 UTC | 30m |
| 2026-07-08 | SAN → SMF | Jul 8, 14:45 UTC | Jul 8, 16:20 UTC | 1h 35m |
Specifications
| Registration | N413SY |
| Operator | SKYWEST AIRLINES INC |
| Mode-S code | A4E0EC · 51160354 (octal) |
Looking for transponder-level data? View the Mode-S A4E0EC page for country allocation, callsign history, and ADS-B signal details.
N413SY frequently asked
Who operates N413SY?
N413SY is operated by SKYWEST AIRLINES INC.
What is the Mode-S transponder code for N413SY?
N413SY broadcasts on Mode-S (ICAO 24-bit) address A4E0EC (octal 51160354). View the transponder page.
What route does N413SY typically fly?
N413SY most frequently flies between SAN and SFO based on observed flights.
Where is N413SY right now?
N413SY is not currently being tracked; last seen 6h ago.