WELL · 42-409-32683 · DISTRICT 4

Haisley #4

Plugged

San Patricio County · Harvey West (McKamey Sd.) field  · Vertical

Haisley #4 (API 42-409-32683) is a plugged well in San Patricio County, plugged March 26, 2018, last operated by Sandel Operating Company.

The RRC has issued one drilling permit, issued July 30, 2001, permitted to 10,500 ft.

It was permitted by Mission Resources Corporation and has since transferred to Sandel Operating Company on the wellbore schedule.

Completion filings report 4 formation tops, including Lundberg, Dubose, Watson, Anderson.

Operator of record

Sandel Operating Company

Permitted by Mission Resources Corporation; the EWA schedule now lists a different operator.

Huntsville, TX · P-5 Y, filed Jul 4, 2026 · 11 permits on file · (936) 662-8585

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSandel Operating Company
Production reportsSandel Operating Companythrough Jul 2008
Latest permitMission Resources CorporationJul 30, 2001

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

10,500
total depth, ft
1
permits on file
Jul 30, 2001
last permit issued
Nov 9, 2001
completed
0
cumulative oil, bbl
289K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2001 THROUGH Mar 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 9, 2001
Shut in
—
Plugged
Mar 26, 2018

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
Haisley G-4-186657Harvey, West (McKamey Sd.)Sandel Operating Company10289KNov 2001 – Mar 2018

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. 1Mission Resources CorporationNov 2001 → Oct 2002
  2. 2Matador Operating CompanyNov 2002 → Jul 2003
  3. 3Brown, Tom Inc.Aug 2003 → Dec 2004
  4. 4Encana Oil & Gas(usa) Inc.Jan 2005 → Jul 2007
  5. 5Sandel Operating CompanyJun 2008 → Jul 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
511973-99DrillMission Resources CorporationJul 30, 2001Jul 30, 2001Aug 31, 200110,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-186657————

Formation tops

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

FormationMD ftSubsea
Lundberg9,209-9,190
Dubose9,354-9,335
Watson9,413-9,394
Anderson9,618-9,599

Perforations

Perforated and open-hole intervals.

FromToType
9,2589,294Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,02514.75700 S
5.59,8958.75555 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
00Feb 20, 2002Jan 14, 2002Yes
00Feb 4, 2002——

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