Shame or Fame for McCormack.

McDonaught aviation safety shamelist: ARFFS & Airservices -  Confused

Via BITN thread:

(07-31-2019, 11:45 AM)Peetwo Wrote:  OneSKY trough fund under threat?? 

Just released and tabled in Parliament by the ANAO: https://www.anao.gov.au/work/performance...rangements or https://www.anao.gov.au/sites/default/fi...2020_4.pdf 

Quote:OneSKY: Contractual Arrangements
PUBLISHED
Wednesday 31 July 2019


[Image: onesky_contractual_arrangements_anao.jpg]

Summary

Background

1. The December 2009 National Aviation White Paper identified expected benefits from synchronising civil and military air traffic management through the procurement of a single solution to replace the separate systems of Airservices Australia (Airservices) and the Department of Defence (Defence). The OneSKY Australia program involves the procurement of a Civil Military Air Traffic Management System (CMATS). Airservices is the lead entity for the procurement.

2. The procurement process commenced with a Request for Information issued to industry in May 2010, with 23 responses received. A Request for Tender (RFT) was issued in June 2013. Six tenders were received, four of which proceeded to detailed evaluation, during which one was set aside on the basis that it was clearly not competitive. The two highest ranked tenderers proceeded to the final evaluation stage. Decisions were then taken to set-aside, and later exclude, the second-ranked tenderer from further consideration (on the basis that it was ‘clearly non-competitive’) rather than enter into parallel negotiations with two tenderers.1

3. Negotiations with the successful tenderer (Thales Australia) commenced in September 2014. Offers were submitted by the successful tenderer in October and December 2014. On 27 February 2015, it was announced that an advanced work contracting arrangement would be entered into allowing discrete parcels of work to be performed while negotiation of the acquisition and support contracts was progressed. The earlier offers (including the response to the RFT) expired in October 2015. Another offer was submitted in June 2016, with a final offer submitted in September 2017, followed by further negotiation on scope, price and commercial terms.

4. In February 2018:

an acquisition contract was signed by Airservices and the successful tenderer (as well as a support contract). The acquisition contract had a target price of AUD$1.22 billion and a ceiling price of AUD$1.32 billion (applying exchange rates on the date the contract was signed);
Defence obtained Government approval for a $243 million increase to its project budget (including $90 million identified as relating to CMATS) to enable it to afford its share of project costs. Associated with the budget increase, Airservices and Defence were to undertake cost reduction measures, including capability offsets, to enable work to be delivered within the revised Defence budget for CMATS; and
cost sharing arrangements between Airservices and Defence were updated and formalised through the execution of an On-Supply Agreement. For a fixed price of $521 million, CMATS will be provided to Defence along with an alternative air traffic management tower solution at four sites2 and the voice control switch developed under Advanced Work Order 3. Defence’s contribution to program management costs are also included within this agreed amount. Airservices and Defence are each responsible for their own personnel and resourcing costs.

5. In February 2018 when the decision was taken by Airservices to enter into the acquisition contract, it estimated its acquisition program costs to be $1.517 billion. This figure does not include the fixed acquisition price of $521 million agreed between Airservices and Defence.

Rationale for undertaking the audit

6. OneSKY Australia was selected for audit because it is a significant program. The program has an estimated total cost of more than $4.11 billion.3 Australian airspace covers 11 per cent of the globe and OneSKY is expected to improve safety and efficiency for civil and military air traffic, while catering for the significant forecast growth in the aviation sector.

7. In August 2015, the Minister for Infrastructure and Regional Development and the Senate Rural and Regional Affairs and Transport Legislation Committee requested that the Australian National Audit Office (ANAO) examine the implementation of the OneSKY program. This is the third audit the ANAO has undertaken in response to those requests.4

Audit objective and criteria

8. The objective of the audit was to assess whether the contract for the acquisition of the Civil Military Air Traffic Management System demonstrably represents value for money.

9. To form a conclusion against the audit objective, the ANAO adopted the following high-level criteria:

Were required timeframes achieved for the replacement of existing systems?
Is there adequate assurance that the price being paid is consistent with a value for money outcome for the capability being acquired?

Conclusion

10. Important changes were made, after the successful tenderer was selected, to the timeframe for delivery, scope of work, type of contract and price. An appropriate governance framework was established to evaluate whether negotiations had resulted in contract terms that represent value for money. Shortcomings in the application of that framework mean that value for money has not been adequately demonstrated.

