Skin Codes
In my earlier post, I recommended a procedure which would add an extra layer of safety to our current system, at little or no extra cost. It is heartening to see that the professionals on this forum have supported it. (The abusive posts from the ‘usual suspects’ have confirmed to me that it may be a good idea after all.)
Any good safety system relies upon many layers of defence. Those who
claim to be professional aviators and continue to mouth the ‘keep looking out of the window’ mantra with no other constructive thoughts fail to recognise this and their posts confirm their ignorance of basic safety management.
We use a multi-layered safety system on the roads: Driver training, licensing standards, road maintenance, road rules, law enforcement, vehicle maintenance, vehicle design standards, traffic signs, traffic lights, speed limits,
looking out of the window, ABS braking, seatbelts, airbags, crumple zones etc. Why is it that some people want to base everything on just one aspect of an overall safety system? Placing all of our eggs in this one fragile basket is bound to end up in a lot of egg on a lot of faces.
Whilst I mentioned ‘skin codes’ in that post, I felt that reliance on them might have a few problems. These include:
1. There are 4096 ‘theoretically’ available codes (with many allocated for discrete purposes and therefore not available.)
2. There are more than 11,000 aircraft on the Australian register.
3. Military, many RPT and internationals use call-signs other than their registrations.
4. TAAATS does not
currently support the maintenance of a database which will store code/call-sign relationships.
Possible solutions:
1. Allocate a ‘bin’ of codes (say 1001 to 1777) as a block of permanent codes.
2. Allow aircraft owners to apply for a ‘skin code’ if they meet certain criteria (for example: GA aircraft, mainly VFR use, mainly class G and E, not used internationally, based in or near radar coverage, uses registration as call-sign.)
3. Exclude any aircraft which does not use registration as call-sign.
4. Amend TAAATS software to:
a. Allow a database of code/call-sign relationships;
b. Immediately upon detection of a stored code, attach a call-sign label to the radar track (This could be done automatically, with
no controller input – but any risks of misallocation would need to be assessed and mitigated against);
c. Display this track in a HMI colour different to the current colours. I suggest a colour such as a mid to dark purple, which will be more dominant than the current black ‘not concerned’ colour, but less so than the greet ‘jurisdiction’ or blue ‘announced’ colour.
It is important to note, however that the original proposal could be implemented
now and at
no cost and does not rely upon skin codes. Skin codes would just make it better.
For those of you who have been able to provide constructive input into this discussion, thank you and please feel free to continue (e.g. Capn Laptop, Chief galah, triadic, ReadMyACARS, Chimbu chuckles, Four Seven Eleven, Niles Crane, ferris, Spodman, WhatWasThat, Woomera, snarek, coral, divingduck).
To the others, please don’t bother.
