Forsyth report - IOS monitoring of progress??
#12

(07-13-2015, 07:50 AM)kharon Wrote:  Time has beaten me; I really would like to revisit Forsyth and hammer home the points made.  The main thrust, demanding (albeit politely, but firmly) that CASA must be reformed and changes made is being washed away in a tidal wave of spin, rhetoric and no action.  The organisation has not, in the past year, changed one iota.  In fact, the Skidmore capture has encouraged more disgusting behaviour; the miscreants are either feeling safe tucked up behind their desk; or, believe that change from the top down is simply a gabfest.

Minister Truss, Jeff Boyd and his board; Skidmore and the perhaps the Senators need to be reminded of what we asked for, what we paid and what they have, thus far, failed to deliver.  There are about 60 far reaching, important recommendations outstanding.

Forsyth was not, as Skidmore terms it “a view”; it was a demand for positive action.  

Selah and MMTF.

Okay, think I know where the Ferryman is going with this, so in order to aid & abet his cause please find links & recommendations from the relevant reports... Wink


ASRR Report May 2014

List of recommendations

The Aviation Safety Regulation Review Panel recommends that:

1. The Australian Government develops the State Safety Program into a strategic plan for Australia’s aviation safety system, under the leadership of the Aviation Policy Group, and uses it as the foundation for rationalising and improving coordination mechanisms.

2. The Department of Infrastructure and Regional Development plays a stronger policy role in the State Safety Program.

3. The Australian Transport Safety Bureau investigates as many fatal accidents in the sport and recreational aviation sector as its resources will allow.

4. The Australian Transport Safety Bureau and the Civil Aviation Safety Authority utilise the provision in their bilateral Memorandum of Understanding to accredit CASA observers to ATSB investigations.

5. The Australian Government appoints an additional Australian Transport Safety Bureau Commissioner with aviation operational and safety management experience.

6. The Civil Aviation Safety Authority’s Board exercises full governance control. The non-executive directors should possess a range of appropriate skills and backgrounds in aviation, safety, management, risk, regulation, governance and government.

7. The next Director of Aviation Safety has leadership and management experience and capabilities in cultural change of large organisations. Aviation or other safety industry experience is highly desirable.

8. The Civil Aviation Safety Authority:
a. reinstates publication of Key Performance Indicators for service delivery functions
b. conducts a stakeholder survey every two years to measure the health of its relationship with industry
c. accepts regulatory authority applications online unless there is a valid technical reason against it
d. adopts the same Code of Conduct and Values that apply to the Australian Public Service under the Public Service Act 1999.

9. The Civil Aviation Safety Authority develops a staff exchange program with industry.

10. Airservices Australia, in conjunction with the Department of Infrastructure and Regional Development and the Civil Aviation Safety Authority, reconsiders the policy on ‘Assessment of Priorities’ that stipulates that air traffic controllers sequence arriving aircraft based on category of operation, rather than on the accepted international practice of ‘first come, first served’.

11. The Australian Transport Safety Bureau and the Civil Aviation Safety Authority amend the wording of their existing Memorandum of Understanding to make it more definitive about interaction, coordination, and cooperation.

12. The Civil Aviation Safety Authority delegates responsibility for the day-to-day operational management of airspace to Airservices Australia, including the designation of air routes, short-term designations of temporary Restricted Areas, and temporary changes to the classification of airspace for operational reasons.

13. The Department of Infrastructure and Regional Development and Department of Defence (and appropriate agencies) establish an agreed policy position on safety oversight of civil operations into joint user and military airports.

14. The Civil Aviation Safety Authority changes its regulatory philosophy and, together with industry, builds an effective collaborative relationship on a foundation of mutual understanding and respect.

15. The Civil Aviation Safety Authority continues to provide appropriate indemnity to all industry personnel with delegations of authority.

16. The Civil Aviation Safety Authority finalises its Capability Framework and overhauls its training program to ensure identified areas of need are addressed, including:
a. communication in a regulatory context
b. decision making and good regulatory practice
c. auditing.

17. The Civil Aviation Safety Authority publishes and demonstrates the philosophy of ‘just culture’ whereby individuals involved in a reportable event are not punished for actions, omissions or decisions taken by them that are commensurate with their experience and training. However, actions of gross negligence, wilful violations and destructive acts should not be tolerated.

18. The Civil Aviation Safety Authority reintroduces a ‘use of discretion’ procedure that gives operators or individuals the opportunity to discuss and, if necessary, remedy a perceived breach prior to CASA taking any formal action. This procedure is to be followed in all cases, except where CASA identifies a Serious and Imminent Risk to Air Safety.

