TEXAS · WELLS · GOLIAD COUNTY · HARKINS LEASE · API 42-175-32941 · DISTRICT 02

Harkins #2

Plugged

Goliad County · Sarco Creek (4870) field  · Vertical

Harkins #2 (API 42-175-32941) is a plugged well in Goliad County, plugged March 22, 2006, last operated by Hamman Oil & Refining Company.

The RRC has issued one drilling permit (amended once), issued September 13, 1996, permitted to 5,400 ft.

Completion filings report 3 formation tops, including Catahoula, Frio, Vicksburg.

Its lease has reported 4.43K barrels of oil and 20.1K mcf of gas since February 1997, with no volume in the three years through April 2026.

Operator of record

Hamman Oil & Refining Company

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Jun 1, 2026
Permits on file
359
Phone
(713) 526-7417

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHamman Oil & Refining Company
Production reportsHamman Oil & Refining Companythrough Jun 2002
Latest permitHamman Oil & Refg. Co.Sep 13, 1996
5,400
total depth, ft
2
permits on file
Sep 13, 1996
last permit issued
Feb 19, 1997
completed
4.43K
cumulative oil, bbl
20.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1997 THROUGH Jun 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 19, 1997
Shut in
—
Plugged
Mar 22, 2006

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Harkins O-2-8292Sarco Creek (4870)Hamman Oil & Refining Company14.43K20.1KFeb 1997 – Jun 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. 1Hamman Oil & Refining CompanyFeb 1997 → Feb 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
452477-98DrillHamman Oil & Refg. Co.May 23, 1997Sep 13, 1996—5,400
452477-99DrillHamman Oil & Refg. Co.Sep 10, 1996Sep 13, 1996Jan 28, 19975,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 19, 1997Harkins O-2-8292Sarco Creek (4870)Hamman Oil & Refining CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Catahoula3,010-2,900
Frio3,540-3,430
Vicksburg5,050-4,940

Perforations

Perforated and open-hole intervals.

FromToType
4,8084,814Perforated
4,8364,841Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62555512.25224 S
4.55,0547.875794 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
00May 10, 2001Mar 12, 2001—
00Nov 5, 1997Mar 10, 1997Yes
00Oct 9, 1997——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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