12-24-2016, 11:23 AM
J* find yet another elephant in A320 cargo hold
Rehash :
What are the chances of that?
P7:
MTF...P2
Rehash :
(12-16-2016, 02:25 PM)Peetwo Wrote:(12-11-2016, 10:42 AM)Peetwo Wrote: Hoody: "Pick a trend any trend??" -
Perfect timing Ol'Tom, Gobbles & "K", look here at about 02:05...
On the theme of 'causal chains' and 'trend lines', remember this...
(11-02-2016, 07:06 AM)Peetwo Wrote: Here we go again -
Headline: Jetstar find a un-manifested elephant in A320 cargo hold
- Wonder how long it will be before miniscule DDDD NFI Chester comes out swinging on behalf of Jet * saying that I'm merely scaring the travelling public -
Quote:DARREN CHESTER: No, I don’t think that at all, Fran. I think it’s quite irresponsible and inaccurate to be scaring the travelling public with unfounded claims about safety issues. Now…
From my calculation there is at least three outstanding loading event aberrations for one airline that are currently on the ATSB investigation list and the question of when these investigations will be completed is anyone's guess...
However will wonders never cease because on reading the latest desktop SIB (short investigation bulletin), I was surprised to find that there had been another 'loading duck-up' incident from the same airline that had actually been investigated and completed in just over 3 months...
Quote:Final Report
Final Report
Download Final Report
[ Download PDF: 474KB]
Listen to this PDF
Alternate: [ Download DOCX: 1.83MB]
Now this is where IMO the dots become elephant footprints because this yet again totally inadequate report actually states in the findings...
"..The short turnaround time combined with this being the last flight to Brisbane that night, along with the assumption there was a transcription error, resulted in the leading hand not requesting a new deadload weight statement and container card, and loading the incorrect container on the aircraft..."
What's the chances if you ran that statement, as a point of comparison, over the other three J* loading incidents being investigated; the taxi rash incidents; and some of the YMML ATC aberrations and even possibly some of the min fuel cock-ups; you might find a trend line in the data so far collated...
Just saying -
MTF...P2
Ps > 2 years to 3 months? - Yeah right and elephants might fly...
What are the chances of that?
P7:
Quote:“Oh! Heavens no Sir” says Hood is his best videoed appearance voice; “No and no again; why our trend monitoring is immaculate: almost complete and world class”. “Why, with a second event, monitored event, we will be able to assist another of our star researchers to obtain a higher degree and: and, a higher pay-grade too". “I can assure you, that with full ministerial support, the Beaker legacy lives on”. (Small bow, exeunt stage left; high five to those waiting to give evidence; lunch next, on the expense account. Who knows – maybe a pretty young reporter to dine on- with).Just noticed there is yet another 'loading event' for the Hoodlum to dutifully add to his 'monitoring' database :
What a wonderful word is 'monitoring' thinks Hood as he strolls away, seeking a vacant Uber lift (cost consciousness is an ATSB watch word).
Quote:Loading related event involving Airbus A320, VH-VGI, Melbourne Airport, Victoria, on 21 December 2016My question is? - Why are the bothering to waste resources to investigate, after all this is just a run of the mill 'loading event'. Come on Hoody just flick it to the 'loading occurrence' monitor 'in tray' and move on mate - nothing to see here...
Investigation number: AO-2016-177
Investigation status: Active
The ATSB is investigating a loading related event involving Airbus A320, VH-VGI, at Melbourne Airport, Victoria, on 21 December 2016.
During unloading, ground crew were advised that the incorrect unit load device had been loaded on the aircraft due to an error at the freight organisation.
As part of the investigation, the ATSB will interview personnel from the freight organisation and gather additional information.
A report will be released within several months.
General details
Date: 21 Dec 2016
Investigation status: Active
Time: 9:00 ESuT
Investigation type: Occurrence Investigation
Location (show map): Melbourne Airport
Occurrence type: Loading related
State: Victoria
Occurrence class: Operational
Occurrence category: Incident
Report status: Pending
Highest injury level: None
Expected completion: Mar 2017
Aircraft details
Aircraft manufacturer: Airbus
Aircraft model: A320-232
Aircraft registration: VH-VGI
Serial number: 4466
Operator: Jetstar Airways
Type of operation: Air Transport High Capacity
Sector: Jet
Damage to aircraft: Nil
Departure point: Melbourne, Vic.
Destination: Sunshine Coast, Qld
Last update 23 December 2016
MTF...P2