17.03.2013 Views

JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES

JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES

JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

81<br />

Drew he wanted to wait until the indices were more liquid to add to the portfolio, but by month<br />

end he had to “cover the short.” 514 Mr. Iksil later explained that, in February, he “added to IG9<br />

and S9 forwards in order to contain the P&L loss” and to “cover” the high yield short position. 515<br />

Mr. Iksil said that he had not expected to sell as much protection as he did, but that one hedge<br />

fund was “buying protection outright.” 516<br />

Mr. Macris later said that all of the trades and losses<br />

were “well-communicated” to CIO management, meaning that his supervisors were fully<br />

informed about the status of the SCP book.<br />

When asked about the February trading activity, the OCC told the Subcommittee that the<br />

CIO traders apparently believed that the prices in the markets were wrong, and that the traders<br />

had a strategy to defend their positions and keep the prices from falling by taking on more of<br />

517<br />

them.<br />

(3) March 2012<br />

In March, the CIO traders purchased still more long positions, enlarged the SCP further,<br />

and by the end of the month had moved the SCP firmly into a net long posture. Their actions not<br />

only increased the portfolio’s risk, breaching multiple risk limits along the way, but also<br />

escalated the SCP’s losses which, by the end of the month, exceeded half a billion dollars.<br />

On March 1, Mr. Macris expressed concern about having to reduce the SCP book to<br />

comply with management’s direction to reduce the portfolio’s RWA, writing:<br />

“I am worried that the $20b RWA committed b[y] year-end, is too aggressive, if<br />

we need to [a]ctually reduce the book, we will not able to defend our<br />

positions.” 518<br />

Mr. Macris later told the JPMorgan Chase Task Force investigation that, in the first part of<br />

March, the credit market was “unusually bullish,” and as it continued to rally, the SCP book<br />

519<br />

continued to “underperform.” In fact, the portfolio was not just underperforming; it was<br />

losing substantial value. In response, throughout the month, the traders continued to increase the<br />

size of the long positions in an apparent attempt to staunch the losses.<br />

By mid-March, according to Mr. Macris, there were meetings every other day to discuss<br />

520<br />

the book. According to Mr. Martin-Artajo, the protection the traders bought continued to lose<br />

money relative to the protection the traders sold. 521<br />

Mr. Iksil expressed concern about the size of<br />

514<br />

JPMorgan Chase Task Force interview of Bruno Iksil, CIO (partial readout to Subcommittee on 8/27/2012).<br />

515<br />

3/29/2012 email from Bruno Iksil to Javier Martin-Artajo and others, “First draft of the presentation,” conveying<br />

“CIO Synthetic Credit Update,” (3/2012), JPM-CIO-PSI 0001257.<br />

516<br />

JPMorgan Chase Task Force interview of Bruno Iksil, CIO (partial readout to Subcommittee on 8/27/2012)<br />

(referring to Boaz Weinstein of Saba Capital Management).<br />

517<br />

Subcommittee interview of Scott Waterhouse, OCC (9/17/2012). See also 2013 JPMorgan Chase Task Force<br />

Report, at 39.<br />

518<br />

3/1/2012 email from Achilles Macris, CIO, to Javier Martin-Artajo, CIO, “priorities,” JPM-CIO-PSI 0001219.<br />

519<br />

JPMorgan Chase Task Force interview of Achilles Macris, CIO (partial readout to Subcommittee on 8/28/2012).<br />

520<br />

Id.<br />

521<br />

See undated internal document authored by Bruno Iksil, CIO, with his personal notes and comments on SCP<br />

trading activities from January to March 2012, JPM-CIO-PSI 00021898.

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

Saved successfully!

Ooh no, something went wrong!