posted on Sep, 1 2012 @ 11:30 AM
reply to post by boomer135
As you surmised, the sudden appearance of the 737 is due to the filter on the FAA feed. There have been one or two occasions where the filter didn't
work, both on the Beechcraft IIRC, but not in a long time. I will dig up a track and post it later. As far as I can tell now, Nellis has no bugs in
the FAA feed filter. There should be a post I did on ATS a few years ago where commercial traffic was routed south of Groom Lake. Unlike the
planefinder.net BS tracking, these flights were over the range in fact since they were detected first with ADS-B from a Vegas area resident who
alerted me to the incursion.
I can understand why the Janets act like "real" airlines coming out of Vegas, i.e. filing IFR flight plans and such. Once over the range, the
landings are visual nearly all the time. So you would think a flight from Groom to the TTR would just be visual, but for the 737s, that doesn't seem
to be the case. This could be as simple as insurance rules or some standard operating procedure from the DoD. Certainly flight following is a good
idea for a 737. In any event, the IFR wasn't cancelled for a VFR direct flight. They just flew direct and let the tracking happen. Now maybe that was
The fatal crash of N27RA probably took a similar direct route. It crashed 7 miles southeast of the TTR. At one time there was a google earth marker by
the suspected crash site, but it has been removed. It is on restricted land, so other than for historic purposes, I'm not sure how useful the marker
Google is a very compromised company due to the federal and military contracts they have. There are obvious crap google earth community markers that
have never been removed, but some of the useful markers tend to go away.