WELL · 42-335-33260 · DISTRICT 8

Fuller J. D. #1WS

N

Mitchell County · Sharon Ridge (1700) field  · Vertical

Fuller J. D. #1WS (API 42-335-33260) is a well in Mitchell County operated by Coalinga Corporation, completed November 6, 1986.

The RRC has issued one drilling permit, issued August 12, 1986, permitted to 700 ft.

It was permitted by Keck, W. M., JR., Mrs. and has since transferred to Coalinga Corporation on the wellbore schedule.

Its 2 leases have reported 428K barrels of oil and 41 mcf of gas since January 1993, last reporting in July 2026. The leases carry 40 wells, so these are lease totals, not this well alone.

Operator of record

Coalinga Corporation

Permitted by Keck, W. M., Jr., Mrs.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Feb 2, 1998
Permits on file
68
Phone
(713) 652-0813

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCoalinga Corporation
Production reportsUnitex Oil & Gas, L.L.C.through Apr 2026
Latest permitKeck, W. M., Jr., Mrs.Aug 12, 1986

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

700
total depth, ft
1
permits on file
Aug 12, 1986
last permit issued
Nov 6, 1986
completed
428K
cumulative oil, bbl
41
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 6, 1986
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 40 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Fee Unit O-11-66703Sharon Ridge (1700)Unitex Oil & Gas, L.L.C.40428K41Jan 1993 – Jul 2026
— O-11-5789——000—

Oil, barrels lease total

Last 12 months 5,411 · prior 12 5,904(-8%)

0200400600202420252026

Chain of custody

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

  1. 1Coalinga CorporationJan 1993 → Aug 1998
  2. 2Merit Energy CompanySep 1998 → Aug 2000
  3. 3Journey Operating, L.L.C.Sep 2000 → Feb 2006
  4. 4Kinder Morgan Production Co LPMar 2006 → Jun 2006
  5. 5Legacy Reserves Operating LPJul 2006 → Dec 2015
  6. 6Unitex Oil & Gas, L.L.C.Jan 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
305148-99DrillKeck, W. M., Jr., Mrs.Aug 5, 1986Aug 12, 1986—700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-5789————
—— O-11-66703————

Perforations

Perforated and open-hole intervals.

FromToType
280360Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
16152013 S
8.62528012.25185 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
00Aug 7, 1987Jul 15, 1987—
00Aug 1, 1987——

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