SUPREME COURT OF CANADA
Citation: Progressive Homes Ltd. v. Lombard General Insurance Co. of Canada, 2010 SCC 33, [2010] 2 S.C.R.245
Date: 20100923
Docket: 33170
Between:
Progressive Homes Ltd.
Appellant
and
Lombard General Insurance Company of Canada
Respondent
Coram: McLachlin C.J. and Binnie, LeBel, Deschamps, Fish, Abella, Charron, Rothstein and Cromwell JJ.
Reasons for Judgment:
(paras. 1 to 73)
Rothstein J. (McLachlin C.J. and Binnie, LeBel, Deschamps, Fish, Abella, Charron and Cromwell JJ. concurring)
______________________________
Progressive Homes Ltd. v. Lombard General Insurance Co. of Canada, 2010 SCC 33, [2010] 2 S.C.R.245
Progressive Homes Ltd. Appellant
v.
Lombard General Insurance Company of Canada Respondent
Indexed as: Progressive Homes Ltd. v. Lombard General Insurance Co. of Canada
2010 SCC 33
File No.: 33170.
2010: April 20; 2010: September 23.
Present: McLachlin C.J. and Binnie, LeBel, Deschamps, Fish, Abella, Charron, Rothstein and Cromwell JJ.
on appeal from the court of appeal for british columbia
Insurance — Liability insurance — Insurer’s duty to defend — Commercial general liability policy — Scope of coverage — Claims against insured for negligence in construction of buildings and for breach of contract — Insured alleging inadequate construction completed by subcontractors — Insurance policy covers property damage caused by an accident — Whether “property damage” limited to third-party property damage — Whether defective workmanship considered to be an “accident” — Whether insurer owes a duty to defend claims against insured.
Insurance — Liability insurance — Insurer’s duty to defend — Policy exclusion — Whether exclusion for “work performed” includes work completed by subcontractors.
The insured, Progressive Homes, was hired as a general contractor to build several housing complexes. After completion, four actions were initiated against Progressive claiming breach of contract and negligence. It was alleged that significant water damage caused rot, infestation and deterioration to all four buildings. Progressive had secured several commercial general liability insurance policies with the insurer, Lombard. The policies required Lombard to defend and indemnify Progressive when Progressive is legally obligated to pay damages because of property damage caused by an occurrence or accident. Lombard claimed that it did not have a duty to defend because the claims were not covered under the insurance policies. Progressive brought an application for a declaration that Lombard was under a duty to defend in the four actions. The applications judge found that the claims did not fall within the initial grant of coverage under the policies and therefore Lombard did not owe a duty to defend. A majority of the Court of Appeal dismissed the appeal.
Held: The appeal should be allowed.
An insurer is required to defend a claim where the facts alleged in the pleadings, if proven to be true, would require the insurer to indemnify the insured for the claim. It is irrelevant whether the allegations in the pleadings can be proven in evidence. What is required is the mere possibility that a claim falls within the insurance policy. Where it is clear that the claim falls outside the policy, either because it does not come within the initial grant of coverage or is excluded by an exclusion clause, there will be no duty to defend. In examining the pleadings to determine whether the claims fall within the scope of coverage, what is determinative is the true nature or substance of the claim, not the labels selected by the plaintiff.
The focus of insurance policy interpretation should first and foremost be on the language of the policy at issue. For insurance policies that set out coverage, followed by exclusions, followed by exceptions, such as those found in this case, it is generally advisable to interpret the policy in the order of: coverage, exclusions and then exceptions. Each of the insurance policies in this case cover “property damage” caused by an “accident”. The onus is on Progressive to show that the pleadings fall within the initial grant of coverage. The plain and ordinary meaning of “property damage” in this case includes damage to any tangible property and is not limited to damage to third-party property. Hence, damage to one part of a building arising from another part of the same building could be included in the definition. “Accident” should also be given the plain meaning prescribed to it in the policies and should apply when an event causes property damage neither expected nor intended by the insured. The accident need not be a sudden event and can result from continuous or repeated exposure to conditions. Whether defective workmanship is an accident is necessarily a case-specific determination. It will depend both on the circumstances of the defective workmanship alleged in the pleadings and the way in which “accident” is defined in the policy.
The duty to defend only requires a possibility of coverage, and that possibility is made out in this case. The pleadings reveal a possibility of “property damage”. The pleadings describe water leaking in through windows and walls and allege deterioration of the building components resulting from water ingress and infiltration. The pleadings also describe defective property. The pleadings also sufficiently allege an “accident” for the purpose of deciding whether Lombard owes a duty to defend. There is no reference to intentional conduct by Progressive which would suggest that the property damage was expected or intended. The pleadings allege negligence, which, on its face, suggests that the damage was fortuitous. In addition, it is clear from the pleadings that the damage alleged is the result of “continuous or repeated exposure to conditions”, which squarely fits within the definition.
Having found the claims in the pleadings fall within the initial grant of coverage, the onus shifts to Lombard to show that coverage is precluded by an exclusion clause. Lombard has not discharged its burden of showing that the “work performed” exclusion clearly and unambiguously applies to all of the claims made against Progressive and there is thus a possibility of coverage under each version of the policy. Depending on which version of the policy applies, there is a possibility of coverage for damage to work completed by a subcontractor, for damage resulting from work performed by a subcontractor, or for damage resulting from the particular part of the Progressive’s work that was defective. Therefore, the duty to defend is triggered.
Cases Cited
Referred to: Swagger Construction Ltd. v. ING Insurance Co. of Canada, 2005 BCSC 1269, 47 B.C.L.R. (4th) 75; Nichols v. American Home Assurance Co., [1990] 1 S.C.R. 801; Monenco Ltd. v. Commonwealth Insurance Co., 2001 SCC 49, [2001] 2 S.C.R. 699; Jesuit Fathers of Upper Canada v. Guardian Insurance Co. of Canada, 2006 SCC 21, [2006] 1 S.C.R. 744; Non‑Marine Underwriters, Lloyd’s of London v. Scalera, 2000 SCC 24, [2000] 1 S.C.R. 551; Co‑operators Life Insurance Co. v. Gibbens, 2009 SCC 59, [2009] 3 S.C.R. 605; Brissette Estate v. Westbury Life Insurance Co., [1992] 3 S.C.R. 87; Consolidated‑Bathurst Export Ltd. v. Mutual Boiler and Machinery Insurance Co., [1980] 1 S.C.R. 888; Winnipeg Condominium Corporation No. 36 v. Bird Construction Co., [1995] 1 S.C.R. 85; Bird Construction Co. v. Allstate Insurance Co. of Canada, [1996] 7 W.W.R. 609; Alie v. Bertrand & Frère Construction Co. (2002), 222 D.L.R. (4th) 687; Bridgewood Building Corp. (Riverfield) v. Lombard General Insurance Co. of Canada (2006), 266 D.L.R. (4th) 182; Westridge Construction Ltd. v. Zurich Insurance Co., 2005 SKCA 81, 269 Sask. R. 1; Celestica Inc. v. ACE INA Insurance (2003), 229 D.L.R. (4th) 392; Erie Concrete Products Ltd. v. Canadian General Insurance Co., [1969] 2 O.R. 372; Harbour Machine Ltd. v. Guardian Insurance Co. of Canada (1985), 60 B.C.L.R. 360; Supercrete Precast Ltd. v. Kansa General Insurance Co. (1990), 45 C.C.L.I. 248; Canadian Indemnity Co. v. Walkem Machinery & Equipment Ltd., [1976] 1 S.C.R. 309; Martin v. American International Assurance Life Co., 2003 SCC 16, [2003] 1 S.C.R. 158; Fenton v. J. Thorley & Co., Ltd., [1903] A.C. 443; American Family Mutual Insurance Co. v. American Girl, Inc., 673 N.W.2d 65 (2004).
Authors Cited
Audet, Maurice. “Broad Form Completed Operations: An extension of coverage or a trap?” (1984), 51:10 Canadian Underwriter 36.
Couch on Insurance 3D, 3rd ed., vol. 11, by Lee R. Russ and Thomas F. Segalla. Eagan, Minn.: West, 2005 (loose‑leaf updated June 2010).
Lichty, Mark G. and Marcus B. Snowden. Annotated Commercial General Liability Policy, vols. 1 and 2. Aurora, Ont.: Canada Law Book, 1997 (loose‑leaf updated February 2010, release 14).
Wielinski, Patrick J. “CGL Coverage for Defective Workmanship: Current (and Ongoing) Issues”. Paper presented at the 16th Annual Construction Law Conference, State Bar of Texas, Dallas, Texas, March 7, 2003.
APPEAL from a judgment of the British Columbia Court of Appeal (Ryan, Huddart and Kirkpatrick JJ.A.), 2009 BCCA 129, 90 B.C.L.R. (4th) 297, 307 D.L.R. (4th) 460, 268 B.C.A.C. 235, 452 W.A.C. 235, [2009] 8 W.W.R. 261, 72 C.C.L.I. (4th) 163, 78 C.L.R. (3d) 171, [2009] I.L.R. ¶I‑4826, [2009] B.C.J. No. 572 (QL), 2009 CarswellBC 744, affirming a decision of Cohen J., 2007 BCSC 439, 71 B.C.L.R. (4th) 113, [2007] 6 W.W.R. 734, 48 C.C.L.I. (4th) 64, 59 C.L.R. (3d) 225, [2007] I.L.R. ¶I‑4626, [2007] B.C.J. No. 651 (QL), 2007 CarswellBC 635. Appeal allowed.
Gordon Hilliker, Q.C., and Neo Tuytel, for the appellant.
Ward K. Branch, Michael J. Sobkin and Christopher Rhone, for the respondent.
The judgment of the Court was delivered by
[1] Rothstein J. — The issue in this appeal is whether the insurer, Lombard General Insurance Company of Canada (“Lombard”), owes a duty to defend claims against the insured, Progressive Homes Ltd. (“Progressive”). For the reasons that follow, I conclude that Lombard owes a duty to defend.
I. Overview
A. Facts
[2] British Columbia Housing Management Commission (“BC Housing”) hired Progressive as a general contractor to build several housing complexes. After completion, BC Housing initiated four actions against Progressive alleging significant damage caused by water leaking into each of the four buildings. The claims allege breach of contract and negligence. The water damage has allegedly caused significant rot, infestation and deterioration to all four buildings. BC Housing alleges that the buildings are unsafe and pose a serious risk to the health and safety of the occupants.
[3] Progressive had secured five successive commercial general liability insurance policies (“CGL policies”) with Lombard. These successive policies were in place from the time of construction until the time the actions against Progressive were brought. There were three versions of the five successive policies: the first version being the first policy; the second version being the second, third and fourth policies; and the third version being the fifth policy. The policies are “occurrence policies” which insure Progressive against damage caused by “occurrences” or “accidents”. The policies require Lombard to defend and indemnify Progressive when Progressive is legally obligated to pay damages because of property damage caused by an occurrence or accident.
[4] Lombard initially defended Progressive, but later withdrew claiming that it had no duty to defend because the claims were not covered under the insurance policies. The withdrawal was, at least in part, a result of a prior B.C. Supreme Court decision, Swagger Construction Ltd. v. ING Insurance Co. of Canada, 2005 BCSC 1269, 47 B.C.L.R. (4th) 75 (“Swagger”), which found that similar damage was not covered by a similar insurance policy.
[5] Progressive brought an application for a declaration that Lombard is under a duty to defend in the four actions.
B. Pleadings
[6] The issue of the duty to defend requires the consideration of the pleadings in the actions against Progressive to determine if there is a possibility of the claims falling within the insurance coverage. There are four actions against Progressive — one for each housing unit. The four sets of pleadings are very similar. The pleadings allege that Progressive was negligent in its construction of the housing units and that it breached its contract with BC Housing. The pleadings allege that Progressive’s conduct resulted in the following:
DEFECTS
29. As a result of the breaches of contract by Progressive and the negligence of the Defendants and others, and all of them, the Development has sustained since the date of construction and continues to sustain defects and ongoing damage including the following:
(a) water leaking through the exterior walls;
(b) improper and incomplete installation and construction of framing, stucco walls, vinyl siding, windows, sheathing paper, flashings, ventilation, walkway membranes, flashing membranes, eaves troughs, downspouts, gutters, drains, balcony decks, pedestrian walkways, railings, roofs, and patio doors;
(c) insufficient venting and drainage of wall systems;
(d) inadequate exhaust ventilation system;
(e) water leaking through the windows;
(f) improper use of caulking;
(g) poorly assembled and installed windows;
(h) deterioration of the building components resulting from water ingress and infiltration
all of which are collectively referred to as the “Defects” and were caused by the Defendants and all of which constitute further breaches of the terms of the agreements referenced above.
30. As a reasonably foreseeable consequence of Defects and particulars outlined above, significant portions of the Development have suffered since the date of construction and continue to suffer considerable moisture penetration, resultant rot and infestation which has caused the Development to be unsafe and hazardous and to pose a substantial physical danger to the health and safety of the occupants.
. . .
DAMAGES
33. As a result of the Defects and of the negligence and breaches of contract by the Defendants the Plaintiffs have suffered damages including but not limited to the following:
(a) inspection and professional advice concerning the Defects;
(b) cost to date of remedial work, both permanent and temporary;
(c) cost of relocation and alternate housing of tenants during remediation work and other tenant expenses;
(d) diminution in value of the Development; and
(e) expense, inconvenience and hardship caused by the construction and design deficiencies and their repair.
In essence, the pleadings allege that the condos were inadequately constructed, resulting in significant water damage.
[7] Progressive asserts that the inadequate construction was completed by subcontractors. The pleadings identify several subcontractors who were responsible for the installation of vinyl decking, a waterproof membrane and a ventilation system.
C. Insurance Policies
[8] At all material times Progressive has had successive CGL policies in place from 1987 to 2005. While the details of the individual policies differ, the basic features of the policies are the same. Under each policy, Progressive is covered (subject to specific exclusions) for property damage caused by an accident. The description of coverage is not materially different in each version of the policy. The first policy states:
COVERAGE B – Property Damage Liability
To pay on behalf of the Insured all sums which the Insured shall become legally obligated to pay as damages because of property damage caused by accident.
[9] Under each policy, Lombard owes a duty to defend Progressive. For example, the first policy states:
As respects insurance afforded by this form, the Insurer shall:
(1) defend in the name and on behalf of the Insured and at the cost of the Insurer any civil action which may at any time be brought against the Insured on account of such bodily injury or property damage but the Insurer shall have the right to make such investigation, negotiation and settlement of any claim as may be deemed expedient by the Insurer; [Emphasis added.]
[10] “Property damage” is a defined term in the policies. The first policy defines “property damage” as:
“Property damage” means (1) physical injury to or destruction of tangible property which occurs during the policy period, including the loss of use thereof at any time resulting therefrom, or (2) loss of use of tangible property which has not been physically injured or destroyed provided such loss of use is caused by an accident occurring during the policy period.
[11] “Accident” is a defined term in the first policy:
“Accident” includes continuous or repeated exposure to conditions which result in property damage neither expected nor intended from the standpoint of the Insured.
In subsequent policies, the term “occurrence” is used. It is defined in the second and third versions of the policy as:
“Occurrence” means an accident, including continuous or repeated exposure to substantially the same general harmful conditions.
[12] Even if the claims fall within the initial grant of coverage — that is, there is property damage caused by an accident — then coverage may still be excluded if the insurance company shows that an exclusion clause applies. Of particular importance to this appeal is the “work performed” exclusion, which appears in three forms in the successive policies. This exclusion precludes coverage for damage to the insured’s own work once it has been completed. The details of this exclusion will be examined more closely below.
II. Judicial History
A. Supreme Court of British Columbia, 2007 BCSC 439, 71 B.C.L.R. (4th) 113
[13] Mr. Justice Cohen examined the pleadings and policies to determine whether there was a possibility that the claims in the pleadings fell within the insurance coverage. He concluded that Lombard did not owe a duty to defend. Cohen J. followed a line of authority, most recently the Swagger decision, that upheld the proposition that defective construction is not an “accident” unless it causes damage to the property of a third party. He found that the court could not artificially divide the insured’s work into its component parts for the purpose of establishing resulting property damage.
[14] Cohen J. concluded that the pleadings against Progressive were “simply [a] claim for the cost of remediating parts of the unified whole and not ‘property damage’” (para. 57). Therefore, the claims did not fall within the initial grant of coverage under the policies and Lombard did not owe a duty to defend.
B. Court of Appeal for British Columbia, 2009 BCCA 129, 90 B.C.L.R. (4th) 297
[15] A majority of the Court of Appeal dismissed the appeal. Ryan J.A., writing for herself and Kirkpatrick J.A., accepted that the duty to defend must be resolved on the wording of the policy. She also accepted that the plain meaning of the insuring provisions could support the conclusion that the claims against Progressive fell within the insurance coverage. However, she concluded that “such an interpretation flies in the face of the underlying assumption that insurance is designed to provide for fortuitous contingent risk” (para. 69). In her view, damage resulting from faulty workmanship could not be considered fortuitous.
[16] In any event, Ryan J.A. examined the “work performed” exclusion contained in the contracts. Ryan J.A. accepted that in some circumstances work performed by a subcontractor could be covered by the policies, but only if the damage was caused by a distinct item installed by a subcontractor, such as a boiler exploding. However, she found that this was not the situation in this appeal. On her reading, the pleadings alleged that integral parts of the building itself failed to function properly and were not “distinct” components that could be covered. Therefore, she held that Lombard did not owe a duty to defend.
[17] Madam Justice Huddart dissented. She found that the language of the policies supported the conclusion that damage resulting from subcontractor negligence is covered. In her view, the definition of property damage could apply where the damage was to the same building out of which the damage arose. On her reading of the policies, the exclusion clauses did not exclude damage resulting from work by subcontractors. Huddart J.A. would have found that Lombard owed a duty to defend.
III. Issue
[18] The only issue in this appeal is whether Lombard owes a duty to defend the claims against Progressive.
IV. Analysis
A. The Duty to Defend
[19] An insurer is required to defend a claim where the facts alleged in the pleadings, if proven to be true, would require the insurer to indemnify the insured for the claim (Nichols v. American Home Assurance Co., [1990] 1 S.C.R. 801, at pp. 810-11; Monenco Ltd. v. Commonwealth Insurance Co., 2001 SCC 49, [2001] 2 S.C.R. 699, at para. 28; Jesuit Fathers of Upper Canada v. Guardian Insurance Co. of Canada, 2006 SCC 21, [2006] 1 S.C.R. 744, at paras. 54-55). It is irrelevant whether the allegations in the pleadings can be proven in evidence. That is to say, the duty to defend is not dependent on the insured actually being liable and the insurer actually being required to indemnify. What is required is the mere possibility that a claim falls within the insurance policy. Where it is clear that the claim falls outside the policy, either because it does not come within the initial grant of coverage or is excluded by an exclusion clause, there will be no duty to defend (see Nichols, at p. 810; Monenco, at para. 29).
[20] In examining the pleadings to determine whether the claims fall within the scope of coverage, the parties to the insurance contract are not bound by the labels selected by the plaintiff (Non-Marine Underwriters, Lloyd’s of London v. Scalera, 2000 SCC 24, [2000] 1 S.C.R. 551, at paras. 79 and 81). The use or absence of a particular term will not determine whether the duty to defend arises. What is determinative is the true nature or the substance of the claim (Scalera, at para. 79; Monenco, at para. 35; Nichols, at p. 810).
B. General Principles of Insurance Policy Interpretation
[21] Principles of insurance policy interpretation have been canvassed by this Court many times and I do not intend to give a comprehensive review here (see, e.g., Co‑operators Life Insurance Co. v. Gibbens, 2009 SCC 59, [2009] 3 S.C.R. 605, at paras. 20-28; Jesuit Fathers, at paras. 27-30; Scalera, at paras. 67-71; Brissette Estate v. Westbury Life Insurance Co., [1992] 3 S.C.R. 87, at pp. 92-93; Consolidated‑Bathurst Export Ltd. v. Mutual Boiler and Machinery Insurance Co., [1980] 1 S.C.R. 888, at pp. 899-902). However, a brief review of the relevant principles may be a useful introduction to the interpretation of the CGL policies that follow.
[22] The primary interpretive principle is that when the language of the policy is unambiguous, the court should give effect to clear language, reading the contract as a whole (Scalera, at para. 71).
[23] Where the language of the insurance policy is ambiguous, the courts rely on general rules of contract construction (Consolidated‑Bathurst, at pp. 900-902). For example, courts should prefer interpretations that are consistent with the reasonable expectations of the parties (Gibbens, at para. 26; Scalera, at para. 71; Consolidated-Bathurst, at p. 901), so long as such an interpretation can be supported by the text of the policy. Courts should avoid interpretations that would give rise to an unrealistic result or that would not have been in the contemplation of the parties at the time the policy was concluded (Scalera, at para. 71; Consolidated-Bathurst, at p. 901). Courts should also strive to ensure that similar insurance policies are construed consistently (Gibbens, at para. 27). These rules of construction are applied to resolve ambiguity. They do not operate to create ambiguity where there is none in the first place.
[24] When these rules of construction fail to resolve the ambiguity, courts will construe the policy contra proferentem — against the insurer (Gibbens, at para. 25; Scalera, at para. 70; Consolidated-Bathurst, at pp. 899-901). One corollary of the contra proferentem rule is that coverage provisions are interpreted broadly, and exclusion clauses narrowly (Jesuit Fathers, at para. 28).
[25] With these interpretive principles in mind, I turn to the insurance policies at issue in this appeal.
C. The Lombard Insurance Policies
[26] The insurance contracts in this appeal are CGL policies. CGL insurance policies typically consist of several sections (see Jesuit Fathers, at para. 34; see also M. G. Lichty and M. B. Snowden, Annotated Commercial General Liability Policy (loose‑leaf), vol. 1, at p. 1-9). The policy will set out the types of coverage contained in the agreement, for example, property damage caused by an accident.
[27] This is typically followed by specific exclusions to coverage. Exclusions do not create coverage — they preclude coverage when the claim otherwise falls within the initial grant of coverage. Exclusions, should, however, be read in light of the initial grant of coverage (Annotated Commercial General Liability Policy, vol. 1, at p. 1-10).
[28] A CGL policy may also contain exceptions to exclusions. Exceptions also do not create coverage — they bring an otherwise excluded claim back within coverage, where the claim fell within the initial grant of coverage in the first place (Annotated Commercial General Liability Policy, vol. 1, at p. 1-10). Because of this alternating structure of the CGL policy, it is generally advisable to interpret the policy in the order described above: coverage, exclusions and then exceptions.
(1) Coverage
[29] Each insurance policy covers property damage caused by an accident. The question, then, is what are the meanings of “property damage” and “accident” in these policies. The onus is on the insured, Progressive, to show that the pleadings fall within the initial grant of coverage.
(a) Property Damage
[30] The definition of “property damage” in the first policy is:
“Property damage” means (1) physical injury to or destruction of tangible property which occurs during the policy period, including the loss of use thereof at any time resulting therefrom, or (2) loss of use of tangible property which has not been physically injured or destroyed provided such loss of use is caused by an accident occurring during the policy period.
In later versions of the policies, the references to destruction were removed:
“Property damage” means:
a. Physical injury to tangible property, including all resulting loss of use of that property; or
b. Loss of use of tangible property that is not physically injured.
[31] Lombard’s main argument is that “property damage” does not result from damage to one part of a building arising from another part of the same building. According to Lombard, damage to other parts of the same building is pure economic loss, not property damage. What follows from this argument is that “property damage” is limited to third-party property.
[32] Lombard’s argument stems from a distinction between property damage and pure economic loss that is drawn in tort law. It relies on a passage from this Court’s decision in Winnipeg Condominium Corporation No. 36 v. Bird Construction Co., [1995] 1 S.C.R. 85. This was a claim in negligence against a general contractor, subcontractor and architect after a storey-high section of cladding fell from the side of a building to the ground below. The Court found that the loss was not property damage, but a recoverable form of economic loss. The passage on which Lombard relies is the adoption of an excerpt from a House of Lords decision, which rejects the notion that a building can be subdivided into its component parts for the purpose of finding resulting property damage. At para. 15 of Winnipeg Condominium, La Forest J. stated:
In [Murphy v. Brentwood District Council, [1990] 2 A11 E.R. 908 (H.L.)], at pp. 926‑28, Lord Bridge reconsidered and rejected the “complex structure” theory he had suggested in D & F Estates, criticizing the theory on the following basis (at p. 928):
The reality is that the structural elements in any building form a single indivisible unit of which the different parts are essentially interdependent. To the extent that there is any defect in one part of the structure it must to a greater or lesser degree necessarily affect all other parts of the structure. Therefore any defect in the structure is a defect in the quality of the whole and it is quite artificial, in order to impose a legal liability which the law would not otherwise impose, to treat a defect in an integral structure, so far as it weakens the structure, as a dangerous defect liable to cause damage to ‘other property’.
A critical distinction must be drawn here between some part of a complex structure which is said to be a ‘danger’ only because it does not perform its proper function in sustaining the other parts and some distinct item incorporated in the structure which positively malfunctions so as to inflict positive damage on the structure in which it is incorporated. Thus, if a defective central heating boiler explodes and damages a house or a defective electrical installation malfunctions and sets the house on fire, I see no reason to doubt that the owner of the house, if he can prove that the damage was due to the negligence of the boiler manufacturer in the one case or the electrical contractor in the other, can recover damages in tort on Donoghue v. Stevenson principles.
I am in full agreement with Lord Bridge’s criticisms of the “complex structure” theory. [Emphasis added.]
[33] After the defendants were found liable in Winnipeg Condominium, the general contractor, Bird, sought indemnification from its insurer in Bird Construction Co. v. Allstate Insurance Co. of Canada, [1996] 7 W.W.R. 609. The Manitoba Court of Appeal relied on the passage from Winnipeg Condominium to conclude that the claim was not covered because it was not a claim for property damage (para. 11). However, the court also found that coverage was precluded because of a specific exclusion for worked performed by or on behalf of the policyholder (para. 12).
[34] Lombard relies on this reasoning to assert its position that “property damage” in the CGL policies cannot mean damage caused by other parts of the same building. Lombard argues that property damage is limited to third-party property damage and does not include damage to the insured’s own work.
[35] I cannot agree with Lombard’s interpretation of “property damage”. The focus of insurance policy interpretation should first and foremost be on the language of the policy at issue. General principles of tort law are no substitute for the language of the policy. I see no limitation to third-party property in the definition of “property damage”. Nor is the plain and ordinary meaning of the phrase “property damage” limited to damage to another person’s property. Indeed, the Ontario and Saskatchewan Courts of Appeal reached the same conclusion with respect to similar definitions of “property damage” in CGL policies: Alie v. Bertrand & Frère Construction Co. (2002), 222 D.L.R. (4th) 687 (Ont. C.A.), at paras. 26, 41 and 45, and Bridgewood Building Corp. (Riverfield) v. Lombard General Insurance Co. of Canada (2006), 266 D.L.R. (4th) 182 (Ont. C.A.), at paras. 6-7; Westridge Construction Ltd. v. Zurich Insurance Co., 2005 SKCA 81, 269 Sask. R. 1, at para. 38.
[36] I would construe the definition of “property damage”, according to the plain language of the definition, to include damage to any tangible property. I do not agree with Lombard that the damage must be to third-party property. There is no such restriction in the definition.
[37] The plain meaning of “property damage” is consistent with reading the policy as a whole. Qualifying the meaning of “property damage” to mean third-party property would leave little or no work for the “work performed” exclusion (discussed in more detail below). Lombard argues that the exclusion clauses do not create coverage. This is true. But reading the insurance policy as a whole is not the same as conjuring up coverage when there was none in the first place. Consistency with the exclusion clauses is a further indicator that the plain meaning of “property damage” is the definition intended by the parties.
[38] Does the definition of “property damage” exclude defects? Or, can defective property constitute “property damage” as defined in the policies? Progressive concedes that the effect of the definition of “property damage” is to exclude coverage for a claim to repair a defect. Lombard agrees that defects are not included in the definition of “property damage”.
[39] While this point was not contested and nothing turns on it in this appeal, it is not obvious to me that defective property cannot also be “property damage”. In particular, it may be open to argument that a defect could not amount to a “physical injury”, especially where the harm to the property is “physical” in the sense that it is visible or apparent (see, e.g., Annotated Commercial General Liability Policy, vol. 1, at p. 10-10). Moreover, where a defect renders the property entirely useless it may be arguable that defective property may be covered under “loss of use”, the second portion of the definition of “property damage”.
[40] I would also note that not barring defective property from the definition of “property damage” at the outset gives meaning to the exclusion clauses discussed below. Specifically, the second version of the policies expressly excludes coverage for defects. This would be redundant if defects were excluded from “property damage” at the outset. While perfect mutual exclusivity in an insurance contract is not required, this redundancy supports the view that the definition of “property damage” may not categorically exclude defective property.
[41] Do the pleadings allege “property damage”? In my view, they do. The pleadings describe water leaking in through windows and walls and allege “deterioration of the building components resulting from water ingress and infiltration”. The pleadings also describe defective property, which may also be “property damage”: e.g., improperly built walls, inadequate ventilation system, poorly installed windows. Whether specific property actually falls within the definition of “property damage” is a matter to be determined on the evidence at trial. This meets the low threshold of showing that the pleadings reveal a possibility of property damage for the purpose of deciding whether Lombard owes a duty to defend.
(b) Accident
[42] Progressive must also show that the property damage described above was caused by an accident.
[43] “Accident” is defined in the first policy as:
“Accident” includes continuous or repeated exposure to conditions which result in property damage neither expected nor intended from the standpoint of the Insured.
As indicated before, essentially the same definition applies to “occurrence” which is used in later versions of the policies.
[44] Progressive again relies on the plain meaning of the definition of accident. It argues that “accident” includes the negligent act that caused damage that was neither expected nor intended by Progressive.
[45] Lombard disagrees. Lombard argues that when a building is constructed in a defective manner, the end result is a defective building, not an accident. It relies on case law that, in its view, supports its argument that faulty workmanship is not an accident (e.g., Celestica Inc. v. ACE INA Insurance (2003), 229 D.L.R. (4th) 392 (Ont. C.A.); Erie Concrete Products Ltd. v. Canadian General Insurance Co., [1969] 2 O.R. 372 (H.C.J.); Harbour Machine Ltd. v. Guardian Insurance Co. of Canada (1985), 60 B.C.L.R. 360 (C.A.); Supercrete Precast Ltd. v. Kansa General Insurance Co. (1990), 45 C.C.L.I. 248 (B.C.S.C.)). It relies on Ryan J.A.’s conclusion, in the court below, that this interpretation would offend the assumption that insurance provides for fortuitous contingent risk. Lombard argues that interpreting accident to include defective workmanship would convert CGL policies into performance bonds. In my opinion, these general propositions advanced by Lombard do not hold upon closer examination.
[46] First, whether defective workmanship is an accident is necessarily a case‑specific determination. It will depend both on the circumstances of the defective workmanship alleged in the pleadings and the way in which “accident” is defined in the policy. I, therefore, cannot agree with Lombard’s view that faulty workmanship is never an accident. This Court’s jurisprudence shows that there is no categorical bar to concluding in any particular case that defective workmanship is an accident. In Canadian Indemnity Co. v. Walkem Machinery & Equipment Ltd., [1976] 1 S.C.R. 309, at pp. 315-17, the Court found that the negligent repair of a crane constituted an accident. Therefore, I see no impediment to concluding the same in the present case, unless of course it is not supported by the specific language of the policy.
[47] Second, I cannot agree with Justice Ryan’s conclusion that such an interpretation offends the assumption that insurance provides for fortuitous contingent risk. Fortuity is built into the definition of “accident” itself as the insured is required to show that the damage was “neither expected nor intended from the standpoint of the Insured”. This definition is consistent with this Court’s core understanding of “accident”: “an unlooked-for mishap or an untoward event which is not expected or designed” (Gibbens, at para. 22; Martin v. American International Assurance Life Co., 2003 SCC 16, [2003] 1 S.C.R. 158, at para. 20; Canadian Indemnity, at pp. 315-16; originating in Fenton v. J. Thorley & Co., Ltd., [1903] A.C. 443, at p. 448). When an event is unlooked for, unexpected or not intended by the insured, it is fortuitous. This is a requirement of coverage; therefore, it cannot be said that this offends any basic assumption of insurance law.
[48] Finally, I am not persuaded by Lombard’s argument that equating faulty workmanship to an accident will convert CGL policies into performance bonds. There seems to be a fairly significant difference between a performance bond and the CGL policies at issue in this case: a performance bond ensures that a work is brought to completion (Couch on Insurance 3D (3rd ed. (loose-leaf)), vol. 11, by L. R. Russ and T. F. Segalla, at p. 163-20), whereas the CGL policies in this case only cover damage to the insured’s own work once completed (see Annotated Commercial General Liability Policy, vol. 2, at p. 22-1: “products-completed operations hazard”). In other words, the CGL policy picks up where the performance bond leaves off and provides coverage once the work is completed.
[49] “Accident” should be given the plain meaning prescribed to it in the policies and should apply when an event causes property damage neither expected nor intended by the insured. According to the definition, the accident need not be a sudden event. An accident can result from continuous or repeated exposure to conditions.
[50] In my view, the pleadings sufficiently allege an “accident”. There is no reference to intentional conduct by Progressive which would suggest that the property damage was expected or intended. The pleadings allege negligence, which, on its face, suggests that the damage was fortuitous. In addition, it is clear from the pleadings that the damage alleged is the result of “continuous or repeated exposure to conditions”, which squarely fits within the definition. If at trial it emerges that the damage was expected or intended by Progressive, then Lombard would not be required to indemnify Progressive. However, the duty to defend only requires a possibility of coverage and I am satisfied that possibility is made out in this case.
(2) Exclusions From Coverage
[51] Having found that the claims in the pleadings fall within the initial grant of coverage, the onus now shifts to Lombard to show that coverage is precluded by an exclusion clause. Because the threshold for the duty to defend is only the possibility of coverage, Lombard must show that an exclusion clearly and unambiguously excludes coverage (Nichols, at p. 808). For example, in Nichols, this Court found that an exclusion clause that stated that the policy did not apply to “any dishonest, fraudulent, criminal or malicious act or omission of an Insured” (p. 807) clearly and unambiguously precluded coverage for a claim against the insured for fraudulent conduct. Thus there was no possibility that the insurer would have to indemnify the insured on the claim as pleaded.
(a) “Work Performed” Exclusion
[52] The central exclusion in this appeal is the “work performed” exclusion. This common exclusion clause and its relationship to work completed by subcontractors have received a great deal of attention, both in Canada and the United States (Annotated Commercial General Liability Policy, vol. 2, at pp. 22-4 and 22-11). The standard form version of the “work performed” exclusion precludes coverage for damage to the insured’s own work once it is completed. However, the text of this exclusion has been modified several times during Progressive’s coverage by Lombard. There are three versions of the “work performed” exclusion in Progressive’s successive CGL policies.
[53] Lombard’s primary submissions in this appeal were with respect to the proper construction of “property damage” and “accident”. Its submissions on the work performed exclusion are very brief. It argues that the “work performed” exclusion excludes coverage for damage to the worked performed by Progressive — in this case the four housing units in their entirety. It argues there is no “subcontractor exception” in the first or second versions of the CGL policies, which could operate to bring the damage caused by subcontractors or damage to the subcontractors’ work back within coverage. Therefore, it says, the claims are clearly outside the scope of coverage and the duty to defend does not arise. The third version of the policy expressly includes a subcontractor exception, which provides coverage for damage caused by subcontractors or damage to the subcontractors’ work. Lombard argues that the pleadings do not trigger the duty to defend under the third version because they do not allege that subcontractors caused the damage. This is the full extent of Lombard’s submissions on the “work performed” exclusion.
[54] Lombard has not discharged its burden of showing that the “work performed” exclusion clearly and unambiguously applies to all of the claims made against Progressive. In my view, there is a possibility of coverage under each version of the policy.
[55] In the first version of the policy the original “work performed” exclusion was modified by what was called a General Liability Broad Form Extension Endorsement, which Progressive purchased in addition to the basic CGL policy. The original “work performed” exclusion read:
This insurance does not apply to:
. . .
(i) property damage to work performed by or on behalf of the Named Insured arising out of the work or any portion thereof, or out of materials, parts or equipment furnished in connection therewith; [Emphasis added.]
Clause (i) was replaced by clause (Z) in the Broad Form Extension Endorsement, which read:
(Z) With respect to the completed operations hazard to property damage to work performed by the Named Insured arising out of the work or any portion thereof, or out of materials, parts or equipment furnished in connection therewith. [Emphasis added.]
[56] The clause (Z) exclusion is limited to work performed by the insured. Unlike the clause that it replaced, it does not apply to work performed on behalf of the insured. The plain language is unambiguous and only excludes damage caused by Progressive to its own completed work. It does not exclude property damage:
· that is caused by the subcontractor’s work;
· to the subcontractor’s work, regardless of whether the damage is caused by the subcontractor itself, another subcontractor, or the insured.
[57] Had there been any ambiguity in the language of clause (Z), interpretive principles lead to the same result. In accordance with the rule of contra proferentem, the “work performed” exclusion should be interpreted narrowly — this favours limiting the exclusion to only damage caused by Progressive to its own work. Further, this result appears to support the reasonable expectations of the parties. In purchasing the Broad Form Extension Endorsement, Progressive would have expected to receive something different from the standard CGL form. To give clause (Z) the same meaning as the standard form clause would deprive the replacement of any meaning. Indeed, coverage for work completed by subcontractors seems to be the purpose of upgrading to the Broad Form Extension (see American Family Mutual Insurance Co. v. American Girl, Inc., 673 N.W.2d 65 (Wis. 2004), at para. 68; see also M. Audet, “Broad Form Completed Operations: An extension of coverage or a trap?” (1984), 51:10 Canadian Underwriter 36, at p. 38; Annotated Commercial General Liability Policy, vol. 2, at p. 22-11).
[58] The pleadings indicate the involvement of subcontractors (see para. 7, above), which is sufficient to trigger the duty to defend. If, at trial, it materializes that the damage was caused to a subcontractor’s work, or that a subcontractor’s work caused the damage, these claims will fall within the scope of coverage.
[59] The “work performed” exclusion takes on a different form in the second version of the CGL policies:
J. ‘Property damage’ to ‘that particular part of your work’ arising out of it or any part of it and included in the ‘products - completed operations hazard.’
“Your work” means:
a. Work or operations performed by you or on your behalf; and
b. Materials, parts or equipment furnished in connection with such work or operations.
[60] Lombard again argues that under this version of the policy there is no subcontractor exception and coverage for damage is excluded.
[61] Lombard is correct that there is no exception for subcontractors in this version of the exclusion, nor is the text limited in the same way as the Broad Form Extension Endorsement. However, this does not end the matter. On my reading of the exclusion, all that is excluded is coverage for defects.
[62] Unlike the standard form version of the “work performed” exclusion (clause (i)) reproduced above, this version expressly contemplates the division of the insured’s work into its component parts by the use of the phrase “that particular part of your work”. For example, the exclusion could read:
“Property damage” to “the window” arising out of “the window” or any part of “the window” and included in the ‘products-completed operations hazard’.
[63] This means that coverage for repairing defective components would be excluded, while coverage for resulting damage would not (see P. J. Wielinski, “CGL Coverage for Defective Workmanship: Current (and Ongoing) Issues”, paper presented at the 16th Annual Construction Law Conference, State Bar of Texas, March 7, 2003, at pp. lxi-iv and lxviii). This interpretation was not refuted by Lombard.
[64] Much like the first version of the policy, this version of the “work performed” exclusion was a specific endorsement which amended the standard version of the exclusion. The phrase “that particular part of your work” replaced the phrase “your work”. The presumption must be that this change in language represents a change in meaning. Lombard has not provided any contrary rationale for the change in language.
[65] Again, I find there is a possibility of coverage under the second version of the policy. It will have to be determined at trial which “particular parts” of the work caused the damage. Repairs to those defective parts will be excluded from coverage under this version, regardless of whether they were the result of Progressive’s own work or the work of subcontractors. If, as Lombard alleges, the buildings are wholly defective, then the exclusion will apply and Lombard will not have to indemnify Progressive. However, the pleadings allege that there was resulting damage: deterioration of the building components resulting from water ingress and infiltration. This is sufficient to trigger the duty to defend under the second version of the policy.
[66] In the third and final version of the policy, the “work performed” exclusion reads:
j. “Property damage” to that particular part of “your work” arising out of it or any part of it and included in the “products-completed operations hazard”.
This exclusion does not apply if the damaged work or the work out of which the damage arises was performed on your behalf by a subcontractor.
[67] Lombard bears the burden of showing that this exclusion does not apply to any of the claims in the pleadings. Lombard accepts that there is an express subcontractor exception in this version of the policy but argues that the pleadings do not trigger the exception.
[68] The third version of the “work performed” exclusion is simply a combination of the first and second versions. The “exclusion” portion of this clause is identical to the second version of the policy, thus it only excludes coverage for defective property. Coverage would remain for resulting damage. This version of the policy also expressly incorporates the “subcontractor exception”, which was previously implicit in the Broad Form Extension Endorsement. The subcontractor exception expands coverage again. It would allow for coverage of defective work where it is work completed by a subcontractor.
[69] As there was a possibility of coverage under both the first and second versions of the policies, there is a possibility of coverage under this version as well.
[70] I conclude that the “work performed” exclusions in each version of the policies do not clearly and unambiguously exclude the claims alleged in the pleadings. There is still a possibility of coverage; therefore, the duty to defend is triggered.
(b) Other Exclusions
[71] Finally, Lombard mentioned in passing that two other exclusions — the “contract” exclusion and “product” exclusion — may apply to remove the claims in this case from the scope of coverage. As the onus is on Lombard to show that these exclusions clearly and unambiguously apply, and it did not offer argument on these points, I am not satisfied that it has discharged its burden.
V. Conclusion
[72] I conclude that Lombard owes a duty to defend Progressive in the four actions initiated by BC Housing. Under the first version of the CGL policy, there is a possibility of coverage for damage to work completed by a subcontractor and for damage resulting from work performed by a subcontractor. Under the second version of the policy, there is a possibility of coverage for damage resulting from the particular part of the insured’s work that was defective. Under the third version of the policy, there is a possibility of coverage both for resulting damage and for any damage to work completed by a subcontractor.
[73] I would allow the appeal with costs in this Court and in the courts below.
Appeal allowed with costs.
Solicitor for the appellant: Gordon Hilliker, Belcarra, British Columbia.
Solicitors for the respondent: Branch MacMaster, Vancouver.
I am a geek, world history buff, my interests and hobbies are too numerous to mention. I'm a political junkie with a cynical view. I also love law & aviation!
Wednesday, December 15, 2010
Tuesday, December 14, 2010
can we trust Police Chief Bill Blair again?? G20.
Chris Selley, Jonathan Goldsbie and Matt Gurney debate whether Police Chief Bill Blair can regain Torontonians’ trust, and how best to hold his political masters to account.
SELLEY: Several times over the past couple of years, I’ve been amazed and heartened by the number of people who’ve abandoned their knee-jerk support for the police. And each time, something else has come along and diminished those ranks even further. Some people seem to have actually switched camps from instinctively supporting police to instinctively being skeptical of them, based in no small part on the impression, right or wrong, that on G20 weekend, police stood by and did nothing while idiots smashed windows, and then used their actions as a pretense to arrest a thousand people who hadn’t done anything. In this environment, the pressure is mounting steadily on Police Chief Bill Blair, who, for all his protestations of wanting to get to the bottom of things, doesn’t seem to really understand, and certainly doesn’t reflect, the level of anger that’s out there. So, a simple question: Should Chief Blair offer to resign? Should he be relieved of his duties? Or can he learn from this and regain the public’s trust?
GURNEY: As someone who once would have freely admitted to being a reflexive cop backer, I have to agree with Chris that this hasn’t been a good time for the police. To directly take on the issue of whether or not Blair should resign, though, I can’t say I’m convinced he should. If there is a case to be made that he should fall on his sword, I think it’s because of the deception over the extent of the five-metre law, which absolutely lands squarely in his lap, rather than the excesses of the officers under his command. There’s no reason to assume that any fewer batons would have been swung by officers under the command of Chiefs Gurney, Selley or Goldsbie. But where Blair has been failing since then has been in reacting to the PR disaster that the media, mostly in the form of Rosie DiManno, has been inflicting on the Service. Obviously the Chief needs to defend his organization, but that goes beyond simply defending it from zingers in the press. He has to defend its interests, and by not dealing with the issue of rogue officers harshly, quickly and publicly, Blair has probably set the Service up for a shellacking it could have otherwise avoided.
GOLDSBIE: In a column that Chris and I wrote on the Sunday afternoon of the G20 weekend, I quite explicitly and passionately called on Chief Bill Blair to resign or, failing that, to lose his job in disgrace. And while I still believe that either of those things would be entirely appropriate given how deeply he has lost the public’s confidence, I am increasingly reluctant to openly advocate for them. Given the significant imminent turnover of members on the Toronto Police Services Board (which is responsible for hiring and firing the Chief), there is even more uncertainty than usual regarding what type of commander his successor might be. The process of finding a new chief is likely to become excessively politicized, and I’m concerned that rhetoric (rather than sound policy, vision or strategy) may carry the day. Just because Blair was infinitely superior to his own predecessor does not mean he is excused from responsibility for what happened under his command or for his ensuing months of foot dragging. But, at this point, I am willing to concede that pushing for his resignation is not far removed from pushing our luck.
GURNEY: To that point, the main problem we’re facing, when you boil it down to the core of the issue, is whether or not the police (and their political masters) consider themselves servants of the people or their own force/party/union. If Blair loses his head right now, when the TPS is under seige, whomever replaces him (I know of no one exactly waiting in the wings that we could turn to as the default choice) is going to have to immediately go through a whole period of chest thumping and outreach to the officers under his command to establish trust with the force that he’ll end up commanding long after the current political issue passes. We’d end up with someone whose future ability to command the force would essentially hinge on his refusal to spank it and send it to bed without any dinner in the short term. I don’t really see any benefit to that. That’s hardly a ringing endorsement of Blair’s continued command, but that’s good, because I’m not out to endorse him. In the abstract, I’d probably prefer to see him gone. I just can’t imagine a way to accomplish that that improves matters, and most scenarios I can foresee would leave us worse off without him.
SELLEY: Some excellent points there. I’d add that I’ve never understood the value of these symbolic offers to resign from public figures. Surely saying “I’m sorry for [INSERT DEBACLE HERE] and pledge to do better and it’s up to my bosses whether or not I stay” is just as good. That said, much of what’s gone wrong is institutional rather than personally related to Blair’s leadership. Officers have exercised their right not to talk to the SIU. I think it’d be nice if Blair seemed angry about that … but hey, rights are rights. Same goes with his stated desire to see the wrongdoing officers punished. The punishments are, in many cases, laughable — certainly far short of what the public demands in the current environment. So Blair can advocate fixing these problems, but ultimately they’re not his to fix, and they’d remain in place no matter who took over from him. My instinct right now is to stand pat with Blair and keep up the pressure on him, and on the people who can fix these institutional shortcomings. It’s working so far, albeit slowly.
GOLDSBIE: Why does it seem like the media is the only institution that ever manages to hold the police in this city to a meaningful standard of accountability? It shouldn’t have taken consecutive days of Blair-baiting front pages for the police Chief to accept some responsibility for the conduct of his force and his own role in preserving trust in it. But then that’s often been the way that police reforms have come about in Toronto — with the media conducting investigations into troubles, both isolated and systemic, and then hammering away until there is at least some token gesture of improvement. While the press is never better than when it is doing this, surely it should not feel alone in the crusade. The G20 aftermath has made me question whether the official oversight bodies (the Police Services Board, the Special Investigations Unit, the Office of the Independent Police Review Director, and so on) have their own institutional issues that prevent them from serving as an adequate check on police power. I am encouraged by the fact that — according to the Globe — the Ontario Ombudsman is once again carrying out a comprehensive probe into the effectiveness of the SIU. And, although such a change might come with complications of its own, I would also not object to the Ombudsman’s legal jurisdiction being broadened to include the police.
SELLEY: A fine idea in principle, although another self-aggrandizing press conference from André Marin might be enough to turn public opinion back in favour of the police.
GURNEY: There’s no doubt the system of watching the watchers is broken (Thank you, Ottawa police, for making that especially clear recently). I suspect Marin is busy enough with the rest of the province to take on the added burden, though. A revamped, stronger SIU is the better bet.
GOLDSBIE: And, hey, how about a full public inquiry? Just because our elected leaders are hesitant to subject themselves to such scrutiny doesn’t mean we can’t embarrass them into it the same way we did with Chief Blair.
Read more: http://news.nationalpost.com/2010/12/12/posted-toronto-political-panel-after-g20-can-we-trust-police-chief-bill-blair-again/#ixzz183kebjNI
SELLEY: Several times over the past couple of years, I’ve been amazed and heartened by the number of people who’ve abandoned their knee-jerk support for the police. And each time, something else has come along and diminished those ranks even further. Some people seem to have actually switched camps from instinctively supporting police to instinctively being skeptical of them, based in no small part on the impression, right or wrong, that on G20 weekend, police stood by and did nothing while idiots smashed windows, and then used their actions as a pretense to arrest a thousand people who hadn’t done anything. In this environment, the pressure is mounting steadily on Police Chief Bill Blair, who, for all his protestations of wanting to get to the bottom of things, doesn’t seem to really understand, and certainly doesn’t reflect, the level of anger that’s out there. So, a simple question: Should Chief Blair offer to resign? Should he be relieved of his duties? Or can he learn from this and regain the public’s trust?
GURNEY: As someone who once would have freely admitted to being a reflexive cop backer, I have to agree with Chris that this hasn’t been a good time for the police. To directly take on the issue of whether or not Blair should resign, though, I can’t say I’m convinced he should. If there is a case to be made that he should fall on his sword, I think it’s because of the deception over the extent of the five-metre law, which absolutely lands squarely in his lap, rather than the excesses of the officers under his command. There’s no reason to assume that any fewer batons would have been swung by officers under the command of Chiefs Gurney, Selley or Goldsbie. But where Blair has been failing since then has been in reacting to the PR disaster that the media, mostly in the form of Rosie DiManno, has been inflicting on the Service. Obviously the Chief needs to defend his organization, but that goes beyond simply defending it from zingers in the press. He has to defend its interests, and by not dealing with the issue of rogue officers harshly, quickly and publicly, Blair has probably set the Service up for a shellacking it could have otherwise avoided.
GOLDSBIE: In a column that Chris and I wrote on the Sunday afternoon of the G20 weekend, I quite explicitly and passionately called on Chief Bill Blair to resign or, failing that, to lose his job in disgrace. And while I still believe that either of those things would be entirely appropriate given how deeply he has lost the public’s confidence, I am increasingly reluctant to openly advocate for them. Given the significant imminent turnover of members on the Toronto Police Services Board (which is responsible for hiring and firing the Chief), there is even more uncertainty than usual regarding what type of commander his successor might be. The process of finding a new chief is likely to become excessively politicized, and I’m concerned that rhetoric (rather than sound policy, vision or strategy) may carry the day. Just because Blair was infinitely superior to his own predecessor does not mean he is excused from responsibility for what happened under his command or for his ensuing months of foot dragging. But, at this point, I am willing to concede that pushing for his resignation is not far removed from pushing our luck.
GURNEY: To that point, the main problem we’re facing, when you boil it down to the core of the issue, is whether or not the police (and their political masters) consider themselves servants of the people or their own force/party/union. If Blair loses his head right now, when the TPS is under seige, whomever replaces him (I know of no one exactly waiting in the wings that we could turn to as the default choice) is going to have to immediately go through a whole period of chest thumping and outreach to the officers under his command to establish trust with the force that he’ll end up commanding long after the current political issue passes. We’d end up with someone whose future ability to command the force would essentially hinge on his refusal to spank it and send it to bed without any dinner in the short term. I don’t really see any benefit to that. That’s hardly a ringing endorsement of Blair’s continued command, but that’s good, because I’m not out to endorse him. In the abstract, I’d probably prefer to see him gone. I just can’t imagine a way to accomplish that that improves matters, and most scenarios I can foresee would leave us worse off without him.
SELLEY: Some excellent points there. I’d add that I’ve never understood the value of these symbolic offers to resign from public figures. Surely saying “I’m sorry for [INSERT DEBACLE HERE] and pledge to do better and it’s up to my bosses whether or not I stay” is just as good. That said, much of what’s gone wrong is institutional rather than personally related to Blair’s leadership. Officers have exercised their right not to talk to the SIU. I think it’d be nice if Blair seemed angry about that … but hey, rights are rights. Same goes with his stated desire to see the wrongdoing officers punished. The punishments are, in many cases, laughable — certainly far short of what the public demands in the current environment. So Blair can advocate fixing these problems, but ultimately they’re not his to fix, and they’d remain in place no matter who took over from him. My instinct right now is to stand pat with Blair and keep up the pressure on him, and on the people who can fix these institutional shortcomings. It’s working so far, albeit slowly.
GOLDSBIE: Why does it seem like the media is the only institution that ever manages to hold the police in this city to a meaningful standard of accountability? It shouldn’t have taken consecutive days of Blair-baiting front pages for the police Chief to accept some responsibility for the conduct of his force and his own role in preserving trust in it. But then that’s often been the way that police reforms have come about in Toronto — with the media conducting investigations into troubles, both isolated and systemic, and then hammering away until there is at least some token gesture of improvement. While the press is never better than when it is doing this, surely it should not feel alone in the crusade. The G20 aftermath has made me question whether the official oversight bodies (the Police Services Board, the Special Investigations Unit, the Office of the Independent Police Review Director, and so on) have their own institutional issues that prevent them from serving as an adequate check on police power. I am encouraged by the fact that — according to the Globe — the Ontario Ombudsman is once again carrying out a comprehensive probe into the effectiveness of the SIU. And, although such a change might come with complications of its own, I would also not object to the Ombudsman’s legal jurisdiction being broadened to include the police.
SELLEY: A fine idea in principle, although another self-aggrandizing press conference from André Marin might be enough to turn public opinion back in favour of the police.
GURNEY: There’s no doubt the system of watching the watchers is broken (Thank you, Ottawa police, for making that especially clear recently). I suspect Marin is busy enough with the rest of the province to take on the added burden, though. A revamped, stronger SIU is the better bet.
GOLDSBIE: And, hey, how about a full public inquiry? Just because our elected leaders are hesitant to subject themselves to such scrutiny doesn’t mean we can’t embarrass them into it the same way we did with Chief Blair.
Read more: http://news.nationalpost.com/2010/12/12/posted-toronto-political-panel-after-g20-can-we-trust-police-chief-bill-blair-again/#ixzz183kebjNI
Monday, December 13, 2010
After DDOS attacks and the loss of its domain name, the WikiLeaks whistleblower site is as potent as ever.
Massive network attacks and other punitive actions taken against WikiLeaks over the past few days only appear to have made the site and its contents far more resilient to takedown attempts, a security researcher said.
In the 10 days since WikiLeaks began releasing classified cables from the U.S Department of State, wikileaks.org was hit with massive denial of service attacks, the termination of its its domain hosting service, the loss of Amazon.com as a host, and the loss of PayPal, MasterCard and Visa Europe services.
Yet, in what's becoming an interesting case study in Internet resilience, WikiLeaks not only continues to serve up its controversial content, it appears to have bolstered its ability to do so, said James Cowie, chief technology officer at Renesys, an Internet monitoring firm.
Cowie has been tracking the WikiLeaks saga over the past few days and yesterday detailed the whistleblower Website's efforts to stay afloat in the face of growing adversity in a blog post.
More in Security Center Before WikiLeaks started releasing the classified State Department cables, its content was hosted by two Swedish ISPs and another based in France. WikiLeaks added Amazon.com's cloud server to the list earlier this month after it began releasing the documents, Cowie noted. Amazon quickly stopped hosting WikiLeaks, apparently over terms of service violations.
After Amazon's actions, WikiLeaks began hosting the wikileaks.org domain with two different ISPs one in France, and another in Sweden, Cowie said. Then a couple of days later, WikiLeaks' DNS provider, EveryDNS, terminated its domain name service.
In response, WikiLeaks established several new country-level domains, such as wikileaks.ch in Switzerland, wikileaks.at in Austria and wikileaks.cc in Cocos Islands. It then pointed the new domains back to existing IP addresses, or began having the new domains hosted with service providers in different countries.
The Swiss site (wikileaks.ch) itself has been heavily reinforced to avoid a repeat of what happened with EveryDNS, Cowie said. To mitigate the possibility of one DNS provider once again shutting off the domain as EveryDNS did, WikiLeaks this time has signed up with separate DNS service providers in eight different countries, including Switzerland, Canada and Malaysia.
A total of 14 different name servers across 11 different networks today provide authoritative name services for the wikileaks.ch domain, Cowie noted. "If you ask any of those 14 servers where to find wikileaks.ch, they'll point you to one of three differently routed IP blocks," in the Netherlands, Sweden and France, he added.
The geo-diversification makes it very hard to take WikiLeaks down, he said.
For the moment, the WikiLeaks content is hosted mostly on servers based in Europe. If WikiLeaks were to start hosting its content outside Europe as well, the challenge to those trying to stop the site will become even harder, Cowie said.
In addition to such moves, close to 1000 mirror sites serving up WikiLaks content have popped up around the globe over the last few days, he said.
"Within a couple days, the WikiLeaks web content has been spread across enough independent parts of the Internet's DNS and routing space that they are, for all intents and purposes, now immune to takedown by any single legal authority," Cowie wrote in his blog. "If pressure were applied, one imagines that the geographic diversity would simply double, and double again."
In an interview with Computerworld, Cowie added that even if WikiLeaks were taken down completely "bits and pieces of its content will probably be mirrored for ever," on the Internet, he said.
Just as important is the role that Google and Twitter played in making information available on WikiLeaks newly spawned sites and how to find them, he said,
"Even after the domain went away, people were Tweeting raw IP numbers" in order to let others know how to find WikiLeaks, Cowie said.
In the 10 days since WikiLeaks began releasing classified cables from the U.S Department of State, wikileaks.org was hit with massive denial of service attacks, the termination of its its domain hosting service, the loss of Amazon.com as a host, and the loss of PayPal, MasterCard and Visa Europe services.
Yet, in what's becoming an interesting case study in Internet resilience, WikiLeaks not only continues to serve up its controversial content, it appears to have bolstered its ability to do so, said James Cowie, chief technology officer at Renesys, an Internet monitoring firm.
Cowie has been tracking the WikiLeaks saga over the past few days and yesterday detailed the whistleblower Website's efforts to stay afloat in the face of growing adversity in a blog post.
More in Security Center Before WikiLeaks started releasing the classified State Department cables, its content was hosted by two Swedish ISPs and another based in France. WikiLeaks added Amazon.com's cloud server to the list earlier this month after it began releasing the documents, Cowie noted. Amazon quickly stopped hosting WikiLeaks, apparently over terms of service violations.
After Amazon's actions, WikiLeaks began hosting the wikileaks.org domain with two different ISPs one in France, and another in Sweden, Cowie said. Then a couple of days later, WikiLeaks' DNS provider, EveryDNS, terminated its domain name service.
In response, WikiLeaks established several new country-level domains, such as wikileaks.ch in Switzerland, wikileaks.at in Austria and wikileaks.cc in Cocos Islands. It then pointed the new domains back to existing IP addresses, or began having the new domains hosted with service providers in different countries.
The Swiss site (wikileaks.ch) itself has been heavily reinforced to avoid a repeat of what happened with EveryDNS, Cowie said. To mitigate the possibility of one DNS provider once again shutting off the domain as EveryDNS did, WikiLeaks this time has signed up with separate DNS service providers in eight different countries, including Switzerland, Canada and Malaysia.
A total of 14 different name servers across 11 different networks today provide authoritative name services for the wikileaks.ch domain, Cowie noted. "If you ask any of those 14 servers where to find wikileaks.ch, they'll point you to one of three differently routed IP blocks," in the Netherlands, Sweden and France, he added.
The geo-diversification makes it very hard to take WikiLeaks down, he said.
For the moment, the WikiLeaks content is hosted mostly on servers based in Europe. If WikiLeaks were to start hosting its content outside Europe as well, the challenge to those trying to stop the site will become even harder, Cowie said.
In addition to such moves, close to 1000 mirror sites serving up WikiLaks content have popped up around the globe over the last few days, he said.
"Within a couple days, the WikiLeaks web content has been spread across enough independent parts of the Internet's DNS and routing space that they are, for all intents and purposes, now immune to takedown by any single legal authority," Cowie wrote in his blog. "If pressure were applied, one imagines that the geographic diversity would simply double, and double again."
In an interview with Computerworld, Cowie added that even if WikiLeaks were taken down completely "bits and pieces of its content will probably be mirrored for ever," on the Internet, he said.
Just as important is the role that Google and Twitter played in making information available on WikiLeaks newly spawned sites and how to find them, he said,
"Even after the domain went away, people were Tweeting raw IP numbers" in order to let others know how to find WikiLeaks, Cowie said.
Sunday, December 12, 2010
Concerns over secret border deal are just : The pending deal will bind Canada more tightly to the United States on many fronts. Immigration, security and law enforcement policies
Politics can be complicated but one time-saving way to arrive at an educated opinion is to find out what the Council of Canadians thinks and to then take the diametric opposite position. If Maude Barlow thinks the "secret Canada-United States perimeter security plan" is an "outrageous attack on the rights of Canadians," it follows it must be a good thing.
Since the National Post broke the story about the imminent signing of a trade and security deal by Prime Minister Stephen Harper and President Barack Obama, the Council has been frothing at the gills about threats to Canadian sovereignty and privacy that would be created by a "zip-lock North America."
Perhaps it's the infinite monkey theorem at work -- that is, given enough time, a chimpanzee would write Hamlet. In this case, given enough issues, the Council will eventually raise a legitimate concern. On the potential border deal, they may have one. If badly crafted, it does have the potential to intrude on Canadian sovereignty, particularly in the Arctic. The Americans may seek to be more muscular in patrolling the Far North, particularly in areas of disputed sovereignty like parts of the Beaufort Sea and the Northwest Passage.
The pending deal will bind Canada more tightly to the United States on many fronts. Immigration, security and law enforcement policies will be "harmonized" -- that is, tailored to become more similar to what exists in the States. That is only desirable if the trade benefits are tangible in the form of a "thinner" border.
John Manley, the former Liberal deputy prime minister and now president of the Canadian Council of Chief Executives, is right when he points out the need to focus on our trade relationship with the United States. As he said, Canada should diversify, but its trade with India amounts to two and half days worth of trade with the United States. Linking improved access to the United States through common consumer goods regulations and pre-clearance of cross-border cargo with tighter border security, a key American concern, is a smart strategy.
Yet if this deal is not negotiated well, we may inherit the worst of all worlds -- a border that remains "thick" with security apparatus, as well as increased American presence in Canada's North.
One person familiar with the Americans' security demands said he is skeptical that the huge border infrastructure the U.S. Department of Homeland Security has built up along the 49th parallel will be slimmed down in response to any deal. He said there are also legitimate fears that the they will be unwilling to let Canada alone police the northern perimeter of the continent. "The Americans want concentric rings of security," he said.
The Prime Minister will be very aware that his legacy Arctic sovereignty project does not dovetail well with a perimeter deal. We already have an air perimeter deal under the North American Aerospace Defence Command but the New Border Vision could end up making a nonsense of our claim that we are standing on guard for Canada's Far North.
This deal has the potential to dramatically alter our relationship with the elephant with which we're obliged to sleep. Canadians should look closely at its details to judge whether the price paid is worth it.
Read more: http://www.nationalpost.com/news/canada/Concerns+over+secret+border+deal+just/3962197/story.html#ixzz17sAilQmT
Since the National Post broke the story about the imminent signing of a trade and security deal by Prime Minister Stephen Harper and President Barack Obama, the Council has been frothing at the gills about threats to Canadian sovereignty and privacy that would be created by a "zip-lock North America."
Perhaps it's the infinite monkey theorem at work -- that is, given enough time, a chimpanzee would write Hamlet. In this case, given enough issues, the Council will eventually raise a legitimate concern. On the potential border deal, they may have one. If badly crafted, it does have the potential to intrude on Canadian sovereignty, particularly in the Arctic. The Americans may seek to be more muscular in patrolling the Far North, particularly in areas of disputed sovereignty like parts of the Beaufort Sea and the Northwest Passage.
The pending deal will bind Canada more tightly to the United States on many fronts. Immigration, security and law enforcement policies will be "harmonized" -- that is, tailored to become more similar to what exists in the States. That is only desirable if the trade benefits are tangible in the form of a "thinner" border.
John Manley, the former Liberal deputy prime minister and now president of the Canadian Council of Chief Executives, is right when he points out the need to focus on our trade relationship with the United States. As he said, Canada should diversify, but its trade with India amounts to two and half days worth of trade with the United States. Linking improved access to the United States through common consumer goods regulations and pre-clearance of cross-border cargo with tighter border security, a key American concern, is a smart strategy.
Yet if this deal is not negotiated well, we may inherit the worst of all worlds -- a border that remains "thick" with security apparatus, as well as increased American presence in Canada's North.
One person familiar with the Americans' security demands said he is skeptical that the huge border infrastructure the U.S. Department of Homeland Security has built up along the 49th parallel will be slimmed down in response to any deal. He said there are also legitimate fears that the they will be unwilling to let Canada alone police the northern perimeter of the continent. "The Americans want concentric rings of security," he said.
The Prime Minister will be very aware that his legacy Arctic sovereignty project does not dovetail well with a perimeter deal. We already have an air perimeter deal under the North American Aerospace Defence Command but the New Border Vision could end up making a nonsense of our claim that we are standing on guard for Canada's Far North.
This deal has the potential to dramatically alter our relationship with the elephant with which we're obliged to sleep. Canadians should look closely at its details to judge whether the price paid is worth it.
Read more: http://www.nationalpost.com/news/canada/Concerns+over+secret+border+deal+just/3962197/story.html#ixzz17sAilQmT
Labels:
Canada,
Conservative Party of Canada,
news,
people,
US GOV
Saturday, December 11, 2010
Talk of security perimeter hits nerve.: this is not going to go well at all!
Talk of security perimeter hits nerve
. Documents indicate the U.S. and Canada will sign a deal in January to 'pursue a perimeter approach to security.'
The secret government documents had barely leaked into the media this week before the political howling started over the latest plan to fix what ails an increasingly clogged Canada-U.S. border.
The documents describe a plan to improve the flow of people and goods across the border between the two countries by creating a continental security perimeter around them.
Even in the fear-filled days following the 9/11 terrorist attacks, the words "security perimeter" touched off ferocious political debate in this country.
In fact, accusations that Canada was ceding sovereignty to Uncle Sam sent the Liberal government of the day into full and hasty retreat from the whole concept.
Nine years later, with the Conservatives in power, the mention of continental security still hits a political nerve as hyper-nationalists and opposition parties pounded Prime Minister Stephen Harper's government this week over the leaked documents.
Details scarce
So far, it is all much ado about not much detail.
According to one of the documents, Prime Minister Harper and U.S. President Barack Obama will sign a deal in January "to pursue a perimeter approach to security, working together within, at, and away from the borders of our two countries."
Prime Minister Harper is working with U.S. President Barack Obama on a perimeter deal.
A draft declaration by the two leaders states: "We intend to address threats at the earliest point possible, including outside the perimeter of our two countries."
But there is little in the documents to suggest the two countries are anywhere close to figuring out exactly how they will lighten security at the border by increasing it around the perimeter of the continent.
While the draft declaration of the two leaders is filled with the best of intentions, that is all they are — intentions.
For example: "We intend to work together in co-operation and partnership to develop, implement, manage, and monitor security initiatives, standards and practices to fulfil our vision."
"We intend to pursue creative and effective solutions to manage the flow of traffic between Canada and the United States."
And so on.
Some of the proposed initiatives are common sense.
The plan, for instance, talks about investing in modern technology and infrastructure at international cargo ports.
The two countries would also like to expand existing "trusted traveler programs" that provide express passes for those who frequently cross the border and are willing to submit to special up-front security checks.
The scheme contemplates "shared border infrastructure where appropriate" that would allow, say, American Customs clearance of cargo arriving in Canada bound for the U.S., to avoid having to clear it a second time at the American border.
All of which has been in the works for years, and even the most vociferous critics would be hard-pressed to argue any of it is ceding Canada's sovereignty to the Americans.
Security sharing of concern
But the plan does include proposals that the Canadian government concedes are likely to touch off public controversy — and with good reason.
One highly classified government document obtained by CBC's Rosemary Barton describes various political and communications issues connected with the perimeter security plan. It warns the "safeguarding of privacy and sovereignty will be of concern to Canadians."
No kidding. Security information-sharing with the Americans has had a bad name since U.S. agents used erroneous RCMP data to grab Canadian engineer Maher Arar as a suspected terrorist and shipped him off to Syria for a year of torture.
The government documents leaked this week also caution that the perimeter security proposals would likely invoke the wrath of refugee and immigration agencies claiming the plan would "somehow limit immigration."
That might help to explain why there is no mention of immigration anywhere else in the documents, even though it is one aspect of Canadian security that the Americans would probably most like to change.
Since 2001, Canada has been battling the false image of being overrun with potentially dangerous refugees without security checks, and generally a terrorist haven from which the 9/11 attacks were launched.
It doesn't help that two of the many prominent Americans who have propagated the myth of Canada as a home to terrorists are the current U.S. Secretary of State, Hillary Clinton, and her cabinet colleague, Homeland Security Secretary Janet Napolitano.
It also doesn't help that some of the U.S. concerns are legitimate.
Refugee program fraught with problems
Canada's refugee program has long been fraught with security problems, such as the government's losing track of more than 35,000 failed claimants ordered deported, and who have simply disappeared.
On the other hand, the U.S. has an even larger problem identifying 10.6 million illegal immigrants currently living in America.
At the end of the day, the proposed plan for a fortress North America is probably more about bringing some political urgency to growing border problems than it is a radical way to solve them.
The last major border program, called the Security and Prosperity Partnership, was launched in 2005 by the respective governments of Paul Martin and George W. Bush, and is now all but dead.
The leaked documents suggest Harper and Obama would like to launch their own version of a border plan, even if it is actually just more of what is already happening.
Clearly, with more than $1 billion a day in bilateral trade just across the Windsor-Detroit bridge alone, the two leaders know neither country can afford to do nothing.
Read more: http://www.cbc.ca/politics/story/2010/12/10/f-weston-security-perimeter.html#ixzz17mQMtL2j
. Documents indicate the U.S. and Canada will sign a deal in January to 'pursue a perimeter approach to security.'
The secret government documents had barely leaked into the media this week before the political howling started over the latest plan to fix what ails an increasingly clogged Canada-U.S. border.
The documents describe a plan to improve the flow of people and goods across the border between the two countries by creating a continental security perimeter around them.
Even in the fear-filled days following the 9/11 terrorist attacks, the words "security perimeter" touched off ferocious political debate in this country.
In fact, accusations that Canada was ceding sovereignty to Uncle Sam sent the Liberal government of the day into full and hasty retreat from the whole concept.
Nine years later, with the Conservatives in power, the mention of continental security still hits a political nerve as hyper-nationalists and opposition parties pounded Prime Minister Stephen Harper's government this week over the leaked documents.
Details scarce
So far, it is all much ado about not much detail.
According to one of the documents, Prime Minister Harper and U.S. President Barack Obama will sign a deal in January "to pursue a perimeter approach to security, working together within, at, and away from the borders of our two countries."
Prime Minister Harper is working with U.S. President Barack Obama on a perimeter deal.
A draft declaration by the two leaders states: "We intend to address threats at the earliest point possible, including outside the perimeter of our two countries."
But there is little in the documents to suggest the two countries are anywhere close to figuring out exactly how they will lighten security at the border by increasing it around the perimeter of the continent.
While the draft declaration of the two leaders is filled with the best of intentions, that is all they are — intentions.
For example: "We intend to work together in co-operation and partnership to develop, implement, manage, and monitor security initiatives, standards and practices to fulfil our vision."
"We intend to pursue creative and effective solutions to manage the flow of traffic between Canada and the United States."
And so on.
Some of the proposed initiatives are common sense.
The plan, for instance, talks about investing in modern technology and infrastructure at international cargo ports.
The two countries would also like to expand existing "trusted traveler programs" that provide express passes for those who frequently cross the border and are willing to submit to special up-front security checks.
The scheme contemplates "shared border infrastructure where appropriate" that would allow, say, American Customs clearance of cargo arriving in Canada bound for the U.S., to avoid having to clear it a second time at the American border.
All of which has been in the works for years, and even the most vociferous critics would be hard-pressed to argue any of it is ceding Canada's sovereignty to the Americans.
Security sharing of concern
But the plan does include proposals that the Canadian government concedes are likely to touch off public controversy — and with good reason.
One highly classified government document obtained by CBC's Rosemary Barton describes various political and communications issues connected with the perimeter security plan. It warns the "safeguarding of privacy and sovereignty will be of concern to Canadians."
No kidding. Security information-sharing with the Americans has had a bad name since U.S. agents used erroneous RCMP data to grab Canadian engineer Maher Arar as a suspected terrorist and shipped him off to Syria for a year of torture.
The government documents leaked this week also caution that the perimeter security proposals would likely invoke the wrath of refugee and immigration agencies claiming the plan would "somehow limit immigration."
That might help to explain why there is no mention of immigration anywhere else in the documents, even though it is one aspect of Canadian security that the Americans would probably most like to change.
Since 2001, Canada has been battling the false image of being overrun with potentially dangerous refugees without security checks, and generally a terrorist haven from which the 9/11 attacks were launched.
It doesn't help that two of the many prominent Americans who have propagated the myth of Canada as a home to terrorists are the current U.S. Secretary of State, Hillary Clinton, and her cabinet colleague, Homeland Security Secretary Janet Napolitano.
It also doesn't help that some of the U.S. concerns are legitimate.
Refugee program fraught with problems
Canada's refugee program has long been fraught with security problems, such as the government's losing track of more than 35,000 failed claimants ordered deported, and who have simply disappeared.
On the other hand, the U.S. has an even larger problem identifying 10.6 million illegal immigrants currently living in America.
At the end of the day, the proposed plan for a fortress North America is probably more about bringing some political urgency to growing border problems than it is a radical way to solve them.
The last major border program, called the Security and Prosperity Partnership, was launched in 2005 by the respective governments of Paul Martin and George W. Bush, and is now all but dead.
The leaked documents suggest Harper and Obama would like to launch their own version of a border plan, even if it is actually just more of what is already happening.
Clearly, with more than $1 billion a day in bilateral trade just across the Windsor-Detroit bridge alone, the two leaders know neither country can afford to do nothing.
Read more: http://www.cbc.ca/politics/story/2010/12/10/f-weston-security-perimeter.html#ixzz17mQMtL2j
Friday, December 10, 2010
Canada’s embattled spy service won three key court rulings Thursday, all centred on a single terrorism suspect: Mohamed Harkat,
Canada’s embattled spy service won three key court rulings Thursday, all centred on a single terrorism suspect: Mohamed Harkat, said a Federal Court judge, is a probable terrorist sleeper agent, one who needs to be banished for the greater good.
The rulings by Mr. Justice Simon Noel amount to a rare and unequivocal victory for the Canadian Security Intelligence Service, which has suffered many legal setbacks of late. A battery of top defence lawyers had failed to impugn CSIS – a fact made all the more significant given that some of Mr. Harket’s counsel had scrutinized highly secret “human source reports” whose release to outsiders would have been unthinkable not very long ago.
Harkat a threat: judge The judge’s rulings could have big implications for Canada’s so-called security-certificate law, a polarizing power that allows federal ministers to jail and deport foreigners on the basis of secret CSIS intelligence.
The rulings uphold three points. First, the security certificate alleging Mr. Harkat is a terrorist threat is reasonable. Second, CSIS’s investigative missteps – and there were some – do not constitute “abuses” significant enough to fundamentally undermine the Harkat case. Third, the government’s security-certificate power remains consistent with Canada’s Charter of Rights and Freedoms.
The federal government hasn’t used the power to launch any new terrorism cases since 2003, when debates about the rights of five Muslim detainees arrested in that era began prompting politicians and judges to blow up Canada’s security-certificate system and rebuild it. The government lost two cases last year; three remain active, including Mr. Harkat’s.
Will Canada now see the return of the law from the crypt to which it’s apparently been relegated? Security certificates remain an “an important piece of kit in the armoury,” said Reid Morden, a former CSIS director. He expressed guarded optimism that Judge Noel’s rulings might “provide quite a bit of comfort to ministers who want to sign off on it.”
University of Toronto law professor Kent Roach disagreed. “Does this mean more security certificates are going to be granted? I would think not,” he said. The cases, he explained, are multimillion-dollar marathons fraught with problems. “CSIS may have won this battle, but are they losing the larger war? This is kind of a war of attrition.”
The Harkat case was launched with his arrest in 2002. Today he lives under a form of house arrest, proclaiming his innocence.
But Judge Noel found that the 42-year-old Algerian refugee claimant is a demonstrable liar – and one who was likely sent to Canada 15 years ago to plan or fund terrorism.
The rulings suggest Mr. Harkat, an ostensible pizza delivery driver, got distracted from his mission by a gambling habit that cost him at least $100,000. Still, CSIS fingered him for having a past life in Islamist extremism he never owned up to. The rulings endorse the CSIS contention that he was affiliated with North African terrorist groups, prior to heading to Pakistan and Afghanistan to fraternize with members of Osama bin Laden’s network.
Judge Noel says Mr. Harkat met and phoned fellow veterans of Islamist guerrilla campaigns after coming to Canada. The most significant association is his relationship with Abu Zubaydah, a Palestinian detainee held in Guantanamo Bay, and the man now known to have been only one of three al-Qaeda suspects ever water-boarded – 83 times – by the U.S. Central Intelligence Agency.
Now, Mr. Harkat faces possible deportation to his homeland, but more hearings are to delve into that debate. Given that Canadian courts are reluctant to send such suspects to countries that torture prisoners, it’s more likely he’ll be subjected to low-level monitoring in Canada for the foreseeable future.
Mr. Harkat’s lawyers plan to appeal the new rulings.
The rulings by Mr. Justice Simon Noel amount to a rare and unequivocal victory for the Canadian Security Intelligence Service, which has suffered many legal setbacks of late. A battery of top defence lawyers had failed to impugn CSIS – a fact made all the more significant given that some of Mr. Harket’s counsel had scrutinized highly secret “human source reports” whose release to outsiders would have been unthinkable not very long ago.
Harkat a threat: judge The judge’s rulings could have big implications for Canada’s so-called security-certificate law, a polarizing power that allows federal ministers to jail and deport foreigners on the basis of secret CSIS intelligence.
The rulings uphold three points. First, the security certificate alleging Mr. Harkat is a terrorist threat is reasonable. Second, CSIS’s investigative missteps – and there were some – do not constitute “abuses” significant enough to fundamentally undermine the Harkat case. Third, the government’s security-certificate power remains consistent with Canada’s Charter of Rights and Freedoms.
The federal government hasn’t used the power to launch any new terrorism cases since 2003, when debates about the rights of five Muslim detainees arrested in that era began prompting politicians and judges to blow up Canada’s security-certificate system and rebuild it. The government lost two cases last year; three remain active, including Mr. Harkat’s.
Will Canada now see the return of the law from the crypt to which it’s apparently been relegated? Security certificates remain an “an important piece of kit in the armoury,” said Reid Morden, a former CSIS director. He expressed guarded optimism that Judge Noel’s rulings might “provide quite a bit of comfort to ministers who want to sign off on it.”
University of Toronto law professor Kent Roach disagreed. “Does this mean more security certificates are going to be granted? I would think not,” he said. The cases, he explained, are multimillion-dollar marathons fraught with problems. “CSIS may have won this battle, but are they losing the larger war? This is kind of a war of attrition.”
The Harkat case was launched with his arrest in 2002. Today he lives under a form of house arrest, proclaiming his innocence.
But Judge Noel found that the 42-year-old Algerian refugee claimant is a demonstrable liar – and one who was likely sent to Canada 15 years ago to plan or fund terrorism.
The rulings suggest Mr. Harkat, an ostensible pizza delivery driver, got distracted from his mission by a gambling habit that cost him at least $100,000. Still, CSIS fingered him for having a past life in Islamist extremism he never owned up to. The rulings endorse the CSIS contention that he was affiliated with North African terrorist groups, prior to heading to Pakistan and Afghanistan to fraternize with members of Osama bin Laden’s network.
Judge Noel says Mr. Harkat met and phoned fellow veterans of Islamist guerrilla campaigns after coming to Canada. The most significant association is his relationship with Abu Zubaydah, a Palestinian detainee held in Guantanamo Bay, and the man now known to have been only one of three al-Qaeda suspects ever water-boarded – 83 times – by the U.S. Central Intelligence Agency.
Now, Mr. Harkat faces possible deportation to his homeland, but more hearings are to delve into that debate. Given that Canadian courts are reluctant to send such suspects to countries that torture prisoners, it’s more likely he’ll be subjected to low-level monitoring in Canada for the foreseeable future.
Mr. Harkat’s lawyers plan to appeal the new rulings.
Thursday, December 9, 2010
Sweden stopped CIA 'terror flights': Planes chartered by the United States to transport terror suspects across Europe made stops in Sweden as late as 2006, the Svenska Dagbladet (SvD) newspaper reports.
Suspicions that the United States was transporting terror suspects via Sweden on clandestine flights resulted in a diplomatic crisis, according to documents released by WikiLeaks
Planes chartered by the United States to transport terror suspects across Europe made stops in Sweden as late as 2006, the Svenska Dagbladet (SvD) newspaper reports.
When the Swedish government requested information clarifying the purpose of the flights, a minor diplomatic crisis erupted and stopovers in Sweden by US government chartered planes carrying prisoners from the war on terror stopped soon thereafter.
Secret US diplomatic cables published by WikiLeaks reveal that two planes carrying terror suspects landed at Stockholm’s Arlanda airport in 2006, one in February and one in April.
According to SvD, the cables are the first public confirmation that both flights had prisoners on board.
The United States’ chargé d'affaires in Stockholm at the time, Stephen V. Noble, wrote in a cable to Washington that the government of Sweden, led at the time by Social Democratic prime minister Göran Persson, had concerns over reports that planes flown by the United States’ CIA intelligence service had been landing at airports throughout Europe.
According to the cable, the Swedish government was bothered by the fact that the plane which had landed in February had been registered as a private plane when in fact it had been chartered by the US government.
Noble describes how, a few days ahead of the scheduled landing of a US plane in April, a high ranking US diplomat was called to the Swedish foreign ministry and made to answer a series of questions about the CIA plane and its mission.
The Persson-government made it clear that it wanted to know if the United States was transporting prisoners and indicated that future flights would be given closer scrutiny.
Confirmation that the planes were transporting prisoners came in April 2006 after a daring “surveillance operation” was ordered by Swedish security service Säpo and carried out without the knowledge of the Americans.
On Säpo’s orders, Swedish military intelligence agents dressed up as airport service personnel and boarded the plane. The agents reported back that the plane was carrying prisoners.
In April 2009, the Expressen newspaper first reported that Swedish intelligence agents had spied on a CIA plane at Arlanda and found it filled with chained prisoners clad with black hoods and unable to move.
A spokesperson for Säpo confirmed for SvD that the agency had carried out a surveillance operation at Arlanda airport in April 2006 on a US government plane suspected of carrying terror suspects, but refused to elaborate on what the operation revealed.
Based on the evidence reviewed by SvD, no more secret American prisoner transports have landed in Sweden since 2006.
Subscribe to:
Posts (Atom)