WELL · 42-433-32445 · DISTRICT 7

Pittcock "A" #7701

N

Stonewall County  · Vertical

Pittcock "A" #7701 (API 42-433-32445) is a permitted well in Stonewall County filed by Anathema, Inc.; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1988 and 1989, permitted to 2,999 ft.

Completion filings report one formation top, including Geneview (Tannehill).

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

Operator of record

Anathema, Inc.

Abilene, TX · P-5 Y, filed Jul 7, 1995 · 72 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsBig al Oil and Gasthrough Apr 2026
Latest permitAnathema, Inc.Jul 12, 1989
2,999
total depth, ft
2
permits on file
Jul 12, 1989
last permit issued
—
completed
190K
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
—
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 17 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State of Texas Tannehill Unit O-8-27908Geneview (Tannehill)Big al Oil and Gas15178K0Jul 1996 – Jul 2026
Pittcock "A" O-8-25190Geneview (Tannehill)Coalinga Corporation212.8K41Jan 1993 – Oct 1996

Oil, barrels lease total

Last 12 months 498 · prior 12 1,095(-55%)

0100200300202420252026

Chain of custody

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

  1. 1Anathema, Inc.Jan 1993 → Dec 1994
  2. 2Lomax Operating Company, Inc.Feb 1995 → Feb 1995
  3. 3Coalinga CorporationMar 1995 → Aug 1998
  4. 4Merit Energy CompanySep 1998 → Aug 2000
  5. 5Journey Operating, L.L.C.Sep 2000 → Dec 2003
  6. 6Alexander Resources, Inc.Jan 2004 → Jan 2012
  7. 7Waco Petro, LPFeb 2012 → Nov 2012
  8. 8Big al Oil and GasDec 2012 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
361349-99RecompletionAnathema, Inc.Jul 10, 1989Jul 12, 1989—2,999
352893-99DrillAnathema, Inc.Nov 1, 1988Nov 3, 1988—2,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-25190————
—— O-8-27908————

Formation tops

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

FormationMD ftSubsea
Geneview (Tannehill)2,778-1,202

Perforations

Perforated and open-hole intervals.

FromToType
2,7782,780Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62510812.2575 S
5.52,8387.875125 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 23, 1996Dec 16, 1988Yes
00Feb 1, 1989Dec 16, 1988Yes
00Dec 23, 1988——

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