WELL · 42-355-33789 · DISTRICT 4

Chapman Ranch J. O. D #175

N

Nueces County · Chapman Ranch (6260) field  · Vertical

Chapman Ranch J. O. D #175 (API 42-355-33789) is a well in Nueces County operated by Decker Operating CO. L.L.C., completed June 22, 2006.

The RRC has issued one drilling permit, issued April 25, 2006, permitted to 7,500 ft.

Completion filings report 4 formation tops, including L-20, Masv. Catahoula, Frio, Top Johns.

Its 3 leases have reported 116K barrels of oil and 21.4K mcf of gas since July 2006, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

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 scheduleDecker Operating Co. L.L.C.
Production reportsDecker Operating Co., L.L.C.through Mar 2026
Latest permitDecker Operating Co., L.L.C.Apr 25, 2006
7,500
total depth, ft
1
permits on file
Apr 25, 2006
last permit issued
Jun 22, 2006
completed
116K
cumulative oil, bbl
21.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 22, 2006
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 JO D O-4-13547Chapman Ranch (Upper Frio Cons.)Decker Operating Co., L.L.C.1101K18.9KNov 2006 – Jul 2026
Chapman, J.O. "D" O-4-13396Chapman Ranch (5600)Decker Operating Co., L.L.C.100Nov 2006 – Jul 2009
Chapman Ranch, J. O. "D" O-4-13389Chapman Ranch (6260)Decker Operating Co., L.L.C.114.8K2.51KJul 2006 – Dec 2006

Oil, barrels lease total

Last 12 months 1,749 · prior 12 2,690(-35%)

0200400202420252026

Chain of custody

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

  1. 1Decker Operating Co., L.L.C.Jul 2006 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
616758-99DrillDecker Operating Co., L.L.C.Mar 30, 2006Apr 25, 2006Apr 29, 20067,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-13389————
—— O-4-13396————
—— O-4-13547————

Formation tops

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

FormationMD ftSubsea
L-203,063-3,026
Masv. Catahoula4,700-4,663
FrioTOP FRIO5,562-5,525
Top Johns6,260-6,223

Perforations

Perforated and open-hole intervals.

FromToType
6,2606,264Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,10312.25342 S
5.56,9617.875365 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 17, 2009——
00Mar 8, 2007Aug 7, 2006Yes
00Dec 12, 2006——
00Nov 16, 2006——

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