WELL · 42-239-33562 · DISTRICT 2

Combs-Patman Unit #1

N

Jackson County · Mauritz West (6600) field  · Vertical

Combs-Patman Unit #1 (API 42-239-33562) is a well in Jackson County operated by Rincon Petroleum Corporation, completed September 29, 2011.

The RRC has issued 2 drilling permits (amended once) between 2011 and 2012, permitted to 7,010 ft.

Completion filings report 2 formation tops, including Greta, Frio.

Its 2 leases have reported 38.6K barrels of oil and 91.2K mcf of gas since September 2011, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Rincon Petroleum Corporation

Corpus Chrsti, TX · P-5 Y, filed Apr 4, 2026 · 259 permits on file · (361) 960-9033

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRincon Petroleum Corporation
Production reportsRincon Petroleum Corporationthrough Mar 2026
Latest permitRincon Petroleum CorporationJun 21, 2012
7,010
total depth, ft
3
permits on file
Jun 21, 2012
last permit issued
Sep 29, 2011
completed
38.6K
cumulative oil, bbl
91.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 29, 2011
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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Combs-Patman Unit O-2-10805Little Kentucky (Frio 5650)Rincon Petroleum Corporation138.6K38.4KJul 2012 – Jul 2026
Combs-Patman Unit G-2-266681Mauritz, West (6600)Rincon Petroleum Corporation1052.8KSep 2011 – Jul 2014

Oil, barrels lease total

Last 12 months 1,060 · prior 12 1,058(+0%)

0100200202420252026

Chain of custody

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

  1. 1Rincon Petroleum CorporationSep 2011 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
742652-99RecompletionRincon Petroleum CorporationJun 12, 2012Jun 21, 2012Jun 21, 20127,010
714149-98DrillRincon Petroleum CorporationOct 19, 2011May 2, 2011May 12, 20117,010
714149-99DrillRincon Petroleum CorporationApr 13, 2011May 2, 2011May 12, 20117,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-266681————
—— O-2-10805————

Formation tops

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

FormationMD ftSubsea
Greta5,365-5,310
FrioMIDDLE FRIO5,700-5,645

Perforations

Perforated and open-hole intervals.

FromToType
5,6905,692Perforated
6,5426,544Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,36512.25505 S
4.56,9987.875446 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
00Jul 31, 2014Jul 9, 2012—
00Mar 22, 2013Nov 15, 2011Yes

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