07.11.2014 Views

Judgment - Reinsurance Focus

Judgment - Reinsurance Focus

Judgment - Reinsurance Focus

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

one has ever suggested that it is necessary to disclose the name<br />

of the person interested in her who is desiring to insure or<br />

reinsure his interest. . . . . .”<br />

28.<br />

As in the case of all such observations, this passage must be read in the context of the issues<br />

that arose in that case. If that is done it will be seen that Scrutton J. was not seeking to<br />

expound any general principles of law but was addressing himself to a particular issue<br />

before the court, namely, whether in accordance with the ordinary practices of the<br />

marine insurance market the defendant brokers were bound to disclose to the plaintiff<br />

insurers the fact that the risks they were seeking to reinsure had been written by their<br />

partners at a higher premium than that being proposed to the plaintiffs. In that context<br />

one can understand why neither the judgment of another underwriter as to the<br />

premium to be charged nor the identity of the proposed reinsured were material<br />

matters. In my view the judge's remarks have limited application to a case such as the<br />

present, save for his insistence that there had to be true disclosure of the ship and the<br />

perils affecting her.<br />

29.<br />

Whether any particular circumstance is or is not material is a question of fact which the court<br />

is usually invited to determine after hearing evidence from those who have practical<br />

experience as underwriters. It is not a question which can be determined on the basis<br />

of the agreed facts. I can understand that in many cases the identity of the undisclosed<br />

principal will be a matter of indifference to the insurer, but I should be surprised if<br />

that were so in the case of Sembawang since its right to be treated as a co-assured<br />

would be likely to affect the insurers' ability to pursue a claim against it in the name<br />

of CPL. It is no answer, as Mr. Kealey pointed out, to say that any claim by the<br />

insurers under the Completion Contract would in any event have been met by a<br />

counter-claim for breach of clause 15.12. At the time of the placing the insurers were<br />

not aware of that clause and were therefore entitled to assess the risk on the basis that<br />

they would be entitled to pursue a claim against the yard if the circumstances<br />

otherwise justified it.<br />

Mr. Flaux submitted that the insurers had in any event waived disclosure of Sembawang's<br />

position as an undisclosed principal by including it as a co-assured under the terms of<br />

the so-called 'Additional Assureds' clause, by the very fact that the law permits an<br />

undisclosed principal to sue on the contract and by including in the 'Additional<br />

Assureds' clause an undertaking to waive their rights of subrogation against anyone in<br />

respect of whom Sea Trucks or CPL asked them to.<br />

I am unable to accept any of those submissions. For the reasons given earlier I am unable to<br />

accept that the clause in question bears the meaning suggested by Mr. Flaux and<br />

therefore I do not accept that it rendered Sembawang a co-assured. The fact that the<br />

law generally recognises the right of an undisclosed principal to sue and be sued on a<br />

contract does not relieve the nominal insured from the duty to make full disclosure of<br />

all material circumstances in each case, including any which may relate to his<br />

undisclosed principal. That is essential to ensure a fair presentation of the risk to the<br />

insurer. Although no attempt has been made to identify the terms of the 'Waiver of<br />

Subrogation' clause to which the slip refers, I see no reason to think that the insurers

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!