Remember this off the UP -
This post was part of a series of posts where we were climbing the ICAO notified differences - Mount Non-compliance... (Ps Ironically since then, unlike most Mountains in the world, Mount NCN has grown to 3116 NCNs & 318 pages...UDB!)
This series culminated ( I think??) in the following post:
Okay so the reason for creating this thread is to; a) kick around and review Murky's latest bollocks SSP; b) attempt to scale (ICAO) Mount Non-compliance and establish whether c) it is possible to reign in the significant growth of NCNs prior to the upcoming ICAO/FAA audit...
MTF...P2
Quote:Newsflash: JQ is Gobble's new chopper pilot in Montreal!
I was half way up Mt Noncompliance contemplating yet another FF crevasse followed by a geyser of FF pony pooh, when lo and behold JQ and Gobbles were hovering above me in a shiny new Bell 406. Gobbles manned the winch and within minutes I was pass the FF PNR onwards and upwards….we proceeded to a point 343 metres above sea level and this is what we found…
Note: Creamy touched on this NCN briefly but perhaps it needs a bit more exploring to test the FF veracity on their proposed actions/inactions (by proxi notified differences) and it is also relevant in regards to the inquiry i.e. Flight recorders err OBRs…err CVRs!
1) FF said they were going to file a difference with ICAO by 31 October 2008! Did they?
Well after much teasing, fluffing, huffing and puffing mixed in with a series of expletives (FFS there must be literally thousands of notified differences to ICAO!) while reading over the extremely convoluted AIP SUP H12/11, I finally think I’ve found it in the Annex 6 section.
Here is what it says at Para 3.6.3.4.2.2…“No standards are specified in Australian legislation for the preservation of flight recorder records.”
However after you read the Annex 6 applicable reference, to which the FAA NCN supposedly refers, you begin to wonder if the notified difference really covers it??
Quote:6.3.11.2
To preserve flight recorder records, flight recorders shall be de-activated upon completion of flight time following an accident or incident. The flight recorders shall not be re-activated before their disposition as determined in accordance with Annex 13.
Note 1.— The need for removal of the flight recorder records from the aircraft will be determined by the investigation authority in the State conducting the investigation with due regard to the seriousness of an occurrence and the circumstances, including the impact on the operation.
Note 2.— The operator’s responsibilities regarding the retention of flight recorder records are contained in 11.6.
And 11.6
Quote:11.6 Flight recorder records
An operator shall ensure, to the extent possible, in the event the aeroplane becomes involved in an accident or incident, the preservation of all related flight recorder records and, if necessary, the associated flight recorders, and their retention in safe custody pending their disposition as determined in accordance with Annex 13.
I also question the paragraph reference ‘3.6.3.4.2.2’ (or any of the para references for that matter) and what on earth the correlation is to the applicable ICAO reference.
Note: Just out of interest I decided to explore our ANZAC ‘brothers in arms’ over the ditch and how they sort out compliance with the ICAO Annexes, in particular Annex 6. Here is what I found ‘Click Here’.
Very user friendly they even have a web page devoted to ICAO Compliance……yet another tick for the Kiwi system!
Anyway back to the FF promised actions and implementation dates…
2) “Address issue during CASR Part 91 drafting and development”…by 31 December 2008…hmm got a feeling this is heading for another FF crevasse but I could be wrong??
Ah that would be a no and also answers this proposed action by FF… 3) “Develop and promulgate CASR Part 91” by 31 December 2009!
So the jury is out but my bet is on a majority vote of 12 on this NCN!
Doin a Sundy arvo Kelpie!
This post was part of a series of posts where we were climbing the ICAO notified differences - Mount Non-compliance... (Ps Ironically since then, unlike most Mountains in the world, Mount NCN has grown to 3116 NCNs & 318 pages...UDB!)
This series culminated ( I think??) in the following post:
Quote:“The future conundrum of Annex 19”
Started a review of the proposed Annex 19 but first a quote from PAIN post #1696 , which is particularly pertinent…
“The proposed ICAO Annex 19, is designed, in part, to assist less fortunate countries achieve compliance with ICAO benchmarks. The Australia - ICAO final report on Safety Oversight Audit of Australia (Feb 2008) released January 2009 provides an excellent starting point for comparison.
There is ever a widening gap between ICAO and the existing Australian version. Annex 19 is about to make that gap almost too large to span. The issues need to be addressed, urgently and properly if Australia is to retain a tenuous hold on its current classification.”
So to the review and warning this is a long post!
From Page 19 of Annex 19:
Quote:3.1.2 The acceptable level of safety performance to be achieved shall be established by the State.
Note.— An acceptable level of safety performance for the State can be demonstrated through the implementation and maintenance of the SSP as well as safety performance indicators and targets showing that safety is effectively managed, built on the foundation of implementation of existing safety-related SARPs.
This means both FF and ATSBeaker will have to define what are acceptable levels of safety for different types of aviation and how they will measure those levels, probably with leading and lagging safety indicators. That way, all parties will know what they're being judged against, and FF will be called to account if (as is the norm) they launch an original punitive frolic.
From page 26 (my bold):
Quote:3.3 The State shall ensure that inspectors are provided with guidance that addresses ethics, personal conduct and the avoidance of actual or perceived conflicts of interest in the performance of official duties.
Well, well Houston we may have a problem?? Not very accommodating for all those imbedded sociopaths like Wodger and that camp guy ‘Bull’.
Then there is page 27 which is headed ‘Resolution of safety issues’(my bold):
Quote:8.1 The State shall use a documented process to take appropriate corrective actions, up to and including enforcement measures, to resolve identified safety issues.
8.2 The State shall ensure that identified safety issues are resolved in a timely manner through a system which monitors and records progress, including actions taken by service providers in resolving such issues.
It also looks like the 'gotcha loopholes' in the EM, SM (and presumably IM) may have to be revisited and the ‘due process’ documentation required in those docs will have to be strongly adhered to or else!
Page 29 paragraphs 1.2 and 1.3 would appear to mean that FF and ATSBeaker would have to have in place accountable managers that are answerable for compliance with documented SSP procedures. Hmm…wonder how that will go down with the FF and bureau execs currently running the shop?
Next on page 30 we have ‘2.1 Hazard identification’ and ‘3.1 Safety performance monitoring and measurement’, which are less immediate issues for the State service providers. However given the recent track record of blaming and flogging pilots (e.g Dom) these parts of the SSP could potentially cause some major areas of discomfort down the track.
Quoting from page 33 (my bold):
Quote:1.3 Accident and incident investigation
The State has established an independent accident and incident investigation process, the sole objective of which is the prevention of accidents and incidents, and not the apportioning of blame or liability. Such investigations are in support of the management of safety in the State. In the operation of the SSP, the State maintains the independence of the accident and incident investigation organization from other State aviation organizations.
Well although the bureau is supposedly ‘independent’ there is one thing that this inquiry has shown and that is the reality is an entirely different matter... “ Beaker please explain!”
Heading of paragraph 1.4 is ‘Enforcement Policy’, and there is enough people on here (and elsewhere..AMROBA, DK, DJ etc) that have an opinion on how that’s working out for the ‘State’, hmm..“Third Reich comes to mind!”
Page 33 and paragraph 2.1 is headed ‘Safety requirements for the service provider’s SMS’. Which again places a requirement on FF to have in place the policies/procedures to ensure transparency in administration. To ensure ICAO compliance these policies will be periodically reviewed…not sure if the Doc’s going to like that too much!
Finally (for now at least) on page 34 we have:
Quote:3.1 Safety oversight
The State has established mechanisms to ensure effective monitoring of the eight critical elements of the safety oversight function. The State has also established mechanisms to ensure that the identification of hazards and the management of safety risks by service providers follow established regulatory controls (requirements, specific operating regulations and implementation policies).
These mechanisms include inspections, audits and surveys to ensure that regulatory safety risk controls are appropriately integrated into the service provider’s SMS, that they are being practised as designed, and that the regulatory controls have the intended effect on safety risks.
Fairly long winded I know, however it would appear that FF must have in place a robust fully accountable framework for administering the SSP.
Yeah like that’s going to happen while the present numbnuts are minding the Fort??
Much more to follow me thinks!
Okay so the reason for creating this thread is to; a) kick around and review Murky's latest bollocks SSP; b) attempt to scale (ICAO) Mount Non-compliance and establish whether c) it is possible to reign in the significant growth of NCNs prior to the upcoming ICAO/FAA audit...
MTF...P2