Proof of ATSB delays

Popinjay to the rescue with AO-2024-035 Prelim report..etc Dodgy

On 4 September PJ was attributed to this bollocks media spin, announcing the Annex 13 non-conforming (by 53 days) prelim report release for Short investigation AO-2024-035... Rolleyes
   
Quote:Preliminary report details passenger 737 flight below minimum safe altitude near Canberra
[Image: AO-2024-035-Figure%203_0.jpg?itok=a5RyaiD3]

A preliminary report from the ATSB’s on-going investigation into a flight below minimum altitude incident involving a Boeing 737 south of Canberra notes the operator involved has taken a number of proactive safety actions. 

On the evening of 13 June 2024, the Boeing 737-800 had departed Denpasar, Indonesia, operating Batik Air’s inaugural flight to Canberra, the report details. Forecast tailwinds resulted in an estimated arrival time just prior to 0600 on 14 June, which was earlier than planned, and before Canberra Tower and Canberra Approach air traffic control commenced services for the day. 

The crew elected to proceed, without delaying to wait for those air traffic services to become available, which meant arriving in Canberra using the Canberra Airport CTAF (common traffic advisory frequency – where pilots use radio calls to announce their positions and arrange separation from other aircraft). 

As the aircraft descended in darkness towards Canberra, the crew prepared to conduct the AVBEG 5A standard arrival route (or STAR – which uses satellite-based positioning waypoints to transition aircraft from en route flight to, in this case, an initial approach fix waypoint for Canberra Airport’s instrument landing system approach). 

“While the crew intended to fly the STAR, they did not request this from the air traffic controller managing the airspace,” ATSB Chief Commissioner Angus Mitchell said. 

Instead, the controller expected the crew to track along the clearance previously provided direct to Canberra Airport from the AVBEG waypoint, which is to the north-west of the airport and is also the first waypoint of the AVBEG 5A STAR. 

The crew proceeded with their planned standard arrival route, which meant the aircraft deviated from the cleared track direct to Canberra, and instead tracked to a series of waypoints to the south-west and south of the airport. 
The controller, unaware of the flight crew’s intentions, did not query the deviation, but did instruct them to maintain 10,000 ft to remain clear of a restricted area around the Deep Space Communications Complex at Tidbinbilla to the west of Canberra (this separation is built into the STAR).  

“After receiving this instruction, the flight crew became uncertain as to whether the aircraft would be operating within, or outside of, controlled airspace during the standard arrival route and approach,” Mr Mitchell explained. 
After levelling the aircraft at 10,000 ft, the crew subsequently requested ATC clearance to conduct the instrument landing system (ILS) approach to Canberra. The controller advised them that the Canberra tower was closed and that CTAF procedures applied for the airspace.  

A short time later, when tracking towards the airport from the south and having descended outside of controlled airspace, the flight crew identified they were above the desired flightpath, and the captain decided to conduct a holding pattern at the approach waypoint of MOMBI to reduce altitude. 

“During this holding pattern, the aircraft levelled out at 4,700 ft, but this meant it descended below minimum holding altitude of 5,600 ft, and at one point the aircraft passed 924 ft above terrain,” Mr Mitchell said. 

After rejoining the approach, the aircraft commenced descending again, following the runway 35 glidepath, and it landed without further incident. 

The report notes that while the aircraft was in the holding pattern, a controller in the Canberra Tower was preparing to commence the tower service for the day and they observed the aircraft below the minimum holding attitude. 

“The Tower controller made multiple attempts to contact the crew on the Canberra CTAF, but did not receive a response,” Mr Mitchell explained. 

At about the same time, the Canberra Approach controller commenced for the day – taking over the frequency the flight crew were listening to – and issued a safety alert that the aircraft was operating below the minimum safe altitude. 

The flight crew responded that they were visual with the runway and continued their approach. 

