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

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

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

noted that plaintiffs’ aiding and abetting claims founded in fraud must also plead the elements of<br />

aiding and abetting with particularity. The court dismissed the aiding and abetting fraud claim as<br />

plaintiffs failed to plead facts reflecting defendant’s actual knowledge of the fraud. The fact that<br />

defendant managed and monitored the companies’ accounts was not enough. The court rejected<br />

plaintiffs’ contention that defendant knew of the alleged fraud based on “know your customer”<br />

rules and other various stock exchange rules and monitoring requirements, as these rules spoke<br />

only to whether defendant should have known of the fraud, they did not reflect actual<br />

knowledge. Plaintiffs’ aiding and abetting breach of fiduciary duty claim was likewise dismissed<br />

as plaintiffs did not sufficiently allege defendant was aware of the companies’ fraudulent<br />

conduct, and asserted no additional facts indicating how defendant knew of the breach of<br />

fiduciary duty. Plaintiffs’ claims for aiding and abetting conversion, premised on fraud, failed to<br />

plead knowledge of fraud with sufficient particularity; thus, the aiding and abetting conversion<br />

claim failed. Further, the court noted that even if it were to assume that a conversion<br />

independent of the fraud was alleged, plaintiffs had not provided facts to support a reasonable<br />

inference that defendant knew of any underlying conversion. The court granted defendant’s<br />

motion to dismiss the complaint and denied leave to amend as plaintiffs had already been<br />

afforded an opportunity to amend and failed to set forth any additional facts indicating how the<br />

pleading deficiencies would be cured.<br />

SEC v. Aragon Capital Advisors, LLC, 2011 WL 3278907 (S.D.N.Y. July 26, 2011).<br />

The Securities and Exchange Commission brought an action against defendants, a father<br />

and his two sons, allegedly engaged in an insider trading scheme. The SEC alleged that the<br />

father, an employee of a publicly-traded pharmaceutical company, opened a brokerage account<br />

in the names of his sons, and traded the pharmaceutical company’s securities in these accounts<br />

while he possessed non-public, material information about the company. The SEC further<br />

alleged that the sons knew about the trading; however, they did not take any steps to stop the<br />

illegal use of their accounts. The SEC charged the sons with violating Section 20(e) of the<br />

Securities Exchange Act of 1934 by aiding and abetting their father’s trades in the accounts held<br />

under their names. Defendants filed a motion to dismiss. In order to make out a prima facie<br />

case for aiding and abetting, the SEC must prove: (1) the existence of a securities law violation<br />

by the primary party; (2) knowledge of this violation on the part of the aider and abettor; and<br />

(3) substantial assistance by the aider and abettor in the achievement of the primary violation.<br />

To properly allege “substantial assistance,” the complaint must contain allegations that the aider<br />

and abettor’s conduct was a substantial causal factor in the perpetuation of the underlying<br />

violation. In denying the defendants’ motion to dismiss, the court held that the SEC’s allegation<br />

that the sons did not take any action to prevent the insider trading in their named accounts was<br />

sufficient “substantial assistance” because it was at a minimum “plausible” that the sons’<br />

inaction was designed intentionally to aid the father’s primary violations of the securities laws.<br />

H.3<br />

272

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

Saved successfully!

Ooh no, something went wrong!