Proof of ATSB delays

O&O report AO-2016-166

The following is an Oz Aviation summary article of this - AO-2016-166 - ATSB FR released three days ago   

Quote:ATSB calls for centreline lighting on wider runways after 2016 incident

written by australianaviation.com.au May 15, 2019

[Image: ao-2016-166_final_1170.jpg]The impact of the Virgin Australia runway excursion at Darwin Airport. (ATSB)

The Australian Transport Safety Bureau (ATSB) is renewing calls for centreline lighting to be installed on wider than usual runways following a 2016 incident where a Virgin Australia flight destroyed six runway lights when it landed 21m off the centre of the runway.

The incident occurred on December 6 2016, when the Virgin Australia Boeing 737-800 VH-VUI flying from Melbourne to Darwin was on approach to Runway 29. There was thunderstorm activity in the area and the flight was due to land at about 2300 local time.

The ATSB final report into the incident published on Wednesday said the flight crew had established and maintained clear visual reference to the runway and surrounds “until they encountered heavy rain shortly before reaching the runway threshold”.

“Under the influence of a light but increasing crosswind, the aircraft drifted right without the flight crew being able to discern the extent of the drift,” the final report said.

“The aircraft landed 21m to the right of the runway centreline and, shortly after touchdown, the right landing gear departed the sealed surface of the runway, destroying six runway lights before the aircraft returned to the runway.

“The aircraft incurred minor damage from ground debris and there were no injuries.”

In addition to the six runway lights being destroyed, the ATSB final report said debris from the lights and ground impacted the aircraft, resulting in minor damage to areas of the right aft fuselage and right horizontal stabiliser, and littered the edge of the runway surface.
There was also a large quantity of grass accumulated in the vicinity of the right wheel well, landing gear and wing flaps.

[Image: ao2016166_figure-2_750.jpg]
Wheel tracks where VH-VUI departed the runway 29 sealed surface and destroyed runway edge lights. (ATSB)

[Image: ao2016166_figure-3_750.jpg]
The tyre damage on VH-VUI. (ATSB)

[Image: ao2016166_figure-4_750.jpg]
The fuselage damage, marked with green tape, on VH-VUI. (ATSB)

Runway 29 at Darwin Airport measures about 60m wide and 3,350m long. The ATSB report noted the runway was about 15m wider than “almost all the other runways used by air transport aircraft in Australia”. It does not have centreline lighting.

As a result, the ATSB said the two rows of lights alongside Runway 29 were further apart than what a flight crew would normally encounter.
The ATSB said the absence of centreline lighting meant there were “very limited visual cues for maintaining runway alignment during night landings in reduced visibility”.

Darwin Airport is a shared civil and military facility. The Department of Defence owns the runway and other airport infrastructure, while Darwin International Airport runs the civilian operation.

The ATSB noted that while international guidelines recommended the use of centreline lighting on wider runways, there was no mandate from the International Civil Aviation Organisation (ICAO) to do so.

[Image: ao2016166_figure-1_750.jpg]
The final approach and landing roll of VH-VUI. (ATSB)

Further, its accident investigation records from 1997 to 2007 showed there had been two other incidents at Darwin Airport where the absence of centreline lighting may have been a factor.

The first was in 2003, when the right landing gear of a Boeing 737 veered off Runway 29 after landing 590m from the threshold, followed by the left landing gear about 760m from the threshold.

Another occurred in 2008, when a Boeing 717 made a “hard landing” at night. The ATSB investigation at the time said the lack of runway centreline lighting had reduced the available visual cues during the latter stages of the approach and landing on Runway 29.

The ATSB had recommended the installation of centreline lighting at Darwin Airport following the 2003 incident.

However, Darwin International Airport responded at the time that “a standard runway centerline system would be prohibitively expensive and is not currently a standard for our runway category”.

The ATSB also raised concerns following the 2008 landing. While the ATSB did not issue recommendation, it did seek a response from the Department of Defence, which said the installation, upgrade and maintenance costs for centreline lighting did not represent value for money.