11. If the current contracted timeframes are achieved, there will be a more than ten year delay (from 2015 to 20265) in the replacement of the existing separate civil and military systems compared with the timeframe envisaged at the start of the procurement process. The capability baseline for the new combined system was established in advance of issuing the Request for Tender through appropriate engagement with industry. Delays with tender evaluation activities were exacerbated by even longer delays in the negotiation phase. Negotiations took so long that the offer submitted by the successful tenderer expired and the lives of the existing separate systems needed to be further extended. Negotiations also resulted in a late change in the contracting model from the one that had been presented to the market in June 2013.

12. There is inadequate assurance that the acquisition price is consistent with a value for money outcome:

For the June 2016 offer, a comprehensive evaluation report was produced that included a clear conclusion that value for money had not been achieved. This was principally due to concerns about the $1.449 billion estimated acquisition cost.
Through further negotiations, changes were made to delivery timeframes, the scope of work and the contract model, leading to a September 2017 final offer (with an estimated target price of $1.23 billion with the ceiling price to be 10 per cent higher) followed by further negotiation on scope, price and commercial terms. An evaluation report addressing each criterion, the expected total cost of ownership and whether the negotiated outcome represented value for money, was not prepared by the CMATS Review Board (CRB) and provided to the Airservices Board to inform the decision to sign the acquisition contract. Rather, the Board was provided with a report prepared by the Lead Negotiator6, who was not authorised to and did not undertake a full evaluation of the offer.7 The records of the relevant Board meeting do not identify or discuss the provision of the February 2018 Lead Negotiator’s Report8, and do not outline the value for money considerations of the Board.

13. Price risk is dealt with in the terms of the acquisition contract.

Supporting findings

Negotiation timeframes

14. The planned timeframe of replacing the systems in 2015 was not met. The current date for acceptance of the replacement system is 2026. Delays with the conduct of the tender, tender evaluation and contract negotiations contributed to this more than ten year delay. This meant that Airservices and Defence had to extend their existing, separate air traffic management systems beyond that which was originally envisaged.

15. Scope requirements for the harmonised civil military air traffic management systems were established prior to entering into negotiations. A request for information and industry briefing process had been undertaken, and the resulting feedback was used to inform the development of the tender requirements. The requirements were released with the June 2013 Request for Tender and updated in October 2013, prior to tenders being received.

16. In November 2016, more than two years after negotiations began, it was decided to change the acquisition contract from the firm fixed price model that had been part of the June 2013 request for tender. A change to a target cost incentive contract model had first been suggested by the successful tenderer in December 2015. Airservices’ decision to change the contracting model was made after various price submissions under the fixed price contract model received during the negotiation process had been identified as not representing value for money and/or as not likely to be affordable. The ceiling price under the target cost incentive model that was then adopted is more than double the price submitted by the successful tenderer in its response to the 2013 request for tender.

17. The delays in negotiating and finalising an acquisition contract, together with the scheduled delay in replacing the existing separate civil and military systems, have required the lives of the existing systems to be extended beyond that which was originally envisaged at an estimated cost of at least $212 million. Delays have also required additional resourcing from both entities for contract negotiations and project management. The costs relating to the additional resources for negotiations and project management were not quantified.

Negotiation outcome

18. Traceability was not maintained between offered requirements and the original Request for Tender. Traceability focused on changes over time in the various offers submitted by the preferred tenderer against updated versions of the requirements. The number of high priority requirements at the end of negotiations was 3.6 per cent greater than at the beginning of negotiations, with 6.7 per cent of the high priority requirements included in the Request for Tender modified in the signed acquisition contract.

19. There is a clear scope specified for the signed acquisition contract. Changes to the contract scope were envisaged before the acquisition contract was signed. To date, two change proposals have been actioned (in August 2018 and December 2018).

20. Price risk is dealt with in the terms of the acquisition contract. Of note is that the contract:

requires the successful tenderer to use its ‘reasonable endeavours’ to ensure that the outturn price is, at final acceptance, lower than a target price of $1.22 billion;
incorporates a painshare/gainshare framework intended to incentivise cost containment. This includes providing that Airservices’ exposure to actual costs being greater than the target price is limited to a 50 per cent share of the costs above the target price up to the ceiling price, capping Airservices’ exposure at $1.32 billion; and
allows the contract scope to be amended, and provides a mechanism for the target and ceiling prices to be adjusted for scope changes.