The ATSB’s continuing investigation will consider, among other elements, Batik Air’s procedures, training and route implementation processes, as well as air traffic control procedures and training. 

“A final report with analysis and findings will be released at the conclusion of the investigation, but we note the operator has already pro-actively taken safety actions,” Mr Mitchell concluded. 

“These include revising their Canberra Airport briefing documentation, issuing flight crew notices highlighting procedures for operating in non-controlled airspace, and rescheduling flights to Canberra to ensure they arrive during air traffic control operating hours.” 

Read the preliminary report: Flight below minimum altitude involving Boeing 737, PK-LDK, 19 km south of Canberra Airport, Australian Capital Territory, on 14 June 2024


Publication Date: 04/09/2024

Hmm...I guess Batik Air is fair and uncontroversial game, being as it's an international operator not associated with QF or VA. However what is the point of continuing with this investigation and having PJ contributing 'attributable to' commentary, that effectively says the operator has already addressed the safety issues identified?  Rolleyes

Next we get DTS Dr Godlike being attributed to this media report announcing the release of SAN AO-2024-013-SAN-01

Quote:Chipmunk owners urged to ensure rivets are maintained to specifications following Jandakot accident

[Image: AO-2024-013-SAN-NewsItem.jpg?itok=GTiD44AW]

The ATSB advises DHC-1 Chipmunk maintainers and owners that crashworthiness could be significantly compromised if incorrect specification rivets are used.

The safety advisory notice has been issued as part of the ATSB’s continuing investigation into a fatal accident involving a Chipmunk at Jandakot Airport, WA, on 26 April 2024. 

As detailed in a preliminary report in July, shortly after take-off the aircraft was observed turning to the left at a low height before colliding with the ground, fatally injuring the pilot.

During the ongoing investigation the ATSB has identified that non-specification rivets had been installed on the aircraft, attaching the upper structure between the front and rear cockpits to the fuselage. This structure provides the attach point for the front cockpit shoulder harness.

“Two sets of rivets – 12 in total – attaching the structure to the fuselage sheared during the accident,” Director Transport Safety Dr Stuart Godley said. 

“The ATSB found that the rear row of rivets in each set – that is, three of the six rivets on each side – were pure or near-pure aluminium.”

This meant the rivets did not meet the specification of the relevant modification.

“Testing indicated a significant reduction in strength, estimated to be about one-third of the specification strength,” Dr Godley said.

The rivets would have been originally replaced during the embodiment of modification H.268, issued in 1966 by the aircraft’s type certificate holder at the time, Hawker Siddeley, to replace alloy structure elements with steel.
The aircraft may have modified in the 1960s, however the ATSB has not determined precisely when, or if, the rivets had been replaced since the modification.

It is important to note that while the crashworthiness of the aircraft had been compromised by the presence of non-specification rivets, the ATSB has yet to establish whether it contributed to the outcome of this accident.

However, as there is the potential for other Chipmunks to have incorrect rivets installed in this location, the ATSB determined it was important to bring the issue to the wider attention of Chipmunk operators.

“The ATSB’s safety advisory notice highlights the importance of maintaining aircraft crashworthiness design elements, including its restraint system, to keep the occupant within an aircraft’s ‘living space’ during an accident sequence,” Dr Godley said.

“The use of upper torso restraints such as a shoulder harness can prevent the occupant from striking the surrounding structure during an accident. It is crucial that all components forming part of that restraint system and the structures to which they are attached are maintained to defined specifications.”

The notice therefore advises DHC-1 Chipmunk maintainers and owners to be aware that fitment of incorrect specification rivets where the upper structure between the front and rear cockpits attaches to the gussets on either side could significantly compromise the crashworthiness of the aircraft.

“Those conducting work on aircraft must ensure modifications are carried out to the required specification, or during maintenance returned to that specification,” Dr Godley concluded.

The investigation is continuing, and the ATSB will issue a final report, which will detail findings and analysis, at the conclusion of the investigation.

