SAN JOSE - Anthony Scott Levandowski submitted documents today requesting that the court accept his plea of guilty to theft of trade secrets charges, announced United States Attorney David L. Anderson and Federal Bureau of Investigation Special Agent in Charge John F. Bennett. The documents include a request to William H. Alsup, United States District Judge, to accept a proposed plea agreement and a request to schedule a date for a sentencing hearing.
Levandowski, 39, of Marin County, worked in Google’s self-driving car program for approximately seven years. According to the proposed plea agreement, Levandowski acknowledged that during this time, he was aware his employment agreement required that he keep Google’s valuable non-public information confidential. He also knew that the non-public information related to Project Chauffeur was sensitive and subject to the confidentiality requirement. Nevertheless, while Levandowski was considering leaving Google, and prior to his departure in 2016, he obtained and stored thousands of confidential files with the intent to use them for his personal benefit after his departure from the company. Specifically, on December 11, 2015, Levandowski downloaded approximately 14,000 files from an internal, password-protected Google server known as “SVN,” which was hosted on Google’s network. Then, on or about December 14, 2015, he transferred those SVN files from his Google-issued laptop to his personal laptop. In addition, prior to his departure from Google, he downloaded a variety of files from a corporate Google Drive repository to his personal laptop.
Within months after Levandowski’s departure from Google, he created a new company that was then purchased by Uber. Levandowski admitted that while he was working for Google, he downloaded at least 20 files from Google Drive. Among the files downloaded between October 2015 and January 2016, was an internal tracking document entitled “Chauffeur TL weekly updates – Q4 2015.” The update contained a variety of details regarding the status of Google’s self-driving car program. Levandowski admitted he downloaded the file with the intent to use it for the benefit of himself and Uber and that he accessed the document after his resignation from Google. Levandowski acknowledged that the document qualified as a trade secret. In sum, Levandowski admitted a reasonable estimate of the loss attributed to his conduct is up to $1,500,000.
A federal grand jury indicted Lewandowski on August 15, 2019, charging him with 33 counts of theft and attempted theft of trade secrets, in violation of 18 U.S.C. § 1832. If the court accepts the plea agreement, Levandowski will plead guilty to one count and the Court will dismiss the remaining counts at sentencing.
Should the court accept his plea, Levandowski will face a maximum sentence of 10 years in prison and a fine of $250,000, plus restitution. However, any sentence following conviction would be imposed by the court after consideration of the U.S. Sentencing Guidelines and the federal statute governing the imposition of a sentence, 18 U.S.C. § 3553.
The prosecution is being handled by the Office of the U.S. Attorney, Northern District of California’s Corporate Fraud Strike Force and is the result of an investigation by the FBI.
SAN JOSE - A federal grand jury in San Jose has indicted Anthony Scott Levandowski on theft of trade secrets charges, announced United States Attorney David L. Anderson and Federal Bureau of Investigation Special Agent in Charge John F. Bennett.
The indictment was returned on August 15, 2019, and unsealed on August 26, 2019. The indictment alleges Levandowski, 39, of Marin County, was a Google engineer and one of the founding members of the group that worked on Google’s self-driving car project. Levandowski worked on the project from 2009 until he resigned from Google without notice on January 27, 2016.
“All of us have the right to change jobs,” said U.S. Attorney Anderson, “none of us has the right to fill our pockets on the way out the door. Theft is not innovation.”
At the time of his resignation, Levandowski was the lead of Google’s Light Detecting and Ranging (LiDAR) engineering team. The indictment alleges that in the months before his departure, Levandowski downloaded from secure Google repositories numerous engineering, manufacturing, and business files related to Google’s custom LiDAR and self-driving car technology. The files downloaded included circuit board schematics, instructions for installing and testing LiDAR, and an internal tracking document. The indictment also alleges that at the time he took the files, Levandowski was involved with two companies competing with Google in the self-driving space: Tyto LiDAR LLC and 280 Systems, Inc., the latter of which would become Ottomotto. Ottomotto acquired Tyto in May 2016, shortly after Uber Technologies, Inc. agreed to acquire Ottomotto and hire Levandowski.
The indictment charges Levandowski with 33 counts of theft and attempted theft of trade secrets, in violation of 18 U.S.C. § 1832. He is scheduled to be arraigned on the charges on August 27, 2019, at 1:30 p.m. before U.S. Magistrate Judge Nathanael M. Cousins.
An indictment merely alleges that crimes have been committed, and all defendants are presumed innocent until proven guilty beyond a reasonable doubt. If convicted, the defendant faces a maximum sentence of 10 years and a fine of $250,000, plus restitution, for each violation of 18 U.S.C. § 1832. However, any sentence following conviction would be imposed by the court after consideration of the U.S. Sentencing Guidelines and the federal statute governing the imposition of a sentence, 18 U.S.C. § 3553.
The prosecution is being handled by the Office of the U.S. Attorney, Northern District of California’s new Corporate Fraud Strike Force and is the result of an investigation by the FBI.
Description: The fiscal year of the data file obtained from the AOUSC
Format: YYYY
Description: The code of the federal judicial circuit where the case was located
Format: A2
Description: The code of the federal judicial district where the case was located
Format: A2
Description: The code of the district office where the case was located
Format: A2
Description: Docket number assigned by the district to the case
Format: A7
Description: A unique number assigned to each defendant in a case which cannot be modified by the court
Format: A3
Description: A unique number assigned to each defendant in a case which can be modified by the court
Format: A3
Description: A sequential number indicating whether a case is an original proceeding or a reopen
Format: N5
Description: Case type associated with the current defendant record
Format: A2
Description: A concatenation of district, office, docket number, case type, defendant number, and reopen sequence number
Format: A18
Description: A concatenation of district, office, docket number, case type, and reopen sequence number
Format: A15
Description: The status of the defendant as assigned by the AOUSC
Format: A2
Description: A code indicating the fugitive status of a defendant
Format: A1
Description: The date upon which a defendant became a fugitive
Format: YYYYMMDD
Description: The date upon which a fugitive defendant was taken into custody
Format: YYYYMMDD
Description: The date when a case was first docketed in the district court
Format: YYYYMMDD
Description: The date upon which proceedings in a case commenced on charges pending in the district court where the defendant appeared, or the date of the defendant’s felony-waiver of indictment
Format: YYYYMMDD
Description: A code used to identify the nature of the proceeding
Format: N2
Description: The date when a defendant first appeared before a judicial officer in the district court where a charge was pending
Format: YYYYMMDD
Description: A code indicating the event by which a defendant appeared before a judicial officer in the district court where a charge was pending
Format: A2
Description: A code indicating the type of legal counsel assigned to a defendant
Format: N2
Description: The title and section of the U.S. Code applicable to the offense committed which carried the highest severity
Format: A20
Description: A code indicating the level of offense associated with FTITLE1
Format: N2
Description: The four digit AO offense code associated with FTITLE1
Format: A4
Description: The four digit D2 offense code associated with FTITLE1
Format: A4
Description: A code indicating the severity associated with FTITLE1
Format: A3
Description: The FIPS code used to indicate the county or parish where an offense was committed
Format: A5
Description: The date of the last action taken on the record
Format: YYYYMMDD
Description: The date upon which judicial proceedings before the court concluded
Format: YYYYMMDD
Description: The date upon which the final sentence is recorded on the docket
Format: YYYYMMDD
Description: The date upon which the case was closed
Format: YYYYMMDD
Description: The total fine imposed at sentencing for all offenses of which the defendant was convicted and a fine was imposed
Format: N8
Description: A count of defendants filed including inter-district transfers
Format: N1
Description: A count of defendants filed excluding inter-district transfers
Format: N1
Description: A count of original proceedings commenced
Format: N1
Description: A count of defendants filed whose proceedings commenced by reopen, remand, appeal, or retrial
Format: N1
Description: A count of defendants terminated including interdistrict transfers
Format: N1
Description: A count of defendants terminated excluding interdistrict transfers
Format: N1
Description: A count of original proceedings terminated
Format: N1
Description: A count of defendants terminated whose proceedings commenced by reopen, remand, appeal, or retrial
Format: N1
Description: A count of defendants pending as of the last day of the period including long term fugitives
Format: N1
Description: A count of defendants pending as of the last day of the period excluding long term fugitives
Format: N1
Description: The source from which the data were loaded into the AOUSC’s NewSTATS database
Format: A10
Description: A sequential number indicating the iteration of the defendant record
Format: N2
Description: The date the record was loaded into the AOUSC’s NewSTATS database
Format: YYYYMMDD
Description: Statistical year ID label on data file obtained from the AOUSC which represents termination year