WELL · 42-163-33403 · DISTRICT 1

West Patrick #1

Plugged

Frio County · Eagleville (Eagle Ford Sour) field  · Horizontal

West Patrick #1 (API 42-163-33403) is a plugged horizontal well in Frio County, plugged July 23, 2024, last operated by Cabot Oil & Gas Corporation.

The RRC has issued one drilling permit, issued October 23, 2009, permitted to 12,700 ft.

Completion filings report 3 formation tops, including Eagle Ford, Georgetown, Pearsall.

Its 2 leases have reported 84.1K barrels of oil and 47.8K mcf of gas since March 2010, last reporting in August 2024. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Cabot Oil & Gas Corporation

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Apr 1, 2021
Permits on file
1,040
Phone
(817) 589-4600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCabot Oil & Gas Corporation
Production reportsVenado Operating Company LLCthrough May 2021
Latest permitCabot Oil & Gas CorporationOct 23, 2009

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

12,700
total depth, ft
1
permits on file
Oct 23, 2009
last permit issued
Mar 8, 2010
completed
84.1K
cumulative oil, bbl
47.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2010 THROUGH Aug 2024

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 8, 2010
Shut in
—
Plugged
Jul 23, 2024

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Patrick West O-1-15326Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLC158K36.5KJan 2011 – Aug 2024
West, Patrick O-1-15180Eagleville (Eagle Ford Sour)Cabot Oil & Gas Corporation126.1K11.3KMar 2010 – Feb 2012

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. 1Cabot Oil & Gas CorporationMar 2010 → Jan 2018
  2. 2Venado Operating Company LLCFeb 2018 → May 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
686527-99DrillCabot Oil & Gas CorporationOct 23, 2009Oct 23, 2009Nov 7, 200912,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-15180————
—— O-1-15326————

Formation tops

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

FormationMD ftSubsea
Eagle Ford7,680-7,185
Georgetown8,035-7,540
Pearsall10,905-10,410

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,00812.251,454 S
5.510,9608.751,431 S
9.625—12.25250 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
00Dec 21, 2011Apr 7, 2010Yes
00Jul 14, 2010Apr 7, 2010Yes
00Jul 7, 2010——

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