19. The Australian Transport Safety Bureau transfers information from Mandatory Occurrence Reports to the Civil Aviation Safety Authority, without redaction or de-identification.

20. The Australian Transport Safety Bureau transfers its safety education function to the Civil Aviation Safety Authority.

21. The Civil Aviation Safety Authority changes its organisational structure to a client-oriented output model.

22. The Civil Aviation Safety Authority establishes small offices at specific industry centres to improve monitoring, service quality, communications and collaborative relationships.

23. The Civil Aviation Safety Authority shares the risk assessment outputs of Sky Sentinel, itscomputerised risk assessment system, with the applicable authorisation holder.

24. The Civil Aviation Safety Authority provides full disclosure of audit findings at audit exit briefings in accordance with international best practice.

25. The Civil Aviation Safety Authority introduces grading of Non-Compliance Notices on a scale of seriousness.

26. The Civil Aviation Safety Authority assures consistency of audits across all regions, and delivers audit reports within an agreed timeframe.

27. The Civil Aviation Safety Authority implements a system of using third-party commercial auditsas a supplementary tool to its surveillance system.
 
28. The Civil Aviation Safety Authority establishes a safety oversight risk management hierarchy based on a categorisation of operations. Rule making and surveillance priorities should be proportionate to the safety risk.

29. Recreational Aviation Administration Organisations, in coordination with the Civil Aviation Safety Authority, develop mechanisms to ensure all aircraft to be regulated under CASR Part 149 are registered.

30. The Civil Aviation Safety Authority changes the current two-tier regulatory framework (act and regulations) to a three-tier structure (act, regulations and standards), with:
a. regulations drafted in a high-level, succinct style, containing provisions for enabling standards and necessary legislative provisions, including offences
b. the third-tier standards drafted in plain, easy to understand language.

31. The Civil Aviation Safety Authority structures all regulations not yet made with the three-tier approach, and subsequently reviews all other Civil Aviation Safety Regulation Parts (in consultation with industry) to determine if they should be remade using the three-tier structure.

32. The Civil Aviation Safety Authority reassesses the penalties in the Civil Aviation Safety Regulations.

33. The Civil Aviation Safety Authority applies a project management approach to the completion of all Civil Aviation Safety Regulation Parts not yet in force, with drafting to be completed within one year and consultation completed one year later, with:
a. a Steering Committee and a Project Team with both CASA and industry representatives
b. implementation dates established through formal industry consultation.

34. The Civil Aviation Safety Authority’s Director of Aviation Safety meet with industry sector leaders to jointly develop a plan for renewing a collaborative and effective Standards Consultative Committee.

35. The Civil Aviation Safety Authority devolve to Designated Aviation Medical Examiners the ability to renew aviation medical certificates (for Classes 1, 2, and 3) where the applicant meets the required standard at the time of the medical examination.

36. The Australian Government amends regulations so that background checks and the requirement to hold an Aviation Security Identification Card are only required for unescorted access to Security Restricted Areas, not for general airside access. This approach would align with international practice.

37. The Civil Aviation Safety Authority amends the current Terms of Reference of the Industry Complaints Commissioner so that:
a. the ICC reports directly to the CASA Board
b. no CASA staff are excluded from the ICC’s jurisdiction
c. the ICC will receive complaints that relate to both the merits and the process of matters
d. on merits matters, including aviation medical matters, the ICC is empowered to convene an appropriately constituted review panel, chaired by a CASA non-executive director, to review the decision
e. while all ICC findings are non-binding recommendations, the original decision-maker is required to give reasons to the CASA Board if a recommendation is not followed.

Senate Inquiry Pel-Air report

List of Recommendations

Recommendation 1

3.68      The committee recommends that the ATSB retrieve VH-NGA flight data recorders without further delay.

Recommendation 2

4.41      The committee recommends that the minister, in issuing a new Statement of Expectations to the ATSB, valid from 1 July 2013, make it clear that safety in aviation operations involving passengers (fare paying or those with no control over the flight they are on, e.g. air ambulance) is to be accorded equal priority irrespective of flight classification.

Recommendation 3

4.43      The committee recommends that the ATSB move away from its current approach of forecasting the probability of future events and focus on the analysis of factors which allowed the accident under investigation to occur. This would enable the industry to identify, assess and implement lessons relevant to their own operations.

Recommendation 4

4.69      The committee recommends that the ATSB be required to document investigative avenues that were explored and then discarded, providing detailed explanations as to why.

Recommendation 5

4.78      The committee recommends that the training offered by the ATSB across all investigator skills sets be benchmarked against other agencies by an independent body by, for example, inviting the NTSB or commissioning an industry body to conduct such a benchmarking exercise.

Recommendation 6

