WELL · 42-355-33261 · DISTRICT 4

J.O. Chapman #133C

N

Nueces County  · Vertical

J.O. Chapman #133C (API 42-355-33261) is a permitted well in Nueces County filed by Decker Operating CO., L.L.C.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 2000 and 2012, permitted to 8,100 ft.

Completion filings report 2 formation tops, including Chapman Ranch (L-20-3), Chapman Ranch (A).

Operator of record

Decker Operating Co., L.L.C.

Houston, TX · P-5 Y, filed Jan 4, 2026 · 137 permits on file · (361) 289-1641

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsDecker Operating Co., L.L.C.through May 2015
Latest permitDecker Operating Co., L.L.C.Feb 16, 2012
8,100
total depth, ft
3
permits on file
Feb 16, 2012
last permit issued
—
completed
0
cumulative oil, bbl
684K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2000 THROUGH Mar 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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 3 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Chapman, J. O. G-4-267998Chapman Ranch (Mid. Frio Cons.)Decker Operating Co., L.L.C.1019.6KOct 2011 – Mar 2020
Chapman, J. O. G-4-180218Chapman Ranch (Miocene Cons.)Decker Operating Co., L.L.C.10322KNov 2000 – Oct 2011
Chapman, J. O. G-4-180214Chapman Ranch (A)Shana Petroleum Company10343KNov 2000 – Feb 2002

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. 1Shana Petroleum CompanyNov 2000 → Apr 2002
  2. 2Neg Operating LLCMay 2002 → May 2004
  3. 3Decker Operating Co., L.L.C.Jun 2004 → May 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
733153-99RecompletionDecker Operating Co., L.L.C.Feb 3, 2012Feb 16, 2012Oct 24, 20118,050
523403-99RecompletionNeg Operating LLCSep 5, 2002Sep 5, 2002—7,720
499816-99DrillShana Petroleum CompanySep 19, 2000Sep 20, 2000Oct 8, 20008,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-180214————
—— G-4-180218————
—— G-4-267998————

Formation tops

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

FormationMD ftSubsea
Chapman Ranch (L-20-3)3,030-2,985
Chapman Ranch (A)7,904-7,859

Perforations

Perforated and open-hole intervals.

FromToType
3,0383,042Perforated
7,5507,556Perforated
7,9047,914Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,04012.25425 S
4.58,0367.875930 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
00Jun 3, 2013Feb 22, 2012—
00Jan 28, 2003Sep 6, 2002—
00Mar 1, 2001Dec 7, 2000Yes
00Feb 28, 2001Dec 7, 2000Yes
00Jan 10, 2001—Yes

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