![]() |
[Home]
[Databases]
[WorldLII]
[Search]
[Feedback]
Federal Court of Australia |
Last Updated: 21 December 2010
FEDERAL COURT OF AUSTRALIA
Tropical Reef Shipyard Pty Ltd v QBE Insurance (Australia) Limited
(No 3) [2010] FCA 1439
|
Citation:
|
Tropical Reef Shipyard Pty Ltd v QBE Insurance (Australia) Limited (No 3)
[2010] FCA 1439
|
|
|
|
|
|
|
Parties:
|
||
|
|
|
|
|
File number:
|
VID 157 of 2009
|
|
|
|
|
|
|
Judge:
|
GORDON J
|
|
|
|
|
|
|
Date of judgment:
|
||
|
|
|
|
|
Catchwords:
|
||
|
|
|
|
|
Legislation:
|
||
|
|
|
|
|
Cases cited:
|
QBE Insurance (Australia) Limited v Tropical
Reef Shipyard Pty Ltd [2009] FCAFC 161
Tropical Reef Shipyard Pty Ltd v QBE Insurance (Australia) Limited [2009] FCA 1088 Tropical Reef Shipyard Pty Ltd v QBE Insurance (Australia) Limited (No 2) [2010] FCA 1093 Commonwealth v Verwayen (1990) 170 CLR 394 |
|
|
|
|
|
|
|
|
|
|
Date of last submissions:
|
9 December 2010
|
|
|
|
|
|
|
Place:
|
Melbourne
|
|
|
|
|
|
|
Division:
|
GENERAL DIVISION
|
|
|
|
|
|
|
Category:
|
Catchwords
|
|
|
|
|
|
|
Number of paragraphs:
|
||
|
|
|
|
|
|
|
|
|
Solicitor for the Applicant:
|
Turks Legal
|
|
|
|
|
|
|
Counsel for the Respondent:
|
DL Williams QC with HNG Austin
|
|
|
|
|
|
|
Solicitor for the Respondent:
|
HWL Ebsworth Lawyers
|
|
|
AND:
|
THE COURT ORDERS THAT:
Note: Settlement and entry of orders is dealt with in Order 36 of
the Federal Court Rules.
The text of entered orders can be located using
Federal Law Search on the Court’s website.
|
BETWEEN:
|
TROPICAL REEF SHIPYARD PTY LTD
(ACN 098 851 775)
Applicant |
|
AND:
|
QBE INSURANCE (AUSTRALIA) LIMITED
(ACN 003 191 035)
Respondent |
|
JUDGE:
|
GORDON J
|
|
DATE:
|
21 DECEMBER 2010
|
|
PLACE:
|
MELBOURNE
|
REASONS FOR JUDGMENT
Background
...
...
Question 4:
Upon the assumption that:
(a) the Actual Weekly Turnover and Average Weekly Turnover figures pleaded in Annexures D, G and H to the Applicant’s Claim are correct (as corrected by paragraphs 21-23 of the Supplementary Report of Stephen Munro Gibson dated 10 June 2009);
(b) the allegations pleaded in paragraphs 1, 2, 4 to 15, 22 to 26, and 32 to 36 of the Applicant’s Claim are established;
(c) the Respondent has paid a total sum of $2,000,000 to the Applicant in respect to the claims made in the proceedings; and
(d) the Applicant’s claims pursuant to the 2005 renewal (as defined in paragraph 5 of the Applicant’s Claim) and the 2006 renewal (as defined in paragraph 8 of the Applicant’s Claim) are as pleaded in Annexures D, G, H and I to the Applicant’s Claim (as corrected by paragraphs 21-23 of the Supplementary Munro dated 10 June 2009);
upon the proper construction of the 2005 renewal and the 2006 renewal, is the Applicant entitled to any and if so what amount under the 2005 renewal and/or the 2006 Renewal in respect to loss of Turnover under the said policies?
Answer: The Applicant is entitled to loss of Turnover under:
(a) the 2005 Renewal for the weeks ending 12 April 2007 to 25 October 2007 in respect to the September 2006 Incident;
(b) the 2006 Renewal for the weeks ending 22 February 2007 to 5 April 2007 and 1 November 2007 to 14 February 2008 in respect to the November 2006 Incident;
calculated in accordance with the methodology identified in the reasons for judgment, subject to proof of the loss of Turnover and the causal connection required by the terms of each of the policies.
(Emphasis added.)
To do so [TRS] will have to replead its case in accordance with the following methodology. First step – identify the date of commencement of interruption. Second step – calculate the Actual Average Weekly Turnover for the 12 months preceding the date of commencement of interruption. Third step – calculate the weekly Turnover for each relevant week: that is for each week in respect of which loss is claimed. I have described how Turnover is to be calculated for purposes of both step two and step three. Fourth step – calculate the loss of weekly Turnover by deducting weekly Turnover from the Actual Average Weekly Turnover for each week. Fifth step – establish that any reduction in income is caused by the interruption. One way of proving causation is to: (1) identify the vessels TRS was unable to slip and repair in the relevant period; (2) estimate the vessels it lost the opportunity to slip and repair in the relevant period; and (3) determine the value of the work that could have been performed on those vessels and the date or dates upon which invoices for that work would have been issued. There may be other ways to prove causation. Sixth step – reduce the loss of weekly Turnover by the Rating Classification percentage and (where applicable) reduce the figure to the maximum Weekly Sum Insured.
(Emphasis added.)
[29]. In the premises of paragraphs 23-28, above, throughout the period 3 April 2007 – 22 October 2007, [TRS]:
(a) was unable to, and did not, slip any vessels which required the use of the bottom 15 metres of the slipway;
(b) sustained interference to the work schedule of vessels in fact on the slipway, as a result of an inability to utilize the bottom 15 metres of the slipway;
(c) lost opportunities to undertake double slipping of vessels, as a result of an inability to utilize the bottom 15 metres of the slipway;
(d) lost opportunities to seek smaller vessels (which did not need to use chainage 174 – 189) by reason of the need to investigate and undertake repairs of the type described above;
(e) further to the above, lost opportunities to slip and repair vessels by reason of the closure in April 2007, the investigations in April and May 2007, the repairs in July and August 2007, the closure for further repairs in each of September 2007 and October 2007 and the stranding of HMAS Leeuwin on the slipway in October 2007.
Loss
[30]. Accordingly, in these premises, in the period 3 April 2007 – 22 October 2007, the ship repair and engineering business of [TRS] was interrupted or interfered with.
[31]. By virtue of the interruption and/or interference set out above, [TRS] sustained loss and damage, constituted both by direct losses and, further, by reason of lost opportunities to slip and repair vessels.
Particulars
(a) By virtue of the business undertaken by [TRS] in the periods April – October 2005, April – October 2006 and April – October 2008, in which the bottom 15 metres of the slipway were utilized, [TRS] would have expected to slip four vessels requiring the use of the bottom 15 metres of the slipway in the period April – October 2007, and derive revenue from that work. In the premises above, that did not occur;
(b) [TRS] suffered both direct loss and lost opportunities loss as a result of interference to the work schedule which, but for the damage to the slipway, would have occurred as follows:
(i) because the DPI Pontoon was stranded on the slipway while investigations of the slipway damage were conducted and the slipway bogies were recovered;
(ii) in respect of the vessel “HMAS Leeuwin”, because the tides were not sufficiently high to allow the vessel to be slipped without the use of the bottom 15 metres of the slipway;
(iii) in respect of the vessel “HMAS Leeuwin”, because the tides were not sufficiently high to allow the vessel to be unslipped without the use of the bottom 15 metres of the slipway leaving it stranded on the slipway until repairs to that part of the slipway were completed;
(iv) in or about October 2007, in respect of the vessel “Melville”, a sister ship to HMAS Leeuwin, by reason of the fact that the slipway was closed for three weeks and HMAS Leeuwin was stranded on the slipway for a further two weeks resulting in the slipping occurring later than planned and previously requested work being reduced in scope.
(c) further to (b) above, [TRS] lost the opportunity to double slip vessels as follows:
(i) in or about April 2007, the vessels “GHT22” and “Wilunga”;
(ii) in or about April 2007, the vessels “Mermaid” and “Peluma”;
(d) further to (b) and (c) above, by reason of its inability to slip vessels that would or might require the bottom 15 metres of the slipway in order to be slipped, and/or by reason of the fact that it was required to turn away vessels during the slipway closures in April and September 2007 while repairs to the bottom end of the slipway were undertaken, [TRS] lost opportunities to undertake work on vessels as follows:
(i) in or about April/May 2007, several large purse seine vessels;
(ii) in or about April/May 2007, the vessel “ACPB Bundaberg”;
(iii) in or about May 2007, the vessel “Western Triumph”;
(iv) in or about May/June 2007, the vessel “Solomon Chiefton”;
(v) in or about September 2007, the vessel “Caroline Voyager”;
(vi) in or about September 2007, the vessel “Cruise Whitsundays”.
(e) further to (a) – (d) above, throughout the period April – October 2007, the necessity to repair the bottom 15 metres of the slipway caused management to focus not on attracting new business, but rather, and to the contrary, on the necessary investigations and repairs of the bottom 15 metres of the slipway.
(a) First Step – identify date of commencement of interruption.
(b) Second Step – calculate “Actual Average Weekly Turnover” for the 12 months preceding the said date of commencement of interruption;
(c) Third Step – calculate “Loss of Weekly Turnover” from the said date of commencement of interruption, until 22 October 2007, on a “week by week” basis;
(d) Fourth Step – apply to each week’s “Loss of Weekly Turnover” figure:
(i) the “Rating Classification” percentage; and
(ii) (where applicable) reduce the figure to the maximum “Weekly Sum Insured”.
I will deal with each methodology in turn.
Primary Methodology
First Step
Second Step ...
34A. As set out in page 1 of 2 of Annexure E1 hereto, the “Actual Average Weekly Turnover,” for the period 4 April 2006 – 3 April 2007, is $392,431. The methodology applied in calculating that figure is explained in paragraph 34B below.
34B In allocating “Turnover” to each week, in the period 4 April 2006 – 3 April 2007 in order to give effect to the language: “money paid or payable to [TRS] for goods sold and for services rendered”, regard has been had to:
(a) the value of invoices issued in each week;
less
(b) the value of credit notes issued in each week,
without regard to the timing of the rendering of services.
...
Third Step ...
37A As set out in Annexure F1 hereto, for each week in the period 3 April 2007 – 22 October 2007, “Loss of Weekly Turnover” is as set out in the column, styled “Loss/(Gain) of Average Weekly Turnover”.
37B. The methodology in relation to the quantification of turnover within the column styled “Weekly Turnover” is equivalent to the methodology described in paragraph 34B above ...
...
Fourth Step ...
40A. As identified in Annexure F1 hereto, total loss in the period 3 April 2007 – 22 October 2007, after applying the “Rating Classifications percentage” and (where applicable) the weekly cap, totals $3,187,059.
Although his Honour said (see [6] above) that there may have been other ways to prove causation, in the present case TRS did not suggest that there was another way. Indeed, TRS submitted that they had adopted what was colloquially described as the “Finkelstein template” or the “Invoice Methodology”: see [6] above.
|
Week of Indemnity
|
Week commencing
|
...
|
Weekly Turnover [(Actual)]
|
Loss/(Gain) of Average Weekly Turnover
|
|---|---|---|---|---|
|
1
|
3 Apr 2007
|
|
95,455
|
296,976
|
|
2
|
10 Apr 2007
|
|
12,780
|
379,652
|
|
3
|
17 Apr 2007
|
|
96,996
|
295,435
|
|
4
|
24 Apr 2007
|
|
2,214,658
|
(1,822,227)
|
|
5
|
1 May 2007
|
|
474
|
391,957
|
|
6
|
8 May 2007
|
|
918,202
|
(525,771)
|
|
7
|
15 May 2007
|
|
414,481
|
(22,050)
|
|
8
|
22 May 2007
|
|
188,870
|
203,561
|
|
9
|
29 May 2007
|
|
2,273,657
|
(1,881,226)
|
|
10
|
5 Jun 2007
|
|
751,142
|
(358,711)
|
|
11
|
12 Jun 2007
|
|
10,096
|
382,335
|
|
12
|
19 Jun 2007
|
|
20,193
|
372,239
|
|
13
|
26 Jun 2007
|
|
2,027,686
|
(1,635,255)
|
|
14
|
3 Jul 2007
|
|
373,853
|
18,578
|
|
15
|
10 Jul 2007
|
|
40,255
|
352,176
|
|
16
|
17 Jul 2007
|
|
349,928
|
42,503
|
|
17
|
24 Jul 2007
|
|
140,661
|
251,770
|
|
18
|
31 Jul 2007
|
|
56,513
|
335,918
|
|
19
|
7 Aug 2007
|
|
181,004
|
211,427
|
|
20
|
14 Aug 2007
|
|
579,700
|
(187,269)
|
|
21
|
21 Aug 2007
|
|
31,307
|
361,124
|
|
22
|
28 Aug 2007
|
|
670
|
391,761
|
|
23
|
4 Sep 2007
|
|
216,853
|
175,578
|
|
24
|
11 Sep 2007
|
|
(191,227)
|
583,658
|
|
25
|
18 Sep 2007
|
|
1,125,981
|
(733,550)
|
|
26
|
25 Sep 2007
|
|
814,526
|
(422,095)
|
|
27
|
2 Oct 2007
|
|
(139,154)
|
531,586
|
|
28
|
9 Oct 2007
|
|
628,753
|
(236,321)
|
|
29
|
16 Oct 2007
|
|
219,377
|
173,055
|
|
|
|
|
13,453,693
|
(2,073,185)
|
4.1 Milestone invoicing – where the customer may only be able to be invoiced when particular milestones are achieved (for example, completion of particular work);
4.2 Progress invoicing – either on a dollar value or time basis (or both) as agreed with the customer (for example, every two weeks value of work in progress); and / or
4.3 Completion invoicing – where invoices are raised on completion of the work.
The Policy provided indemnity for losses incurred on a week by week basis. In other words, if a weekly claim had been made, for example, on 17 April 2007, TRS was obliged to establish the causal link between the loss claimed in that week and the interruption to TRS’ business. If it was established, then the claim was paid within “seven days whenever practicable”. The next week the same was required of TRS and so on. The facts for each week may well have been different because the cause or causes of the loss (if there was a loss) may well have been different. In the case of TRS, given the nature of its business and the different contractual and payment terms with different customers (see [17] above), it would be expected that the loss in any one week was caused by a different set of facts and matters.
Alternative Methodology
CONCLUSIONS
|
I certify that the preceding twenty-five (25) numbered paragraphs are a
true copy of the Reasons for Judgment herein of the Honourable
Justice
Gordon.
|
Associate:
Dated: 21
December 2010
AustLII:
Copyright Policy
|
Disclaimers
|
Privacy Policy
|
Feedback
URL: http://www.austlii.edu.au/au/cases/cth/FCA/2010/1439.html