4.79      The committee recommends that, as far as available resources allow, ATSB investigators be given access to training provided by the agency's international counterparts. Where this does not occur, resultant gaps in training/competence must be advised to the minister and the Parliament.

Recommendation 7

4.87      The committee recommends that the Transport Safety Investigation Act 2003 be amended to require that the Chief Commissioner of the ATSB be able to demonstrate extensive aviation safety expertise and experience as a prerequisite for the selection process.

Recommendation 8

4.101      The committee recommends that an expert aviation safety panel be established to ensure quality control of ATSB investigation and reporting processes along the lines set out by the committee.

Recommendation 9

4.103      The committee recommends that the government develop a process by which the ATSB can request access to supplementary funding via the minister.

Recommendation 10

6.41      The committee recommends that the investigation be re-opened by the ATSB with a focus on organisational, oversight and broader systemic issues.

Recommendation 11

6.52      The committee recommends that CASA processes in relation to matters highlighted by this investigation be reviewed. This could involve an evaluation benchmarked against a credible peer (such as FAA or CAA) of regulation and audits with respect to: non-RPT passenger carrying operations; approach to audits; and training and standardisation of FOI across regional offices.

Recommendation 12

6.55      The committee recommends that CASA, in consultation with an Emergency Medical Services industry representative group (eg. Royal Flying Doctor Service, air ambulance operators, rotary wing rescue providers) consider the merit, form and standards of a new category of operations for Emergency Medical Services. The minister should require CASA to approve the industry plan unless there is a clear safety case not to. Scope for industry to assist as part of an audit team should also be investigated where standardisation is an issue. This should be completed within 12 months and the outcome reported publicly.

Recommendation 13

6.58      The committee recommends that a short inquiry be conducted by the Senate Standing Committee on Rural and Regional Affairs and Transport into the current status of aviation regulatory reform to assess the direction, progress and resources expended to date to ensure greater visibility of the processes.

Recommendation 14

7.15      The committee recommends that the ATSB-CASA Memorandum of Understanding be re-drafted to remove any ambiguity in relation to information that should be shared between the agencies in relation to aviation accident investigations, to require CASA to:
  • advise the ATSB of the initiation of any action, audit or review as a result of an accident which the ATSB is investigating.
  • provide the ATSB with the relevant review report as soon as it is available.
Recommendation 15

7.16      The committee recommends that all meetings between the ATSB and CASA, whether formal or informal, where particulars of a given investigation are being discussed be appropriately minuted.

Recommendation 16

8.35      The committee recommends that, where relevant, the ATSB include thorough human factors analysis and discussion in future investigation reports. Where human factors are not considered relevant, the ATSB should include a statement explaining why.

Recommendation 17

9.18      The committee recommends that the ATSB prepare and release publicly a list of all its identified safety issues and the actions which are being taken or have been taken to address them. The ATSB should indicate its progress in monitoring the actions every 6 months and report every 12 months to Parliament.

Recommendation 18

9.40      The committee recommends that where a safety action has not been completed before a report being issued that a recommendation should be made. If it has been completed the report should include details of the action, who was involved and how it was resolved.

Recommendation 19

9.42      The committee recommends that the ATSB review its process to track the implementation of recommendations or safety actions to ensure it is an effective closed loop system. This should be made public, and provided to the Senate Regional and Rural Affairs and Transport Committee prior to each Budget Estimates.

Recommendation 20

9.44      The committee recommends that where the consideration and implementation of an ATSB recommendation may be protracted, the requirement for regular updates (for example 6 monthly) should be included in the TSI Act.

Recommendation 21

9.45      The committee recommends that the government consider setting a time limit for agencies to implement or reject recommendations, beyond which ministerial oversight is required where the agencies concerned must report to the minister why the recommendation has not been implemented or that, with ministerial approval, it has been formally rejected.

Recommendation 22

9.77      The committee recommends that Airservices Australia discuss the safety case for providing a hazard alert service with Fijian and New Zealand ATC (and any other relevant jurisdictions) and encourage them to adopt this practice.

Recommendation 23

9.104      The committee recommends that the relevant agencies review whether any equipment or other changes can be made to improve the weather forecasting at Norfolk Island. The review would include whether the Unicom operator should be an approved meteorological observer.

Recommendation 24

9.106      The committee recommends that the relevant agencies investigate appropriate methods to ensure that information about the incidence of, and variable weather conditions at, Norfolk Island is available to assist flight crews and operators managing risk that may result from unforseen weather events.

Recommendation 25

9.108      The committee recommends that the Aeronautical Information Package (AIP) En Route Supplement Australia (ERSA) is updated to reflect the need for caution with regard to Norfolk Island forecasts where the actual conditions can change rapidly and vary from forecasts.