21. There is inadequate assurance that the contracted acquisition price is consistent with a value for money outcome for the capability being acquired. Assessment governance arrangements for the June 2016 offer (which was rejected for not providing value for money) were appropriate. There were shortcomings in the application of the governance arrangements for the final (accepted) September 2017 offer. Of significance was that the CMATS Review Board did not prepare a comprehensive assessment report that addressed each of the evaluation criteria, quantified the expected total cost of ownership and analysed whether value for money had been achieved.

Hmm...quite damning really but I guess much like most damning Parliamentary inquiry, Government review reports (eg Forsyth review) into the aviation safety sector; this ANAO wet lettuce report at the first chance will be quietly filed and shelf-wared for all eternity... Dodgy

[Image: irs-taxes-cartoon-lost-ark-warehouse-2-598x427.jpg]


MTF...P2  Tongue

(08-02-2019, 12:12 PM)Peetwo Wrote:  ARFFS Senate Inquiry report tabled. 

[Image: D2Obcu1VYAAGfDY.jpg]

View full report HERE or pdf version HERE ; these are the recommendations (note number 1 -  Rolleyes ): 

Quote:List of Recommendations

Recommendation 1
7.11
The committee recommends that the Australian Government conduct a review of Australia's adherence to the International Civil Aviation Organization Standards and Recommended Practices for the provision of Aviation Rescue Fire Fighting Services in Australia. The review should consider:

Subpart 139.H of the Civil Aviation Safety Regulations 1998;

the associated Manual of Standards;

Australia's adherence to Chapter 9 of Annex 14 of the Chicago Convention; and

any other relevant regulations, standards and procedures (including those issued by the National Fire Protection Association).
Where the review identifies non‑compliance with international standards, the rationale for this should be explained.
Recommendation 2
7.18
The committee recommends that the Civil Aviation Safety Authority conduct an audit of all Aviation Rescue Fire Fighting Service (ARFFS) vehicles and equipment currently in operation across Australia, to determine the level of compliance with the International Civil Aviation Organization standards, and associated Australian regulations and standards (such as the Civil Aviation Safety Regulations 1998 and the Manual of Standards). The audit should consider whether the vehicles and equipment adhere to the relevant ARFFS airport category at each aerodrome.
Recommendation 3
7.22
The committee recommends that the Civil Aviation Safety Authority implement a testing program for the firefighting foams in use at Australian airports, in accordance with International Civil Aviation Organization guidelines. The testing should take place under conditions unique to Australia (such as higher ambient temperatures), to establish whether the foams operate effectively to extinguish aviation fires.
Recommendation 4
7.36
The committee recommends that the Civil Aviation Safety Authority mandates that Aviation Rescue Fire Fighting Service (ARFFS) providers use the Task Resource Analysis (TRA) methodology, as prescribed by the International Civil Aviation Organization, to determine the suitable staffing levels for ARFFS at all aerodromes in Australia where an ARFFS is provided. The TRA should take into consideration the category of each aerodrome.
Recommendation 5
7.42
The committee recommends that the Civil Aviation Safety Authority mandate that the Task Resource Analysis (TRA) process undertaken by Airservices must involve appropriate consultation, via the direct engagement of Aviation Rescue Fire Fighting staff and officers at all stages of the TRA process. The consultation should be transparent, and the outcomes made publicly available as soon as is practicable.
Recommendation 6
7.47
The committee recommends that the Australian Government introduce legislation which stipulates the minimum Aviation Rescue Fire Fighting (ARFF) staffing level in accordance with airport category, at all Australian aerodromes where an ARFF service is provided. The legislated staffing levels should reflect the outcomes of the Task Resource Analysis at each aerodrome.
Recommendation 7
7.56
The committee recommends that the Department of Infrastructure, Transport, Cities, and Regional Development undertake a review of the current establishment criteria used for determining whether to implement an Aviation Rescue Fire Fighting Service (ARFFS). The review should consider whether the current methodology of utilising passenger numbers allows for sufficient provision of ARFFS across Australian aerodromes, in light of increasing passenger numbers in recent years.
Recommendation 8
7.63
The committee recommends that the Australian Government mandate the establishment of a Task Resource Analysis for Domestic Response Services responding to emergencies at aerodromes (DRS TRA). The DRS TRA should determine the additional Aviation Rescue and Fire Fighting (ARFF) staff required for responses to non‑regulated ands non‑aviation emergencies across the aerodrome, over and above the staff required for an ARFF station to maintain category in the case of an aviation emergency.

