WELL · 42-373-30637 · DISTRICT 3

Arco Fee D #1

Plugged

Polk County · Segno N.E. (Wilcox A) field  · Vertical

Arco Fee D #1 (API 42-373-30637) is a plugged well in Polk County, plugged July 31, 2015, last operated by Rotation Incorporated.

The RRC has issued one drilling permit, issued January 3, 1986, permitted to 9,000 ft.

It was permitted by Sanchez-O'Brien Oil & Gas Corp. and has since transferred to Rotation Incorporated on the wellbore schedule.

Completion filings report 2 formation tops, including Cockfield, Wilcox.

Its lease has reported 53.8K barrels of oil and 46.8K mcf of gas since January 1993, last reporting in February 2016.

Operator of record

Rotation Incorporated

Permitted by Sanchez-O'Brien Oil & Gas Corp.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Oct 7, 2016 · 2 permits on file · (713) 248-8290

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRotation Incorporated
Production reportsRotation, Incorporatedthrough Apr 2015
Latest permitSanchez-O'Brien Oil & Gas Corp.Jan 3, 1986

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

9,000
total depth, ft
1
permits on file
Jan 3, 1986
last permit issued
Feb 9, 1986
completed
53.8K
cumulative oil, bbl
46.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2016

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 9, 1986
Shut in
—
Plugged
Jul 31, 2015

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 "D" O-3-19069Segno, N.E. (Wilcox A)Rotation, Incorporated153.8K46.8KJan 1993 – Feb 2016

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. 1Southwest Oil & Land, Inc.Jan 1993 → May 1994
  2. 2Petroglyph Operating Company IncJun 1994 → Feb 1997
  3. 3Brito Oil Co., IncMar 1997 → May 2002
  4. 4Rotation, IncorporatedJun 2002 → Apr 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
294321-99DrillSanchez-O'Brien Oil & Gas Corp.Jan 3, 1986Jan 3, 1986—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-19069————

Formation tops

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

FormationMD ftSubsea
Cockfield4,900-4,741
Wilcox7,800-7,641

Perforations

Perforated and open-hole intervals.

FromToType
7,8347,841Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,86712.25900 S
5.58,0167.625506 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 10, 1986Feb 11, 1986Yes
00Mar 6, 1986——

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