If you want to terminally drift your own thread you xxxxxx, so be it
As previously posted by one of my colleagues:
I mistakenly thought that after this terrible accident that there would be a quick move to utilise the radar properly in this area – i.e. introduce new procedures or Class E airspace. Of course, this has not happened.
Prior to this crash not all RNAV approach points were available to ATC to insert into flight plans, so if a flight was cleared direct to such a point in E airspace or a pilot advised he was doing so in G airspace we would just expect him to be up to 15 NM away from his planned route.
Now the points have been defined and it has been indicated to ATC that we must monitor tracking and advise discrepancies, regardless of the class of airspace.
Of course, this has not happened.
Of course, you have got it wrong again.
The ATSB report makes it quite clear the controller WAS monitoring the track of the aircraft, he was just confused about which point the flight was heading for. Despite the points not being defined the discrepancy WAS noted, but the when the ATC weighed the probabilities of he or the GPS being wrong he decided he must have got it wrong. We all know better now.
Except you apparently. By the way, while you are barking at the base of you NAS tree, the Seasprite is getting away over there...