I just recently completed the ADS-B upgrade. On the last few IFR flights up and down the east coast, I have had ATC call out VFR traffic that they had radar paint on, and even though I could see the traffic visually, it wasn’t showing up on my ADS-B feed.
You know when a controller says ‘I’m not talking to him’, it’s not always because it’s non-participating VFR traffic.....
It’s fascinating to me that in the timeframe between the Cerritos accident and all the work done to mitigate that type of collision, we’ve already gone from “thank goodness he vectored me around that traffic” to “traffic vectors are annoying”. LOL.
What was once a fiery ball of 727 and Cessna death less than one generation ago is now “turn 20 right? You’ve GOT to be kidding me!” Hahahah.
First world problems.
Google the FAA ADS-B interactive coverage map and play with the altitude slider. There’s whole States with almost no coverage below 5000’ AGL.
It’s one of those things on which are found on either side of a river but that’s not important right now.
Thanks!
The first time I ever heard a controller say that to me was in San Diego. I was IFR flying into the same airport in the OP (MYF).
Ah yes, the classic ‘did someone else call, I was on the land line’!When the sector controller next to them or above/below them told them on the land line.
Find something? How is flying in Class E careless and reckless? It isn't. Even if you're flying in the approach path of a commercial airport. That's exactly why we have A, B, C, & D airspace. If the FAA doesn't want me flying it without taking to someone, they know how to make that happen. I fly out of an airport under a B's outer shelf. They're not supposed to bring big iron in under the shelf, but they do. And guess who gets called out when there's a conflict?
Is it self-absorbed disregard for others to follow the rules and expect others to as well? That's pretty bizarre. Is it self absorbed to expect controllers not to tell pilots, "Possible pilot deviation . . ." when it isn't remotely true?
Which would be further examples of bureaucratic arrogance. The only surefire way to cut that problem off at the pass is better airspace design to begin with. Although I am with those who say it is better to be talking to (and complying with) ATC when near busy airspace that accommodates heavy iron, I also agree that the fault does not lie with the nonparticipating VFR pilot if separation limits are violated because ATC failed to provide adequate separation from traffic in the underlying Class E.
Airspace will expand or contract based on the different player's agendas, political clout, and maybe a dash of common sense. Fully automated flight is as likely as fully automated boating. . .
Yes and just a few years ago over Brown field there was a miscommunication, I actually ATC was at least partly to blame for that, that resulted in a middar
So if I’m reading this right, we’re planning a POA fly in where we all do VFR laps around the outside edge of an inner Bravo ring under the shelf?
Flight of twenty?
And we’re all not going to utilize VFR advisories?
Whoooo hoooo! LOL.
As I recall, the Tower got primary cause on that one.
As long as @SixPapaCharlie pulls the chute, he can cross the line without penalty and we all lose to him.
1978 ... a 172 practicing instrument approaches “under the control of San Diego Approach Control” in CAVU conditions, rear-ended by the 727 turning a right base on a visual approach for 27. Crew reported traffic in sight, but there was a question whether he was seeing a second aircraft in the area.
