WELL · 42-311-36821 · DISTRICT 1

Edwards #6H

Y

McMullen County · Eagleville (Eagle Ford-1) field · Producing  · Horizontal

Edwards #6H (API 42-311-36821) is a horizontal well in Mcmullen County operated by Bpx Operating Company, completed May 24, 2019 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued April 5, 2018, permitted to 14,000 ft.

Completion filings report 10 formation tops, including Yegua, Wilcox, Navarro, Escondido.

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

Operator of record

BPX Operating Company

Denver, CO · P-5 Y, filed May 4, 2026 · 1,575 permits on file · (720) 439-5104

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBPX Operating Company
Production reportsBPX Operating Companythrough Apr 2026
Latest permitBPX Operating CompanyApr 5, 2018
14,000
total depth, ft
2
permits on file
Apr 5, 2018
last permit issued
May 24, 2019
completed
0
cumulative oil, bbl
1.27M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2018 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 24, 2019
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

28.369669, -98.641817

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in McMullen County.

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
Edwards G-1-286553Eagleville (Eagle Ford-1)BPX Operating Company101.27MJul 2018 – Jul 2026

Gas, mcf lease total

Last 12 months 55,753 · prior 12 73,960(-25%)

05K10K15K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1BPX Operating CompanyAug 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
837254-98DrillBPX Operating CompanyNov 15, 2019Apr 5, 2018Jun 11, 201814,000
837254-99DrillBHP Billiton Pet(txla OP) CoMar 7, 2018Apr 5, 2018Jun 11, 201814,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-286553————

Formation tops

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

FormationMD ftSubsea
YeguaYEGUA - DISPOSAL1,411-1,050
WilcoxWILCOX - DISPOSAL4,126-3,765
Navarro8,395-8,034
Escondido8,415-8,054
Olmos9,230-8,869
Anacacho11,164-10,803
Austin Chalk11,707-11,346
Eagle FordEAGLE FORD - H2S11,776-11,415
CatahoulaCATAHOULA - DISPOSAL——
FrioFRIO - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
12,14117,950Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2011026—
9.6255,80312.251,745 S
5.518,0198.751,655 S
518,0196.751,655 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 11, 2019Aug 23, 2019Yes
00Jun 10, 2019May 3, 2019Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Edwards42-311-36822

0.0 KM · BPX Operating Company · Section with this well →

Yegua1,397-1,036
Wilcox4,152-3,791
Navarro8,392-8,031
Escondido8,412-8,051
Olmos9,226-8,865
Anacacho11,135-10,774
Austin Chalk11,678-11,317
Eagle Ford11,748-11,387

10 TOPS · FIRST 8

Edwards42-311-36897

0.1 KM · BPX Operating Company · Section with this well →

Yegua1,019-657
Wilcox3,768-3,406
Navarro8,003-7,641
Escondido8,022-7,660
Olmos8,838-8,476
Anacacho10,752-10,390
Austin Chalk11,270-10,908
Eagle Ford11,332-10,970

10 TOPS · FIRST 8

Edwards42-311-36896

0.1 KM · BHP Billiton Pet(txla OP) Co · Section with this well →

Yegua1,390-1,028
Wilcox4,142-3,780
Navarro8,387-8,025
Escondido8,405-8,043
Olmos9,222-8,860
Anacacho10,748-10,386
Austin Chalk11,274-10,912
Buda—

10 TOPS · FIRST 8

Edwards42-311-34532

0.5 KM · Petrohawk Operating Company · Section with this well →

Olmos6,469-6,116
Anacacho10,968-10,615
Eagle Ford11,670-11,317
Eagle Ford11,670-11,317

Edwards42-311-36380

0.9 KM · BHP Billiton Pet(txla OP) Co · Section with this well →

Yegua452-91
Sparta2,287-1,926
Queen City2,482-2,121
Wilcox4,157-3,796
Escondido8,457-8,096
Navarro8,457-8,096
Olmos9,645-9,284
Anacacho11,203-10,842

13 TOPS · FIRST 8

Edwards42-311-37191

0.9 KM · BPX Operating Company · Section with this well →

Navarro8,031-7,678
Olmos9,282-8,929
Anacacho11,182-10,829
Austin Chalk11,728-11,375
Eagle Ford11,813-11,460
Catahoula—
Yegua—
Wilcox—

10 TOPS · FIRST 8

Edwards42-311-36382

0.9 KM · BHP Billiton Pet(txla OP) Co · Section with this well →

Yegua431-70
Sparta2,266-1,905
Queen City2,461-2,100
Wilcox4,136-3,775
Navarro8,427-8,066
Escondido8,436-8,075
Olmos9,624-9,263
Anacacho11,179-10,818

12 TOPS · FIRST 8

Edwards42-311-37190

0.9 KM · BPX Operating Company · Section with this well →

Navarro8,052-7,700
Olmos9,295-8,943
Anacacho11,193-10,841
Austin Chalk11,746-11,394
Eagle Ford11,830-11,478
Escondido—
Frio—
Catahoula—

10 TOPS · FIRST 8

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