Hmm...I note recommendations 1 & 2 but will it just be ignored &/or obfuscated like all other inquiry/review recommendations??  Dodgy

[Image: D3Qx9wUUUAEfnt5.jpg]

Plus today from Ironsider, via the Oz.. Wink :


Quote:Regional airports ill-equipped to handle disaster


[Image: 5607f97b5c626059faf8ec1c6a77b0eb?width=650]

Firefighters work on a burning aircraft at an airport in Russia. Picture: AFP
  • ROBYN IRONSIDE
    AVIATION WRITER
    @ironsider

  • 12:00AM AUGUST 5, 2019
  • 2 COMMENTS

Firefighters based at Australian airports say a lack of fire trucks, the removal of power saws and training restrictions on tall ladders has left them ill-equipped to deal with an actual emergency.

A Senate committee for rural and regional affairs and transport heard stations at Rockhampton, Gladstone and the Sunshine Coast must share a fire truck despite being 543km apart.

In addition, rescue saws were removed from the service last September despite being required under the manual of standards and training on ladders restricted to 2m for safety reasons.

In its final report, the committee made eight recommendations, including a government review of Australia’s compliance with international standards for fire services, after hearing more than 300 airports had no onsite protection.

“There were a number of serious concerns raised throughout the inquiry as to the performance of Airservices in its delivery of aviation rescue and fire fighting services (ARFFS) across Australia’s major airports,” the report said.

“In particular, concerns were raised with regard to the suitability of some ARFF equipment and resources in use across the country, and decisions of Airservices which would directly impact on the ability of the ARFFS to respond quickly to an emergency.”

The recommendations included a Civil Aviation Safety Authority audit of airport firefighting equipment and vehicles to ensure compliance with international standards.

“The committee was alarmed by the removal of rescue saws from operation despite no replacement for the saws having yet been identified and despite the fact the removal meant the airport fire service was no longer compliant with the manual of standards,” the report said. “Further, the implementation of training for firefighters on ladders below 2m remains an ongoing concern for the committee. This limited height training is not reflective of operational conditions, particularly for larger aircraft.”

The United Firefighting Union of Australia said the height limit had been lifted to 2.5m since their concerns were first raised, but that was still inadequate.

UFUA aviation branch secretary Mark von Nida said the training restriction was implemented despite the fact firefighters had never had an accident using the ladders. “It’s just not practical. You’re working up to heights of 9m, you’ve got to be able to operate at that,” Mr von Nida said.

The report also questioned whether Australia’s aviation firefighting services met international standards more broadly, after hearing evidence only 26 airports had a dedicated fire station.

Whereas the threshold for airport fire stations in the US was aircraft carrying more than 12 people, and more than 30 people in New Zealand, in Australia the threshold was much higher.

“We’ve got 180-seat aircraft and above landing at airports that aren’t protected, like Dubbo, Mt Isa, Proserpine and Newman,” Mr von Nida said.

“There’s only the local fire service there to put it out, and it might take 15 minutes until they actually get on scene.”
Although airports with more than 350,000 passenger movements a year qualified for a fire station, Mr von Nida said Proserpine and Newman reached that level in 2017, and were still waiting.

An Airservices Australia spokeswoman said ARFFS operated at “the highest standards and has a world-class safety record”.

“We are examining the report’s recommendations,” the spokeswoman said.


MTF...P2  Tongue
Reply


