WELL · 42-295-33405 · DISTRICT 10

Liepe #2831H

N

Lipscomb County · Lipscomb S. W. (Cleveland) field  · Horizontal

Liepe #2831H (API 42-295-33405) is a horizontal well in Lipscomb County operated by Chesapeake Operating Inc., completed February 14, 2009.

The RRC has issued one drilling permit, issued September 10, 2008, permitted to 12,000 ft.

Completion filings report 4 formation tops, including Lansing, Kansas City, Checkerboard, Cleveland.

Its 2 leases have reported 112K barrels of oil and 1.03M mcf of gas since February 2009, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Chesapeake Operating Inc.

Based in
Oklahoma City, OK
P-5 status
Delinquent (D)
P-5 last filed
Dec 10, 2024
Permits on file
13,061
Phone
(405) 935-3100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating Inc.
Production reports4P Energy Texas, LLCthrough Apr 2018
Latest permitChesapeake Operating, Inc.Sep 10, 2008

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

12,000
total depth, ft
1
permits on file
Sep 10, 2008
last permit issued
Feb 14, 2009
completed
112K
cumulative oil, bbl
1.03M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 14, 2009
Shut in
—
Plugged
—

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Liepe G-14-265734Lipscomb (Cleveland)Unbridled Resources, LLC10224KJan 2012 – Jul 2026
Liepe O-14-7970Lipscomb, S. W. (Cleveland)Chesapeake Operating, Inc.2112K811KFeb 2009 – Feb 2013

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Chesapeake Operating, Inc.Feb 2009 → Oct 2014
  2. 2Chesapeake Operating, L.L.C.Nov 2014 → Aug 2015
  3. 34P Energy Texas, LLCJun 2017 → Apr 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
669598-99DrillChesapeake Operating, Inc.Aug 21, 2008Sep 10, 2008Nov 1, 200812,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-265734————
—— O-14-7970————

Formation tops

As filed on W-2/G-1. Subsea from 2,628 ft elevation.Download CSV →

FormationMD ftSubsea
Lansing7,736-5,108
Kansas City7,945-5,317
Kansas City7,971-5,343
Checkerboard8,081-5,453
Checkerboard8,114-5,486
Cleveland8,229-5,601
Cleveland8,322-5,694

Perforations

Perforated and open-hole intervals.

FromToType
8,34012,162Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,81512.25950 S
5.512,2328.51,215 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 7, 2013Feb 9, 2012Yes
00Jun 29, 2009Mar 25, 2009Yes
00Jun 8, 2009——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/29533405, documented in the API reference.