WELL · 42-175-33842 · DISTRICT 2

Breeden P. H. Gas Unit #1 #1

Plugged

Goliad County · Cottonwood Creek E. (Middle Wx.) field  · Vertical

Breeden P. H. Gas Unit #1 #1 (API 42-175-33842) is a plugged well in Goliad County, plugged April 27, 2009, last operated by Texcal Energy (GP) LLC.

The RRC has issued one drilling permit, issued October 12, 2005, permitted to 12,000 ft.

It was permitted by Pogo Producing Company and has since transferred to Texcal Energy (GP) LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Yegua, Cook Mountain, Reklaw, Wilcox.

Operator of record

Texcal Energy (GP) LLC

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

Denver, CO · P-5 Y, filed Jul 3, 2010 · 26 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTexcal Energy (GP) LLC
Production reportsTexcal Energy (GP) LLCthrough Mar 2009
Latest permitPogo Producing CompanyOct 12, 2005

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

12,000
total depth, ft
1
permits on file
Oct 12, 2005
last permit issued
Aug 3, 2006
completed
0
cumulative oil, bbl
100K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2006 THROUGH Apr 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 3, 2006
Shut in
—
Plugged
Apr 27, 2009

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
Breeden, P. H. Gas Unit #1 G-2-220852Cottonwood Creek,e. (Middle Wx.)Texcal Energy (GP) LLC10100KFeb 2006 – Apr 2009

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. 1Pogo Producing CompanyAug 2006 → Mar 2007
  2. 2Texcal Energy (GP) LLCApr 2007 → Mar 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
607749-99DrillPogo Producing CompanyOct 12, 2005Oct 12, 2005Dec 9, 200512,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-220852————

Formation tops

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

FormationMD ftSubsea
Yegua4,990-4,814
Cook Mountain5,390-5,214
Reklaw7,950-7,774
Wilcox8,300-8,124

Perforations

Perforated and open-hole intervals.

FromToType
10,15810,166Perforated
10,24710,254Perforated
10,30410,308Perforated
10,66410,680Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,50714.751,205 S
7.6259,7899.875470 S
511,2866.75230 S
4.511,2866.75230 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
00Mar 7, 2007Aug 21, 2006—
00Mar 1, 2007May 24, 2006Yes
00Nov 7, 2006——

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