Read the Safety Advisory Notice: DHC-1 Chipmunks may have incorrect rivets fitted


Publication Date:
11/09/2024

I guess kudos for the proactive initiative of releasing a SAN, however I'm not sure why Dr Godlike needs to be involved? I also query the timetable on when the safety issue was 1st identified to the release of the SAN nearly 5 months after the accident occurred?

Next 'attributed to' DTS Stewie Macleod announcing the release and findings of Short investigation AO-2022-066 (note the excuse for the delay in the investigation):

Quote:Saab 340 engine failure due to incorrectly seated coupling securing hydro-mechanical unit to accessory gearbox
[Image: AO-2022-066-NewsItem_0.jpg?itok=x0brLdjv]

The right engine of a Saab 340 flamed out shortly after the aircraft reached cruising altitude, after the engine’s hydro-mechanical unit driveshaft decoupled from the accessory gearbox due to an incorrectly seated coupling, leading to a fuel pump failure, an ATSB investigation report details.

The aircraft, with 2 flight crew, 1 cabin crew and 32 passengers on board, was operating a scheduled Regional Express service from Perth to Albany, WA, on the evening of 21 December 2022.

After climbing to 15,000 ft and establishing a direct track to Albany, the flight crew felt 2 bumps pass through the airframe, and felt the aircraft yaw.

Identifying that the right engine had failed, they conducted the associated checklists, secured the right engine, and returned to Perth where the aircraft landed without further incident.

“The ATSB’s investigation found that the right engine’s hydro-mechanical unit was incorrectly seated, resulting in a misalignment with the engine’s accessory gearbox, leading to significant wear and the eventual decoupling of the hydro‑mechanical unit’s drive shaft from the accessory gearbox,” ATSB Director Transport Safety Stuart Macleod explained.

“As a result, the fuel pump within the hydro-mechanical unit could not function, leading to the engine flameout.”
The engine, a GE Aerospace CT7, was removed from the aircraft for inspection at an authorised CT7 maintenance facility.

“While this inspection put the ATSB investigation on hold for an extended period, it did reveal that the V-band coupling securing the flanges of the hydro-mechanical unit to the accessory gearbox had wear on its inner surface from contact with the accessory gearbox flange,” Mr Macleod noted.

“Interference wear in this area was evidence of a misalignment and non-seating of the hydro‑mechanical unit onto the accessory gearbox.”

Maintenance records showed that the last recorded maintenance that required installation of the hydro-mechanical unit onto the accessory gearbox was during an engine workshop visit at a contractor maintenance facility in February 2018.

“This incident highlights that the incorrect alignment or seating of an aircraft or engine component may not be readily apparent after the installation of a V-band coupling or clamp,” Mr Macleod said. 

“As such it serves as a reminder to maintenance personnel installing V-band couplings to ensure the correct seating and alignment of flanges and the V-band coupling prior to the fitment and torquing of attaching hardware.”

Regional Express has since commenced a fleetwide inspection of its Saab aircraft to confirm the correct fitment of the V-band coupling, while GE Aerospace intends to share the learnings of this occurrence with its customers and maintenance facilities.

Read the report: Engine failure involving Saab 340B, VH-RXE, 141 km south of Perth, Western Australia, on 21 December 2022


Publication Date:
12/09/2024

MTF...P2 Tongue
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: Proof of ATSB delays - by Peetwo - 07-26-2024, 07:51 PM
RE: Proof of ATSB delays - by Peetwo - 09-14-2024, 11:02 AM
RE: Proof of ATSB delays - by Peetwo - 09-19-2024, 08:14 PM
RE: Proof of ATSB delays - by Kharon - 09-20-2024, 06:47 AM
RE: Proof of ATSB delays - by Peetwo - 10-16-2024, 11:06 PM
RE: Proof of ATSB delays - by Kharon - 10-17-2024, 06:14 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: 4 Guest(s)