WELL · 42-413-32215 · DISTRICT 7

Jones B #8

N

Schleicher County · Eldorado (Canyon) field  · Vertical

Jones B #8 (API 42-413-32215) is a well in Schleicher County operated by Pogo Producing Company, completed September 9, 2004.

The RRC has issued one drilling permit, issued July 12, 2004, permitted to 6,900 ft.

Completion filings report 3 formation tops, including Wolfcamp, Canyon, Black Shale.

No lease production has been reported under this well’s leases.

Operator of record

Pogo Producing Company

Based in
Houston, TX
P-5 status
Delinquent (D)
P-5 last filed
Jul 31, 2007
Permits on file
479
Phone
(713) 297-5000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePogo Producing Company
Production reportsOXY USA Inc.through Jul 2017
Latest permitPogo Producing Co.Jul 12, 2004

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

6,900
total depth, ft
1
permits on file
Jul 12, 2004
last permit issued
Sep 9, 2004
completed
0
cumulative oil, bbl
75K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 9, 2004
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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Jones "B" G-9-207771Eldorado (Canyon)Hilcorp Energy Company1074.3KSep 2004 – Jul 2026
Jones "B" O-9-15581Eldorado (Canyon)Pogo Producing Company10774Sep 2004 – Jun 2005

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 CompanySep 2004 → Jan 2008
  2. 2Pogo Producing Company LLCFeb 2008 → Feb 2008
  3. 3OXY USA Inc.Mar 2008 → Jul 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
548043-99DrillPogo Producing Co.Jul 9, 2004Jul 12, 2004Aug 14, 20046,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-207771————
—— O-9-15581————

Formation tops

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

FormationMD ftSubsea
WolfcampLOWER WOLFCAMP4,694-2,266
CanyonCANYON SAND6,280-3,852
CanyonCANYON SD6,280-3,852
Black Shale6,532-4,104

Perforations

Perforated and open-hole intervals.

FromToType
6,2576,261Perforated
6,2576,468Perforated
6,4366,444Perforated
6,4636,468Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62563111230 S
4.56,6127.875651 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
00Jul 15, 2005Mar 3, 2005—
00Jul 14, 2005Jan 10, 2005—
00Apr 27, 2005——
00Nov 8, 2004Sep 20, 2004Yes
00Oct 7, 2004——

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) and the University Lands library. 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/41332215, documented in the API reference.