throbber
Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 1 of 14
`
`UNITED STATES DISTRICT COURT
`DISTRICT OF KANSAS
`
`
`
`
`
`
`Case No. 6:17-cv-01217
`
`
`
`
`
`
`
`
`LOGANTREE LP,
`
` Plaintiff,
`vs.
`
`GARMIN INTERNATIONAL, INC.,
`GARMIN USA, INC., and GARMIN, LTD,
`
`
`
`
`
`
`Defendants.
`
`GARMIN’S MEMORANDUM OF LAW IN SUPPORT OF ITS
`MOTION TO DISMISS PURSUANT TO FED. R. CIV. P. 12(B)(6)
`
`The current lawsuit is LoganTree’s third attempt to set forth a complaint that identifies a
`
`plausible claim of patent infringement against Garmin International, Inc. and Garmin, USA, Inc.
`
`(“Garmin”).1 Unfortunately, it fares no better and continues a troubling pattern of LoganTree
`
`failing to set forth any good faith basis for its allegations. LoganTree previously filed suit against
`
`Garmin in the Western District of Texas. In that complaint, LoganTree failed to provide any
`
`allegations as to how Garmin’s products allegedly infringed the below key limitation of the
`
`patent—as required by Federal Circuit precedent:
`
`•  
`
` “storing . . . the first time stamp information reflecting a time at which the movement
`
`data causing the first user-defined event occurred.”
`
`After a telephone conference between the parties, LoganTree admitted it could not
`
`provide the required details on how Garmin’s products infringed this limitation of the ‘576
`
`patent. Garmin was then forced to file a Motion to Dismiss LoganTree’s initial complaint
`
`                                                                                                                
`1 As used in this motion, “Garmin” refers to Garmin International, Inc. and Garmin USA, Inc.
`Named defendant Garmin, Ltd. has not been served and is not voluntarily appearing in this
`lawsuit through this motion.
`
`  
`
`1
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 2 of 14
`
`detailing how LoganTree’s complaint ignored this critical limitation. After LoganTree was
`
`unable to provide those critical details in its responsive brief, Garmin noted in its Reply brief that
`
`LoganTree’s position raised serious concerns that it had failed to conduct an adequate pre-suit
`
`investigation, as required by Rule 11. While the Western District of Texas never had a chance to
`
`rule on that Motion,2 LoganTree implicitly acknowledged the merit of Garmin’s position when it
`
`refiled its Complaint in the present action (“Complaint”) by attempting to cover up its prior
`
`shortcomings.
`
`Unfortunately, while LoganTree’s complaint is long on words and charts, it still fails to
`
`explain how Garmin’s products allegedly infringe this key limitation. The inclusion of claim
`
`charts is a new development, presumably done to give the appearance that LoganTree did, in
`
`fact, have a viable infringement theory. But LoganTree’s claim chart is still silent on how
`
`Garmin’s products are “storing” as required by the asserted patent claims. The charts simply do
`
`not provide any details whatsoever on where or how Garmin’s products store a time stamp
`
`reflecting a time at which the movement data causing the first user-defined event occurred.
`
`LoganTree’s third bite at the apple raises significant questions as to its good faith basis to
`
`bring this suit. In two separate briefs to the court, Garmin identified this very same key limitation
`
`from the asserted patent claims and LoganTree still cannot identify how Garmin’s accused
`
`products infringe (or meet) that key “storing” limitation. Garmin should not be forced to
`
`repeatedly expend its time and resources defending infringement claims that LoganTree knows,
`
`or should know, lack any plausible basis for infringement. Accordingly, Garmin respectfully
`
`requests this Court dismiss LoganTree’s Complaint with prejudice.
`
`                                                                                                                
`2 The Case was dismissed for improper venue and then, after a significant delay, was refiled in
`Kansas.    
`
`  
`
`2
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 3 of 14
`
`I.   LEGAL STANDARDS
`
`
`
`A complaint should be dismissed pursuant to Rule 12(b)(6) when it fails to plead “enough
`
`facts to state a claim to relief that is plausible on its face.” Bell Atl. Corp. v. Twombly, 550 U.S.
`
`544, 570 (2007). A “mere possibility” is not enough. Ashcroft v. Iqbal, 556 U.S. 662, 679
`
`(2009). A complaint demonstrates plausibility when “the plaintiff pleads factual content that
`
`allows the court to draw the reasonable inference that the defendant is liable for the misconduct
`
`alleged.” Iqbal, 556 U.S. at 678.
`
`
`
`Prior to December of 2015, to sufficiently plead direct infringement, a Plaintiff needed
`
`only comply with the minimal requirements of Form 18, which set forth a sample direct
`
`infringement pleading. These requirements included:
`
`(1) an allegation of jurisdiction; (2) a statement that the plaintiff owns the patent;
`(3) a statement that defendant has been infringing the patent “by making, selling,
`and using [the device] embodying the patent”; (4) a statement that the plaintiff has
`given the defendant notice of its infringement; and (5) a demand for an injunction
`and damages.
`
` Lyda v. CBS Corp., 838 F.3d 1331, 1338 (Fed. Cir. 2016). However, Form 18 was abrogated in
`
`December of 2015, and since then courts have consistently held that a Plaintiff pleading direct
`
`infringement has the burden of meeting the standards set forth by the Supreme Court in Iqbal and
`
`Twombly. See, e.g., Gracenote, Inc. v. Sorenson Media, Inc., No. 2:16-cv-950 CW, 2017 WL
`
`2116173 at *2 (D. Utah May 15, 2017) (noting that the case law following the abrogation of
`
`Form 18 strongly suggested that the Iqbal and Twombly standard applied to the pleading of direct
`
`infringement).
`
`Under Iqbal/Twombly, establishing a plausible basis for infringement requires Plaintiff to
`
`show how the Accused Products infringe each limitation of at least one claim of the asserted
`
`patent. See e.g., Atlas IP, LLC v. Exelon Corp., 189 F.Supp.3d 768, 775 (N.D. Ill. May 17, 2016)
`
`  
`
`3
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 4 of 14
`
`(requiring factual allegations that allow a court to infer that the accused product meets each
`
`limitation of at least one claim to meet the standards set forth under Iqbal and Twombly). The
`
`“limitations” are the distinct parts or steps that describe the patented invention, and which are
`
`recited within the patent’s claims. See, e.g., Duz-Mor, Inc. v. Hein-Werner Corp., No. 87-1643-
`
`MLB, 1994 WL 715628, *4 (D. Kan. Dec. 2, 1994). Accordingly, to comply with the pleading
`
`standard established by the Supreme Court in Iqbal/Twombly, the Plaintiff must show that the
`
`Accused Products contain each and every one of the distinct parts or steps set forth in at least one
`
`of the asserted claims. If even a single limitation is missing, the Plaintiff has failed to comply
`
`with its burden. Id.
`
`
`
`PROCEDURAL BACKGROUND
`
`A.
`
`The Reexamined ‘576 Patent
`
`The ‘576 patent, which is entitled “Training and Safety Device, System and Method To
`
`Aid In Proper Movement During Physical Activity,” originally issued on May 9, 2000 with 29
`
`claims. Dkt. 1 Ex. A. Each of those claims required a “portable, self-contained’ device capable
`
`of measuring data associated with “unrestrained movement in any direction.” See id.,
`
`independent claims 1 and 13.
`
`Fourteen years later, on April 4, 2014, LoganTree filed a reexamination request with the
`
`United States Patent and Trademark Office. Dkt. 1 Ex. B. None of the 29 originally-issued
`
`claims survived the reexamination. Id. Instead, through the reexamination process, LoganTree
`
`was forced to add narrowing limitations to argue around the prior art. In particular, LoganTree
`
`added the following two limitations to all of the claims:
`
`•   “detecting a first user-defined event based on the movement data and at least one of the
`
`user-defined operational parameters regarding the movement data,” and
`
`  
`
`4
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 5 of 14
`
`•   “storing . . . the first time stamp information reflecting a time at which the movement
`
`data causing the first user-defined event occurred.”
`
`Dkt. 1 ¶ 25 (reciting above-referenced limitations in “Claim 1 (the ‘Device Claim’)”, ¶ 28
`
`(reciting above-referenced limitations in “Claim 13 (the ‘System Claim’), and ¶ 30 (reciting
`
`above-referenced limitations in “Claim 20 (the ‘Method Claim’);” see also Dkt. 1 Ex. B
`
`(emphasis added). All 185 claims of the Reexamined ‘576 patent include these limitations. Dkt.
`
`1 Ex. B.
`
`Explicit in the claim language is the requirement that the “user-defined event” must be
`
`caused by movement data (such as the angle and velocity of the user’s movement, see Dkt. 1 Ex.
`
`B, Reexamined ‘576 patent claim 1) and at least one of the other user-defined operational
`
`parameters (such as, for example, the “angular levels at which notices will be generated,” ‘576
`
`patent at 7:11-14). Then, a “time stamp” is stored that reflects the time when the user-defined
`
`event occurs.
`
`As is evident from the prosecution history, LoganTree added these limitations as
`
`“clarifying amendments” to “tie the claimed first time stamp information such that it reflects a
`
`time at which the movement data causing the first user-defined event occurred.” Ex. A
`
`(Response to Ex Parte Reexamination Final Office Action, Jan. 9, 2015, p. 48).3 The following
`
`example provided by LoganTree during the reexamination is instructive:
`
`                                                                                                                
`3 In deciding a Rule 12(b)(6) motion, a court may take judicial notice of the prosecution
`histories, which are “public records.” Won-Door Corp. v. Cornell Iron Works, Inc., No. 2:13-
`CV-331 TS, 2014 WL 119320 at *2 (D. Utah Jan. 13, 2014) (noting that in the Tenth Circuit,
`district courts are allowed “to take judicial notice of patent documents such as the patent’s
`prosecution history.”); Fin. Acquisition Partners LP v. Blackwell, 440 F.3d 278, 286 (5th Cir.
`2006) (“[i]n ruling on Rule 12(b)(6) motions,” courts are permitted “to rely on matters of public
`record”); Genetic Techs. Ltd. v. Bristol-Myers Squibb Co., 72 F. Supp. 3d 521, 526 (D. Del.
`2014) (noting that patent prosecution histories are “public records”).
`
`  
`
`5
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 6 of 14
`
`For instance, upon detection of the event, such as when a user’s measured
`movement passes a given angle (or some other type of movement threshold), time
`stamp information is recorded. This recorded time stamp information reflects a
`time at which the user’s movements (e.g., passing the given angle) caused the
`event to occur . . . .
`
`Id. (emphasis added). Importantly, LoganTree repeatedly disclaimed a user manually pushing a
`
`button to indicate movement, making clear that the claims of the Reexamined ‘576 patent
`
`required that “the microprocessor” must detect the user-defined event (i.e., the movement data
`
`and operational parameters) and store time-stamp information reflecting the time at which the
`
`movement data causing the event occurred:
`
`For example, in the Office Action, it is asserted that the alleged event in Flentov
`occurs when the user (skier) pushes a button 58 instructing the system to stop
`recording movement data . . . PO respectfully submits that even if Flentov is
`interpreted this way, it still does not teach the claimed detection operation because
`the Examiner is overlooking the fact that the claims require the microprocessor
`to detect a first user-defined event based on the movement data and at least one
`of the user-defined operational parameters.
`
`That is, the event is detected by the microprocessor based on the movement data,
`not the user. . . .
`
`Id. at 50-51 (emphasis in original); see also id. at 56 (disclaiming Vock prior art “teachings of a
`
`user pressing the start/stop button 58 to signal the end of a run (e.g., down a hill) as
`
`corresponding to the claimed event detection,” emphasizing that “the claimed microprocessor”
`
`must detect the event “based on the movement data” and store the time stamp).
`
`B.
`
`LoganTree’s Initial Complaint Against Garmin in the Western District of Texas
`
`LoganTree filed its initial complaint against Garmin on February 10, 2017, in the
`
`Western District of Texas. LoganTree LP v. Garmin Int’l, Inc. et al., No. 5:17-cv-00098, Dkt. 1
`
`(W.D. Tex. Feb. 10, 2017). The initial complaint generally alleged direct infringement of the
`
`“Reexamined ‘576 Patent,” referencing each of the three independent claims – which it
`
`characterizes as “Device” (claim 1), “System” (claim 13), and “Method” (claim 20) – and the
`
`  
`
`6
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 7 of 14
`
`182 “other claims dependent” on them. Id. ¶¶ 24, 27, 28, 29. The initial complaint broadly
`
`defined the “Accused Products” as “wearable accelerometer-based activity tracker[s],” and
`
`included a laundry list of product lines. Id. ¶ 24.
`
`For each of the independent claims, the initial complaint contained a paragraph stating
`
`that, “[o]n information and belief, the Accused Products infringe” the claim and its dependents.
`
`Dkt. 1 ¶¶ 27 (“Device” claim), 28 (“System” claim), 29 (“Method” claim). However, the initial
`
`complaint provided no additional information, and no attempted claim mapping, for any of the
`
`182 dependent claims. Id. Further, for the “user-defined event” and “time stamp” limitations,
`
`which were added during the reexamination proceeding and were the focus of LoganTree’s
`
`arguments over the prior art, the initial complaint was noticeably silent. Id. Garmin identified
`
`these missing allegations in its motion to dismiss but LoganTree was unable to provide any
`
`further details. The Western District of Texas never reached the merits of Garmin’s original
`
`motion to dismiss on 12(b)(6) grounds, instead dismissing the case for improper venue under
`
`12(b)(3) in light of the Supreme Court’s decision in TC Heartland. LoganTree, No. 5:17-cv-
`
`00098, Dkt. 26 (W.D. Tex. June 22, 2017).
`
`
`
`
`
`C.
`
`LoganTree’s Complaint in the Present Action
`
`
`
`LoganTree refiled its lawsuit against Garmin in the District of Kansas on August 23,
`
`2017. The infringement allegations in LoganTree’s Complaint are largely identical to those in the
`
`initial complaint filed in the Western District of Texas, with one notable difference. In an
`
`implicit acknowledgment that its initial Complaint was deficient, LoganTree included a new
`
`exhibit, Exhibit C, which is a claim chart LoganTree alleges maps features from three of
`
`  
`
`7
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 8 of 14
`
`Garmin’s Products (out of the over 80 products within the 14 Accused Product families) to the
`
`claim limitations of independent claim 1. Dkt. 1, ¶ 35; Ex. C. The claim chart provides
`
`screenshots from various Garmin sources, along with highlighting to show the extent of
`
`LoganTree’s allegations on how Garmin’s products meet the “storing” limitation:
`
`
`
`
`
`8
`
`Dkt. 1, Ex. C at 8; 11.
`
`  
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 9 of 14
`
`As this chart shows, LoganTree has done nothing more than merely circle words in an
`
`instruction manual suggesting a user can review activity information through Garmin Connect.
`
`There is absolutely no identification of where or how Garmin Connect would “stor[e] . . . the
`
`first time stamp information reflecting a time at which the movement data causing the first
`
`user-defined event occurred.”
`
`II.   ARGUMENT
`
`A.  
`
`LoganTree’s Complaint Fails to Plead a Plausible Claim for Direct
`Infringement
`
`LoganTree’s Complaint fails to plead “enough facts to state a claim to relief that is
`
`plausible on its face.” Twombly, 550 U.S. at 570. To state a plausible claim for direct
`
`infringement, LoganTree must, at a minimum, show how it contends the Accused Products
`
`infringe each limitation of at least one claim of the Reexamined ‘576 Patent. See Atlas IP, 189
`
`F.Supp.3d at 775.
`
`
`
`Through the reexamination process that led to the issuance of the 185 claims of the
`
`Reexamined ‘576 Patent, LoganTree amended the claims to include additional limitations in an
`
`effort to argue around the prior art. For example, LoganTree specifically argued that the claims
`
`of the Reexamined ‘576 Patent do not cover a manual button press by a user of a movement
`
`monitoring device to “detect” a “user-defined event” or to “store” a time stamp. Ex. A
`
`(Response to Ex Parte Reexamination Final Office Action, Jan. 9, 2015, p. 48-56). Instead, the
`
`microprocessor in the device must detect the “user-defined event,” which is caused by movement
`
`data and at least one of the user-defined operational parameters regarding the movement data,
`
`and then must store a time stamp reflecting the time when the movement data caused the user-
`
`defined event. Id.
`
`  
`
`9
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 10 of 14
`
`
`
`As was the case with LoganTree’s Texas complaint, LoganTree’s Kansas Complaint is
`
`completely silent on these key limitations. LoganTree ignores the limitations entirely when
`
`alleging infringement of independent claims 1 and 13, and merely regurgitates the claim
`
`language when alleging infringement of independent claim 20. In fact, there is not a single
`
`factual allegation within the complaint itself that plausibly suggests that the Accused Products
`
`infringe a single claim of the Reexamined ‘576 Patent. This is woefully short of the pleading
`
`required to satisfy the Iqbal/Twombly standard.
`
`
`
`While LoganTree’s newly added claim chart goes further than the Complaint by at least
`
`purporting to map the claim limitations to features of the Accused Products, it too falls short as
`
`to exactly those key claim limitations LoganTree knows are deficient in its Complaint. As an
`
`initial matter, LoganTree only provides a claim chart as to three of Garmin’s Products, and yet
`
`the Product families accused by LoganTree for infringement contain over 80 products.
`
`LoganTree has no explanation as to how it could plausibly plead infringement as to all 80 widely
`
`different products based solely on its claim chart of 3 products.
`
`
`
`More problematic, even to those products LoganTree has mapped, LoganTree’s claim
`
`chart makes no attempt to show where in those products, or even if, time stamp information
`
`reflecting a time at which the movement data causing the first user-defined event occurred is
`
`stored on the Accused Products. For example, LoganTree identifies Garmin’s Virtual Pacer
`
`feature in the Forerunner device as one such “user-defined event.” Dkt. 1, Ex. C at 8:
`
`  
`
`10
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 11 of 14
`
`
`
`LoganTree also identified a user exceeding or dropping below the target pace as a “user-defined
`
`operational parameter.” Id. Therefore, to establish plausible infringement of the time-stamp
`
`limitation, LoganTree must identify some feature in Garmin’s Accused Products—in this
`
`example, the Forerunner device—showing that time stamp information is stored reflecting the
`
`time when a user drops or exceeds a target pace. LoganTree has failed to make any such
`
`allegations. Instead, all LoganTree has shown is that Garmin’s “Garmin Connect” program
`
`allows a user to review detailed time data. Id. at 11. Garmin and the Court are simply left to
`
`guess as to whether this time data would include any indication of a time stamp that was stored
`
`when the user exceeded or fell below the user-defined pace. The law requires more—LoganTree
`
`must plausibly identify where and how each limitation is met and, because it has failed to do so,
`
`its Complaint should be dismissed.
`
`
`
`Requiring LoganTree to identify the allegedly infringing product functionality is
`
`especially important here, where the complaint broadly accuses more than 80 products within the
`
`14 different product families, many with different features, functionalities, and settings.
`
`LoganTree’s blanket assertion that all 80 of these products infringe all 185 claims of the
`
`  
`
`11
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 12 of 14
`
`Reexamined ‘576 Patent—without any factual suggestion to indicate that any products meet a
`
`minimal threshold of infringing even one claim—fails to give Garmin even “scant notice of what
`
`is truly alleged to be at issue in the case.” Joao Control & Monitoring Sys., LLC v. Protect
`
`America, Inc., No. 1-14-CV-134-LY, 2015 WL 3513151 at *4 (W.D. Tex. Mar. 24, 2015) (“A
`
`pleading that alleges ‘one or more’ of the over 900 claims in the patents-in-suit are infringed
`
`gives [Defendant] and this court scant notice of what is truly alleged to be at issue in this case.”).
`
`Moreover, it raises a serious question as to the adequacy of Plaintiff’s pre-suit investigation
`
`required under Rule 11, especially in light of the fact that many of the products have been
`
`discontinued by Garmin. See Atlas IP, 189 F.Supp.3d at 775 (“[G]iven the investigation that
`
`Rule 11(b) requires before filing a complaint, it is difficult to imagine how an action for
`
`infringement could be brought without a tentative but nonetheless coherent theory of which
`
`claims are allegedly infringed and how the accused products practice—or, because Rule 11(b)(3)
`
`permits pleading on information and belief, may practice—each of those claims’ elements.”).
`
`III.   CONCLUSION
`
`
`
`For all of the reasons stated herein, Garmin respectfully requests that the Court dismiss
`
`this case in its entirety, with prejudice.
`
`Dated: October 24, 2017
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Adam P. Seitz
`Adam P. Seitz, KS Bar #21059
`Megan J. Redmond, KS Bar #21999
`Clifford T. Brazil, KS Bar #27408
`ERISE IP, P.A.
`6201 College Blvd., Suite 300
`Overland Park, Kansas 66211
`Telephone: (913) 777-5600
`Facsimile: (913) 777-5601
`adam.seitz@eriseip.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`  
`
`12
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 13 of 14
`
`
`
`
`
`
`
`
`
`
`
`
`
`megan.redmond@eriseip.com
`cliff.brazil@eriseip.com
`
`ATTORNEYS FOR DEFENDANTS
`GARMIN INTERNATIONAL, INC. AND
`GARMIN USA, INC.
`
`
`
`
`
`
`
`
`
`
`
`
`
`  
`
`13
`
`

`

`Case 6:17-cv-01217-EFM-ADM Document 11 Filed 10/24/17 Page 14 of 14
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that, on October 24, 2017, the foregoing document filed with the Clerk of
`the Court using CM/ECF and that all counsel of record who are deemed to have consented to
`electronic service are being served with a copy of this document via the Court’s CM/ECF system
`accordingly.
`
`
`
`  
`
`
`By: /s/ Adam P. Seitz
`Adam P. Seitz
`
`
`
`14
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket