04.01.2014 Views

Broker-Dealer Litigation - Greenberg Traurig LLP

Broker-Dealer Litigation - Greenberg Traurig LLP

Broker-Dealer Litigation - Greenberg Traurig LLP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

subject to protection under the Private Securities <strong>Litigation</strong> Reform Act of 1995’s safe harbor.<br />

The court found that most of the alleged misstatements related to objectively verifiable facts and,<br />

thus, were not forward-looking statements eligible for safe harbor protection. In addition, the<br />

court found that plaintiffs adequately alleged that defendants knew the forward-looking<br />

statements were false when they were made and, thus, even the forward-looking statements were<br />

not protected by the safe harbor. Accordingly, the court denied defendants’ motion to dismiss.<br />

Plumbers and Pipefitters Local Union No. 630 Pension-Annuity Trust Fund v. Allscripts-Misys<br />

Healthcare Solutions, Inc., 778 F. Supp. 2d 858 (N.D. Ill. 2011).<br />

In a putative securities fraud class action, the district court granted defendants’ motion to<br />

dismiss claims related to allegedly false and misleading financial forecasts and statements<br />

regarding implementation of new software developed by the defendant company. Defendants<br />

argued that statements related to these issues were forward-looking and accompanied by<br />

meaningful cautionary language which shielded them from liability under the Private Securities<br />

<strong>Litigation</strong> Reform Act of 1995’s safe harbor provisions. Plaintiffs argued that defendants’<br />

cautionary language was not meaningful because it was not specific enough and defendants’<br />

allegedly knew that the risks they were warning about were actually occurring. The court<br />

rejected the former argument because cautionary language in the defendant company’s<br />

regulatory filings which was incorporated by reference into the statements at issue discussed at<br />

length twenty-five separate business-specific risk factors, including the very risks plaintiffs<br />

alleged had caused the company’s underperformance. The court rejected the latter argument<br />

because it found that defendants’ state of mind was irrelevant to whether forward-looking<br />

statements qualify for protection under the first prong of the safe harbor. Accordingly, the court<br />

found that safe harbor protection was warranted and granted defendants’ motion to dismiss.<br />

St. Lucie Cty. Fire Dist. Fire-Fighters’ Pension Trust Fund v. Motorola, Inc., 2011 WL 814932<br />

(N.D. Ill. Feb. 28, 2011).<br />

In a putative securities fraud class action, the district court granted defendants’ motion to<br />

dismiss claims related to allegedly false and misleading earnings per share forecasts.<br />

Specifically, plaintiffs alleged that defendants engaged in “channel stuffing” and made various<br />

false and misleading statements regarding the company’s financial performance as a result.<br />

Defendants argued that its earnings per share forecasts were accurate and, even if they were not<br />

accurate, then they were forward-looking statements shielded from liability by the Private<br />

Securities <strong>Litigation</strong> Reform Act of 1995’s safe harbor provisions. The court first noted that<br />

defendants’ forecasts appeared to be accurate once special charges that were specifically<br />

excluded from the forecasts were considered. Next, to the extent that the projections were false<br />

because they did not include the special charges, the court found that cautionary language cited<br />

by defendants rendered the projections inactionable under the safe harbor because the warnings<br />

addressed plaintiffs’ particular allegations in individualized terms. Accordingly, the court<br />

granted defendants’ motion to dismiss.<br />

D.3<br />

D.3<br />

200

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

Saved successfully!

Ooh no, something went wrong!