“A wide runway without centreline lighting, such as at Darwin, poses a particular challenge for aircraft making approaches in darkness and heavy rain,” ATSB executive director for transport safety Nat Nagy said in a statement.

“In these circumstances centreline lighting greatly helps flight crews align the aircraft with the runway.”

The ATSB has issued a safety recommendation to ICAO to review the runway lighting standards in light of the new evidence available.

“The Australian Transport Safety Bureau recommends that the International Civil Aviation Organization review the effectiveness of Annex 14, recommendation 5.3.12.2 (for the installation of runway centreline lighting on Category I runways that are wider than 50 m), given that Category I runways that are wider than 50 m and without centreline lighting are over-represented in veer-off occurrences involving transport category aircraft landing in low visibility conditions,” the ATSB said.

The ATSB said both Darwin Airport and the Department of Defence had advised it that the installation of centreline lighting would be considered during any future runway works.

Meanwhile, the ATSB final report said Virgin Australia had introduced additional guidance to flight crews for approach to Darwin airport, including notes about runway surface, slope, width, lighting, and ambient light.

The carrier had also initiated specific training to pilots for loss of visibility in heavy rain, investigated enhancements to simulator modelling of degraded visibility at low levels, reviewed risk profiles for each airport including Darwin, commenced a program to investigate the potential to install hydrophobic windshield coatings on its 737 fleet, initiated a review of callouts for loss of visibility and reviewed the use of autopilot in poor weather, the ATSB said.

The full report can be read on the ATSB website.

[Image: 737-800_VH-VUI_SYDNEY_5NOVEMBER2016_SETH...1_1170.jpg]

On the face of it the report seems reasonable, however once you start to dissect, push, probe and compare IMO this is just another in a long..long series of top cover reports by the Hooded Canary and his not so merry team... Rolleyes

To begin why on earth did this investigation take 2 years, 5 months and 10 days (or 616 working days) to complete?

According to the safety issue addressed to Virgin the airline's SMS team had their identified safety issue(s) addressed inside of 2 months:

Quote:Aviation safety issues and actions
Operator guidance to flight crews
Issue number: AO-2016-166-SI-03
Who it affects: Virgin Australia Airlines flight crews operating into Darwin airport
Issue owner: Virgin Australia Airlines
Operation affected: Aviation: Air transport
Background: Investigation Report AO-2016-166
Date: 15 May 2019
Safety issue description
Virgin Australia did not have formal guidance for flight crews regarding the limited visual cues for maintaining alignment to runway 11/29 at Darwin during night landings in reduced visibility.

Proactive Action
Action organisation: Virgin Australia Airlines
Action number: AO-2016-166-NSA-012
Date: 20 January 2018
Action status: Closed
On 20 January 2017, the operator introduced additional guidance to flight crews for approach to Darwin airport, including notes about runway surface, slope, width, lighting, and ambient light.

Current issue status: Adequately addressed
Status justification:
The operator’s action, in conjunction with other safety actions, should provide crews with adequate guidance to enable them to assess risk and prepare for approaches in low visibility conditions at Darwin Airport.


Last update 15 May 2019

One has to ask how is it possible for an ATSB identified safety issue (above) be proactively addressed by the addressee a year before the safety issue was identified? And why wasn't the safety issue once identified then disseminated across the international aviation/airline industry? Surely if this was a deficiency in one airline this could also have a been a deficiency in other airlines?

Extract from the ATSB report:

Quote:Runway design standards and guidance

The International Civil Aviation Organization (ICAO) specifies standards and recommended practices (SARPS) for international aviation operations in a series of Annexes. ICAO Annex 14 (Aerodromes, Volume 1 Aerodrome Design and Operations, 7th edition July 2016) stated that runway centreline lights and touchdown zone lights shall be provided for runways with a category II or III[19] precision approach. It also stated:


Quote:5.3.12.2 Recommendation— Runway centre line lights should be provided on a precision approach runway category I, particularly when the runway is used by aircraft with high landing speeds or where the width between the runway edge lights is greater than 50 m.

Annex 14 had included the same or similar recommendation since 1966. There was no recommendation for touchdown zone lights for category I runways.

