Position Info
Aircraft Info
Aircraft Model
Registration
Mode-S
Serial Number
SH3212
Last Activity
10 hours ago
Last Known Location
Yuma, AZ, United States






















| Date | Origin | STD | ATD | Destination | STA | Aircraft | Delay | Status | Duration | Replay |
|---|---|---|---|---|---|---|---|---|---|---|
| 2026 Feb 11 | Yuma Proving Ground(Yuma), AZ (LGF/KLGF) | 23:32 MST | SH33 (N312WW) | Departed | ||||||
| 2026 Feb 12 | First seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Status N/A | |||||||
| 2026 Feb 11 | Yuma Proving Ground(Yuma), AZ (LGF/KLGF) | 20:45 MST | SH33 (N312WW) | Departed | ||||||
| 2026 Feb 12 | First seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Status N/A | |||||||
| 2026 Feb 12 | First seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Status N/A | |||||||
| 2026 Feb 11 | First seen near Yuma Proving Ground(Yuma), AZ, United States | Yuma, AZ (YUM/KNYL) | SH33 (N312WW) | Landed 23:18 MST Landing time derived from ADS-B/Radar data | ||||||
| 2026 Feb 11 | First seen near Yuma Proving Ground(Yuma), AZ, United States | Yuma Proving Ground(Yuma), AZ (LGF/KLGF) | SH33 (N312WW) | Landed 22:33 MST Landing time derived from ADS-B/Radar data | ||||||
| 2026 Feb 10 | Yuma, AZ (YUM/KNYL) | 16:34 MST | Last seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Landed | |||||
| 2026 Feb 10 | First seen near Yuma Proving Ground(Yuma), AZ, United States | Yuma, AZ (YUM/KNYL) | SH33 (N312WW) | Landed 22:55 MST Landing time derived from ADS-B/Radar data | ||||||
| 2026 Feb 10 | First seen near Yuma Proving Ground(Yuma), AZ, United States | Last seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Landed | ||||||
| 2026 Feb 10 | First seen near Yuma Proving Ground(Yuma), AZ, United States | Last seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Landed | ||||||
| 2026 Feb 10 | First seen near Yuma Proving Ground(Yuma), AZ, United States | Last seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Landed | ||||||
| 2026 Feb 9 | Coolidge, AZ (KP08) | 14:35 MST | Last seen near Yuma Proving Ground(Yuma), AZ, United States | SH33 (N312WW) | Landed | |||||
| 2026 Feb 6 | Lake Havasu City, AZ (HII/KHII) | 14:39 MST | Coolidge, AZ (KP08) | SH33 (N491AK) | Landed 15:41 MST Landing time derived from ADS-B/Radar data | 01h02m | ||||
| 2026 Feb 6 | Lake Havasu City, AZ (HII/KHII) | 13:48 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 14:10 MST Landing time derived from ADS-B/Radar data | 00h21m | ||||
| 2026 Feb 6 | Lake Havasu City, AZ (HII/KHII) | 12:38 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 12:54 MST Landing time derived from ADS-B/Radar data | 00h16m | ||||
| 2026 Feb 6 | Lake Havasu City, AZ (HII/KHII) | 11:05 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 11:54 MST Landing time derived from ADS-B/Radar data | 00h49m | ||||
| 2026 Feb 6 | Lake Havasu City, AZ (HII/KHII) | 10:04 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 10:21 MST Landing time derived from ADS-B/Radar data | 00h17m | ||||
| 2026 Feb 5 | Lake Havasu City, AZ (HII/KHII) | 19:52 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 20:32 MST Landing time derived from ADS-B/Radar data | 00h39m | ||||
| 2026 Feb 5 | Lake Havasu City, AZ (HII/KHII) | 19:04 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 19:51 MST Landing time derived from ADS-B/Radar data | 00h47m | ||||
| 2026 Feb 5 | Lake Havasu City, AZ (HII/KHII) | 16:12 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 16:49 MST Landing time derived from ADS-B/Radar data | 00h37m | ||||
| 2026 Feb 5 | Lake Havasu City, AZ (HII/KHII) | 15:25 MST | Lake Havasu City, AZ (HII/KHII) | SH33 (N491AK) | Landed 16:11 MST Landing time derived from ADS-B/Radar data | 00h45m |
Flight history for SHERPA9 is available for a period over 7 days under our Basic subscription. More details here
More airport data is available for purchase. Please check our On Demand API.