TEXAS · WELLS · ANDREWS COUNTY · CLAMPETT, JED 'D' LEASE · API 42-003-39488 · DISTRICT 7B

Clampett Jed D #12 W

Shut in

Andrews County · Means field · Shut In  · Vertical

Clampett Jed D #12 W (API 42-003-39488) is a well in Andrews County operated by Hilcorp Energy Company, completed October 21, 2005 and listed as shut in on the RRC schedule, shut in September 1, 2023.

The RRC has issued one drilling permit, issued February 11, 2005, permitted to 4,950 ft.

It was permitted by Pogo Producing Company and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 3 formation tops, including Queen, Grayburg, San Andres.

Its lease has reported 140K barrels of oil and 108K mcf of gas since November 2000, last reporting volume in April 2026. The lease carries 9 wells, so these are lease totals, not this well alone.

It holds an active disposal or injection permit.

Operator of record

Hilcorp Energy Company

Permitted by Pogo Producing Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
Mar 27, 2026
Permits on file
3,458
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsOXY USA EOR, LLCthrough Apr 2026
Latest permitPogo Producing CompanyFeb 11, 2005

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

4,950
total depth, ft
1
permits on file
Feb 11, 2005
last permit issued
Oct 21, 2005
completed
140K
cumulative oil, bbl
108K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2000 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 21, 2005
Shut in
Sep 1, 2023
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.

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; they carry 9 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Clampett, Jed 'D' O-10-36525MeansOXY USA EOR, LLC9140K108KNov 2000 – Apr 2026

Oil, barrels lease total

Last 12 months 505 · prior 12 741(-32%)

050100150202420252026

Gas, mcf lease total

Last 12 months 240 · prior 12 754(-68%)

050100150202420252026

Chain of custody

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

  1. 1Triumph Exploration, Inc.Nov 2000 → Oct 2003
  2. 2Pogo Producing CompanyNov 2003 → Jan 2008
  3. 3Pogo Producing Company LLCFeb 2008 → Feb 2008
  4. 4OXY USA Inc.Mar 2008 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
557568-99DrillPogo Producing CompanyFeb 11, 2005Feb 11, 2005Sep 24, 20054,900

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 21, 2005Clampett Jed D O-10-36525MeansHilcorp Energy CompanyShut In · shut in Sep 1, 20234,950

Formation tops

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

FormationMD ftSubsea
Queen4,229-1,044
Grayburg4,257-1,072
San Andres4,596-1,411

Perforations

Perforated and open-hole intervals.

FromToType
4,6304,706Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,84012.25950 S
4.54,9307.8751,235 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
00Jun 30, 2006Dec 2, 2005Yes
00Feb 2, 2006——

Well logs

1 log loaded from the RRC's log index, the latest received Oct 24, 2006. 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
ResistivityDUAL LATEROLOG MICROGUARDSpans Queen, Grayburg, San AndresTIFF3,900 to 4,888Oct 24, 2006run Oct 2, 2005—

"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. The University Lands library has no per-well link: then paste it into its search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
1.17M
bbl, all reported
Mar 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000095204H-1 InjectionActive2502,2254,550–4,800

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120252026

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