TEXAS · WELLS · PANOLA COUNTY · CARTHAGE GAS UNIT 110 LEASE · API 42-365-37335 · DISTRICT 06

Carthage Gas Unit 110 #16

On schedule

Panola County · Carthage (Cotton Valley) field · Producing  · Directional

Carthage Gas Unit 110 #16 (API 42-365-37335) is a well in Panola County operated by Diversified Production LLC, completed May 6, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 9, 2008, permitted to 9,675 ft.

It was permitted by Devon Energy Production CO, L.P. and has since transferred to Diversified Production LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Pettit, Travis Peak, Cotton Valley.

Its lease has reported 8.05K barrels of oil and 1.21M mcf of gas since May 2009, last reporting volume in April 2026.

Operator of record

Diversified Production LLC

Permitted by Devon Energy Production Co, L.P.; the EWA schedule now lists a different operator.

Based in
Keithville, LA
P-5 status
Active – Extension (X)
P-5 last filed
Mar 25, 2026
Permits on file
11
Phone
(318) 751-3917

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiversified Production LLC
Production reportsDiversified Production LLCthrough Apr 2026
Latest permitDevon Energy Production Co, L.P.Dec 9, 2008

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

9,675
total depth, ft
1
permits on file
Dec 9, 2008
last permit issued
May 6, 2009
completed
8.05K
cumulative oil, bbl
1.21M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · MAY 2009 THROUGH APR 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 6, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Carthage Gas Unit 110 G-6-249089Carthage (Cotton Valley)Diversified Production LLC18.05K1.21MMay 2009 – Apr 2026

Gas, mcf lease total

Last 12 months 27,641 · prior 12 24,580(+12%)

01K2K3K202420252026

Wells named Carthage Gas Unit 110

Diversified Production LLC's other wells filed under this lease name in Panola County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Devon Energy Production Co, L.P.May 2009 → Jun 2016
  2. 2Sheridan Production Company, LLCJul 2016 → Dec 2019
  3. 3Sheridan Production Co III, LLCJan 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
675900-99DrillDevon Energy Production Co, L.P.Dec 5, 2008Dec 9, 2008Feb 26, 200912,500

Completions

CompletedLeaseFieldOperatorStatusDepth
May 6, 2009Carthage Gas Unit 110 G-6-249089Carthage (Cotton Valley)Diversified Production LLCProducing9,675

Formation tops

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

FormationMD ftSubsea
Pettit5,911-5,574
Travis Peak6,293-5,956
Cotton Valley8,235-7,898

Perforations

Perforated and open-hole intervals.

FromToType
8,6249,526Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
11.7565014.75345 S
8.6255,66210.6251,515 S
5.59,7527.875970 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Aug 14, 2009Jun 26, 2009Yes
00Jul 10, 2009——

Well logs

1 log loaded from the RRC's log index, the latest received Mar 28, 2012. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Pettit, Travis Peak, Cotton ValleyTIFF100 to 9,765Mar 28, 2012run Mar 18, 20090.31

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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/36537335, documented in the API reference.