Thread Rating:
  • 1 Vote(s) - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Times up for Pel_air MkII
#61
BRB brain teaser: The Iron Ring mole within?

Damn that Blind Freddy is good -  Wink

Still haven't worked out all the dots and complimentary dashes myself and yet BF is already second guessing the brain teaser plot...  Undecided

As many will be aware I have been otherwise engaged in hoovering up the ATSB ADREP/ECCAIRS aberration crumb trail and what I have discovered so far poses more troubling questions than answers. However I will try to step the BRB through the mess of scattered and fragmented crumbs in order to provide background to this year's AGM brain teaser... Wink  

 Quote from previous post: "..From that PDF it would appear that the original report was modified on 10/11/2015 at 8:13:02 am (click 'file' then click 'properties') by 'author' E.Hargreaves (ATSB REPCON Manager & ICAO co-ordinator)..." 

The date is interesting as it was 8 days out from the anniversary of the VH-NGA ditching. In the context of the re-opened investigation this should mean that a public interim statement was about to be released with details of the progress of the ongoing investigation.

Although not obliged to under Annex 13, most States tend to keep ICAO in the loop and forward the interim statement (e.g. MH370).

Given the nature of the VH-NGA re-investigation (findings from the Senate AAI inquiry & TSBC peer review) I believe EH has felt obliged; or was instructed to file a ADREP/ECCAIRS notification/progress report.

In that process it would appear that EH has discovered that the VH-NGA ditching had no prelim or original final report on file... Confused  

In an attempt to track any other similar aberrations/duck-ups I began to work my way through all Australian serious incidents and accidents notified to ICAO from 2008 till today.

That was when I noticed that a large volume of ATSB AAI prelim/final PDF reports were created and forwarded to ICAO ADREP/ECCAIRS in the same week the ATSB REPCON manager/ICAO co-ordinator modified the PDF copy of VH-NGA prelim report.

Most of the reports submitted to ICAO in that week and a bit were investigations from 2008 to 2010 and had final reports made public before 2012. This just so happens to correspond to when EH was appointed in the role as REPCON Manager.

For obvious reasons, this got me thinking to who it was that EH had replaced in the role...  Huh

Here is an extract from the previous manager's LinkedIn webpage:

Quote:former Manager, Notifications & Confidential Reporting

Company Name: Australian Transport Safety Bureau
Dates Employed: Nov 2001 – Apr 2014
Employment Duration: 12 yrs 6 mos
Location: Canberra

Oversight of the assessment and categorisation and data entry of all mandatory aviation safety incident reports and the ATSB's confidential reporting system (REPCON). Other responsibilities include:

Safety education coordinator and presenter
Database management including data extraction (non technical)
Change management board member
TSI Regulation reporting oversight and development
International Confidential Aviation Safety Systems (ICASS) member
 
Still many fascinating connections and parallels to explore with this individual but for the benefit of the BRB, I refer to the before (ATSB) & after (ATSB) vocation entries for SY:
Quote:Before:
[Image: AAEAAQAAAAAAAAPdAAAAJDRlYzVlY2Q0LWMxYWEt...OTYxMg.png]
Flight Data Officer/Research Officer/Administration
Company Name: Airservices Australia
Dates Employed: Jan 1990 – Nov 2001
Employment Duration: 11 yrs 11 mos
Location: Adelaide & Canberra

Joined as FDO in Adelaide and transferred to Canberra as an admin officer. Held positions in Regulation (pre CASA), AIS, Flow Management (database admin), HR and Environment (ESIR data management). Seconded to the ATSB for 3 months before ultimately transferring there 12 months later on promotion as the Database Administrator.


[/url][Image: AAEAAQAAAAAAAAayAAAAJDdjOWQ2MTc5LWE4ZDUt...ZTY1Zg.png]
Loadmaster

Company Name: Royal Australian Air Force
Dates Employed: Jul 1975 – Nov 1987
Employment Duration: 12 yrs 4 mos
Location: Canberra, Pearce, Sinai (Egypt)

