WELL · 42-215-31183 · DISTRICT 4

Coates BB #3P

N

Hidalgo County · Jeffress E. (Vicksburg T) field  · Vertical

Coates BB #3P (API 42-215-31183) is a well in Hidalgo County operated by El Paso E & P Company L. P., completed November 7, 1981.

The RRC has issued 2 drilling permits between 1981 and 2006, permitted to 14,500 ft.

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

Operator of record

EL Paso E & P Company L. P.

Houston, TX · P-5 Y, filed Feb 6, 2015 · 582 permits on file · (713) 420-2600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEL Paso E & P Company L. P.
Production reportsEL Paso E & P Company, L. P.through Dec 2006
Latest permitEL Paso E & P Company, L. P.Aug 14, 2006
14,500
total depth, ft
2
permits on file
Aug 14, 2006
last permit issued
Nov 7, 1981
completed
0
cumulative oil, bbl
1.12M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 7, 1981
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 4 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Coates "B" G-4-222982Jeffress, E. (Vicksburg L)Merit Energy Company100Nov 2006 – Jul 2026
Coates "BB" G-4-96185Jeffress, E. (Vicksburg T)EL Paso E & P Company, L. P.101.12MJan 1993 – Jan 2008
Coates "B" G-4-222977Jeffress, E. (Vicksburg O\p)EL Paso E & P Company, L. P.100Nov 2006 – Dec 2006
Coates "B" G-4-222980Jeffress, E. (Vicksburg S)EL Paso E & P Company, L. P.100Nov 2006 – Dec 2006

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. 1Coastal Oil & Gas CorporationJan 1993 → Jun 2001
  2. 2EL Paso Production Oil & Gas Co.Jul 2001 → Jul 2006
  3. 3EL Paso E & P Company, L. P.Sep 2006 → Dec 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
624272-99RecompletionEL Paso E & P Company, L. P.Aug 14, 2006Aug 14, 2006Aug 16, 200612,780
134564-99DrillBorder Exploration Co.Sep 28, 1981Sep 28, 1981—14,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-96185————
—— G-4-222977————
—— G-4-222980————
—— G-4-222982————

Perforations

Perforated and open-hole intervals.

FromToType
9,0679,163Perforated
9,6119,650Perforated
9,6119,686Perforated
9,6609,686Perforated
10,42410,486Perforated
12,04113,352Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,50017.51,100 S
9.6257,92012.25840 S
2.87511,950——
5.513,5966.75300 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
00May 16, 2007Mar 15, 2007—
00Apr 3, 2007Nov 30, 2006Yes
00Dec 8, 2006Nov 30, 2006—
00Dec 8, 2006——
00Jan 12, 1984Nov 18, 1981—

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