ATSB fading into oblivion -
Over on the 'Accidents - Domestic' thread Cap'n Wannabe also picked up on the (above) Oz Flying article and an incident that occurred at Essendon Airport yesterday:
With both of these occurrences there is some interesting scuttlebutt and trivia that IMO highlights how the ATSB under Hoody continues to slide towards inevitable oblivion as an effective State (ICAO Annex 13) AAI.
Beginning with the Mallard investigation, I was under the misconception that the important update was disseminated by Hitch in the context of an ATSB media release. However after a brief search on the ATSB Newsroom and Social media it would appear that Hitch on his own initiative had diligently sourced the update from the investigation webpage:
Note that the update occurred on the 22 September, the same date that the ATSB discontinued the 7 week AO-2017-077 investigation...
With the Essendon incident yesterday the ATSB are yet to indicate whether they will be conducting an investigation into Australian registered B200 aircraft, VH-OWN.
If they do investigate I wonder if this is the first time that an incident aircraft will be involved in two active ATSB investigations at the same time?
Ironically this brings me to the next non-notified ATSB AAI update because apparently the other 'serious incident' investigation involving this aircraft was updated just last week - AO-2015-108 :
It should also be remembered that AO-2015-108 occurrence involved the pilot that was tragically killed in the Essendon B200 DFO accident (Preliminary report AO-2017-024.). It is also rumoured that the DFO accident aircraft (VH-SCR) was the replacement aircraft for VH-OWN, which went U/S that tragic day...
With the bizarre disconnect with the lack of dissemination of ATSB identified safety issues and information in active investigations, one wonders how hard it would be for the ATSB investigation updates to auto-notify on the accident investigation webpage index...
MTF...P2
Over on the 'Accidents - Domestic' thread Cap'n Wannabe also picked up on the (above) Oz Flying article and an incident that occurred at Essendon Airport yesterday:
(10-01-2017, 06:22 PM)Cap\n Wannabe Wrote: Story with video here
Quote:Passengers scramble to safety after plane makes rough landing at airport
A plane has made a dramatic emergency landing after running into trouble above Essendon Fields in Melbourne this afternoon.
Emergency services responded to the runway about 6pm after reports the landing gear of the plane was not working.
The pilot was forced to burn off fuel for more than 15 minutes, according to the Metropolitan Fire Brigade (MFB)
The 9NEWS chopper camera captured the aircraft hitting the runway with force, with smoke seen coming from the wheels as it came to a stop.
All five people onboard were shown running from the door of the plane, with two girls hugging on the tarmac.
No one was injured in the incident.
More to come.Quote:From Oz Aviation..
With both of these occurrences there is some interesting scuttlebutt and trivia that IMO highlights how the ATSB under Hoody continues to slide towards inevitable oblivion as an effective State (ICAO Annex 13) AAI.
Beginning with the Mallard investigation, I was under the misconception that the important update was disseminated by Hitch in the context of an ATSB media release. However after a brief search on the ATSB Newsroom and Social media it would appear that Hitch on his own initiative had diligently sourced the update from the investigation webpage:
Quote:Updated: 22 September 2017
On 26 January 2017, a Grumman American Aviation Corp G-73 amphibian aircraft, registered VH‑CQA, aerodynamically stalled and impacted water while participating in an air display, as part of the City of Perth Australia Day Skyworks event. The pilot and passenger were fatally injured.
This web update complements information already provided in the preliminary investigation report that was published on the ATSB website on 8 March 2017.
The investigation has not identified any evidence to indicate that pilot incapacitation or aircraft serviceability were contributing factors to the collision with water. Further analysis around the aircraft performance and operational factors, as well as the review of the planning, approval and oversight of the air display is ongoing.
During the investigation of the occurrence, the ATSB has examined the sequence of events leading up to the occurrence, aspects of the air display coordination, as well as the regulations, procedures and guidance relating to Civil Aviation Safety Authority (CASA)‑authorised air displays. This has included:
The ATSB has also examined the Aircraft Accident Report AAR 1/2017 – G-BXFI, 22 August 2015 that was published by the Air Accidents Investigation Branch United
- approval processes for several years of the Perth Australia Day Sky Show air display and for other air display events across Australia
- the applications to conduct air displays, from this event and others across Australia
- Air Display Safety and Administrative Arrangements manual (in use at the time of the occurrence) and the revised Air Display Administration and Procedure Manual (published September 2017). This manual provides guidance to CASA and the air display organiser
- surveillance and oversight of air displays.
Kingdom.[1] In summary:
At 1222 UTC (1322 BST) on 22 August 2015, Hawker Hunter G-BXFI crashed on to the A27, Shoreham Bypass, while performing at the Shoreham Airshow, fatally injuring eleven road users and bystanders. A further 13 people, including the pilot, sustained other injuries.
Preliminary analysis of this information has identified differences in the approval process within CASA, between civil and military (including combined) displays and between Australia and other countries. The ATSB is continuing to analyse this information, to determine whether there are any systemic safety issues in relation to authorised air displays.
The investigation is continuing.
The information contained in this web update is released in accordance with section 25 of the Transport Safety Investigation Act 2003 and is derived from the ongoing investigation of the occurrence. Readers are cautioned that new evidence will become available as the investigation progresses that will enhance the ATSB's understanding of the accident as outlined in this web update.
-----
[1] AAIB reports can be viewed via www.gov.uk/aaib-reports
Note that the update occurred on the 22 September, the same date that the ATSB discontinued the 7 week AO-2017-077 investigation...
With the Essendon incident yesterday the ATSB are yet to indicate whether they will be conducting an investigation into Australian registered B200 aircraft, VH-OWN.
Quote:ASN Wikibase Occurrence # 200056
Last updated: 1 October 2017
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.
Date:
01-OCT-2017
Time:
07:18Z
Type:
Beechcraft B200 King Air
Owner/operator:
Private
Registration:
VH-OWN
C/n / msn:
BB-936
Fatalities:
Fatalities: 0 / Occupants: 5
Other fatalities:
0
Airplane damage:
Substantial
Location:
Essendon Airport, Melbourne, VIC - Australia
Phase:
Landing
Nature:
Private
Departure airport:
Sunshine Coast Airport (MCY)
Destination airport:
Essendon Airport (MEB)
Narrative:
The aircraft sustained a partial landing gear collapse upon landing after the gear failed to lock-down. There were no injuries.
Sources:
http://www.9news.com.au/videos/cj88fnf26...cy-landing
http://www.9news.com.au/national/2017/10...alfunction
________________________
https://www.flightradar24.com/data/aircr...wn#f0f24db
Images:
If they do investigate I wonder if this is the first time that an incident aircraft will be involved in two active ATSB investigations at the same time?
Ironically this brings me to the next non-notified ATSB AAI update because apparently the other 'serious incident' investigation involving this aircraft was updated just last week - AO-2015-108 :
Quote:Updated: 27 September 2017
The draft report has been finalised and is currently undergoing an internal review process prior to approval by the ATSB Commission. Once complete, the draft report will be forwarded to relevant parties for comment prior to the completion and release of the final report.
It should also be remembered that AO-2015-108 occurrence involved the pilot that was tragically killed in the Essendon B200 DFO accident (Preliminary report AO-2017-024.). It is also rumoured that the DFO accident aircraft (VH-SCR) was the replacement aircraft for VH-OWN, which went U/S that tragic day...
With the bizarre disconnect with the lack of dissemination of ATSB identified safety issues and information in active investigations, one wonders how hard it would be for the ATSB investigation updates to auto-notify on the accident investigation webpage index...
MTF...P2