WELL · 42-241-30503 · DISTRICT 3

Arco Fee Diamond #6

Plugged

Jasper County · Buna West (Wilcox) field  · Vertical

Arco Fee Diamond #6 (API 42-241-30503) is a plugged well in Jasper County, plugged September 18, 2006, last operated by Kerr-Mcgee Oil & Gas Onshore LP.

The RRC has issued one drilling permit, issued November 19, 1990, permitted to 12,000 ft.

It was permitted by Rio Bravo Oil Company and has since transferred to Kerr-Mcgee Oil & Gas Onshore LP on the wellbore schedule.

Completion filings report one formation top, including Wilcox.

Operator of record

Kerr-McGee Oil & Gas Onshore LP

Permitted by Rio Bravo Oil Company; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Oct 4, 2025 · 234 permits on file · (713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleKerr-McGee Oil & Gas Onshore LP
Production reportsWestport Oil and Gas Company, LPthrough Jun 2004
Latest permitRio Bravo Oil CompanyNov 19, 1990

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
Nov 19, 1990
last permit issued
Sep 21, 1999
completed
0
cumulative oil, bbl
284K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2006

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 21, 1999
Shut in
—
Plugged
Sep 18, 2006

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
Arco Fee Diamond G-3-136831Buna, West (Wilcox)Kerr-McGee Oil & Gas Onshore LP10284KJan 1993 – Sep 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. 1Rio Bravo Oil CompanyJan 1993 → Sep 1993
  2. 2Kriti Exploration, Inc.Oct 1993 → Aug 1996
  3. 3Smith Production Inc.Sep 1996 → Sep 2002
  4. 4Westport Oil and Gas Company, LPOct 2002 → Jun 2004

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
381171-99DrillRio Bravo Oil CompanyNov 16, 1990Nov 19, 1990Nov 22, 199012,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-136831————

Formation tops

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

FormationMD ftSubsea
WilcoxTOP WILCOX10,833-10,779

Perforations

Perforated and open-hole intervals.

FromToType
10,98311,014Perforated
10,99510,997Perforated
11,00311,014Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1685——
10.752,80514.751,915 S
7.62510,6209.875408 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
00Oct 20, 1999Oct 5, 1999—
00Feb 26, 1991Feb 1, 1991Yes
00Feb 11, 1991——

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