Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse

Report 393

Associated Incidents

Incident 2830 Report
2010 Market Flash Crash

Loading...
Why the Cause of the 2010 Stock Market Flash Crash Really Matters
nautil.us · 2015

At about 2:30pm on May 6, 2010, an asset management firm began executing a series of orders on the Chicago Mercantile Exchange. Located in Overland Park, Kansas, Waddell & Reed was (and is) one of the oldest mutual fund companies in America. It followed a strategy based on fundamental analysis—Wall Street code for old-fashioned investing. That afternoon, it wanted to sell 75,000 futures contracts on the S&P 500, a major market index, before the market closed at 4 p.m. The order was large but basically unremarkable, and Waddell & Reed had been executing similar trades for decades.

But this time something was different. Within 20 minutes of Waddell & Reed’s initial order, S&P 500 futures had declined 5 percent, and individual equity prices began to oscillate wildly. The price of the consulting firm Accenture declined from roughly $30 to $0.01 in seven seconds. Consumer goods giant Procter and Gamble dropped from around $60 to $39. Shares of Apple tumbled 20 percent from their pre-crash price of approximately $250, and also traded at nearly $100,000 per share (trades which were later annulled by the exchange). The dramatic futures move and the massive and sudden dislocation in the equities markets on that day came to be known as the Flash Crash.

How did the Flash Crash happen? The Securities and Exchange Commission (SEC) and the Commodity Futures Trading Commission (CFTC) arrived at one explanation in their official joint report, published in September of 2010. According to the report, many of the firms that bought the initial batch of futures from Waddell & Reed used automated trading software. Each purchase introduced additional market exposure and risk, prompting these trading programs to hedge their own risk by selling these same futures. Other automated traders took the other side of these trades, then also sought to offload their risk in the market. Each trade that Waddell & Reed made therefore caused multiple trades in response. In addition, Waddell & Reed had instructed their own trading program to trade no more than 9 percent of the total volume of the futures contracts traded at any given time, so that their algorithm didn’t trade too aggressively. But the algorithm wasn’t given any restrictions on price, or the time it should take to finish its order. It began to ramp up its own volumes exponentially in response to the activity that it itself had initiated, all the while maintaining its 9 percent volume cap. As the firms buying from Waddell & Reed accumulated risk, they began to require more incentive to continue buying futures. Prices began to fall. And since the different firms that were trading with Waddell & Reed’s orders also were generally using similar algorithms, their behavior became strongly correlated, pushing the markets in the same direction: down.

TIMOTHY A. CLARY/AFP/Getty Images

But then, almost as quickly as it had started, the crisis resolved itself. During the next few minutes, following an automatically triggered pause in futures trading, firms began to see the depressed market as a buying opportunity. Trading systems were reactivated and liquidity was restored. The market recovered to almost to its pre-crash level.

Some commentators remain skeptical of the SEC-CFTC’s official explanation. For example, the Chicago Mercantile Exchange, where the trades were executed, argued that a trade of the sort that Waddell & Reed had executed was too small, or too common, to explain such an extreme and unusual event. Firms like Waddell & Reed may make dozens, even hundreds, of similar trades without a hitch every year. Then just this past Tuesday, on April 21, a United Kingdom-based futures trader called Navinder Singh Sarao was arrested on wire fraud and market manipulation charges. He stands accused of placing large sell orders in S&P 500 futures without ever intending to have those orders fulfilled. Instead, regulators and prosecutors allege, his orders were intended to trick the market by increasing sell pressure on the futures. Regulators allege that the trick worked, making Sarao millions of dollars in profit. Furthermore, regulators have taken pains to emphasize that he employed this strategy on the day of the Flash Crash. His activity caused a sudden loss of liquidity and “directly contributed to the ... price crash,” according to the CFTC’s complaint.

Also in Economics Drowning in Light By Dirk Hanson In 1996, Yale economist William D. Nordhaus calculated that the average citizen of Babylon would have had to work a total of 41 hours to buy enough lamp oil to equal a 75-watt light bulb burning for one hour. At...READ MORE

Like a nuclear power plant, modern markets are both interactively complex and tightly coupled.

So which explanation captures the dynamics that led to the crash? Could an ordinary order in the futures market or a lone market manipulator really cause the crash? The simple answer is that this is the wrong question to ask. From the perspective of the joint report and the

Read the Source

Research

  • Defining an “AI Incident”
  • Defining an “AI Incident Response”
  • Database Roadmap
  • Related Work
  • Download Complete Database

Project and Community

  • About
  • Contact and Follow
  • Apps and Summaries
  • Editor’s Guide

Incidents

  • All Incidents in List Form
  • Flagged Incidents
  • Submission Queue
  • Classifications View
  • Taxonomies

2024 - AI Incident Database

  • Terms of use
  • Privacy Policy
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • e1b50cd