Messages In This Thread
Shame or Fame for McCormack. - by Kharon - 07-23-2018, 07:54 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 07-23-2018, 10:28 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-23-2018, 02:54 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 07-23-2018, 04:28 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 07-23-2018, 08:16 PM
RE: Shame or Fame for McCormack. - by thorn bird - 07-23-2018, 08:34 PM
RE: Shame or Fame for McCormack. - by Kharon - 07-24-2018, 08:20 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 07-24-2018, 01:10 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-24-2018, 07:41 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 07-24-2018, 07:54 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-26-2018, 08:44 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 07-26-2018, 03:31 PM
RE: Shame or Fame for McCormack. - by Kharon - 07-27-2018, 08:49 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-27-2018, 09:58 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-28-2018, 11:10 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-17-2018, 09:32 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 07-27-2018, 11:25 AM
RE: Shame or Fame for McCormack. - by thorn bird - 07-28-2018, 06:42 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 07-28-2018, 02:40 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 07-29-2018, 07:18 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-30-2018, 08:22 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-01-2018, 10:53 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-01-2018, 01:30 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 08-01-2018, 07:12 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-04-2018, 09:17 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-06-2018, 06:55 AM
RE: Shame or Fame for McCormack. - by thorn bird - 08-08-2018, 06:35 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-08-2018, 08:56 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-10-2018, 12:54 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-11-2018, 09:47 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-17-2018, 11:06 AM
RE: Shame or Fame for McCormack. - by Kharon - 08-20-2018, 08:55 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-22-2018, 10:55 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-23-2018, 10:09 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-23-2018, 11:53 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-24-2018, 08:59 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-25-2018, 11:24 AM
RE: Shame or Fame for McCormack. - by Kharon - 08-27-2018, 07:18 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-27-2018, 10:03 AM
RE: Shame or Fame for McCormack. - by Kharon - 08-28-2018, 07:31 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 08-28-2018, 03:15 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-05-2018, 09:40 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-07-2018, 04:08 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-06-2018, 06:09 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-10-2018, 08:18 AM
RE: Shame or Fame for McCormack. - by Peetwo - 09-11-2018, 08:14 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 09-11-2018, 09:43 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-11-2018, 09:51 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-12-2018, 10:24 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 09-12-2018, 06:04 PM
RE: Shame or Fame for McCormack. - by Kharon - 09-14-2018, 08:14 AM
RE: Shame or Fame for McCormack. - by Peetwo - 09-14-2018, 12:34 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-15-2018, 11:35 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 09-14-2018, 10:01 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-22-2018, 09:57 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 09-22-2018, 02:26 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 09-22-2018, 08:08 PM
RE: Shame or Fame for McCormack. - by Sandy Reith - 09-23-2018, 03:58 PM
RE: Shame or Fame for McCormack. - by Kharon - 09-24-2018, 07:48 AM
RE: Shame or Fame for McCormack. - by Peetwo - 10-05-2018, 10:39 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 10-05-2018, 07:30 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 10-11-2018, 11:14 AM
RE: Shame or Fame for McCormack. - by P7_TOM - 10-11-2018, 07:59 PM
RE: Shame or Fame for McCormack. - by Peetwo - 10-17-2018, 09:01 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 10-17-2018, 09:27 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 10-17-2018, 11:20 PM
RE: Shame or Fame for McCormack. - by Peetwo - 10-20-2018, 07:26 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 10-20-2018, 01:13 PM
RE: Shame or Fame for McCormack. - by Peetwo - 10-31-2018, 09:59 PM
RE: Shame or Fame for McCormack. - by thorn bird - 11-01-2018, 06:08 AM
RE: Shame or Fame for McCormack. - by Peetwo - 11-01-2018, 09:40 AM
RE: Shame or Fame for McCormack. - by Peetwo - 11-05-2018, 07:06 PM
RE: Shame or Fame for McCormack. - by Peetwo - 11-30-2018, 09:02 AM
RE: Shame or Fame for McCormack. - by Peetwo - 12-04-2018, 10:30 AM
RE: Shame or Fame for McCormack. - by P7_TOM - 12-04-2018, 07:35 PM
RE: Shame or Fame for McCormack. - by Peetwo - 12-14-2018, 12:39 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 12-14-2018, 01:37 PM
RE: Shame or Fame for McCormack. - by BRhoades - 12-14-2018, 05:49 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-01-2019, 11:35 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 12-15-2018, 06:04 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 12-17-2018, 09:59 PM
RE: Shame or Fame for McCormack. - by Kharon - 12-18-2018, 05:32 AM
RE: Shame or Fame for McCormack. - by Peetwo - 12-18-2018, 09:05 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 12-18-2018, 11:25 AM
RE: Shame or Fame for McCormack. - by Peetwo - 12-18-2018, 01:57 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 12-18-2018, 07:52 PM
RE: Shame or Fame for McCormack. - by Peetwo - 12-19-2018, 09:56 AM
RE: Shame or Fame for McCormack. - by Kharon - 12-19-2018, 05:48 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 01-01-2019, 11:06 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-04-2019, 07:50 AM
RE: Shame or Fame for McCormack. - by Peetwo - 01-04-2019, 01:16 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-07-2019, 10:36 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-08-2019, 03:36 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-11-2019, 01:33 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-25-2019, 01:26 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-26-2019, 02:22 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 01-11-2019, 06:28 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-26-2019, 08:00 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 01-26-2019, 07:02 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-30-2019, 05:46 PM
RE: Shame or Fame for McCormack. - by Peetwo - 01-31-2019, 08:04 AM
RE: Shame or Fame for McCormack. - by Peetwo - 01-31-2019, 09:25 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-01-2019, 07:38 AM
RE: Shame or Fame for McCormack. - by thorn bird - 02-01-2019, 12:27 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-01-2019, 02:43 PM
RE: Shame or Fame for McCormack. - by Kharon - 02-02-2019, 08:18 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-02-2019, 05:03 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-03-2019, 07:56 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-03-2019, 01:46 PM
RE: Shame or Fame for McCormack. - by thorn bird - 02-03-2019, 02:49 PM
RE: Shame or Fame for McCormack. - by Kharon - 02-04-2019, 07:38 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-07-2019, 10:55 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-07-2019, 04:38 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-08-2019, 08:33 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-09-2019, 07:34 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-08-2019, 10:14 AM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-09-2019, 10:05 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 02-11-2019, 08:22 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-11-2019, 09:32 PM
RE: Shame or Fame for McCormack. - by Cap'n Wannabe - 02-12-2019, 11:28 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-12-2019, 05:51 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-12-2019, 05:55 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-12-2019, 06:23 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 02-12-2019, 08:19 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-12-2019, 09:11 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-13-2019, 08:43 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-13-2019, 10:05 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-17-2019, 08:49 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-19-2019, 07:35 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-21-2019, 11:01 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-21-2019, 10:45 PM
RE: Shame or Fame for McCormack. - by Sandy Reith - 02-22-2019, 03:50 PM
RE: Shame or Fame for McCormack. - by Kharon - 02-23-2019, 08:23 AM
RE: Shame or Fame for McCormack. - by Peetwo - 02-23-2019, 12:27 PM
RE: Shame or Fame for McCormack. - by Kharon - 02-25-2019, 08:32 AM
RE: Shame or Fame for McCormack. - by thorn bird - 02-25-2019, 09:46 AM
RE: Shame or Fame for McCormack. - by Kharon - 02-25-2019, 09:49 PM
RE: Shame or Fame for McCormack. - by Peetwo - 02-26-2019, 06:29 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 02-25-2019, 10:48 PM
RE: Shame or Fame for McCormack. - by Kharon - 03-04-2019, 07:40 PM
RE: Shame or Fame for McCormack. - by Peetwo - 03-08-2019, 09:25 AM
RE: Shame or Fame for McCormack. - by Peetwo - 03-08-2019, 11:31 AM
RE: Shame or Fame for McCormack. - by Peetwo - 03-14-2019, 11:22 PM
RE: Shame or Fame for McCormack. - by Gobbledock - 03-24-2019, 01:12 PM
RE: Shame or Fame for McCormack. - by Peetwo - 03-25-2019, 08:37 PM
RE: Shame or Fame for McCormack. - by Peetwo - 03-26-2019, 05:16 PM
RE: Shame or Fame for McCormack. - by Peetwo - 03-27-2019, 08:13 AM
RE: Shame or Fame for McCormack. - by Peetwo - 04-01-2019, 08:35 PM
RE: Shame or Fame for McCormack. - by Peetwo - 04-02-2019, 08:15 PM
RE: Shame or Fame for McCormack. - by Kharon - 04-06-2019, 07:44 AM
RE: Shame or Fame for McCormack. - by Peetwo - 04-09-2019, 08:54 PM
RE: Shame or Fame for McCormack. - by Kharon - 04-10-2019, 08:00 AM
RE: Shame or Fame for McCormack. - by Peetwo - 04-10-2019, 10:00 AM
RE: Shame or Fame for McCormack. - by Peetwo - 04-12-2019, 12:29 PM
RE: Shame or Fame for McCormack. - by Kharon - 04-13-2019, 07:36 AM
RE: Shame or Fame for McCormack. - by Peetwo - 04-13-2019, 10:09 AM
RE: Shame or Fame for McCormack. - by Peetwo - 04-13-2019, 11:34 AM
RE: Shame or Fame for McCormack. - by Kharon - 05-14-2019, 08:33 AM
RE: Shame or Fame for McCormack. - by Kharon - 05-29-2019, 08:38 AM
RE: Shame or Fame for McCormack. - by Peetwo - 06-13-2019, 10:54 AM
RE: Shame or Fame for McCormack. - by Peetwo - 06-17-2019, 07:58 AM
RE: Shame or Fame for McCormack. - by P7_TOM - 06-17-2019, 08:07 PM
RE: Shame or Fame for McCormack. - by Kharon - 06-24-2019, 07:26 AM
RE: Shame or Fame for McCormack. - by Peetwo - 06-24-2019, 11:09 PM
RE: Shame or Fame for McCormack. - by Kharon - 06-25-2019, 08:33 AM
RE: Shame or Fame for McCormack. - by Peetwo - 06-30-2019, 11:34 AM
RE: Shame or Fame for McCormack. - by P7_TOM - 06-30-2019, 08:19 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-04-2019, 09:46 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-05-2019, 02:10 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-10-2019, 11:04 AM
RE: Shame or Fame for McCormack. - by Cap'n Wannabe - 07-12-2019, 05:02 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-12-2019, 12:06 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-12-2019, 11:00 PM
RE: Shame or Fame for McCormack. - by Kharon - 07-15-2019, 08:14 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-19-2019, 02:37 PM
RE: Shame or Fame for McCormack. - by Kharon - 07-22-2019, 08:16 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-27-2019, 10:25 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-30-2019, 05:50 PM
RE: Shame or Fame for McCormack. - by Peetwo - 07-31-2019, 10:34 AM
RE: Shame or Fame for McCormack. - by Peetwo - 07-31-2019, 11:07 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-01-2019, 02:36 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-05-2019, 08:16 AM
RE: Shame or Fame for McCormack. - by Kharon - 08-06-2019, 09:18 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-07-2019, 08:42 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-07-2019, 08:59 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-08-2019, 06:36 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 08-08-2019, 07:18 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-09-2019, 05:35 PM
RE: Shame or Fame for McCormack. - by thorn bird - 08-11-2019, 09:42 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-12-2019, 09:17 PM
RE: Shame or Fame for McCormack. - by thorn bird - 08-13-2019, 07:50 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-13-2019, 10:09 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-14-2019, 09:11 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-16-2019, 12:21 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-18-2019, 10:37 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-20-2019, 10:28 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-20-2019, 11:21 AM
RE: Shame or Fame for McCormack. - by Sandy Reith - 08-20-2019, 11:16 AM
RE: Shame or Fame for McCormack. - by Kharon - 08-21-2019, 08:37 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-22-2019, 06:45 PM
RE: Shame or Fame for McCormack. - by Peetwo - 08-27-2019, 08:04 AM
RE: Shame or Fame for McCormack. - by Peetwo - 08-27-2019, 05:09 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 08-27-2019, 05:55 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 09-05-2019, 08:31 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-06-2019, 10:53 AM
RE: Shame or Fame for McCormack. - by Peetwo - 09-07-2019, 10:22 AM
RE: Shame or Fame for McCormack. - by thorn bird - 09-07-2019, 09:09 PM
RE: Shame or Fame for McCormack. - by Peetwo - 09-19-2019, 09:03 AM
RE: Shame or Fame for McCormack. - by P7_TOM - 09-19-2019, 08:45 PM
RE: Shame or Fame for McCormack. - by Kharon - 09-21-2019, 08:52 AM
RE: Shame or Fame for McCormack. - by thorn bird - 09-23-2019, 06:10 AM
RE: Shame or Fame for McCormack. - by Peetwo - 09-23-2019, 09:46 AM
RE: Shame or Fame for McCormack. - by thorn bird - 09-23-2019, 03:42 PM
RE: Shame or Fame for McCormack. - by Kharon - 09-24-2019, 08:52 AM
RE: Shame or Fame for McCormack. - by thorn bird - 09-24-2019, 02:38 PM
RE: Shame or Fame for McCormack. - by P7_TOM - 09-25-2019, 09:43 PM
RE: Shame or Fame for McCormack. - by Kharon - 10-14-2019, 08:00 AM
RE: Shame or Fame for McCormack. - by Kharon - 10-15-2019, 07:58 AM
RE: Shame or Fame for McCormack. - by Peetwo - 10-15-2019, 09:24 PM
RE: Shame or Fame for McCormack. - by Kharon - 10-16-2019, 07:21 AM
RE: Shame or Fame for McCormack. - by Peetwo - Today, 08:11 AM
RE: Shame or Fame for McCormack. - by P7_TOM - 3 hours ago



Users browsing this thread: 5 Guest(s)