[url=https://www.linkedin.com/company-beta/946571/]Operations and instructor on Iroquois (UH-1B/H) And Squirrel (AS350B). Total flying time 2,750 hours. Search & Rescue duties 2FTS at RAAF Pearce, WA. Peace keeping duties in the Sinai Peninsula between Aug 83 to Feb 84

After:

[Image: AAEAAQAAAAAAAAPdAAAAJDRlYzVlY2Q0LWMxYWEt...OTYxMg.png]
Data Analyst
Company Name: Airservices Australia
Dates Employed: Jul 2015 – Present
Employment Duration: 2 yrs
Location: Canberra, Australia
   
Which finally brings me to the BRB (pop quiz) brain teaser Wink : Q/ Why would such an experienced, long serving and faithful public servant, leave a secure middle management job with the ATSB, for an unexplained 15 month leave of absence, only to return to a lesser position with AirServices Australia?  Rolleyes  


MTF...P2  Tongue
Reply
#62
Ahem; (cough): if I may, I’d like to interrupt P2’s fun and games for a just moment, to mention the small revolution building within the BRB and IOS. For those who don’t play – it’s a simple enough explanation; once a year, there is a ‘puzzle’ set, usually to do with ‘matters aeronautical’, the prize of Choc Frogs and bragging rights, is contested, robustly. Apart from one or two lone wolfs, many form ‘teams’ – bit like a pub quiz sort of thing. The bait is tossed out and they set to work. Provided the ‘clues’ are ‘plentiful’ they usually manage to arrive close, if not spot on to the solution.

Now this ICAO puzzle P2 is ‘researching’ and the paltry information provided so far is creating rumbling noises – not only with the BRB, but within ICAO itself. Seems they are as puzzled as we are. That aside; it would be politic to throw out a few more breadcrumbs, before the rumbles become howls of protest. Now I know that the final ‘question’ will be fully researched and the solution unimpeachable; however….

That’s it P2; they have smelled the stew and are milling about the back door; throw ‘em a bone or two, just to keep ‘em happy until supper is served up. Go on, you know you want to.

“Two more here please barkeep” – (aside) perhaps another ale or two will loosen “K’s” tongue – unlikely; but you never know - any excuse eh?
Reply
#63
The adventure of the veiled question.

Watson – “The source of these out-rages is known, and if they are repeated I have Mr. Holmes’s authority for saying that the whole story concerning the politician, the lighthouse, and the trained cormorant will be given to the public. There is at least one reader who will understand.”

Much like Watson; I find myself in a similar, tantalising position. I know, that within the confidential archives, there is a story begging to be told. The BRB can smell the whiff of outrageous scandal and speculation is rife. P7 did indeed try to ply me with ale; and, much as I dislike disappointing him; and the crew, fact is they have about as much information as I have. Breadcrumbs and signposts are about the limit of my knowledge; well, that and the digging I have done, but P2 holds the strings on this one, albeit a tenuous hold. This is the problem when ‘digging’: layers of disconnection, miles of ‘legal’ wriggle room, carefully concealed bolt holes and more smoke than is healthy.

Clues? Well, without the faintest notion of the final research result, anything I may tip is likely to be misleading; but, I may without leading anyone astray say that it all has to do with the reporting of accident and incident to ICAO. I can also state that at present we seem to have more idea of what is going on than ICAO’s Australian ‘Excellency’; but I doubt that will last for long. The chap in Montreal is deemed ‘proper’, righteous and upright; I expect P2 is awaiting that response before getting ‘fair-dinkum’ about his brain twister.

[Image: 84de018d02d773f8ce5c283f2f740b47.jpg]

So patience and forbearance is required; speculate away, no harm there: but, be advised, the ‘tote’ is firmly closed. I cannot even frame a field of runners yet, let alone lay odds. No doubt when P2 finishes on the 18th green and marked his card, we shall hear more.

Meanwhile, I am always happy to have an ale or two with a mate – I can set several rabbits running, enjoy my ale and watch the fun; fair warning.

Toot – toot.
Reply
#64
BRB BT: The IR mole & the ADREP cock-up(rort)? Confused   
Sorry guys got tied up checking with some sources at the 19th - Big Grin

Anyway still waiting on some feedback from his 'Excellency' but in the meantime I have some more dots & dashes on the Iron Ring 'mole' that should help "K" firm up the field for the 'ICAO Obfuscation Cup' - Wink

Reference: 2004 ICAO ATSB - Audit Report [ Download PDF: 2.86MB]

At page 5 to 6 and para 4.6:
Quote:4.6 Safety recommendations are issued by the ATSB in conformity with Annex 13 requirements. ADREP Preliminary Reports and Data Reports sent by the ATSB to ICAO were incomplete, partly due to the differences in the taxonomy format. Since the ATSB is in the process of acquiring a new accident and incident data reporting system, it is recommended that the new database system be ADREP-ECCAIRS compatible in order to facilitate reporting and international exchange of data. Between 1988 and February 2004, the ATSB managed a voluntary incident reporting system named Confidential Aviation Incident Reporting (CAIR). A new voluntary non-punitive incident reporting scheme, entitled Aviation Self-Reporting Scheme (ASRS), replaced the CAIR on 21 February 2004 but has not yet been broadened to receive CAIR reports, pending further legislative measures. In addition to accident and incident investigation, the ATSB undertakes safety data analysis and research. All the ATSB reports, safety recommendations and key safety information are available on the ATSB website.

& from Appendix 5-1:

Quote:FINDING:

The ATSB has been reporting accidents and investigated incidents to the ICAO ADREP data system (Preliminary Reports and Data Reports), however, they are incomplete partly due to the differences in the taxonomy format.

RECOMMENDATION:

Since the ATSB is in the process of acquiring a new accident and incident data reporting system, it is recommended that this new database system be ADREP-ECCAIRS compatible. It is also recommended that further discussions take place between the ATSB database system personnel and the ICAO ADREP system administrator in order to facilitate the reporting to the ADREP using the ATSB existing system before the new ATSB system becomes operational.

CORRECTIVE ACTION PROPOSED BY THE ATSB:

There was some confusion prior to the audit between the ATSB and the ICAO secretariat which meant that the ATSB was not aware of the ADREP reporting problems. The ATSB is currently investigating the feasibility of incorporating an ECCAIRS compatible ADREP into the new accident/incident database. However, a determination is still several months away. As a result of the audit, the ATSB has obtained a copy of the latest ADREP (Form D) and is seeking to create a template that will capture the necessary data applicable. The ATSB is committed to fully meet the ICAO obligation in both the short and longer terms.

ACTION TAKEN BY THE ATSB:

The use of ECCAIRS was considered as an option for the occurrence database module of the ATSB's newly developed Safety Investigation Information Management System. Given that most of the aviation data collected by the ATSB is high-volume, low-detail data, the complexity of the ECCAIRS taxonomy was not considered appropriate. A bespoke taxonomy for safety events and safety factors was developed by the ATSB which better suits its needs, particularly for the purposes of safety research and for the application of its investigation safety analysis methodology. However, a mapping exercise was carried out to ensure that there was comparability between the ATSB and ECCAIRS taxonomies. For the purposes of notification, preliminary and final ADREP data reports, the ATSB continues to provide this information in the ECCAIRS format, including the use of the ECCAIRS taxonomies.

P2 comment - In other words the ATSB will continue to forward only those (PDF copied) reports it deems not politically and (big end of town) industry sensitive for the ICAO ADREP Secretariat to input via the ECCAIRS IT application - and it remains so to this day. 

And for the benefit of the BRB here is the list of the ATSB officials contacted for the 2004 audit:

Mr. Kym Bills Executive Director

Mr. Rob Graham Director Safety Investigations Branch

Mr. Alan Stray Deputy Director Aviation Safety Investigation

Mr. Patrick Hornby Legal Advisor

Mr. Lawrie Brown Team Leader, Quality and Audit

Mr. Christopher Filor Deputy Director Surface Safety Investigation

Mr. Ian Sangston Senior Transport Safety Investigator

Mr. Phil Robertson Senior Transport Safety Investigator

Mr. Julian Walsh Acting Team Leader, Technical Analysis and

Notification

Mr. Joe Hattley Team Leader, Aviation Investigations

Mr. Greg Walsh Notifications Officer

Mr. Steve Young OASIS Data Administrator

Mr. Andrew Roberton Senior Transport Safety Investigator


 
MTF...P2 Cool
Reply
#65
Entry form now available.

P2 – “I have some more dots & dashes on the Iron Ring 'mole' that should help "K" firm up the field for the 'ICAO Obfuscation Cup'”.

The imp in P2 emerges from behind the mountains of research, with a cheeky challenge. Very well – I accept.

Any sponsored event in the Race to the Bottom series requires a rule set, to make the rules we need to know ‘how is the winner to be decided’, this is based on information available. It appears, from data on hand, that someone, for some reason has been playing fast and loose with the ICAO statistics; which may have had the effect of making the nations great safety record a little better than it actually is, in reality. Not proven yet, but, there is enough data available to ‘frame’ a race, make some rules and begin accepting entries. The ‘tote’ will remain closed and no ante post bets will be accepted as this may change when ‘his Excellency’ finishes his research.

[Aside]: There has been some gentle probing done, just to establish basic facts – such as why Canley Vale, Mildura, the Coal loader and other events were not on the ICAO data base. There has been a ‘reaction’ from the more sensitive parts of the bureaucratic anatomy; which means they are aware of the probes. So, to factor odds at this early stage is almost impossible – we need to see and hear the ‘official’ spin machine cover story first; which will provide a final field and allow the setting of realistic odds.

There are two elements which require consideration – if we are to accept the premise that someone, for some reason, has been at silly buggers with ‘statistics. This naturally begs the questions – who and why?. Then we must ask is it the one agency or a joint effort by the big three stables to ‘fix’ the odds? Given that all three have some serious skin in the game – funding, credibility, kudos and power; it is hard to deny the possibility of collusion – we have, after all, seen it done before. This Muddy’s the waters and makes setting both field and odds difficult.

However; P2 has provided a list of potential, entrants from the ATSB, although this is considered incomplete as the ALIU (bridge between ATSB and CASA) has been omitted on a technicality. We shall, at a later date, define which stable this amorphous entity is racing for.

So, the napsters cryptic picks for the ATSB potentials:-

Singalong Lad – ran a close second in the Pel-Air cup narrowly avoiding disqualification from racing.

Walshing Mitdolan – also implicated in the scandal following the Pel-Air cup; the connections were offered an option of a long suspension or being warned off.

Walky-Tawky – another serious contender, veteran of the Pel-Air cup and winner of last years ‘Bully boy stakes’ made infamous by his persistent attacks on mares and filly’s which challenge his running. The sponsors will definitely accept that entry.

Oasis Dreamer – never raced publicly in the major events; however, rumours of a murky history in interference and cooperative running in minor events, away from the main game are persistent.

Uriah Heep – veteran of the Obfuscation cup may yet emerge from retirement; the connections unable to resist the prize offered. If they decide to run UH in this championship race, it will be tough to get sensible odds.

That, boys and girls is as far as the organisers are prepared to take the field. Much depends on the sponsorship to hold event being forthcoming; we shall wait and we shall see. Not too many sleeps now, then I’ll get it sorted. BRB and IOS protests will be ignored.

Toot – toot.
Reply
#66
More crumbs from P2 -

Aussie O&O of the ICAO ADREP system: cont/-

To perhaps help provide a running form guide for the potential entrants to the BRB sponsored ICAO Obfuscation Cup, I will continue to publicly reveal my discoveries as I troll through the records of Australian (non-)conformity with occurrence reporting to the ICAO ADREP system.

Reference: BRB BT: The IR mole & the ADREP cock-up(rort)?

   Quote:
   ACTION TAKEN BY THE ATSB:


   The use of ECCAIRS was considered as an option for the occurrence database module of the ATSB's newly developed Safety Investigation Information Management System. Given that most of the aviation data collected by the ATSB is high-volume, low-detail data, the complexity of the ECCAIRS taxonomy was not considered appropriate. A bespoke taxonomy for safety events and safety factors was developed by the ATSB which better suits its needs, particularly for the purposes of safety research and for the application of its investigation safety analysis methodology. However, a mapping exercise was carried out to ensure that there was comparability between the ATSB and ECCAIRS taxonomies. For the purposes of notification, preliminary and final ADREP data reports, the ATSB continues to provide this information in the ECCAIRS format, including the use of the ECCAIRS taxonomies.

   Reference: 2004 ICAO ATSB - Audit Report [ Download PDF: 2.86MB]

Okay so from the above it can be seen, that even as far back as 2004, the ATSB had some serious deficiencies in forwarding safety issue information, occurrence notifications and preliminary/final reports to be inputted into the ICAO ADREP (iSTAR and ECCAIRS databases). So for other than the original occurrence notification, the ATSB solution (ref: Appendix 5-1) was not to try and match the ECCAIRS taxonomy but for everything (data/prelim/final reports) to be forwarded to the ICAO ADREP Secretariat in a copied PDF format.

On a read of the minutes of the 2008 ICAO IAG divisional meeting it was discovered that the taxonomy issue with the ECCAIRS IT application, was a common problem with some individual States. The IAG recommended a proactive action plan to tackle this.

Based on the 2008 ICAO audit report on Australia (the audit occurred before the IAG meeting), it would appear that the issue had been effectively addressed by Australia.

The problem was also lessened for Australia by the introduction of notified differences to ICAO Annex 13. In particular the ATSB exempted itself from forwarding all preliminary reports for discontinued/not to be investigated occurrences.

There was also a ND for the requirement to investigate the accidents/serious incidents that would normally be required under Annex 13.

This was discovered in the course of the 2008 ICAO audit, with the finding leading to the issuing of an audit recommendation:

   Quote:
   [Image: App-3_6_1.jpg]
   [Image: App-3_6_1_1.jpg]

 
Remembering that the IR data input mole was in charge of the forwarding of data to ADREP from 2001 until sometime in 2012. This was when EH became the REPCON manager and presumably the ATSB ICAO coordinator.

I then fast forward to November 2015 with the discovery that EH had modified a PDF copy of the VH-NGA prelim report (created 15/01/2010). However tracking the changes to this document finds no changes. I could be wrong but IMO signifies that this document was on file at the ATSB and was simply forwarded by EH to ADREP on the 10/11/2015.

This then got me thinking that maybe there were other similar aberrations...
This led me to reviewing all PDF copied prelim/final reports from 2009 till 2015. What I discovered was that nearly every report from occurrences between 2009 till 2011 was inputted by an ATSB Officer in the course of a week before and after EH modified the VH-NGA PDF copied prelim report.

I also discovered that there are still a significant number of serious incident/accident reports that have to this day not been submitted to ICAO and are not listed on either the ECCAIRS or ICAO iSTAR databases. One of these occurrences just so happens to be an occurrence that had the real potential to be Australia's worst aviation accident disaster - i.e. the Mildura Fog landing...

TICK..TOCK 6D, Malcolm in the middle & Barmybaby, TICK..TOCK indeed!

MTF? Definitely...P2
Reply
#67
Pel-Air re-investigation rumour mill -  Confused

Word is that there is going to be an extension to the DIP review of the 500+ page VH-NGA re-investigation 'DRAFT' final report... Huh

As a consequence there is also a rumour that the IIC, Dr 'Ghost who walks', is none too impressed with this delay... Dodgy

While we wait for the rumours to be confirmed, here is a rehash of why it was that PAIN always had issues with the ATSB guru of Human Factors being appointed in the position of IIC of the PelAir re-investigation... Angry
Quote:Ghost who walks & talks beyond Reason- [Image: angry.gif]


Off the selfie-King & miniscule Dazzling Dazza's thread, a full boiler post from the Ferryman... [Image: confused.gif] :
(09-26-2016, 08:50 AM)kharon Wrote: Wrote:Full Steam GD.  Pour it On.

Damn the guns and hammer the engines – we have an urgent pick up and delivery mission.

Made a routine ‘how gozit’ call Karen Casey, see what was new and how things were progressing. On the positive side Sen. Cameron has taken an interest in the matter and there are positive signs from that. Here endeth the good news.

To business: stunned is the only way I can describe my reaction to the following; incredulous followed, then fury. Plain old fashioned outrage, in spades, redoubled.  It goes like this, paraphrased for brevity.

KC rings ATSB – Walker, to see when the second ATSB report may emerge from deep sleep chamber.

Walkers response was unbelievable; but notes and a statutory declaration take the matter to truth. In short, he was rude and aggressive. Statements like “Karen, just what do hope to gain from this report” “What do you want to get out of it”.  “It is your fault there is a delay”.  The whole debacle seems to be Karen’s fault all of a sudden and the ATSB is offended; etc. grossly miffed.

It was not Karen’s fault the aircraft ditched; it was not Karen’s fault she got badly hurt and it most certainly was not Karen’s fault that the ATSB and CASA got caught sweeping the whole thing under the table; nor was it Karen’s fault that Albo dived out of the back door as soon as the smoke alarum went off.  Karen had little to do with the Senate findings and the pasting dished out to both ATSB and CASA was well deserved. They got away very lightly, considering.

None of this is any excuse for being rude to anyone. Who the duck does Walker think he is? ATSB should be calling for his resignation.  No matter who rings with a genuine concern no one should be treated in the manner Karen was.

What chance a honest report when the man in charge turns out to be a coward and a bully?  Those types, when under pressure and attempting to justify that which cannot be justified habitually turn out to be not only disingenuous but happy to offset the blame to anyone else they can.

If the Walker attitude reflects the ‘new’ ATSB approach to victims of air accident then it is time for the minister to step in. I know that had I spoken to anyone in the workplace in that manner, my head would be following my arse out of the door before I could say ‘Sorry’.

If Walker won’t resign, then the minister needs to act, swiftly.  Fair warning, this is not going away.

A metaphorical head in basket is demanded: I don’t care how it gets there.

I cannot properly express the full measure of contempt and disgust this story has generated. The Pel-Air charade was a national disgrace; mentally kicking an accident victim when they are down and struggling to get through life with pain and grief is beneath contempt, particularly when the thread which keeps Karen attached to this world is tenuous, even on a good day.

Lets go and pick up this prick GD; seems he is late for his appointment with the Boss.

More to follow - bet your life on it.

Toot – bloody – toot.

As you would expect when someone has just been bumped up to PAIN public enemy No1.; down the pipe came the order for me to cyber-troll and re-visit the PAIN archives for any scurrilous dirt on the infamous black-box whisperer and the man who believes the causal chain for accidents, for example QF1's embarrassing runway overrun at Bangkok in 1999; or the Lockhart River tragedy, can be simply explained through a 'cloud association' diagram.

Here is Walker's cloud diagram for the Lockhart River causal chain:

[Image: page58image1432.jpg]
 

 (Hint: take note of dates) This is where it starts to get interesting because that diagram was extracted from a research paper that was co-authored by Walker and the former ATSB CEO Kym Bills, which was subsequently published in 2008 (P2 - note the research paper title): Reference - AR2007-053 

Quote: Wrote:Analysis, Causality and Proof in Safety Investigations

Summary

The quality of a safety investigation's analysis activities plays a critical role in determining whether the investigation is successful in enhancing safety. However, safety investigations require analysis of complex sets of data and situations where the available data can be vague, incomplete and misleading. Despite its importance, complexity, and reliance on investigators' judgements, analysis has been a neglected area in terms of standards, guidance and training of investigators in most organisations that conduct safety investigations.

To address this situation, the Australian Transport Safety Bureau (ATSB) developed a comprehensive investigation analysis framework. The present report provides an overview of the ATSB investigation analysis framework and concepts such as the determination of contribution and standard of proof. The report concludes by examining the nature of concerns that have been raised regarding the ATSB analysis framework and the ATSB's consideration of these concerns.

The ATSB believes that its investigation analysis framework is well suited to its role as an independent, no-blame safety investigation body. It is hoped and expected that ongoing development and provision of information about the framework can help the safety investigation field as a whole consider some important issues and help develop the best means of conducting safety investigations to enhance future safety.

Type: Research and Analysis Report
Author(s): Michael B. Walker and Kym M. Bills
Series number: 2007053
Publication date: 26 June 2008
Publication number: 08196
Related: Human factors
 

[Image: share.png][Image: feedback.png]

Last update 07 April 2014

In the lead up to that research paper Walker also made a presentation to an ISASI seminar in Mexico 2006 - see page 10 HERE:

[Image: Dr-W.jpg]

Quote: Wrote:...In recent years, the ATSB and other safety investigation agencies
successfully used the Reason Model of organizational accidents
(Reason 1990, 1997) to guide the analysis phase of some investigations.
Although the Reason Model is widely accepted, some
of its features limit its usefulness. The ATSB has adapted the Model
to better suit the requirements of safety investigation and to make
the Model more applicable to a wider range of investigations.
The primary changes to the Reason Model include broadening
the scope beyond a focus on human factors, and to more functionally
define the components of the model so as to reduce overlaps and
confusions when categorizing a factor. In particular, ATSB’s model
clearly distinguishes between the things an organization puts in place
at the operational level to minimise risk (i.e., “risk controls” such as
training, procedures, warning alarms, shift rosters) and the conditions
that influence the effectiveness of these risk controls (i.e., “organizational
influences” such as risk-management processes, training
needs analysis processes, regulatory surveillance)... (P2 - Hmm...that sounds familiar -  [Image: huh.gif]
)

...Therefore I now believe that Dr W is in fact the bureau version of Hoodoo Voodoo (i.e. Dr A) and was the primary motivator for Beaker launching and adopting his 'beyond (all sensible) Reason' methodology. Which ironically IMO means Dr W is part of the 'causal chain' in the diabolical original Norfolk Island VH-NGA ditching accident investigation and the now approaching 2 year re-investigation... [Image: dodgy.gif]

Combined with the discovery that Dr W is also a Sociopath (Ferryman post) and speaks with forked tongue, has to represent the biggest conflict of interest for this parasite to be anywhere near the PelAir re-investigation, let alone the Investigator in Charge...FDS!  [Image: angry.gif]  

MTF...P2  Cool
Reply
#68
The Bookmakers lament:

P2 – “Word is that there is going to be an extension to the DIP review of the 500+ page VH-NGA re-investigation 'DRAFT' final report...

I wondered how big a pile of paper 500 pages actually is – the answer was easy – within easy reach, the neat package for the printer. Got me thinking, if one allows lets say that every page in the ‘new’ Pel-Air analysis is printed single side, that reduces the reading to 250 pages; lets say that 70% of each page is actually used, this reduces the volume of reading down to 135 pages; we can safely allow a 20% discount on that for waffle, tables, graphs etc. and possibly a few more off for indexing etc. Let’s say there are approximately 100 pages of pertinent information (just for a number). Then we may ask ‘what’ may we expect within those 100 pages. That, boys and girls is my puzzle for today. As the Pel-Air report release time approaches I must set my tote odds. One of the board lines represents the number of ‘useful and of value’ pages will be found within the information provided. Most of the BRB can do the simple math, but the numbers are now being refined; varying from a light weight 1% to an optimistic 40%.  It’s not really fair play, but, intrigued, I asked some of the BRB how they settled on the % selected.

Those (many) who were opting for the lower >2 - <10 % values – simply stated that the ‘accident’ stand alone was a simple, single issue affair. The holes in Mr Reasons famous cheese lined up, perfectly synchronised, the results inevitable. Nothing new there and a rehash of the same circumstances, no matter how clinical, would provided little in the way of ‘new’ data, let alone point at the under laying causal chain. Perish the thought of departmental or company shortcomings being mentioned.

Those (not many) who selected >20 - <50 % values believed that a ‘factual’ analysis would provide some additional data of value - provided ‘all’ the data was included.

Which left me with a problem – if I am to keep my shirt – how to lay off the bets of those who are solidly backing a < 1% result. There are a lot of ‘em, heaps; and I must accept the wagers and formulate the odds. Don’t believe that the Bookies always win; sometimes the tote gets a flogging and I feel it in my bones; this is going to be one of those times. In a nutshell, the general consensus is that the ‘new’ report will be ‘clinical’, cut and dried but only on the ‘facts presented’ and those are pretty well known anyway. Where the report will stumble is in the ‘language’ used, many believe that will subtly, but inevitably lead back to it all being pilot error. “This is a crock” say my punters; “why”? I ask. So they tell me (paraphrased without the invective).  “The company and every single government agency owns a piece of this accident, James was let down by his own operating culture and lack of training – which CASA happily accepted, failing miserably to ensure that the thin policy and procedure promulgated was ‘alive and valid’”. “Fatigue, training, operational support, lack of proper planning procedure, lack of even RTOW data all sent a flight crew into a high risk situation”, they say, and more.

“Condensed”, they add, “it all comes down to the report ‘justifying’ and excusing everyone ‘official’ from any part in the event; ATC, BoM, CASA, Company”. “These contributing factors will not only be written out of the story, but be exonerated”.

The real story of the Pel-Air at Norfolk saga is not that of the ditching ‘how’; but one of the ‘why’ and the actions taken after the event by ATSB and CASA. My punters all say the same thing; “show us a report on that and we’ll read it – all of it; or, get the Senators to finish what they started: getting the lid off the real tale, the one of appearing to defraud the public and misleading the Senate; now that is a tale of interest”  

That is how the betting stands; there are some other ‘interesting’ lines on my tote odds board related to this; I may get some of my shirt back from them. More on those closer to the release date.

Toot - toot.
Reply
#69
Willow brings up PelAir ditching at ISASI presentation - WTD?? 

Reference:
Quote:Similar occurrences to that at Mildura in June 2013

A further review of the ATSB occurrence database identified five occurrences that had happened since 1999 and were similar to this occurrence. These occurrences were investigated by the ATSB  website and are detailed below.

ATSB investigation 199904029

ATSB investigation 200401270

ATSB investigation 200605473

ATSB investigation AO-2012-073

ATSB investigation AO-2015-067

..In order to better quantify the residual risk, specifically the likelihood of unforecast weather deterioration, the ATSB is examining the reliability of aerodrome forecasts as part of research investigation AR-2013-200 Reliability of aviation weather forecasts. This research investigation will initially examine the reliability of the aerodrome forecasts for Mildura and Adelaide Airports, before expanding to cover other major Australian airports.

With the release of the ATSB AO-2013-100 (Mildura fog duck-up above) I was critical that in the 'related occurrences' section there was no mention of the VH-NGA ditching; nor was there mention of the previous unforecast weather related incidents that led to the ATSB issuing safety recommendation R20000040 on 22 February 2000... Dodgy 

(P2 comment: As a 'passing strange' coincidence I have also now discovered that all the listed un-forecast wx related occurrences, including the Norfolk serious incidents/accident, have mysteriously not been listed/recorded on the ICAO (ADREP & ECCAIRS) iSTAR database.)

I was also critical that in the first David Wilson - AR-2013-200 - report that again the Norfolk incidents and ditching had seemingly been glossed over yet again... Huh

However I am pleased to inform people that I can actually retract some of my previous criticisms... Blush

This is because 2 weeks ago Willow made a presentation to the ISASI 2017 annual seminar (see HERE, day 2 between 1:30-2:30pm), which included much data related to unforecast wx at remote islands plus a reference to the VH-NGA ditching: Effect of ICAO Type Aerodrome Weather Forecasts on Aircraft Operations 

Quote:Comparison between remote islands and mainland airports

This algorithm was used by the ATSB to support an investigation of a serious weather-related incident at a remote Australian island. Specific hypotheses were put forward regarding the reliability of remote island forecasting, and the analysis conducted allowed definitive conclusions to be drawn regarding the relative reliability of these forecasts from the perspective of the historical likelihood of unforecast weather conditions below the landing minima.
        
This would seem to indicate that Willow's 'algorithm' will be featuring in the upcoming re-investigation final report into the ditching of VH-NGA... Rolleyes

So does this mean the ATSB finally acknowledge the very real parallel causal factors between the Mildura fog duck-up and the PelAir cover-up?

Well apparently not as it is rumoured that in the title of the 500+ page VH-NGA re-investigation final report, 'fuel management' is mentioned but not a serious weather-related incident (ditching).

 However this does not mean that the BRB can't examine in detail the (IMO) striking parallels related to the unforecast wx Swiss cheese hole... Wink

Reference Willow's ISASI presentation:
Quote:Methods

The results presented required the development of a computer program (the algorithm). Full details are available on the ATSB’s website (www.atsb.gov.au) under investigation AR-2013-200.

The objective of the algorithm was to help calculate the probability of using the weather forecast system as it affects pilots, and number of expected aircraft arrivals during selected weather conditions. It uses actual historical weather forecasts (TAFs and TTFs) compared to reported observations (METARs and SPECIs) as they would be used by pilots. It also can examine what would have happened if a different type of forecast was used or the forecast was retrieved later in flight.
        
Now a relevant reference from AO-2013-100:
Quote:Use of weather observations for decision making

The flight crews of Velocity 1384 and Qantas 735 reported assessing the Mildura weather prior to diverting from Adelaide Airport. Both reported considering the observation reports that were current at the time as a more reliable indicator of the weather at Mildura Airport than the relevant forecast. The captain of Qantas 735 reported feeling that the observation reports were more reliable given the inaccuracy of the forecast at Adelaide.

The crew of Velocity 1384 reported using the observation reports to confirm their understanding of Mildura’s suitability as an alternate destination.

The ATSB asked CASA for a ruling on the use of observations in-flight. CASA responded that a pilot is able to use a valid forecast and observation information. They also cautioned that observations should only be used if the arrival time was proximal to the observation and, if the forecast indicated conditions below minima, the forecast would have precedence over observations. That is, crews must carry sufficient fuel to meet the forecast requirements affecting a destination, even if the observations at that location indicate that the weather is suitable for an arrival.

While the crew of Qantas 735 reported considering the implications of the TEMPO on the 0158 Mildura TAF, and calculated that they had sufficient fuel to meet this requirement, the crew of Velocity 1384 did not complete that consideration. The FO of Velocity 1384 raised the TEMPO as an issue with the captain; however, at that time the captain’s attention was on another matter and the TEMPO was not discussed. As such, when the crew of Velocity 1384 initiated the diversion to Mildura Airport, they had not confirmed sufficient fuel to meet the TEMPO requirement.

Irrespective, the extent and duration of the deterioration meant that even meeting the TEMPO fuel requirement, this would not have provided sufficient fuel to hold until the fog and low cloud at Mildura cleared sufficiently. Unless early consideration was given to a return to Adelaide Airport for an emergency autoland approach, a landing below minima at Mildura Airport was the only option at Mildura Airport.

Mildura Airport

The 0358 amended TAF for Mildura that morning forecast light winds and scattered cloud at 3,000 ft and broken cloud at 6,000 ft. The TAF also included TEMPO periods between 0500 and 1000 in which the cloud base was forecast to reduce to 600 ft AGL.

A new routine TAF was issued for Mildura at 0902 that was valid from 1000. This TAF forecasted visibility in excess of 10 km and scattered cloud at 3,000 and 5,000 ft. No significant weather was listed on the TAF and no indication of low cloud or fog was given. Neither crew were aware of this TAF nor would they have been able to use this forecast in support of their decision to divert. This was because the Aeronautical Information Publication (AIP) Australia stated that a TAF that is valid for 30 minutes prior to the arrival must be used for flight planning purposes. As such, it could not be used for arrivals at Mildura prior to 1000.

A further amended TAF was issued for Mildura at 0952 and covered the period 1000–2200. This TAF forecasted a visibility of 3,000 m in mist, with scattered cloud at 300 ft AGL and broken at 4,000 ft AGL. In addition there was a 30 per cent probability of 500 m visibility in fog and broken cloud at 200 ft AGL between 1000 and 1200.

Next a reference from the once hidden now infamous CASA parallel investigation report CAIR 09/3:
Quote:[Image: CAIR-1.jpg]
[Image: CAIR-2.jpg]

Now referencing Fig.2 &  original VH-NGA final report:

Quote:[Image: Figure-2-Original-VH_NGA-FR.jpg]
[Image: VH_NGA-1.jpg]
& finally the part that highlights the (apparently) completely glossed over 'fact' and elephant in the room related to the PelAir causal chain, reference page 16 of the original VH-NGA final report:
Quote:An amended Norfolk Island TAF that was valid for the aircraft’s ETA was issued by the Australian BoM at 0803. In that TAF, the visibility was forecast to be 10 km or more, with Broken cloud at 1,000 ft above the ARP. Those conditions indicated that the weather would be below the alternate minima for Norfolk Island at the aircraft’s ETA, but above the landing minima. The flight crew were not advised, and were not required by any international agreement to be advised, of the amended forecast and they did not request an updated forecast for Norfolk Island during the flight.
  
So on one hand we had two crew that were (nearly) fully aware that their alternate airport had a TAF operational requirement (60 minutes TEMPO YMIA), but on the other hand we had a crew who had no idea that an amended TAF had been issued which automatically placed a operational (alternate) requirement on the conduct of the rest of the flight... Angry

MTF...P2 Cool

Ps It should be remembered that auto wx observations do not place a legal operational requirement on a flight crew... Undecided
Reply
#70
Its not too hard to imagine that the whole ATSB report on the NF event is designed to support the Skulls hypothesis that the "pilot Dunnit" and justify his subsequent embuggerance. I think its curious the way he was treated compared with the RPT guys for essentially the same "Offence?".
Reply
#71
TB – “I think its curious the way he was treated compared with the RPT guys for essentially the same "Offence?".

Just by the numbers alone – at no time did James receive a met report indicating an operational requirement. The RPT took off with full knowledge and full operational support and both flew past viable options and diverted to a field with an operational requirement.

Going to be interesting to see what ‘the report’ contains by way of meteorological updates, advice and warnings – particularly on the ‘time line’ and amended forecasts.

The report should only now contain the CVR data and a couple of twiddles – how it got to be 500 pages is going to make for interesting reading. Will they call a ‘fuel’ related incident or a ‘weather’ related accident ?– the title page will say it all.

Toot toot.
Reply
#72
(09-13-2017, 06:38 AM)kharon Wrote: TB – “I think its curious the way he was treated compared with the RPT guys for essentially the same "Offence?".

Just by the numbers alone – at no time did James receive a met report indicating an operational requirement. The RPT took off with full knowledge and full operational support and both flew past viable options and diverted to a field with an operational requirement.

Going to be interesting to see what ‘the report’ contains by way of meteorological updates, advice and warnings – particularly on the ‘time line’ and amended forecasts.

The report should only now contain the CVR data and a couple of twiddles – how it got to be 500 pages is going to make for interesting reading. Will they call a ‘fuel’ related incident or a ‘weather’ related accident ?– the title page will say it all.

Toot toot.

"..Going to be interesting to see what ‘the report’ contains by way of meteorological updates, advice and warnings – particularly on the ‘time line’ and amended forecasts..." - Yes indeed "K" it will be very interesting... Huh 

Reference 4 Corners transcript:

Quote:GEOFF THOMSON: With good weather forecast, Dominic James headed to Norfolk Island with his fuel tanks 83 per cent full.
The first weather update for Norfolk comes from Air Traffic Control in Fiji.

It says there's some cloud over Norfolk island at 6,000 feet.

This is wrong.

MICK QUINN: In review when you look at the actual weather report that was issued, the actual cloud base was not at 6,000 feet. It was at 600 feet.

That indicates to Dominic, it reinforces his mental picture, that the forecast still is as it was, it's even better than what it was when he got the original forecast when he departed.

MARTIN DOLAN: That's not one that I am familiar with at the level of detail in the report so ...

GEOFF THOMPSON: So it might be a mistake.

MARTIN DOLAN: It, it may well be a mistake. I'll have to take a look at that.

GEOFF THOMSON: And he did.

Last Friday the ATSB acknowledged Dominic James received incorrect weather report from Fiji and changed its report.

DOMINIC JAMES: If I'd been told that there was cloud at 600 feet, even given the fact that I suspected the automatic system was overstating the weather at Norfolk, I would've gone to Fiji.

GEOFF THOMSON: But moments later another weather report comes from Fiji which is acknowledged by the flight crew as the latest weather available.

It contradicts what they've just heard and says weather conditions on Norfolk Island are in fact deteriorating.

DOMINIC JAMES: I maintain that that weather report, exactly as it appears in that transcript, is not what we had on the flight deck. That's not what I copied down, it's not what I comprehended.

GEOFF THOMPSON: And how do you explain that?

DOMINIC JAMES: To be honest with you, I can't.

I am also curious as to whether there will be mention of what I believe led to the ATSB making the above elementary but crucial factual error in the original VH-NGA final report... Huh

My theory is that in the course of the dodgy CASA AAI, that was apparently being conducted under the parallel investigation terms of reference (paragraph 4.1 'parallel Investigations) of the then yet to be released 2010 MoU, it was agreed (as per subpara 4.1.4) that in order to conserve resources that the CASA ALIU would take responsibility for interpreting the ATC transcript and the subsequent dissemination by the flight crew of the ATC relayed wx reports for Norfolk island.

This was ultimately what led (my theory) to the ATSB making the fundamental factual error of 600ft versus 6000 feet as conveyed by Nadi. This error and the CASA biased interpretation of what the Flight crew actually assimilated from the ATC wx report transmissions and which was subsequently reported on in the dodgy CAIR 09/3..

 
Quote:From PDF page 45 here - Attachment 5(PDF 6032KB)



[Image: CAIR-2.jpg]

[Image: Untitled_Clipping_091417_122520_PM.jpg]
 
...was what ultimately led to the ATSB completely glossing over the significance that the only wx report that placed a legal operational requirement on the PIC, the 0803 AMD TAF, was never relayed by ATC to the flight crew of VH-NGA - Dodgy

One would hope that the record of all the interactions between the CASA ALIU and the ATSB, in the course of the conduct of the 2010 MoU defined parallel investigation, will at least be an appendix to the re-investigation final report as IMO it could go a long way to explaining how the first final report was so comprehensively ducked up... Blush


MTF...P2 Cool
Reply
#73
P2 – “[as] IMO it could go a long way to explaining how the first final report was so comprehensively ducked up...”

Cluster O’ Ducks is more like and that is putting it mildly. This second report should trigger a Judicial inquiry into the entire ‘investigation’. There are some pressing questions of both operational legality and of a legal (as in the Act) nature which the 500 page manhole cover will go nowhere near.

I would be intrigued to understand what prompted he CASA ‘parallel’ investigation and the existing head of power under the MoU which allegedly supported. Then there is the question of how many ALIU ‘parallel ‘ investigations have been triggered since the Norfolk event – did the Mildura fiasco prompt such feverish activity from CASA? Did any of the recent ‘big ticket’ incidents (ATR’s for example) bring a swarm of CASA auditors and managers and FOI’s to the investigation? Bear in mind the latest round of ‘incidents’ have all been RPT; not AWK.

This new report should be used as a tombstone. All this time, trouble, effort and money to regurgitate what is, in essence, a simple accident. The report will not explain why ATSB and CASA did the things they did and went as near as toucher to attempting to deceive a Senate committee and the public. There are harsh words used in the real world to define their combined actions; usually preceded by the time honoured “you have the right to remain silent” etc.

500 pages of soft soap; and, the BoM off the hook just wont do; nowhere near good enough, not by a long shot. We need a report into the actions of the regulator prior and subsequent to the event. This to explain the miraculous speed of the return to normal services, the dreadful operations manuals, fuel policy, training, operational control and stuff like that. Don’t care if the new ATSB report don’t delve too deep – we have: and, not one of the 500 pages will answer our questions, bet the next round on it – and I ain’t even read the bloody thing yet.

Ah, my medication arrives – thank you barkeep – yes: we’ll have two more shortly, before the crew lobs in.
Reply
#74
Of parallel investigations, MoUs, MALIUs & Directives - Huh

P7 - "...I would be intrigued to understand what prompted the CASA ‘parallel’ investigation and the existing head of power under the MoU which it allegedly supported..."

Still trying to fathom the very strange disconnected timeline with the original VH-NGA ATSB investigation and apparent change in CASA policy for parallel investigations in the lead up to the introduction of the 2010 MoU... Undecided

Reference CAIR 09/3 (see PDF link above):  
Quote:[Image: Untitled_Clipping_091517_101201_AM.jpg]


Note that the MoU reference that the MALIU uses actually predates the introduction of the 2010 MoU (PDF Page 28) and not the 2004 MoU:

Quote:[Image: Untitled_Clipping_091517_101717_AM.jpg]
 
I have also come across another bizarre connection with the 2010 MoU and the introduction of the CASA ALIU. The following is quoted from this former DAS McComic's Directive - Download das-pn015-2010.pdf (Ps Note the date):
Quote:
Policy

In addition to meeting any obligations under the Transport Safety Investigation Act 2003 and the Civil Aviation Act (1988), CASA is committed to cooperation with the ATSB in accordance with the Memorandum of Understanding (MoU) established between the two agencies.

CASA has established an Accident Liaison and Investigation Unit (ALIU) to manage the day-to-day interaction and to act as a contact point for the ATSB. The ALIU is headed by the Manager Accident Liaison and Investigation Unit (MALIU) who reports to the Deputy Director of Aviation Safety.

Under the terms of the MoU, all requests from the ATSB for assistance, advice or interviews should be coordinated through the Accident Liaison and Investigation Unit (ALIU).

If CASA personnel are contacted directly by the ATSB in respect to any investigation or requests for information they should refer the request to the ALIU.

The ALIU also acts as the conduit for advice back to the ATSB. Staff should not contact or provide advice to the ATSB without first consulting the ALIU.

CASA officers participating in or supporting ATSB investigations have a responsibility to keep Manager ALIU informed of the progress of an investigation and to advise him immediately of information which indicates a need for CASA to take urgent safety-related action. 

John F. McCormick

Director of Aviation Safety

Date 03 August 2011
    
Hmm..wonder what it was that prompted former DAS McComic to issue that directive 1 year, 5 months and 25 days after the 2010 MoU was officially signed? Rolleyes
The chain of command and the underlying warning to not step outside the official lines of communication with the ATSB is quite specific:
Quote: 
Responsibility

The Director of Aviation Safety is responsible for approving all CASA regulatory policy.

The Deputy Director of Aviation Safety is responsible for the development, maintenance and publication of this policy.

All amendments to this policy shall be made in accordance with CASA Document Control policy and procedures.

Purpose of the Policy

The purpose of this policy is to govern the way in which CASA performs its functions under paragraph 9(3)(a) of the Civil Aviation Act (1988) and fulfils its obligations under the Memorandum of Understanding (MoU) established between CASA and the Air Transport Safety Bureau (ATSB).

Application of the Policy

This policy is intended to guide the actions of all CASA staff in their interaction with the ATSB.
 
It is also interesting to note that, much like the current version of the CASA enforcement manual, the DAS Directive was revisited in February 2016 but was not amended in any way that I can detect: https://www.casa.gov.au/files/das-pn015-2010pdf
Quote:Download das-pn015-2010.pdf (52.25 KB)

Date modified: 17/02/2016
 
In terms of the 2015 MoU and probably in the interests of embracing the ASRR recommendations in relation to the SSP...

Quote:3 STATE SAFETY PROGRAMME

3.1 ATSB and CASA are committed to ensure the effective implementation of the

State Aviation Safety Programme, as published by the Department of

Infrastructure and Regional Development. Cooperative priorities for improving

implementation of the Programme during the period of this MOU include, but

are not limited to:

(a) Improving information collection and sharing processes, having regard to

the standards and recommended practices in Annexes 13 and 19 to the

Convention on International Civil Aviation, done at Chicago 7 December

1944

(b) Cooperative research and analysis to review safety trends and identify

areas for safety improvement

© Public communication and education on aviation safety matters.

...it would appear the concept of parallel investigations as intended in paragraph 4.1 of the 2010 MoU has been abandoned (see paragraphs 6 & 7, plus ATTACHMENT A ­‐ Participation in investigations).

However it would also appear that the position of the MALIU is still the go to person as per the still in force McComic directive:

Quote:Participation in investigations will be co-ordinated through the Manager ALIU, CASA and the Director Aviation Safety Investigations, ATSB.


MTF...P2 Cool
Reply
#75
Do we yet know, when the new, revamped, rumored 500+ page, PelAir Mk-2(alpha) report is "actually" due out ?
Reply


Forum Jump:


Users browsing this thread: Cap'n Wannabe, 1 Guest(s)