Recommendation 26

[b]10.35      The committee recommends that in relation to mandatory and confidential reporting, the default position should be that no identifying details should be provided or disclosed. However, if there is a clear risk to safety then the ATSB, CASA and industry representatives should develop a process that contains appropriate checks and balances.[/b]


 MTF P2 Tongue
Reply


Messages In This Thread
Forsyth report - IOS monitoring of progress?? - by Peetwo - 03-27-2015, 09:47 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 03-28-2015, 06:36 AM
RE: Forsyth report - IOS monitoring of progress?? - by thorn bird - 03-29-2015, 02:27 PM
Thai takeaway anyone?? - by Peetwo - 03-31-2015, 07:59 PM
RE: Forsyth report - IOS monitoring of progress?? - by P7_TOM - 04-01-2015, 05:40 AM
New DAS Skidmore - Hallelujah or last hurrah?? - by Peetwo - 04-08-2015, 05:39 PM
RE: Forsyth report - IOS monitoring of progress?? - by Sheikh Yer Booti - 04-09-2015, 01:06 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 06-26-2015, 06:19 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 06-26-2015, 10:32 AM
RE: Forsyth report - IOS monitoring of progress?? - by P1_aka_P1 - 06-30-2015, 05:54 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 07-13-2015, 07:50 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 07-13-2015, 09:55 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 07-13-2015, 10:42 PM
RE: Forsyth report - IOS monitoring of progress?? - by P7_TOM - 08-09-2015, 03:51 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 08-11-2015, 07:18 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 08-11-2015, 09:20 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 09-03-2015, 09:39 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 09-04-2015, 06:37 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 10-14-2015, 08:22 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 10-14-2015, 11:52 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 10-16-2015, 06:46 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 11-04-2015, 06:03 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 11-04-2015, 10:09 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 11-05-2015, 07:08 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 11-05-2015, 10:52 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 11-06-2015, 07:07 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 11-06-2015, 07:34 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 11-06-2015, 11:39 AM
RE: Forsyth report - IOS monitoring of progress?? - by Sandy Reith - 11-15-2015, 09:16 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 11-24-2015, 01:50 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 11-24-2015, 02:55 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 11-25-2015, 08:35 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 11-25-2015, 05:05 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 11-26-2015, 05:11 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 12-02-2015, 01:33 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 12-02-2015, 10:16 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 12-09-2015, 09:28 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 12-09-2015, 04:50 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 12-10-2015, 05:29 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 12-15-2015, 03:40 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 12-16-2015, 05:22 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 12-16-2015, 01:03 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 12-17-2015, 04:52 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 02-04-2016, 09:39 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 02-22-2016, 02:06 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 02-22-2016, 09:43 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 02-26-2016, 02:22 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 02-27-2016, 05:25 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 03-02-2016, 05:41 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 03-18-2016, 11:19 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 05-10-2016, 08:45 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 05-10-2016, 09:35 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 05-26-2016, 10:15 AM
RE: Forsyth report - IOS monitoring of progress?? - by Sandy Reith - 05-26-2016, 06:03 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 06-17-2016, 03:06 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 07-03-2016, 08:07 AM
RE: Forsyth report - IOS monitoring of progress?? - by thorn bird - 07-03-2016, 08:43 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 07-04-2016, 07:04 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 07-14-2016, 10:03 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 08-21-2016, 09:58 AM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 07-14-2016, 10:19 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 08-28-2016, 12:26 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 08-31-2016, 03:15 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 08-28-2016, 05:11 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 08-31-2016, 07:57 PM
RE: Forsyth report - IOS monitoring of progress?? - by P7_TOM - 08-31-2016, 09:38 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 10-19-2016, 02:24 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 12-09-2016, 07:31 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 12-09-2016, 07:58 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 12-15-2016, 07:24 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 12-16-2016, 06:09 AM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 12-18-2016, 07:41 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 03-09-2017, 07:11 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 03-10-2017, 05:57 AM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 04-07-2017, 08:48 AM
RE: Forsyth report - IOS monitoring of progress?? - by P7_TOM - 04-08-2017, 06:20 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 04-09-2017, 07:39 PM
RE: Forsyth report - IOS monitoring of progress?? - by Gobbledock - 04-09-2017, 08:19 PM
RE: Forsyth report - IOS monitoring of progress?? - by Kharon - 04-09-2017, 08:34 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 04-10-2017, 09:21 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 05-26-2017, 12:33 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 07-24-2017, 06:52 PM
RE: Forsyth report - IOS monitoring of progress?? - by Peetwo - 11-21-2017, 09:16 AM



Users browsing this thread: 4 Guest(s)