ICAO also published other guidance about aerodrome lighting. For example, ICAO document 9157 (Aerodrome Design Manual, Part 4 Visual Aids) stated:

Quote:The function of the centre line lighting is to provide the pilot with lateral guidance during the flare and landing ground roll or during a take-off. In normal circumstances, a pilot can maintain the track of the aircraft within approximately 1 to 2 m of the runway centre line with the aid of this lighting cue. The guidance information from the centreline is more sensitive than that provided from the pilot’s assessment of the degree of asymmetry between the runway edge lighting. In low visibility conditions, the use of the centre line is also the best means of providing an adequate segment of lighting for the pilot to use. The greater distances involved in viewing the runway edge lighting together with the need for the pilot to look immediately ahead of the aircraft during the ground roll also contribute to the requirements for a well-lit runway centre line.


Another section of the manual stated:

Quote:…Some of the most difficult tasks when flying an aircraft visually are judging the approach to a runway and the subsequent landing manoeuvre. During the approach, not only must the speed be carefully controlled, but continuous simultaneous corrections in all three dimensions are necessary in order to follow the correct flight path.


…There are two reasons why approach and runway lighting systems are provided with patterns that emphasize the centre line. One obvious reason is that the ideal landing position is along the centre of the runway. The other is that the fovea of the eye, the region of sharp vision, is only about 1.5 degrees in width…

Studies have shown that the average time required for a pilot to switch from outside visual cues to instruments and back to outside cues is about 2.5 seconds. Since high performance aircraft will travel at least 150 m in this time period, it is apparent that in so far as possible the visual aids should provide the utmost in guidance and information, enabling the pilot to proceed without the necessity of cross-checking the instruments…

Consistent with Annex 14, the MOS for CASR Part 139 required centreline and touchdown zone lighting for runways with category II or II approaches and recommended centreline lighting for category I runways with a width of more than 50 m.

Next from under 'other factors that increase risk' the ATSB report addressed a SR to ICAO:
Quote:Standards for installation of runway centreline lighting on wider runways [Image: internal_link.png?width=18&height=18&mode=max]

Safety issue number:  AO-2016-166-SI-01
Safety issue: Category I runways that are wider than 50 m and without centreline lighting are over-represented in veer-off occurrences involving transport category aircraft landing in low visibility conditions. The installation of centreline lighting on wider category I runways is recommended but not mandated by the International Civil Aviation Organization Annex 14.

Safety recommendation to the International Civil Aviation Organization

The Australian Transport Safety Bureau recommends that the International Civil Aviation Organization review the effectiveness of Annex 14, recommendation 5.3.12.2 (for the installation of runway centreline lighting on Category I runways that are wider than 50 m), given that Category I runways that are wider than 50 m and without centreline lighting are over-represented in veer-off occurrences involving transport category aircraft landing in low visibility conditions.

"..recommended but not mandated.." - Hmm...I thought everyone knew that ICAO only 'recommends'? After all the ICAO Annexes (SARPs) are exactly 'Standards And Recommended Practices' and a country which wishes to have a difference to those SARPs simply notifies that difference. Mandating is something the ICAO doesn't have the power to do but mandating is something that a signatory State's NAA (National Aviation Authority) is ultimately responsible for. This begs the question to why it is that the Hooded Canary team have not addressed a similar SR to CASA?

...Consistent with Annex 14, the MOS for CASR Part 139 required centreline and touchdown zone lighting for runways with category II or III approaches and recommended centreline lighting for category I runways with a width of more than 50 m...

Hmm...MTF? - Definitely...P2  Dodgy

ps Although there is no notified difference from Australia for Annex 14 Ch 5 para 5.3.12.2 there is one for 5.3.12.3 which is listed as a rare 'More exacting or exceeds' ND:


Quote:Runway centreline lights must be provided on the following: (a) a Cat II or III precision approach runway; (b) a runway intended for take-offs with an operating minimum below an RVR of 350 m.
 
Hmm...as usual 'nothing to see here, move along' -  Dodgy
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)