Proof of ATSB delays

O&O investigation No: AO-2014-032

Not that the average punter, stakeholder or even DIP would know it but the now No1. longest O&O'd ongoing ATSB AAI went past it's 4th Anniversary without so much as an Annex 13 interim statement; or any recognisable update since 05 May 2017. However apparently the investigation webpage was revisited a week after the 4th Anniversary on 28 February 2018 - WTD... Huh

Blush Slightly embarrassed (because I'd missed it before), I noticed that on the AAI webpage a link for a passing strange 'Explanatory Statement', also dated 05 May 2017 (i.e. spot the disconnects Dodgy ).
 

  Media release
ATSB issues second interim ATR report: 5 May 2017

Explanatory Statement
Investigation AO-2014-032 - ATR in flight pitch disconnect
Quote:Explanatory Statement - ATSB Investigation AO-2014-032 ATR in flight pitch disconnect
With highly technical investigations, the ATSB considers it appropriate to provide an explanatory statement that describes the nature of the technical investigations in a manner which is more easily understood by readers of this report.

Background

ATR42 and ATR72 aircraft are twin-turboprop, short-haul, regional airliner and cargo aircraft built in France and Italy by ATR, and have been in service around the world since the mid-1980s. They seat between 48 and 78 passengers. The entire fleet of the two aircraft types have operated in excess of 20 million flight hours.

There are currently a small number of both aircraft types operating in Australia.

2014 incident

On 20 February 2014, a Virgin Australia Regional Airlines ATR 72 aircraft, registered VH‑FVR, operating on a scheduled passenger flight from Canberra, Australian Capital Territory to Sydney, New South Wales sustained a pitch disconnect while on descent into Sydney. The pitch disconnect occurred when the crew applied opposite inputs to the elevator controls while attempting to prevent the airspeed from exceeding the maximum permitted airspeed for the aircraft type. The pitch uncoupling mechanism activated and the elevators deflected in opposite directions, resulting in aerodynamic loads above the design strength of the tail structure, causing significant damage. 

The “pitch uncoupling mechanism” (PUM)

The elevator consists of a left and right control surface and is located at the top of the tail structure on ATR aircraft. It is operated by the pilots pushing or pulling on the control column in the cockpit, which raises or lowers the nose of the aircraft (known as pitch). During normal operation, the left and right elevator deflect in the same direction and in equal amounts.

There is also a mechanism called the pitch uncoupling mechanism (PUM), located between the right and left control surfaces in the tail of the aircraft. In the event of one of the elevators becoming jammed, the PUM can be triggered to have the elevators operate independently of each other. The PUM is activated by the pilot (operating the pitch control for the elevator not jammed) applying significant pressure to the control column in either direction. The pilot is then able to operate the elevator on the non-jammed side.

If significant pressure is applied in the opposite direction on each of the control columns, the PUM may also be triggered. An inadvertent activation of the PUM due to opposing control inputs is what occurred in 2014.

Flight crew procedure

Generally, flight crew procedures prohibit the simultaneous inputs by both pilots on the control column. Established handover/takeover communication protocols reduce the risk of any inadvertent dual input.

The Work of the ATSB 

The ATSB has undertaken an extensive investigation into the safety factors and issues behind the incident. The investigation has considered design, engineering and certification aspects of the aircraft, as well as operational, maintenance, training and regulatory aspects.

On 15 June 2016 the ATSB released its first interim investigation report that identified a safety issue concerning the potential for PUM activation to exceed the strength of the aircraft.

During the continued investigation of the occurrence, the ATSB has obtained an increased understanding of the factors behind this previously identified safety issue. This has identified that there are transient elevator deflections during a pitch disconnect event that could lead to aerodynamic loads capable of exceeding the design strength of the aircraft structure. The ATSB also identified that these transient elevator deflections were not considered during the certification process. The ATSB considers that the potential consequences are sufficiently important to release a further interim report that expands on the identified safety issue, prior to completion of the final investigation report. Readers are cautioned that new evidence may become available as the investigation progresses that will enhance the ATSB’s understanding of the occurrence.

In order to ensure the veracity of the analysis of the evidence leading to the identified safety issue, the ATSB engaged the UK Air Accidents Investigation Branch (AAIB) to conduct a peer review. The AAIB conducted an analysis of the evidence relating to the safety issue and concluded that their findings were consistent with those provided by the ATSB.

Stakeholder engagement and cooperation

The role of the ATSB is to identify safety issues and communicate them to the relevant organisation(s) to address. Since 2014, ATSB has worked closely with ATR (the aircraft manufacturer), the European Aviation Safety Agency (EASA), the French Bureau d’Enquêtes et d’Analyses (BEA), the United Kingdom Aviation Accident Investigation Branch (AAIB), the Civil Aviation Safety Authority (CASA), Toll as the Australian operator of the Australian ATR42 aircraft, and Virgin Australia as the operator of the ATR72 aircraft. Each of these stakeholders has a specific role in relation to the continued safe operation of these aircraft and has taken the following action to address the safety issue:

ATR

ATR has continued to provide data to ATSB and cooperate more broadly to undertake further aeronautical engineering and assurance work to determine if the aircraft has sufficient strength to withstand the loads resulting from a pitch disconnect. Specifically, ATR has commenced a detailed engineering analysis of the transient elevator deflections that occur during a pitch disconnect. Indications from ATR is that this work will be completed in July 2017.

On 5 February 2016, as a result of this occurrence and a briefing from the ATSB, ATR released an All Operators Message. The message informed operators of ATR 42/72 aircraft of revised maintenance and operational documentation relating to the pitch control system and pitch disconnect occurrences.

EASA

EASA is the issuer of the aircraft’s type certificate and, as such, is the global regulator for the continued safe operation of the word-wide ATR fleet.

While acknowledging the safety issue identified by the ATSB, on 20 December 2016 (and updated on 21 February 2017), EASA issued a related safety information bulletin (SIB) that contained the following statement:

At this time, the safety concern described in this SIB is not considered to be an unsafe condition that would warrant Airworthiness Directive (AD) action ... P2 - So what's the bloody hold up? Confused  

As the global regulator for the aircraft type, EASA is closely monitoring the detailed engineering analysis of the transient elevator deflections being carried out by ATR.

CASA

CASA has advised that they continue to work closely with both EASA and the Australian airline operators of the ATR aircraft, in relation to the continued safe operation of the aircraft type in Australia. ATSB has been advised that this has included both continual dialogue with and specific audits of the airline operators to assure that sufficient pilot training and operational procedures are in place to prevent the recurrence of this event. P2 - Wonder if those audits were conducted in accordance with the recently amended CASA surveillance manual - see Aiding & abetting; or under the busses?? - or as per the McComic black letter regulatory captured days; that brought us strange dichotomies like the PelAir 2009 MAP/SAR vs the Airtex MAP/SAR and AAT embuggerance... Rolleyes     
  
Virgin Australia and Toll

Virgin Australia Airlines advised that, in response to this occurrence, they have taken action to reduce the potential for pitch disconnects and to manage the risk of adverse outcomes from such occurrences. These included:
  • reviewing and revising (where necessary) policy and procedures associated with descent speeds, handover and takeover procedures, overspeed recovery and on ground pitch disconnects
  • incorporation of a number of factors surrounding the event into training material and simulator checks
  • improved pilot awareness through Flight Crew Operations Notices, manufacturer’s communications (All Operators Messages) and ongoing training and checking
  • updated maintenance requirements following a pitch disconnect.
Toll Aviation and Toll Aviation Engineering advised that, as a result of this occurrence, they issued a safety alert to their flight crew and aviation maintenance engineers, which included copies of ATR and EASA service bulletins. This alert advised that, in the event of a pitch disconnect, the aircraft was to be grounded until the appropriate checks had been carried out.

Toll has also developed and delivered enhanced training to their flight crews focused on handover/takeover procedures, unexpected turbulence and high-speed scenarios, and the pitch uncoupling system. Toll have also conducted detailed inspections associated with major  maintenance procedures.

Safety recommendations

While welcoming the safety action taken to this point, in particular ATR’s engineering analysis, the ATSB retains a level of concern as to whether the aircraft has sufficient strength to withstand the loads resulting from a pitch disconnect. As a result the ATSB recommends that:
  • ATR complete the assessment of transient elevator deflections associated with a pitch disconnect as soon as possible to determine whether the aircraft can safely withstand the aerodynamic loads resulting from a pitch disconnect within the entire operational envelope. In the event that the analysis identifies that the aircraft does not have sufficient strength, it is further recommended that ATR take immediate action to ensure the ongoing safe operation of ATR42/72 aircraft.
  • EASA monitor and review ATR’s engineering assessment of transient elevator deflections associated with a pitch disconnect to determine whether the aircraft can safely withstand the aerodynamic loads resulting from a pitch disconnect within the entire operational envelope. In the event that the analysis identifies that the aircraft does not have sufficient strength, it is further recommended that EASA take immediate action to ensure the ongoing safe operation of ATR42/72 aircraft.
  • CASA review ATR’s engineering assessment of transient elevator deflections associated with a pitch disconnect, to determine whether the aircraft can safely withstand the aerodynamic loads resulting from a pitch disconnect within the entire operational envelope. In the event that the analysis identifies that the aircraft does not have sufficient strength, it is further recommended that CASA take immediate action to ensure the ongoing safe operation of Australian‑registered ATR42/72 aircraft. P2 - Funny how for CASA immediate means sometime in the next century... Huh
Summary

Readers of this report are encouraged to read this report in conjunction with, the interim report released on 15 June 2016 report and an update on the ATSB website on 10 June 2014.

A final report is expected to be published in August 2017 (P2 - Must be a typo...err maybe HVH 's motley minions meant August 2027... Big Grin ) and will include the results of the further testing and assurance activity being conducted by ATR, and will also include operational, maintenance, training and regulatory aspects associated with the incident.

 

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

Last update 05 May 2017


Oh well, good to see that HVH and his minions are upholding the Beaker record for making the ATSB the premier international top-cover experts for effective obfuscation of potentially embarrassing aviation accident investigations.

For classic example please refer to the ongoing OI search for MH370:

[Image: Untitled_Clipping_101817_073106_AM.jpg]
Oh but that's right.. "nothing to do with us your honour" ... Undecided    







MTF...P2 Cool
Reply


Messages In This Thread
Overdue and Obfuscated. - by Kharon - 02-19-2015, 07:44 AM
RE: Proof of ATSB delays - by Kharon - 03-21-2019, 08:04 AM
RE: Proof of ATSB delays - by Kharon - 03-22-2019, 08:31 AM
RE: Proof of ATSB delays - by Choppagirl - 03-22-2019, 10:50 PM
RE: Proof of ATSB delays - by Gobbledock - 03-23-2019, 03:11 PM
RE: Proof of ATSB delays - by Choppagirl - 03-23-2019, 08:41 PM
RE: Proof of ATSB delays - by Sandy Reith - 03-24-2019, 01:01 PM
RE: Proof of ATSB delays - by Choppagirl - 03-26-2019, 06:14 AM
RE: Proof of ATSB delays - by Kharon - 03-26-2019, 07:20 AM
RE: Proof of ATSB delays - by Sandy Reith - 03-26-2019, 09:15 PM
RE: Proof of ATSB delays - by Choppagirl - 03-26-2019, 11:01 PM
RE: Proof of ATSB delays - by Kharon - 03-27-2019, 08:11 AM
RE: Proof of ATSB delays - by Choppagirl - 03-27-2019, 10:27 PM
RE: Proof of ATSB delays - by Kharon - 03-29-2019, 08:14 PM
RE: Proof of ATSB delays - by Kharon - 03-29-2019, 08:14 PM
RE: Proof of ATSB delays - by Peetwo - 03-30-2019, 10:40 AM
RE: Proof of ATSB delays - by Choppagirl - 04-02-2019, 03:46 PM
RE: Proof of ATSB delays - by Peetwo - 04-02-2019, 07:09 PM
RE: Proof of ATSB delays - by Choppagirl - 04-02-2019, 08:55 PM
RE: Proof of ATSB delays - by Choppagirl - 04-02-2019, 09:13 PM
RE: Proof of ATSB delays - by Peetwo - 04-03-2019, 12:11 PM
RE: Proof of ATSB delays - by Peetwo - 04-05-2019, 11:21 AM
RE: Proof of ATSB delays - by Peetwo - 04-09-2019, 05:29 PM
RE: Proof of ATSB delays - by Peetwo - 04-10-2019, 10:29 AM
RE: Proof of ATSB delays - by P7_TOM - 04-10-2019, 07:52 PM
RE: Proof of ATSB delays - by Peetwo - 05-18-2019, 11:49 AM
RE: Proof of ATSB delays - by Peetwo - 05-25-2019, 01:39 PM
RE: Proof of ATSB delays - by thorn bird - 05-25-2019, 03:26 PM
RE: Proof of ATSB delays - by P7_TOM - 05-26-2019, 08:27 AM
RE: Proof of ATSB delays - by Kharon - 05-27-2019, 08:06 AM
RE: Proof of ATSB delays - by Peetwo - 05-27-2019, 09:48 PM
RE: Proof of ATSB delays - by Kharon - 05-28-2019, 07:33 AM
RE: Proof of ATSB delays - by Peetwo - 05-29-2019, 11:15 AM
RE: Proof of ATSB delays - by Kharon - 05-30-2019, 07:55 AM
RE: Proof of ATSB delays - by P7_TOM - 05-31-2019, 07:51 AM
RE: Proof of ATSB delays - by Peetwo - 05-31-2019, 10:59 AM
RE: Proof of ATSB delays - by Kharon - 06-01-2019, 08:18 AM
RE: Proof of ATSB delays - by Kharon - 08-07-2019, 08:38 AM
RE: Proof of ATSB delays - by Peetwo - 08-16-2019, 11:14 AM
RE: Proof of ATSB delays - by Choppagirl - 09-14-2019, 06:11 PM
RE: Proof of ATSB delays - by Kharon - 09-18-2019, 08:08 AM
RE: Proof of ATSB delays - by Peetwo - 11-13-2019, 10:18 AM
RE: Proof of ATSB delays - by Kharon - 11-16-2019, 08:18 AM
RE: Proof of ATSB delays - by Peetwo - 11-22-2019, 10:41 AM
RE: Proof of ATSB delays - by Peetwo - 12-20-2019, 10:20 AM
RE: Proof of ATSB delays - by Peetwo - 12-04-2019, 12:31 PM
RE: Proof of ATSB delays - by Kharon - 12-05-2019, 07:37 AM
RE: Proof of ATSB delays - by Peetwo - 12-07-2019, 10:01 AM
RE: Proof of ATSB delays - by Kharon - 01-06-2020, 06:41 AM
RE: Proof of ATSB delays - by Peetwo - 01-07-2020, 10:02 AM
RE: Proof of ATSB delays - by Peetwo - 01-17-2020, 09:21 AM
RE: Proof of ATSB delays - by Peetwo - 01-25-2020, 12:25 PM
RE: Proof of ATSB delays - by Kharon - 01-25-2020, 10:18 PM
RE: Proof of ATSB delays - by Peetwo - 01-27-2020, 09:54 AM
RE: Proof of ATSB delays - by Peetwo - 01-28-2020, 09:54 PM
RE: Proof of ATSB delays - by Peetwo - 01-29-2020, 09:53 AM
RE: Proof of ATSB delays - by P7_TOM - 01-29-2020, 08:31 PM
RE: Proof of ATSB delays - by Peetwo - 01-31-2020, 10:53 AM
RE: Proof of ATSB delays - by Peetwo - 02-01-2020, 12:37 PM
RE: Proof of ATSB delays - by Peetwo - 02-06-2020, 10:51 AM
RE: Proof of ATSB delays - by Peetwo - 02-07-2020, 08:09 AM
RE: Proof of ATSB delays - by Peetwo - 03-07-2020, 12:33 PM
RE: Proof of ATSB delays - by Kharon - 02-08-2020, 08:22 AM
RE: Proof of ATSB delays - by Choppagirl - 02-09-2020, 06:04 AM
RE: Proof of ATSB delays - by Peetwo - 02-12-2020, 10:35 AM
RE: Proof of ATSB delays - by P7_TOM - 02-13-2020, 07:37 PM
RE: Proof of ATSB delays - by Peetwo - 02-26-2020, 09:10 AM
RE: Proof of ATSB delays - by P7_TOM - 02-26-2020, 07:59 PM
RE: Proof of ATSB delays - by P7_TOM - 02-27-2020, 08:02 PM
RE: Proof of ATSB delays - by Peetwo - 02-28-2020, 11:38 PM
RE: Proof of ATSB delays - by Peetwo - 03-12-2020, 11:37 PM
RE: Proof of ATSB delays - by Kharon - 03-13-2020, 06:18 AM
RE: Proof of ATSB delays - by Peetwo - 03-16-2020, 03:20 PM
RE: Proof of ATSB delays - by Peetwo - 04-01-2020, 08:01 AM
RE: Proof of ATSB delays - by Kharon - 04-06-2020, 06:53 AM
RE: Proof of ATSB delays - by thorn bird - 04-06-2020, 08:48 AM
RE: Proof of ATSB delays - by Peetwo - 04-09-2020, 10:54 AM
RE: Proof of ATSB delays - by ventus45 - 04-09-2020, 12:24 PM
RE: Proof of ATSB delays - by Peetwo - 04-10-2020, 03:22 PM
RE: Proof of ATSB delays - by ventus45 - 04-10-2020, 05:20 PM
RE: Proof of ATSB delays - by P7_TOM - 04-10-2020, 08:29 PM
RE: Proof of ATSB delays - by Kharon - 04-14-2020, 08:32 PM
RE: Proof of ATSB delays - by Peetwo - 04-24-2020, 10:16 AM
RE: Proof of ATSB delays - by Peetwo - 05-29-2020, 09:27 AM
RE: Proof of ATSB delays - by Kharon - 04-27-2020, 09:55 PM
RE: Proof of ATSB delays - by Choppagirl - 04-28-2020, 06:41 AM
RE: Proof of ATSB delays - by P7_TOM - 04-29-2020, 09:05 PM
RE: Proof of ATSB delays - by Peetwo - 04-30-2020, 11:27 AM
RE: Proof of ATSB delays - by Peetwo - 04-30-2020, 03:58 PM
RE: Proof of ATSB delays - by Kharon - 05-01-2020, 08:30 AM
RE: Proof of ATSB delays - by Peetwo - 05-01-2020, 01:39 PM
RE: Proof of ATSB delays - by Choppagirl - 05-01-2020, 06:15 PM
RE: Proof of ATSB delays - by Peetwo - 05-06-2020, 11:22 AM
RE: Proof of ATSB delays - by Kharon - 05-06-2020, 07:00 PM
RE: Proof of ATSB delays - by Kharon - 06-02-2020, 06:24 PM
RE: Proof of ATSB delays - by Peetwo - 06-09-2020, 10:36 AM
RE: Proof of ATSB delays - by Peetwo - 06-19-2020, 11:59 AM
RE: Proof of ATSB delays - by Peetwo - 07-03-2020, 01:39 PM
RE: Proof of ATSB delays - by Kharon - 07-04-2020, 07:56 AM
RE: Proof of ATSB delays - by Peetwo - 07-04-2020, 09:40 PM
RE: Proof of ATSB delays - by Kharon - 07-06-2020, 06:41 AM
RE: Proof of ATSB delays - by Peetwo - 07-07-2020, 01:41 PM
RE: Proof of ATSB delays - by Kharon - 07-08-2020, 07:24 AM
RE: Proof of ATSB delays - by Peetwo - 07-08-2020, 11:17 AM
RE: Proof of ATSB delays - by Peetwo - 08-07-2020, 11:20 AM
RE: Proof of ATSB delays - by Kharon - 08-08-2020, 09:15 AM
RE: Proof of ATSB delays - by Choppagirl - 08-11-2020, 05:17 AM
RE: Proof of ATSB delays - by Kharon - 08-09-2020, 06:24 PM
RE: Proof of ATSB delays - by Kharon - 08-11-2020, 08:24 AM
RE: Proof of ATSB delays - by Peetwo - 08-12-2020, 10:38 AM
RE: Proof of ATSB delays - by Kharon - 08-12-2020, 08:23 AM
RE: Proof of ATSB delays - by Peetwo - 08-12-2020, 10:50 AM
RE: Proof of ATSB delays - by Kharon - 08-17-2020, 08:14 AM
RE: Proof of ATSB delays - by P7_TOM - 08-19-2020, 08:14 PM
RE: Proof of ATSB delays - by Peetwo - 09-05-2020, 10:57 AM
RE: Proof of ATSB delays - by thorn bird - 09-05-2020, 09:14 PM
RE: Proof of ATSB delays - by Peetwo - 10-01-2020, 07:03 PM
RE: Proof of ATSB delays - by Peetwo - 11-13-2020, 08:22 AM
RE: Proof of ATSB delays - by Kharon - 11-14-2020, 07:10 AM
RE: Proof of ATSB delays - by Peetwo - 12-15-2020, 09:06 PM
RE: Proof of ATSB delays - by Peetwo - 01-05-2021, 10:34 AM
RE: Proof of ATSB delays - by Peetwo - 01-07-2021, 09:59 AM
RE: Proof of ATSB delays - by Peetwo - 01-20-2021, 10:10 AM
RE: Proof of ATSB delays - by P7_TOM - 01-20-2021, 08:23 PM
RE: Proof of ATSB delays - by Peetwo - 01-29-2021, 12:12 PM
RE: Proof of ATSB delays - by Peetwo - 01-30-2021, 07:10 PM
RE: Proof of ATSB delays - by P7_TOM - 02-01-2021, 07:33 PM
RE: Proof of ATSB delays - by Kharon - 03-31-2021, 06:15 AM
RE: Proof of ATSB delays - by P7_TOM - 05-06-2021, 09:03 PM
RE: Proof of ATSB delays - by Peetwo - 06-24-2021, 11:09 AM
RE: Proof of ATSB delays - by Peetwo - 07-29-2021, 11:10 AM
RE: Proof of ATSB delays - by Peetwo - 03-22-2023, 10:55 PM
RE: Proof of ATSB delays - by Sandy Reith - 03-23-2023, 09:49 AM
RE: Proof of ATSB delays - by Gentle - 03-23-2023, 08:36 PM
RE: Proof of ATSB delays - by Kharon - 03-24-2023, 07:00 AM
RE: Proof of ATSB delays - by Peetwo - 04-25-2023, 08:41 PM
RE: Proof of ATSB delays - by Peetwo - 04-28-2023, 05:41 PM
RE: Proof of ATSB delays - by Peetwo - 05-17-2023, 09:13 PM
RE: Proof of ATSB delays - by Peetwo - 05-20-2023, 09:52 AM
RE: Proof of ATSB delays - by Peetwo - 05-27-2023, 10:08 AM
RE: Proof of ATSB delays - by Peetwo - 06-09-2023, 06:07 PM
RE: Proof of ATSB delays - by Peetwo - 06-18-2023, 09:52 AM
RE: Proof of ATSB delays - by Kharon - 06-23-2023, 07:12 AM
RE: Proof of ATSB delays - by Peetwo - 06-30-2023, 09:10 PM
RE: Proof of ATSB delays - by Peetwo - 07-18-2023, 09:06 AM
RE: Proof of ATSB delays - by Kharon - 07-27-2023, 08:27 AM
RE: Proof of ATSB delays - by Peetwo - 10-12-2023, 10:32 AM
RE: Proof of ATSB delays - by Peetwo - 10-12-2023, 06:56 PM
RE: Proof of ATSB delays - by Peetwo - 10-27-2023, 10:14 AM
RE: Proof of ATSB delays - by P7_TOM - 01-08-2024, 07:55 AM
RE: Proof of ATSB delays - by Peetwo - 01-27-2024, 06:43 PM
RE: Proof of ATSB delays - by Peetwo - 02-01-2024, 06:57 PM
RE: Proof of ATSB delays - by Peetwo - 03-03-2024, 09:15 AM
RE: Overdue and Obfuscated. - by Peetwo - 02-19-2015, 09:28 AM
Hot off Dougy's keyboard - by Peetwo - 02-19-2015, 11:21 AM
RE: Was ICAO mislead? - by Kharon - 02-19-2015, 03:04 PM
RE: Overdue and Obfuscated. - by Peetwo - 02-25-2015, 02:09 PM
RE: Overdue and Obfuscated. - by Peetwo - 02-25-2015, 02:16 PM
RE: Overdue and Obfuscated. - by Peetwo - 04-24-2015, 12:38 PM
Aw shucks P2. - by P7_TOM - 04-24-2015, 01:36 PM
RE: Overdue and Obfuscated. - by Gobbledock - 04-24-2015, 05:14 PM
RE: Overdue and Obfuscated. - by Peetwo - 05-03-2015, 12:46 PM
RE: Overdue and Obfuscated. - by Gobbledock - 05-03-2015, 07:00 PM
RE: Overdue and Obfuscated. - by Peetwo - 05-08-2015, 02:35 PM
A trip down Beaker lane.... - by Gobbledock - 06-08-2015, 03:48 PM
RE: Overdue and Obfuscated. - by Peetwo - 06-15-2015, 08:01 AM
RE: Overdue and Obfuscated. - by Kharon - 06-16-2015, 08:06 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-17-2015, 06:34 PM
The risk is on the Governments head - by Gobbledock - 06-18-2015, 07:58 PM
RE: Overdue and Obfuscated. - by Peetwo - 07-21-2015, 12:12 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-10-2015, 07:21 AM
RE: Overdue and Obfuscated. - by P7_TOM - 11-10-2015, 05:08 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-10-2015, 07:05 PM
RE: Overdue and Obfuscated. - by Gobbledock - 11-10-2015, 07:55 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-10-2015, 08:31 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-11-2015, 09:07 AM
RE: Overdue and Obfuscated. - by ventus45 - 11-11-2015, 06:45 PM
RE: Overdue and Obfuscated. - by Kharon - 11-12-2015, 07:32 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-15-2015, 09:20 AM
RE: Overdue and Obfuscated. - by ventus45 - 11-15-2015, 09:53 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-15-2015, 10:09 PM
RE: Overdue and Obfuscated. - by Gobbledock - 11-15-2015, 10:38 PM
RE: Overdue and Obfuscated. - by Kharon - 11-16-2015, 06:25 AM
RE: Overdue and Obfuscated. - by Gobbledock - 11-16-2015, 12:48 PM
RE: Overdue and Obfuscated. - by 6317alan - 11-17-2015, 01:39 PM
RE: Overdue and Obfuscated. - by ventus45 - 11-17-2015, 03:07 PM
RE: Overdue and Obfuscated. - by 6317alan - 11-18-2015, 09:03 AM
RE: Overdue and Obfuscated. - by ventus45 - 11-18-2015, 11:03 AM
RE: Overdue and Obfuscated. - by 6317alan - 11-18-2015, 11:08 AM
RE: Overdue and Obfuscated. - by 6317alan - 11-18-2015, 11:14 AM
RE: Overdue and Obfuscated. - by ventus45 - 11-18-2015, 11:17 AM
RE: Overdue and Obfuscated. - by Gobbledock - 11-18-2015, 01:16 PM
RE: Overdue and Obfuscated. - by Kharon - 11-18-2015, 03:26 PM
RE: Overdue and Obfuscated. - by 6317alan - 11-19-2015, 04:14 PM
RE: Overdue and Obfuscated. - by P7_TOM - 11-19-2015, 06:22 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-20-2015, 07:57 AM
RE: Overdue and Obfuscated. - by 6317alan - 11-20-2015, 01:05 PM
RE: Overdue and Obfuscated. - by Kharon - 11-22-2015, 06:00 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-25-2015, 12:30 PM
RE: Overdue and Obfuscated. - by Kharon - 11-26-2015, 05:36 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-28-2015, 11:04 AM
RE: Overdue and Obfuscated. - by Kharon - 11-29-2015, 05:37 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-29-2015, 03:43 PM
RE: Overdue and Obfuscated. - by Kharon - 11-30-2015, 07:43 AM
RE: Overdue and Obfuscated. - by Gobbledock - 11-30-2015, 10:01 PM
RE: Overdue and Obfuscated. - by P7_TOM - 01-24-2016, 01:29 PM
RE: Overdue and Obfuscated. - by Peetwo - 01-25-2016, 02:34 PM
RE: Overdue and Obfuscated. - by Peetwo - 02-03-2016, 08:57 AM
RE: Overdue and Obfuscated. - by thorn bird - 02-04-2016, 08:28 AM
RE: Overdue and Obfuscated. - by Kharon - 02-07-2016, 01:35 PM
RE: Overdue and Obfuscated. - by Peetwo - 02-07-2016, 09:54 PM
RE: Overdue and Obfuscated. - by Peetwo - 03-04-2016, 10:21 AM
RE: Overdue and Obfuscated. - by Peetwo - 03-04-2016, 10:38 AM
RE: Overdue and Obfuscated. - by Kharon - 03-06-2016, 06:08 AM
RE: Overdue and Obfuscated. - by Peetwo - 03-10-2016, 07:45 PM
RE: Overdue and Obfuscated. - by Peetwo - 04-06-2016, 09:42 AM
RE: Overdue and Obfuscated. - by Kharon - 04-14-2016, 05:19 AM
RE: Overdue and Obfuscated. - by Peetwo - 04-14-2016, 08:00 AM
RE: Overdue and Obfuscated. - by P7_TOM - 04-14-2016, 05:38 PM
RE: Overdue and Obfuscated. - by Gobbledock - 04-14-2016, 10:58 PM
RE: Overdue and Obfuscated. - by Kharon - 04-15-2016, 07:22 AM
RE: Overdue and Obfuscated. - by Peetwo - 04-17-2016, 11:55 AM
RE: Overdue and Obfuscated. - by Kharon - 04-18-2016, 06:17 AM
RE: Overdue and Obfuscated. - by Peetwo - 04-18-2016, 09:39 AM
RE: Overdue and Obfuscated. - by ventus45 - 04-18-2016, 12:24 PM
RE: Overdue and Obfuscated. - by Gobbledock - 04-18-2016, 09:12 PM
RE: Overdue and Obfuscated. - by Kharon - 04-19-2016, 05:47 AM
RE: Overdue and Obfuscated. - by Peetwo - 04-20-2016, 08:23 PM
RE: Overdue and Obfuscated. - by ventus45 - 04-21-2016, 12:45 AM
RE: Overdue and Obfuscated. - by Kharon - 04-21-2016, 06:57 AM
RE: Overdue and Obfuscated. - by ventus45 - 04-21-2016, 01:17 PM
RE: Overdue and Obfuscated. - by Kharon - 04-22-2016, 07:30 AM
RE: Overdue and Obfuscated. - by ventus45 - 04-23-2016, 10:45 AM
RE: Overdue and Obfuscated. - by MrPeaBody - 05-02-2016, 04:36 PM
RE: Overdue and Obfuscated. - by ventus45 - 05-02-2016, 05:49 PM
RE: Overdue and Obfuscated. - by Peetwo - 05-24-2016, 10:49 PM
RE: Overdue and Obfuscated. - by Kharon - 05-25-2016, 07:36 AM
RE: Overdue and Obfuscated. - by ventus45 - 05-25-2016, 01:56 PM
RE: Overdue and Obfuscated. - by thorn bird - 05-25-2016, 06:28 PM
RE: Overdue and Obfuscated. - by Peetwo - 05-31-2016, 01:27 PM
RE: Overdue and Obfuscated. - by Peetwo - 05-31-2016, 04:18 PM
RE: Overdue and Obfuscated. - by Kharon - 06-01-2016, 08:11 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-01-2016, 08:19 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-01-2016, 10:39 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-03-2016, 01:01 PM
RE: Overdue and Obfuscated. - by Kharon - 06-04-2016, 06:52 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-04-2016, 12:13 PM
RE: Overdue and Obfuscated. - by Kharon - 06-06-2016, 07:30 AM
RE: Overdue and Obfuscated. - by Kharon - 06-08-2016, 08:12 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-15-2016, 07:34 PM
RE: Overdue and Obfuscated. - by P7_TOM - 06-15-2016, 09:20 PM
RE: Overdue and Obfuscated. - by Kharon - 06-16-2016, 08:52 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-16-2016, 11:17 AM
RE: Overdue and Obfuscated. - by P7_TOM - 06-16-2016, 03:15 PM
RE: Overdue and Obfuscated. - by ventus45 - 06-17-2016, 12:28 AM
RE: Overdue and Obfuscated. - by thorn bird - 06-17-2016, 06:21 AM
RE: Overdue and Obfuscated. - by Kharon - 06-17-2016, 08:09 AM
RE: Overdue and Obfuscated. - by Gobbledock - 06-20-2016, 08:59 PM
RE: Overdue and Obfuscated. - by Peetwo - 07-05-2016, 08:59 PM
RE: Overdue and Obfuscated. - by Gobbledock - 07-05-2016, 09:06 PM
RE: Overdue and Obfuscated. - by Peetwo - 07-06-2016, 12:54 PM
RE: Overdue and Obfuscated. - by Peetwo - 07-11-2016, 02:28 PM
RE: Overdue and Obfuscated. - by Peetwo - 08-15-2016, 06:00 PM
RE: Overdue and Obfuscated. - by Peetwo - 08-18-2016, 10:52 AM
RE: Overdue and Obfuscated. - by Gobbledock - 08-18-2016, 07:58 PM
RE: Overdue and Obfuscated. - by Peetwo - 08-19-2016, 07:49 AM
RE: Overdue and Obfuscated. - by Gobbledock - 08-19-2016, 11:16 AM
RE: Overdue and Obfuscated. - by Kharon - 08-20-2016, 08:42 AM
RE: Overdue and Obfuscated. - by Gobbledock - 08-20-2016, 10:19 AM
RE: Overdue and Obfuscated. - by thorn bird - 08-20-2016, 02:46 PM
RE: Overdue and Obfuscated. - by Peetwo - 09-02-2016, 09:41 AM
RE: Overdue and Obfuscated. - by thorn bird - 09-02-2016, 01:35 PM
RE: Overdue and Obfuscated. - by ventus45 - 09-03-2016, 11:56 AM
RE: Overdue and Obfuscated. - by thorn bird - 09-03-2016, 01:30 PM
RE: Overdue and Obfuscated. - by Peetwo - 09-03-2016, 02:39 PM
RE: Overdue and Obfuscated. - by Gobbledock - 09-03-2016, 05:40 PM
RE: Overdue and Obfuscated. - by Peetwo - 10-14-2016, 10:32 AM
RE: Overdue and Obfuscated. - by Gobbledock - 10-14-2016, 11:45 AM
RE: Overdue and Obfuscated. - by Sandy Reith - 10-14-2016, 08:44 PM
RE: Overdue and Obfuscated. - by Peetwo - 10-15-2016, 08:01 AM
RE: Overdue and Obfuscated. - by Peetwo - 10-15-2016, 11:42 AM
RE: Overdue and Obfuscated. - by Gobbledock - 10-15-2016, 12:06 PM
RE: Overdue and Obfuscated. - by Kharon - 10-17-2016, 05:47 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-11-2016, 10:54 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-15-2016, 08:34 PM
RE: Overdue and Obfuscated. - by Kharon - 11-24-2016, 07:17 AM
RE: Overdue and Obfuscated. - by Gobbledock - 11-24-2016, 02:29 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-25-2016, 08:38 AM
RE: Overdue and Obfuscated. - by Gobbledock - 11-25-2016, 09:06 AM
RE: Overdue and Obfuscated. - by Kharon - 11-28-2016, 06:09 AM
RE: Overdue and Obfuscated. - by Gobbledock - 11-28-2016, 12:08 PM
RE: Overdue and Obfuscated. - by Peetwo - 11-29-2016, 05:18 PM
RE: Overdue and Obfuscated. - by Kharon - 11-29-2016, 06:08 PM
RE: Overdue and Obfuscated. - by Gobbledock - 11-29-2016, 11:29 PM
RE: Overdue and Obfuscated. - by ventus45 - 12-01-2016, 12:11 PM
RE: Overdue and Obfuscated. - by Kharon - 12-01-2016, 07:03 PM
RE: Overdue and Obfuscated. - by Peetwo - 02-23-2017, 08:45 PM
RE: Overdue and Obfuscated. - by Peetwo - 06-05-2017, 07:21 AM
RE: Overdue and Obfuscated. - by Gobbledock - 06-05-2017, 09:15 PM
RE: Overdue and Obfuscated. - by Kharon - 06-10-2017, 06:42 AM
RE: Overdue and Obfuscated. - by Peetwo - 07-25-2017, 10:10 AM
RE: Overdue and Obfuscated. - by Peetwo - 10-26-2017, 11:28 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-13-2017, 09:31 PM
RE: Overdue and Obfuscated. - by thorn bird - 11-14-2017, 07:20 AM
RE: Overdue and Obfuscated. - by Kharon - 11-15-2017, 06:43 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-15-2017, 09:46 PM
RE: Overdue and Obfuscated. - by Kharon - 11-17-2017, 06:24 AM
RE: Overdue and Obfuscated. - by Peetwo - 11-24-2017, 10:14 AM
RE: Overdue and Obfuscated. - by Peetwo - 12-01-2017, 06:56 AM
RE: Overdue and Obfuscated. - by Peetwo - 12-14-2017, 05:50 PM
RE: Overdue and Obfuscated. - by P7_TOM - 12-14-2017, 10:35 PM
RE: Overdue and Obfuscated. - by Peetwo - 12-16-2017, 11:27 AM
RE: Overdue and Obfuscated. - by Peetwo - 02-02-2018, 04:57 PM
RE: Overdue and Obfuscated. - by Kharon - 02-08-2018, 08:40 PM
RE: Overdue and Obfuscated. - by Peetwo - 02-19-2018, 08:08 PM
RE: Overdue and Obfuscated. - by Peetwo - 03-03-2018, 08:50 PM
RE: Overdue and Obfuscated. - by Peetwo - 03-17-2018, 12:28 PM
RE: Overdue and Obfuscated. - by Kharon - 03-20-2018, 07:44 AM
RE: Overdue and Obfuscated. - by thorn bird - 03-20-2018, 08:25 PM
RE: Overdue and Obfuscated. - by Kharon - 03-21-2018, 07:57 AM
RE: Overdue and Obfuscated. - by P7_TOM - 03-21-2018, 07:39 PM
RE: Overdue and Obfuscated. - by Kharon - 03-22-2018, 07:54 AM
RE: Overdue and Obfuscated. - by Peetwo - 04-11-2018, 08:04 AM
RE: Overdue and Obfuscated. - by Peetwo - 05-07-2018, 07:58 PM
RE: Overdue and Obfuscated. - by Gobbledock - 05-18-2018, 01:12 PM
RE: Overdue and Obfuscated. - by thorn bird - 05-19-2018, 07:02 AM
RE: Overdue and Obfuscated. - by Gobbledock - 06-02-2018, 09:39 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-02-2018, 01:40 PM
RE: Overdue and Obfuscated. - by Gobbledock - 06-02-2018, 04:07 PM
RE: Overdue and Obfuscated. - by Peetwo - 06-15-2018, 08:40 AM
RE: Overdue and Obfuscated. - by Gobbledock - 06-17-2018, 12:01 PM
RE: Overdue and Obfuscated. - by Peetwo - 06-27-2018, 11:30 AM
RE: Overdue and Obfuscated. - by Kharon - 06-29-2018, 05:51 AM
RE: Overdue and Obfuscated. - by Peetwo - 06-30-2018, 10:17 AM
RE: Overdue and Obfuscated. - by Peetwo - 10-30-2018, 08:15 PM
RE: Overdue and Obfuscated. - by Peetwo - 01-31-2019, 11:20 AM
RE: Overdue and Obfuscated. - by Gobbledock - 01-31-2019, 02:23 PM
RE: Overdue and Obfuscated. - by Kharon - 01-31-2019, 07:37 PM
RE: Overdue and Obfuscated. - by Peetwo - 03-14-2019, 08:58 AM
Proof of ATSB delays - by Choppagirl - 03-20-2019, 08:32 PM
RE: Proof of ATSB delays - by Peetwo - 03-21-2019, 11:03 AM
RE: Proof of ATSB delays - by Choppagirl - 03-22-2019, 02:21 AM



Users browsing this thread: 5 Guest(s)