Going north from the LA basin, I usually file 8K out, and 9K back in. At 8K, I don’t get handed off to LA Center, but instead to Mugu Approach (and then subsequently to Santa Barbara Approach). Most of the flight plans I see of mine and others seem to end their track log at the handoff from SoCal to Mugu.
Coming back, at 9K I go from Santa Barbara Tracon to LA Center to SoCal Tracon, and the track log is complete.
Just poking to make Flightaware of the terminated track logs at Mugu. I don’t know if it is because Mugu is a military Tracon, but it exists.
There does seem to be an issue with the radar data from Mugu controlled flights not making it to the system we get our data from. We’ve noticed the same with our home town Houston Center. :\
So if the track is dropped, the system doesn’t pick it up again when SB Approach takes over?
For that particular flight, I was in SB approach airspace for quite some time as San Luis Obispo already had 4 in the hold stack and was loathe to add another, so they vectored me all over creation, including into Vandenberg R-space just to keep me out of the stack. You should see my GPS track log. grin
We have an Eclipse 500 [N50EJ] that visits “us” fairly frequently that flies out of Buchanan Field (KCCR), Concord, CA. His flight histories frequently have large holes in them that I think are due to the military not passing on the complete tracks. The first RAPCON that picks up departures out of KCCR is Travis AFB (KSUU), which is to the NE of KCCR. NorCAL TRACON doesn’t start showing data until the departure has reached anywhere from 3900 to over 8000 ft. KSUU VORTAC is often reflected as the departure point of the flight.
Am curious if this is common with military airfields.
Speaking of San Luis, I’ve noticed that flights arriving from the north are dropped when they are handed off from Oakland Center to SB approach while arrivals from LA center are tracked to the ground. Most local flights don’t show up at all, SBA-SMX-SBP.
